复活reject论文,与大家交流一点经验

作者分享了一次论文投稿经历,面对负面评论和拒稿,通过详细修改论文并积极与编辑沟通,最终论文被接收。文章强调了学术诚信、沟通技巧与坚持不懈的重要性。

摘要生成于 C知道 ,由 DeepSeek-R1 满血版支持, 前往体验 >

前些时候看到有些虫友论文被拒,灰心。但个人认为,被拒的论文不一定与你的论文水平相 关,有很多因素都决定了最终的决定,例如审稿人的水平、审稿人的个人人品、杂志的办刊宗旨与你论文思想不一致、论文中某些没有照顾到的地方,但总之,只要 论文具有一点创新性,都是有价值发表的,被拒了不要灰心,如果自己认为自己的工作有价值,主要是审稿人在这方面的知识不足造成的,强烈建议详细修改补充论 文后和编辑争辩,毕竟科学的东西只支持正义和真理。
7月份,我写的一篇论文被涂层领域一著名期刊拒了,虽然是第二作者(学生的工作),也不是 通讯作者,但看了审稿人意见后非常生气,写了一个很长的信给编辑对审稿人的个人水平及人品进行了指责,后来编辑看后表示对我的理解,并回复让我们重投论文 (因为上次投的已经形成决议了),他会在一个月内给出最终结果,后来经过我和学生详细讨论,把论文内容进行大幅度改善(主要是讨论部分)重投出去,两个星 期后论文被直接接收。从这件事件,让我对论文投稿又有了一些新的认识,希望大家鼓足勇气,多发paper,挣钱娶媳妇买车。下面把编辑来信(两次)和我的 回信贴出来,和大家交流,欢迎提供宝贵意见。

第一次编辑的拒稿信

Dear ***,

Reviewers' comments on your work have now been received.  You will see that they are advising against publication of your work.  Therefore I must reject it.

For your guidance, I append the reviewers' comments below.

Thank you for giving us the opportunity to consider your work.

Yours sincerely,

***
Editor
***

Reviewers' comments:


Reviewer #1:
Generally, the work is unique but it is not acceptable due to incomplete explanation and routine writing for only publication.   

In Fig. 1. (b), at the magnification x500, the original scale bar was 50 microns in the photo. But authors made a new scale bar which is 20 microns. This is kind of fraud!!!!
English Grammar and style are not satisfied.
My conclusion is that any manuscript from the authors should not be published in this journal.

我的回复:
Dear Editor***

Thank you for your kind attention to consider our work in***. I am terribly sorry for such a terrible conclusion made by the reviewer because of our minor fault about the scale bar in Fig. 1. So, I should give a rebuttal against the comments of the reviewer. I have not been persuaded and I consider the comments are unreasonable and unfair for our work.
I don’t know why the reviewer gave such nasty comments and made a so terrible conclusion about our future work. I doubt whether he has read our manuscript carefully and completely or not.
In Fig.1(b), it is a minor mistake about the scale bar made by authors. I debt that it is very easy to remove the original one in the picture by means of some advanced photo editor softwares if we want. Does the reviewer think we are attempting to cheat the readers using such an obvious mistake which everybody can find, and leaving the original one to make him think it is a “fraud” easily? Why should we do that? If the reviewer read our manuscript carefully and completely, he would not give the unreasonable assessment that “This is a kind of fraud”. In our manuscript, we have never talked about the influence of the size of *** although we consider the *** do influence the ***(与尺寸相异的其它方面) of our ***. It is absolutely unnecessary for us to make this “fraud”. Please kindly judge why we made the “fraud” to make readers unhappy, and us in trouble. Why did the reviewer consider this minor mistake as an unpardonable “fraud” without thinking more about it carefully?
The reviewer said that “the work is unique”. How did he give this comment without any reasons? Since it is unique, why did he reject our work only using the simple reasons of “incomplete explanation” and “routine writing”? We try out best to explain our results. It may be incomplete because of our limitations of corresponding knowledge. But we are eager to improve and perfect it with the help from the reviewers and editors. We are not English native speakers and do realize that our English in this manuscript is not perfect. But, technique paper is different from essay. We consider that it is enough for English grammar or style in technique paper if it can make readers understand our idea and work. Of course, we also can ask help from some English writing companies to improve our English expressions. Thus, we think it is unfair that the reviewer rejected our work only using these unimpressive excuses. It is imprudent to give his conclusion “any manuscript from the authors should not be published in this journal” according to his unfair and irresponsible judgment that Fig.1(b) is “a kind of fraud”.
As an eligible reviewer of the famous journal, he should assess the manuscript from any authors righteously and carefully. He should give reasonable and convictive evidences for his comments. The reviewer should show his understanding to the work that he is reviewing.
In short, we could not accept the comments given by the reviewer #1, and hope that he can withdraw his unjustified conclusions for our present and future work. We are pleased if the editor can justify our rebuttals.
Thank you for your patience and kind attention.
May you have a nice day!

Best Regards
Yours Sincerely
****

编辑的回信
Dear***
     I understand your explanation that you made a simple mistake in Fig. 1b.  If you wish to submit your revised paper, I will send it to another reviewer.  In this case, however, your paper is considered to be new submission because once decision of rejection is reported using the Elsevier on-line system, the paper is removed from the web system.  If you submit the revised version of your paper, I will handle it immediately in order to make a final decision hopefully in a month.  I am very sorry again for reporting you the previous decision.
     I am looking forward to receiving your revised paper.
     With kindest regards;
***

今天收到的论文接收信(投稿两周)
Dear ***,

I am pleased to confirm that your paper "The ***" has been accepted for publication in ***.

Comments from the Editor and Reviewers can be found below.

Thank you for submitting your work to this journal.

With kind regards,

***
Editor
***

Comments from the Editors and Reviewers:

The present paper reports ***.  The authors have shown that ***. The paper contains interesting results and discussion worth for publication in ***.  Therefore, I recommend the publication of the present paper as is.

<think>好的,我现在需要解决用户关于Vue3中Promise的resolve和reject用法的问题。用户之前已经询问过登录弹窗的实现,现在转向Promise的基础概念,特别是resolve和reject的使用方法。我需要结合用户提供的引用内容,尤其是引用1到5中的代码示例,来构建一个清晰的解释。 首先,用户引用的内容中有几个关键点:1.引用1展示了Promise.all的使用,其中包含两个setTimeout的Promise,最终在then中处理结果。2.引用2和引用5提到了在Vue中使用Promise处理异步请求,特别是axios结合的例子。 3.引用3和引用4展示了在Vuex的actions中使用Promise,并演示了reject的用法。用户的问题集中在resolve和reject在Vue3中的具体应用,可能需要了解如何在异步操作中正确使用这两个函数,以及如何处理成功和失败的情况。我需要先解释Promise的基本结构,然后结合Vue3的示例,比如在组件中发起登录请求,使用resolve和reject处理结果。接下来,我需要考虑如何组织回答的结构。通常,先介绍基本概念,再分点说明resolve和reject的作用,然后给出具体的代码示例,比如在Vue组件中发起API请求,在Vuex的actions中处理异步逻辑,以及使用Promise.all处理多个异步任务。同时,用户可能想知道如何在Vue3的setup语法中使用这些方法,所以需要确保示例代码符合Vue3的语法规范。还要注意用户提到的引用内容,例如引用5中的axios拦截器,这可能涉及到全局处理请求和响应,可以适当提及但不需要深入,除非用户的问题涉及。重点还是放在resolve和reject的使用上。需要验证用户提供的代码示例是否正确,比如在引用3中,Vuex的actions返回一个Promise,并在其中使用reject,这应该是正确的做法。同时,在Vue组件中,如何处理Promise的then和catch,以及如何更新组件状态。可能还需要解释为什么在Vue3中推荐使用async/await而不是传统的then链式调用,但用户的问题主要是关于resolve和reject,所以应保持焦点。最后,生成的相关问题需要Promise相关,比如错误处理、状态管理、组合多个Promise等,确保问题符合用户可能进一步探索的方向。</think>### Vue3中Promise的resolvereject用法详解 #### 1. Promise基础结构 Promise是处理异步操作的标准方案,包含三种状态:`pending`(等待)、`fulfilled`(完成)、`rejected`(拒绝)。其核心用法如下: ```javascript const promise = new Promise((resolve, reject) => { // 异步操作 if (/* 成功条件 */) { resolve(value) // 触发.then() } else { reject(error) // 触发.catch() } }) ``` #### 2. resolve用法 `resolve()`用于标记异步操作成功完成,并传递结果值: ```javascript // 在Vue组件中使用 import { ref } from 'vue' const fetchData = () => { return new Promise((resolve) => { setTimeout(() => { resolve({ data: '成功数据' }) }, 1000) }) } // 调用示例 const data = ref(null) fetchData().then(res => { data.value = res.data }) ``` #### 3. reject用法 `reject()`用于标记操作失败,传递错误信息: ```javascript // 结合axios请求示例[^2][^5] const login = () => { return new Promise((resolve, reject) => { axios.post('/api/login', credentials) .then(res => resolve(res.data)) .catch(err => reject(err.response.data)) }) } // 调用时处理错误 login() .then(() => console.log('登录成功')) .catch(error => console.error('错误代码:', error.code)) ``` #### 4. 在Vue3中的典型应用场景 **场景1:组合多个异步请求** ```javascript // 使用Promise.all[^1] const loadAllData = () => { return Promise.all([ fetchUserData(), fetchProductData() ]) } // 组件中调用 loadAllData() .then(([userData, productData]) => { // 更新Vue响应式数据 }) .catch(error => { console.error('加载失败:', error) }) ``` **场景2:Vuex状态管理** ```javascript // store.js中的actions[^3] actions: { fetchData(context) { return new Promise((resolve, reject) => { axios.get('/api/data') .then(res => { context.commit('SET_DATA', res.data) resolve() }) .catch(err => reject(new Error('数据加载失败'))) }) } } // 组件中调用 store.dispatch('fetchData') .then(() => console.log('操作成功')) .catch(error => alert(error.message)) ``` #### 5. 结合async/await语法 推荐使用更清晰的异步处理方式: ```javascript // 在Vue3 setup中 const handleSubmit = async () => { try { const result = await login() console.log('登录结果:', result) } catch (error) { console.error('错误详情:', error) } } ``` ### 核心区别说明 | 方法 | 触发条件 | 流程控制 | 典型应用场景 | |---------|-------------------|----------------|---------------------------| | resolve | 操作成功时调用 | 进入.then()链 | 数据获取成功、表单提交成功| | reject | 操作失败/异常时调用| 进入.catch()链 | 网络错误、验证失败 | ### 最佳实践建议 1. **错误传递**:在reject时始终传递Error对象,保留完整的错误堆栈[^3] 2. **状态管理**:在Vuex actions中返回Promise,便于组件跟踪异步状态[^3] 3. **拦截处理**:使用axios拦截器统一处理错误[^5] 4. **组合请求**:复杂场景使用Promise.all处理并行请求[^1]
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值