Peer Review History

Original SubmissionMay 27, 2021
Decision Letter - Thippa Reddy Gadekallu, Editor

PONE-D-21-16599

Research on rapier loom fault system based on cloud-side collaboration

PLOS ONE

Dear Dr. Wan,

Thank you for submitting your manuscript to PLOS ONE. After careful consideration, we feel that it has merit but does not fully meet PLOS ONE’s publication criteria as it currently stands. Therefore, we invite you to submit a revised version of the manuscript that addresses the points raised during the review process.

ACADEMIC EDITOR:

Based on the comments received from the reviewers and my own observation, I recommend major revisions for the article.

Please submit your revised manuscript by Aug 01 2021 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org. When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file.

Please include the following items when submitting your revised manuscript:

  • A rebuttal letter that responds to each point raised by the academic editor and reviewer(s). You should upload this letter as a separate file labeled 'Response to Reviewers'.
  • A marked-up copy of your manuscript that highlights changes made to the original version. You should upload this as a separate file labeled 'Revised Manuscript with Track Changes'.
  • An unmarked version of your revised paper without tracked changes. You should upload this as a separate file labeled 'Manuscript'.

If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter.

If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols. Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols.

We look forward to receiving your revised manuscript.

Kind regards,

Thippa Reddy Gadekallu

Academic Editor

PLOS ONE

Journal Requirements:

When submitting your revision, we need you to address these additional requirements.

1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf

2. We note that you have stated that you will provide repository information for your data at acceptance. Should your manuscript be accepted for publication, we will hold it until you provide the relevant accession numbers or DOIs necessary to access your data. If you wish to make changes to your Data Availability statement, please describe these changes in your cover letter and we will update your Data Availability statement to reflect the information you provide.

3. Thank you for stating the following financial disclosure:

 [No].

At this time, please address the following queries:

  1. Please clarify the sources of funding (financial or material support) for your study. List the grants or organizations that supported your study, including funding received from your institution.
  2. State what role the funders took in the study. If the funders had no role in your study, please state: “The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript.”
  3. If any authors received a salary from any of your funders, please state which authors and which funders.
  4. If you did not receive any funding for this study, please state: “The authors received no specific funding for this work.”

Please include your amended statements within your cover letter; we will change the online submission form on your behalf.

Additional Editor Comments (if provided):

[Note: HTML markup is below. Please do not edit.]

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. Does the manuscript provide a valid rationale for the proposed study, with clearly identified and justified research questions?

The research question outlined is expected to address a valid academic problem or topic and contribute to the base of knowledge in the field.

Reviewer #1: Yes

Reviewer #2: Yes

**********

2. Is the protocol technically sound and planned in a manner that will lead to a meaningful outcome and allow testing the stated hypotheses?

The manuscript should describe the methods in sufficient detail to prevent undisclosed flexibility in the experimental procedure or analysis pipeline, including sufficient outcome-neutral conditions (e.g. necessary controls, absence of floor or ceiling effects) to test the proposed hypotheses and a statistical power analysis where applicable. As there may be aspects of the methodology and analysis which can only be refined once the work is undertaken, authors should outline potential assumptions and explicitly describe what aspects of the proposed analyses, if any, are exploratory.

Reviewer #1: Yes

Reviewer #2: Yes

**********

3. Is the methodology feasible and described in sufficient detail to allow the work to be replicable?

Reviewer #1: Yes

Reviewer #2: Yes

**********

4. Have the authors described where all data underlying the findings will be made available when the study is complete?

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception, at the time of publication. The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #1: Yes

Reviewer #2: Yes

**********

5. Is the manuscript presented in an intelligible fashion and written in standard English?

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #1: Yes

Reviewer #2: Yes

**********

6. Review Comments to the Author

Please use the space provided to explain your answers to the questions above and, if applicable, provide comments about issues authors must address before this protocol can be accepted for publication. You may also include additional comments for the author, including concerns about research or publication ethics.

You may also provide optional suggestions and comments to authors that they might find helpful in planning their study.

(Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #1: comment-1: According to my understanding, the authors classified the electrical faults of rapier loom into common faults and other faults according to the frequency of occurrence by analyzing process and fault characteristics of rapier loom. Then an expert system is built in the field for edge computing based on knowledge fault diagnosis experience to diagnose common loom faults and reduce the computing pressure in the cloud.

comment-2: The authors claims that this study also "reduce the computing pressure in the cloud", but it is only written in abstract. The authors should also explain this point in intro, proposed and conclusion sections.

comment-3: Paper is well written. Authors should add limitations of the proposed work.

Comment-4: The table-1 can be written in more organized form such that to clear understanding about parameters.

comment-5: The authors should add some more words about HMI.

comment-6: The quality of the figures can be improved more especially the figure-6 and 7. Figures should be eye-catching not blur. It will enhance the interest of the reader.

commnet-7: The authors should add more clear detail in a paragraph on figure-4 by making comparison of used algorithms.

commetn-8: The classification results should also be present in abstract in 1 or 2 sentences.

comment-9: The summary at the end of the literature review should be focused on the limitations of related work.

commnet-10: Authors should explain at least the features of the dataset in a table.

commnet-11: Authors should add the most recent references related to cloud computing:

(1) M. Shabbir et al., "Enhancing Security of Health Information Using Modular Encryption Standard in Mobile Cloud Computing," in IEEE Access, vol. 9, pp. 8820-8834, 2021, doi: 10.1109/ACCESS.2021.3049564.

(2) A. R. Javed, M. Usman, S. U. Rehman, M. U. Khan and M. S. Haghighi, "Anomaly Detection in Automated Vehicles Using Multistage Attention-Based Convolutional Neural Network," in IEEE Transactions on Intelligent Transportation Systems, doi: 10.1109/TITS.2020.3025875.

(3) Swarna Priya R.M., Sweta Bhattacharya, Praveen Kumar Reddy Maddikunta, Siva Rama Krishnan Somayaji, Kuruva Lakshmanna, Rajesh Kaluri, Aseel Hussien, Thippa Reddy Gadekallu,

Load balancing of energy cloud using wind driven and firefly algorithms in internet of everything,

Journal of Parallel and Distributed Computing,

Volume 142,

2020,

Pages 16-26,

ISSN 0743-7315,

https://doi.org/10.1016/j.jpdc.2020.02.010.

(4) Thar Baker, Bandar Aldawsari, Muhammad Asim, Hissam Tawfik, Zakaria Maamar, Rajkumar Buyya,

Cloud-SEnergy: A bin-packing based multi-cloud service broker for energy efficient composition and execution of data-intensive applications,

Sustainable Computing: Informatics and Systems,

Volume 19,

2018,

Pages 242-252,

ISSN 2210-5379,

https://doi.org/10.1016/j.suscom.2018.05.011.

(5) M. Asim, Y. Wang, K. Wang and P. -Q. Huang, "A Review on Computational Intelligence Techniques in Cloud and Edge Computing," in IEEE Transactions on Emerging Topics in Computational Intelligence, vol. 4, no. 6, pp. 742-763, Dec. 2020, doi: 10.1109/TETCI.2020.3007905.

Reviewer #2: • In Introduction section, the drawbacks of each conventional technique should be described clearly.

• Introduction needs to explain the main contributions of the work more clearly.

• The authors should emphasize the difference between other methods to clarify the position of this work further.

• The Wide ranges of applications need to be addressed in Introductions

• The quality of the figures can be improved, in terms of resolution and dimensions. The authors can add the refer the applications of cloud. Load balancing of energy cloud using wind driven and firefly algorithms in internet of everything. Providing diagnosis on diabetes using cloud computing environment to the people living in rural areas of India. A Blockchain Based Cloud Integrated IoT Architecture Using a Hybrid Design.

**********

7. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #1: No

Reviewer #2: No

[NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.]

While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org. Please note that Supporting Information files do not need this step.

Revision 1

Reviewer #1: 

comment-1: According to my understanding, the authors classified the electrical faults of rapier loom into common faults and other faults according to the frequency of occurrence by analyzing process and fault characteristics of rapier loom. Then an expert system is built in the field for edge computing based on knowledge fault diagnosis experience to diagnose common loom faults and reduce the computing pressure in the cloud.

Reply-1: Thanks to the experts for their valuable comments on this article. You have summarized it very well, maybe I need to add some content to facilitate other readers to understand the work better.

Revision-1: Add research context and research questions related to reducing stress in cloud computing to highlight the purpose of the study.

comment-2: The authors claims that this study also "reduce the computing pressure in the cloud", but it is only written in abstract. The authors should also explain this point in intro, proposed and conclusion sections.

Reply-2: Common weaving machine faults can also be diagnosed by cloud computing, however, due to the high frequency of occurrence, knowledge for fault diagnosis can be extracted from the fault data samples. Using this knowledge loom equipment can be used for fault diagnosis using the available computing and storage resources. The existing loom fault diagnosis methods are in the cloud platform for these fault situations also using artificial intelligence algorithms. Due to the high frequency of these loom failures, the existing loom fault diagnosis methods can cause a waste of computing resources in the cloud platform. Under the future development trend of data explosion, significant increase in the number of equipment access, and shortage of data computing resources in the cloud platform, the existing loom fault diagnosis method needs to be improved to reduce the pressure on the cloud computing.

Revision-2: In the introduction section it is explained that this fault diagnosis method reduces the stress of cloud computing compared to the original method. This is further explained in the main content by describing this method of loom fault diagnosis and analyzing the workload of cloud computing using this method and the original method, which is again emphasized in the conclusion section.

comment-3: Paper is well written. Authors should add limitations of the proposed work.

Reply-3: The contribution of the article may need to be more explicit to illustrate the limitations of the work.

Revision-3: Added the necessary conditions for the work in the introduction, especially the problems targeted by the loom fault diagnosis system of Cloud Edge Collaboration.

comment-4: The table-1 can be written in more organized form such that to clear understanding about parameters.

Reply-4: I use table 1 to express the common loom faults and their solutions, but it may seem too bloated to clearly express the parameters.

Revision-4: In order to better express, I split table 1 into two tables. Table 2 uses the number to identify the troubleshooting method of loom, and table 3 uses the number of Table 1 to express the common loom faults and their solutions, so the content is more compact.

comment-5: The authors should add some more words about HMI.

Reply-5: The article may lack a more specific design of the weaving machine human-machine interface, which has been added in the main content, and is not developed in detail since the human-machine interface is not the focus of the discussion.

Revision-5: In the section of the article where the main weaving machine processes are described, the design of the human-machine interface of the weaving machine is explained.

comment-6: The quality of the figures can be improved more especially the figure-6 and 7. Figures should be eye-catching not blur. It will enhance the interest of the reader.

Reply-6: The definition of the figures are not enough, because the figures will become blurred when enlarged.

Revision-6: The size, resolution and sharpness of all figures have been adjusted.

commnet-7: The authors should add more clear detail in a paragraph on figure-4 by making comparison of used algorithms.

Reply-7: The paragraphs in Figure-4 mainly describe the diagnostic effect of the loom fault diagnosis method based on rough sets and Bayesian networks, and the description of other algorithms is rather vague and has been modified.

Revision-7: Added a detailed description of the diagnostic effects of other algorithms, and more detailed description of the correctness and volatility of the diagnostic results.

commetn-8: The classification results should also be present in abstract in 1 or 2 sentences.

Reply-8: Detailed data on the results of the fault classification cannot be presented for commercial reasons, but a general description of the results of the classification can be given and corresponding modifications have been made.

Revision-8: After the fault analysis of the loom, the results of classifying the loom faults into common faults and other faults are described.

comment-9: The summary at the end of the literature review should be focused on the limitations of related work.

Reply-9: At the end of the literature review, the limitations of the related work are summarized.

The literature review only mentions that the fault diagnosis method cannot be applied to the loom and lacks a summary of the limitations of the work related to the loom, which has been made to correspond to the modifications.

Revision-9: The limitations of the related work are explained at the end of the literature review to address the issues studied in this work.

commnet-10: Authors should explain at least the features of the dataset in a table.

Reply-10: In accordance with the formatting requirements of the journal, data preparation should be carried out in the main content, suitable for the insertion of a table explaining the characteristics of the data set, relevant modifications have been made.

Revision-10: Added a paragraph and a table to represent the characteristics of the dataset for troubleshooting.

commnet-11: Authors should add the most recent references related to cloud computing:

(1) M. Shabbir et al., "Enhancing Security of Health Information Using Modular Encryption Standard in Mobile Cloud Computing," in IEEE Access, vol. 9, pp. 8820-8834, 2021, doi: 10.1109/ACCESS.2021.3049564.

(2) A. R. Javed, M. Usman, S. U. Rehman, M. U. Khan and M. S. Haghighi, "Anomaly Detection in Automated Vehicles Using Multistage Attention-Based Convolutional Neural Network," in IEEE Transactions on Intelligent Transportation Systems, doi: 10.1109/TITS.2020.3025875.

(3) Swarna Priya R.M., Sweta Bhattacharya, Praveen Kumar Reddy Maddikunta, Siva Rama Krishnan Somayaji, Kuruva Lakshmanna, Rajesh Kaluri, Aseel Hussien, Thippa Reddy Gadekallu,

Load balancing of energy cloud using wind driven and firefly algorithms in internet of everything,

Journal of Parallel and Distributed Computing,

Volume 142,

2020,

Pages 16-26,

ISSN 0743-7315,

https://doi.org/10.1016/j.jpdc.2020.02.010.

(4) Thar Baker, Bandar Aldawsari, Muhammad Asim, Hissam Tawfik, Zakaria Maamar, Rajkumar Buyya,

Cloud-SEnergy: A bin-packing based multi-cloud service broker for energy efficient composition and execution of data-intensive applications,

Sustainable Computing: Informatics and Systems,

Volume 19,

2018,

Pages 242-252,

ISSN 2210-5379,

https://doi.org/10.1016/j.suscom.2018.05.011.

(5) M. Asim, Y. Wang, K. Wang and P. -Q. Huang, "A Review on Computational Intelligence Techniques in Cloud and Edge Computing," in IEEE Transactions on Emerging Topics in Computational Intelligence, vol. 4, no. 6, pp. 742-763, Dec. 2020, doi: 10.1109/TETCI.2020.3007905.

Reply-11: In order to illustrate the work of this paper, the latest work on cloud computing needs to be introduced in the introduction.

Revision-11: Relevant references have been cited in the article to illustrate the research related to cloud computing.

Reviewer #2:

• In Introduction section, the drawbacks of each conventional technique should be described clearly.

Reply-1: We thank the experts for their valuable comments on this article. The article does not highlight the traditional technology enough when introducing it, and the description of the disadvantages is not detailed enough. Changes have been made to this section.

Revision-1: For each traditional technology introduce the contribution with a description of its shortcomings, rather than a general description at the end.

• Introduction needs to explain the main contributions of the work more clearly.

Reply-2: The article is not sufficiently detailed in its description of the background and problems of the study, and the significance of the work is not adequately explained. The main contribution of the work has been highlighted by the description of the research questions and the significance of the work.

Revision-2: Provide more detail on the background and problems of the study and more detail on the purpose of the study. Highlight the study's best features and main contributions.

• The authors should emphasize the difference between other methods to clarify the position of this work further.

Reply-3: The article lacks the highlighting of the characteristics and advantages of the study in comparing other methods, especially the differences in research questions and research effects. Revisions have been made.

Revision-3: A summary of other methods outlines issues not covered by other methods and describes the research conducted by the proposed method in response to this method. The characteristics of the research and the position of the work in this paper are emphasized in the context of the previous research.

• The Wide ranges of applications need to be addressed in Introductions.

Reply-4: The article does not discuss the value of this approach to be borrowed in other application scenarios. In particular, the theoretical reusability of this approach in other application scenarios. The concept of dividing the computational tasks for application specific needs and distributing them rationally in the field and in the cloud should be discussed.

Revision-4: The boundary conditions of whether this approach of cloud edge synergy can be used and studied in other scenarios of application requirements are discussed.

• The quality of the figures can be improved, in terms of resolution and dimensions. The authors can add the refer the applications of cloud. Load balancing of energy cloud using wind driven and firefly algorithms in internet of everything. Providing diagnosis on diabetes using cloud computing environment to the people living in rural areas of India. A Blockchain Based Cloud Integrated IoT Architecture Using a Hybrid Design.

Reply-5: The definition of the figures are not enough, because the figures will become blurred when enlarged.In order to illustrate the work of this paper, reference literature related to cloud computing needs to be added in the introduction.

Revision-5: The size, resolution and sharpness of all figures have been adjusted.Relevant references have been cited in the article to illustrate the research related to cloud computing.

Attachments
Attachment
Submitted filename: Response to Reviewers.docx
Decision Letter - Thippa Reddy Gadekallu, Editor

Research on rapier loom fault system based on cloud-side collaboration

PONE-D-21-16599R1

Dear Dr. Wan,

We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements.

Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication.

An invoice for payment will follow shortly after the formal acceptance. To ensure an efficient process, please log into Editorial Manager at http://www.editorialmanager.com/pone/, click the 'Update My Information' link at the top of the page, and double check that your user information is up-to-date. If you have any billing related questions, please contact our Author Billing department directly at authorbilling@plos.org.

If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org.

Kind regards,

Thippa Reddy Gadekallu

Academic Editor

PLOS ONE

Additional Editor Comments (optional):

Reviewers' comments:

Reviewer's Responses to Questions

Comments to the Author

1. Does the manuscript provide a valid rationale for the proposed study, with clearly identified and justified research questions?

The research question outlined is expected to address a valid academic problem or topic and contribute to the base of knowledge in the field.

Reviewer #3: Yes

**********

2. Is the protocol technically sound and planned in a manner that will lead to a meaningful outcome and allow testing the stated hypotheses?

The manuscript should describe the methods in sufficient detail to prevent undisclosed flexibility in the experimental procedure or analysis pipeline, including sufficient outcome-neutral conditions (e.g. necessary controls, absence of floor or ceiling effects) to test the proposed hypotheses and a statistical power analysis where applicable. As there may be aspects of the methodology and analysis which can only be refined once the work is undertaken, authors should outline potential assumptions and explicitly describe what aspects of the proposed analyses, if any, are exploratory.

Reviewer #3: Yes

**********

3. Is the methodology feasible and described in sufficient detail to allow the work to be replicable?

Reviewer #3: Yes

**********

4. Have the authors described where all data underlying the findings will be made available when the study is complete?

The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception, at the time of publication. The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified.

Reviewer #3: Yes

**********

5. Is the manuscript presented in an intelligible fashion and written in standard English?

PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here.

Reviewer #3: Yes

**********

6. Review Comments to the Author

Please use the space provided to explain your answers to the questions above and, if applicable, provide comments about issues authors must address before this protocol can be accepted for publication. You may also include additional comments for the author, including concerns about research or publication ethics.

You may also provide optional suggestions and comments to authors that they might find helpful in planning their study.

(Please upload your review as an attachment if it exceeds 20,000 characters)

Reviewer #3: The contribution is exciting and considerably novel. The paper is well written and starts with influencing motivation, and is reflected throughout the paper. I would like to accept this paper.

**********

7. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files.

If you choose “no”, your identity will remain anonymous but your review may still be made public.

Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy.

Reviewer #3: No

Formally Accepted
Acceptance Letter - Thippa Reddy Gadekallu, Editor

PONE-D-21-16599R1

Research on rapier loom fault system based on cloud-side collaboration

Dear Dr. Wan:

I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now with our production department.

If your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information please contact onepress@plos.org.

If we can help with anything else, please email us at plosone@plos.org.

Thank you for submitting your work to PLOS ONE and supporting open access.

Kind regards,

PLOS ONE Editorial Office Staff

on behalf of

Dr. Thippa Reddy Gadekallu

Academic Editor

PLOS ONE

Open letter on the publication of peer review reports

PLOS recognizes the benefits of transparency in the peer review process. Therefore, we enable the publication of all of the content of peer review and author responses alongside final, published articles. Reviewers remain anonymous, unless they choose to reveal their names.

We encourage other journals to join us in this initiative. We hope that our action inspires the community, including researchers, research funders, and research institutions, to recognize the benefits of published peer review reports for all parts of the research system.

Learn more at ASAPbio .