It is encouraging that you took the initiative to write this journal manuscript, but it needs a lot of work as I am afraid that in its current form it is likely to be rejected. Besides the style that needs fixing, my main concern is the claim that the CFD gives more credibility the BEM-Park model, which is not correct according to Fig 7. This may be fixed by the following steps:
1. Numerical methods:
Eqs (1) to (6) are not numerical methods but definitions. They should appear under Section 2, where you should also add the definition of C_P for the dual rotor (you can join expressions together to reduce the number of equations, e.g. the definitions of dual rotor TSRS are all in one equation separated by commas). Instead there should be a description on the BEM-Park model with an explicit expression of the velocity deficit in Park's model under numerical method. Such description appears in your PhD thesis and you can use it as it is not a journal publication. The CFD paragraph can be broken to 2-3 paragraphs and must also include a paragraph how the dual rotor configuration is modelled.
2 Grid convergence:
You should also show convergence in C_P (coefficient of power). It can be for a certain TSR.
3 Single rotor case:
What is the C_P for TI=15%? If it is much reduced, it can explain the better velocity recovery behind the rotor. You should look for a ref where they also got reduced C_P from RANS as compared to other results when the blade is mostly in stall in order to better support the reduced C_P from RANS at theta_T=-2 degs.
4 Dual rotor case:
Fig 7 is a mess. I do not understand the short lines from RANS. Are they for dual rotor where the front rotor is at theta_T=2 degs and the rear rotor is at theta_T=-2 degs? If yes, then something is very wrong with the RANS calculation, because by Fig 6a RANS gives positive C_P for the rear rotor when TSR<6. In IJET paper the front rotor's C_P line was added to the graph of the dual rotor C_P lines in order to show the benefit of using a dual rotor configuration. You can use the same approach for Fig 7 or even better and just show the lines for a dual rotor configuration. The IJET BEM-Park results are for dual rotor with the same RPM (front and rear) which means the same TSR if normalised by the free stream velocity U_infinity or the same TSR which means the TSRs of Eq (4) and (5) for the front and rear rotors respectively.
5 Park wake model evaluation:
By Fig 9(b) it seems that TI=15% case fits pretty well the Park model with k=0.04 (unlike what is written in the text). Can't we get a new k to fit the line of TI=1% and repeat the calculation of BEM-Park model? It will also be of great interest to see the radial distribution of the velocity recovery, i.e. to integrate the velocity over the azimuthal direction. That can be incorporated into the BEM model in a future calculation
6. Journal:
I saw that you used Elsevier LaTeX format. What journal do you have in mind?
7. Authors:
I saw that you added Jiahuan as a author which is fine. However, please note that SEMS regulations require a SEMS academic to be a corresponding author (there can be more than one corresponding author) particularly when SEMS has put some funding into the project, unless there is a unique reason not to. My further specific comments are in the attached.

Feedback on Ch5 paper based on CFD-RANS的更多相关文章

  1. Data of Ch5 --Dual rotor

    * Results *Conclusion*- little effect of rear rotor on Cp_1- Cp1 is independent of TI** TI effect on ...

  2. {ICIP2014}{收录论文列表}

    This article come from HEREARS-L1: Learning Tuesday 10:30–12:30; Oral Session; Room: Leonard de Vinc ...

  3. Convert BSpline Curve to Arc Spline in OpenCASCADE

    Convert BSpline Curve to Arc Spline in OpenCASCADE eryar@163.com Abstract. The paper based on OpenCA ...

  4. 【转】关于KDD Cup '99 数据集的警告,希望从事相关工作的伙伴注意

    Features From: Terry Brugger Date: 15 Sep 2007 Subject: KDD Cup '99 dataset (Network Intrusion) cons ...

  5. [转载]bigtable 中文版

    转载厦门大学林子雨老师的译文 原文: http://dblab.xmu.edu.cn/post/google-bigtable/ Google Bigtable (中文版) 林子雨2012-05-08 ...

  6. 谷歌三大核心技术(三)Google BigTable中文版

    谷歌三大核心技术(三)Google BigTable中文版 Bigtable:一个分布式的结构化数据存储系统 译者:alex 摘要 Bigtable是一个分布式的结构化数据存储系统,它被设计用来处理海 ...

  7. Google Bigtable (中文版)

    http://dblab.xmu.edu.cn/post/google-bigtable/ Abstract BigTable是一个分布式存储系统,它可以支持扩展到很大尺寸的数据:PB级别的数据,包含 ...

  8. 【论文笔记】Social Role-Aware Emotion Contagion in Image Social Networks

    Social Role-Aware Emotion Contagion in Image Social Networks 社会角色意识情绪在形象社交网络中的传染 1.摘要: 心理学理论认为,情绪代表了 ...

  9. googleBigTable

    Bigtable是一个分布式的结构化数据存储系统,它被设计用来处理海量数据:通常是分布在数千台普通服务器上的PB级的数据.Google的很多项目使用Bigtable存储数据,包括Web索引.Googl ...

随机推荐

  1. Python基础知识(2)

    1:if比较运算符.and.or >=:大于或者等于 <=:小于或者等于 ==:等于 !=:不等于  (<>:也是不等于,在Python2中可用.Python3中无法使用) a ...

  2. Python基础知识(1)

    Python 3 1:print:输出信息    例子:   ( 所有的标点符号都要是英文状态下输入,要不然会报错) print(“hello world”) 2:注意 : python 和 pyth ...

  3. Qt文本读写之二:目录操作

    一.简介 QDir类用来访问目录结构及其内容,可以操作路径名.访问路径和文件相关信息以及操作底层的文件系统,还可以访问Qt的资源系统.Qt使用"/"作为通用的目录分隔符和URLs的 ...

  4. LightOj 1170 - Counting Perfect BST (折半枚举 + 卡特兰树)

    题目链接: http://www.lightoj.com/volume_showproblem.php?problem=1170 题目描述: 给出一些满足完美性质的一列数(x > 1 and y ...

  5. iphone6,键盘收起,H5页面下面出现空白

  6. H5页面快速搭建之高级字体应用实践

    原文出处: 淘宝前端团队(FED)- 龙驭 背景 最近在开发一个 H5 活动页快速搭建平台,可以通过拖拽编辑图片,文字等元素组件,快速搭建出一个移动端的活动页面,基本交互和成品效果类似 PPT 软件. ...

  7. json数组某个数值对应渲染

    当你统计某一年的某个值它对应的月份总数时,后台没有直接处理好,某个月对应某个值,这样会增加统计的负担,但当数据时这样的时候,在angularjs中时不能直接引用的. "data": ...

  8. JS编写自己的富文本编辑器

    富文本编辑器,网上有很多功能齐全种类丰富的如百度的Ueditor,简单适用型的如WangEditor等等.在经过一番挑选后,我发现都不适用现在的项目,然后决定自己造轮子玩玩.富文本编辑器中主要涉及到J ...

  9. kde framework概述(KDE Framework译文)

    KDE Frameworks 基于QT框架,提供简单实用的类(例如那些KCoreAddons里的类)去为桌面应用的日常需要整合出解决方案(例如KNewStuff用于在应用中获取可下载的附加内容,或者那 ...

  10. Openrisc的or1200

    1 什么是OpenRISC OpenRISC 是硬件开源社区opencores开发的RISC指令集处理器架构,包括32 bits 的Openrisc1000 和64 bitsOpenrisc 2000 ...