24小时热门版块排行榜    

查看: 1370  |  回复: 15
当前主题已经存档。
当前只显示满足指定条件的回帖,点击这里查看本话题的所有回帖

moller

木虫 (著名写手)

[交流] 虫友看下,被reject了,是不是还有希望申诉或resubmit?

主编好像是拒掉建议不要重投

三个审稿人的态度
第一个婉拒
第二个比较直接拒
第三个还好点

We have received the reports from our advisors on your manuscript, "*****".

With regret, I must inform you that, based on the advice received, the Editor-in-Chief has decided that your manuscript cannot be accepted for publication in *******.

Attached, please find the reviewer comments for your perusal.

I would like to thank you very much for forwarding your manuscript to us for consideration and wish you every success in finding an alternative place of publication.

Best regards,


    *********


Comments for the Author:


Reviewer #1: The paper does not have much novelty, with many of the ideas presented in this work having been said many times in different forms. The elimination of synchronization data points in a way to achieve high accuracy with minimal amount of stored data resembles to the concepts used in tiny-sync and mini-sync protocols, which are cited but with no details in the related work section. This section is of no value to the paper in its current form. The authors should position the proposed work in the current state of the art in this section, and set the grounds for the rest of the paper by highlighting the short-comings of previous work if any and motivate the current proposal. The related work section as it is now is too limited and has no explicit connection to the proposed ideas. This should also be taken into account if the authors wish to extend ideas and resubmit the paper.

The concepts proposed in the paper merely consist in two components: (i) a single-hop synchronization scheme that is a slight variation of two-way message exchange and the reference broadcast sync primitives, (ii) a multi-hop extension of the single-hop synchronization that has no novelty and uses a level-based propagation of the snyc data. Moreover, the selection of the reference node is not investigated in the paper. The single-hop case where a node uses carrier sensing to set itself as the reference node does not apply directly to the multi-hop case. The simulation scenario is limited and the results presented in the paper are not comprehensive.

The paper is poorly written in many sections. For a resubmission the authors should also carefully go through the whole paper and revise the text. One specific comment is to reduce the number of new paragraphs - currently there are many single-sentence paragraphs, which is unnecessary.



Reviewer #2: This reviewer thought that the contribution of the manuscript was marginal, advantages of the proposed time synchronization technique were questionable. Consequently, I suggest to reject the manuscript.


Reviewer #3: This paper aims at presenting a new approach for synchronizing nodes in a wireless network through the use of lightweight computations and small amount of message overhead.
The goal is interesting since this is a major issue in wireless sensor networks in which many applications and algorithms would perform better when nodes are totally synchronized but where synchronization is considered as an expensive tool in terms of message overhead, computation, latency and energy consumption.
Nevertheless, the contribution of this paper is not clearly identified. The authors introduce a model called LFS.
LFS seems very close to existing schemes and this would be useful to clearly identify in what LFS differs from the literature schemes.
Then, LFS is evaluated through simulations. My concern here would be that it would deserve to be compared to more other schemes, once again to help the reader to distinct LFS from other schemes. Indeed, LFS is only compared to BTS-M which is not well explained enough.
At last, results show that LFS performs better than BTS only for some features but perform less for other ones. It would be interesting to explain more deeply why we observe this behavior and why LFS is still competitive.

[ Last edited by moller on 2009-12-15 at 22:26 ]
回复此楼
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

moller

木虫 (著名写手)

恩~~感谢各位的回复
不知道我理解的各个审稿人的意思有没有偏差??

另外,给我写信的是期刊分配给我的area editor,他在审稿过程中起什么作用?
他会不会是三个审稿人之一????

Editor-in-Chief好像是另外一个人,她决定reject

不管怎么样,我决定最好回复一下,出于礼貌
另外把审稿人的意见都解释下,说明自己会努力修改的~~

[ Last edited by moller on 2009-12-17 at 15:54 ]
13楼2009-12-17 15:51:33
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖
查看全部 16 个回答

moller

木虫 (著名写手)

引用回帖:
Originally posted by study163 at 2009-12-15 21:10:
被拒了,改投吧

呵呵~~
想请有经验的人看看主编和3个审稿人的语气,有没有申诉的机会?
另外Reject & Resubmit有没有戏
感觉再找新的审稿人可能不如直接给原来的审稿人更方便
3楼2009-12-15 21:17:07
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

tools888

铁杆木虫 (职业作家)

我觉得你可以放弃了。
4楼2009-12-15 21:40:00
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖

wlalbert

金虫 (正式写手)


小木虫(金币+0.5):给个红包,谢谢回帖交流
没戏了,拒绝的非常彻底。
5楼2009-12-15 21:41:14
已阅   回复此楼   关注TA 给TA发消息 送TA红花 TA的回帖
普通表情 高级回复 (可上传附件)
最具人气热帖推荐 [查看全部] 作者 回/看 最后发表
[基金申请] FileCode能看出啥? +8 要乐观耀哥 2026-08-10 23/1150 2026-08-13 00:35 by 要乐观耀哥
[基金申请] 应该是93bebmhtak前后十一个字符比较关键 +22 Lanmanbaby 2026-08-09 36/1800 2026-08-12 22:50 by sdfapple719
[基金申请] 2019年青年基金涵评意见,大家看看几个A,几个B? +10 Tide man 2026-08-11 10/500 2026-08-12 20:59 by 陈晨晨陈啊
[基金申请] 不应该看fileCode +5 且听虎啸 2026-08-12 6/300 2026-08-12 16:26 by Tide man
[基金申请] 好奇怪的filecode +5 布布和一二 2026-08-08 6/300 2026-08-12 16:11 by 云上清扬
[基金申请] filecode +13 documentary 2026-08-10 15/750 2026-08-12 15:56 by 云上清扬
[基金申请] 奇怪,两个人的filecode固定段从头到尾一模一样 +7 布布和一二 2026-08-10 10/500 2026-08-12 09:12 by 布布和一二
[基金申请] 综述论文作为代表作会不会影响评审专家的印象分? +11 yufeiwaner 2026-08-09 13/650 2026-08-12 08:17 by yufeiwaner
[基金申请] 小木虫上这么多卖论文的,真有人买论文么?感觉没必要啊 +8 Tide man 2026-08-10 9/450 2026-08-11 20:39 by beefly
[基金申请] 帮忙看看fileCode +7 wwncly 2026-08-10 13/650 2026-08-11 19:36 by 冰心玉壶晴
[基金申请] 什么时候出结果,有咨询渠道??? +3 Tide man 2026-08-11 3/150 2026-08-11 17:54 by kudofaye
[基金申请] 我的国基提前知道中了,可是同事的操作让我实在接受不了,怎么会有这样的人 +8 家与远方 2026-08-10 13/650 2026-08-11 09:49 by 家与远方
[基金申请] 确定了,国自然21号放榜 +6 布布和一二 2026-08-10 7/350 2026-08-10 19:15 by 2000zf36392
[基金申请] 据悉今年马上要出结果了 +7 瞬息宇宙 2026-08-10 8/400 2026-08-10 12:42 by Vivilian
[基金申请] 面上项目filecode邪修 +5 西山十月 2026-08-09 7/350 2026-08-10 07:32 by 仁砚薪传
[基金申请] filecode与中标关系的预测 +5 布布和一二 2026-08-07 5/250 2026-08-09 16:15 by 袁向阳007
[基金申请] filecode变化情况 +6 布布和一二 2026-08-07 22/1100 2026-08-07 14:45 by 且听虎啸
[基金申请] 大家散了吧,后缀研究没有意义,别浪费时间了,过好目前的每一天,不要焦虑 +5 Tide man 2026-08-06 7/350 2026-08-07 13:11 by 医学老男孩
[基金申请] filecode +14 等待解的谜 2026-08-06 19/950 2026-08-07 12:20 by wlwhappy
[基金申请] filecode +8 布布和一二 2026-08-06 11/550 2026-08-06 20:41 by tangpu318
信息提示
请填处理意见