<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: The Long and Winding Road: The Story of Complex Exponential Smoothing	</title>
	<atom:link href="https://openforecast.org/2022/08/02/the-long-and-winding-road-the-story-of-complex-exponential-smoothing/feed/" rel="self" type="application/rss+xml" />
	<link>https://openforecast.org/2022/08/02/the-long-and-winding-road-the-story-of-complex-exponential-smoothing/</link>
	<description>How to look into the future</description>
	<lastBuildDate>Tue, 19 Sep 2023 10:26:14 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Ivan Svetunkov		</title>
		<link>https://openforecast.org/2022/08/02/the-long-and-winding-road-the-story-of-complex-exponential-smoothing/#comment-188</link>

		<dc:creator><![CDATA[Ivan Svetunkov]]></dc:creator>
		<pubDate>Tue, 02 Aug 2022 20:46:43 +0000</pubDate>
		<guid isPermaLink="false">https://openforecast.org/?p=2902#comment-188</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://openforecast.org/2022/08/02/the-long-and-winding-road-the-story-of-complex-exponential-smoothing/#comment-187&quot;&gt;Stephan Kolassa&lt;/a&gt;.

Thanks for your comment, Stephan! And I actually agree with you. Maybe my point wasn&#039;t very clear (I feel disturbance in the force :D). Let me clarify. I&#039;ve faced many cases, when a reviewer who was supposed to be an expert in the area (because they accepted to review the paper) did not know much about forecasting and did not even make an effort to understand the paper and judged it hastily, providing comments like &quot;you do not cite papers on forecasting with high frequency data, so I recommend rejection&quot; (this is one of the comments I received for CES). So, this is just a sloppy revision, and my point in the post is that the reviewers need to understand that revision is a serious job. Yes, a reviewer should look critically at the paper and they should help making it more understandable if it is not well written. But the revision is a process done by two sides, not just one. So, if the paper gets to the fourth round without progress, this means that the reviewer and the authors are speaking different languages, and both sides should make an effort to understand each other (preferably, much earlier than on the fourth round). However, there are reviewers that do not want to make that effort and prefer just to get rid of the paper, so that they do not need to do the job, but at the same time can claim that they review papers in this and that journal.
And yes, there are good reviewers as well, I had several during this journey. They were responsible and helpful. And yes, the authors should write papers which are easy to understand. The points above mainly apply to those reviewers who think that doing a sloppy job is fine.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a href="https://openforecast.org/2022/08/02/the-long-and-winding-road-the-story-of-complex-exponential-smoothing/#comment-187">Stephan Kolassa</a>.</p>
<p>Thanks for your comment, Stephan! And I actually agree with you. Maybe my point wasn&#8217;t very clear (I feel disturbance in the force :D). Let me clarify. I&#8217;ve faced many cases, when a reviewer who was supposed to be an expert in the area (because they accepted to review the paper) did not know much about forecasting and did not even make an effort to understand the paper and judged it hastily, providing comments like &#8220;you do not cite papers on forecasting with high frequency data, so I recommend rejection&#8221; (this is one of the comments I received for CES). So, this is just a sloppy revision, and my point in the post is that the reviewers need to understand that revision is a serious job. Yes, a reviewer should look critically at the paper and they should help making it more understandable if it is not well written. But the revision is a process done by two sides, not just one. So, if the paper gets to the fourth round without progress, this means that the reviewer and the authors are speaking different languages, and both sides should make an effort to understand each other (preferably, much earlier than on the fourth round). However, there are reviewers that do not want to make that effort and prefer just to get rid of the paper, so that they do not need to do the job, but at the same time can claim that they review papers in this and that journal.<br />
And yes, there are good reviewers as well, I had several during this journey. They were responsible and helpful. And yes, the authors should write papers which are easy to understand. The points above mainly apply to those reviewers who think that doing a sloppy job is fine.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Stephan Kolassa		</title>
		<link>https://openforecast.org/2022/08/02/the-long-and-winding-road-the-story-of-complex-exponential-smoothing/#comment-187</link>

		<dc:creator><![CDATA[Stephan Kolassa]]></dc:creator>
		<pubDate>Tue, 02 Aug 2022 18:33:21 +0000</pubDate>
		<guid isPermaLink="false">https://openforecast.org/?p=2902#comment-187</guid>

					<description><![CDATA[Thank you for sharing your story, and I agree with two out of your three lessons.

I disagree with one point: if I as a reviewer do not understand a paper, it is usually not my responsibility to invest a lot of time. After all, I am supposedly an expert in the field. (If it turns out that I am assigned a paper in which I am not an expert, then I should notify the editor and withdraw.) Thus, I am precisely the target audience of the papers I review. And therefore, the *author* needs to invest every reasonable effort to make their paper understandable - after all, if the reviewer, an expert, does not understand it, how will later readers understand it?

And yes, there is frequently a tension between &quot;I do not understand X, but the paper is good, so please explain X better&quot; and &quot;I do not understand X, and the paper is generally weak, so I recommend rejection&quot;. I have heard it said that the job of the reviewer is to weed out bad papers and make good papers better. One can err in either direction. But nobody is happy if I get a paper I believe is a publishable-if-better-explained one, and we then have three review rounds before the editor and I are convinced that the author is *not* capable of explaining their idea better, and then the paper is rejected after three rounds.]]></description>
			<content:encoded><![CDATA[<p>Thank you for sharing your story, and I agree with two out of your three lessons.</p>
<p>I disagree with one point: if I as a reviewer do not understand a paper, it is usually not my responsibility to invest a lot of time. After all, I am supposedly an expert in the field. (If it turns out that I am assigned a paper in which I am not an expert, then I should notify the editor and withdraw.) Thus, I am precisely the target audience of the papers I review. And therefore, the *author* needs to invest every reasonable effort to make their paper understandable &#8211; after all, if the reviewer, an expert, does not understand it, how will later readers understand it?</p>
<p>And yes, there is frequently a tension between &#8220;I do not understand X, but the paper is good, so please explain X better&#8221; and &#8220;I do not understand X, and the paper is generally weak, so I recommend rejection&#8221;. I have heard it said that the job of the reviewer is to weed out bad papers and make good papers better. One can err in either direction. But nobody is happy if I get a paper I believe is a publishable-if-better-explained one, and we then have three review rounds before the editor and I are convinced that the author is *not* capable of explaining their idea better, and then the paper is rejected after three rounds.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
