Peer Review History
| Original SubmissionMarch 18, 2025 |
|---|
|
Dear Dr. Liu, 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. Please submit your revised manuscript by Jun 05 2025 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.
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: https://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, Babak Aslani 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 2. Please note that PLOS ONE has specific guidelines on code sharing for submissions in which author-generated code underpins the findings in the manuscript. In these cases, we expect all author-generated code to be made available without restrictions upon publication of the work. Please review our guidelines at https://journals.plos.org/plosone/s/materials-and-software-sharing#loc-sharing-code and ensure that your code is shared in a way that follows best practice and facilitates reproducibility and reuse. 3. We note that the grant information you provided in the ‘Funding Information’ and ‘Financial Disclosure’ sections do not match. When you resubmit, please ensure that you provide the correct grant numbers for the awards you received for your study in the ‘Funding Information’ section. Additional Editor Comments: The reviewers identified several improvement area for your work: 1- Please enhance the quality of literature review and problem description. You need to clearly state the contribution and novelty of your work. In addition, the core terms such as resilience should be clearly defined to highlight the scope of your work. 2- The quality of presentation (e.g., images and insights of results) must be improved. 3- Please carefully revise the language of your work and remove any typos and errors. 4- The research question, research methodology, and selection of ML methods must be justified and the result must be validated more rigorously. [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions Comments to the Author 1. Is the manuscript technically sound, and do the data support the conclusions? Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: Partly Reviewer #4: No ********** 2. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: Yes Reviewer #4: No ********** 3. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: No Reviewer #4: No ********** 4. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #1: Yes Reviewer #2: No Reviewer #3: Yes Reviewer #4: Yes ********** Reviewer #1: The paper proposes a simulation-based resilience assessment model for cascading failures. My major comments are as follows. 1. The C-L model in this paper only considers node degree, but in reality cascading failures don't just depend on degree. For instance the cascading failure in the infrastructure system, link features like flow dynamics and the road conditions also matters. 2. Why choose criticality sum as the resilience metric over other options, like resilience index, downtime, largest connected component size, etc? 3. Why the tree network is the most stable structures? Isn't that counterfactual? 4. A lot of reference in the paper is missing and not showing. 5. In the related work, I suggest to include the recent GNN work for resilience analysis. For instance, "End-to-end heterogeneous graph neural networks for traffic assignment" and "Graph neural network surrogate for seismic reliability analysis of highway bridge systems" 6. The sample size is too small for the model, which could easily over-fit. You need to validate the result 7. How do you apply the methodology into the real world applications? Reviewer #2: 1.In the introduction Section, the analysis of the literature is not deep enough, and it is suggested that the existing research should be classified and elaborated. 2.Many sentences in this paper use We as the subject, which does not conform to the objectivity paradigm of scientific papers. 3.The various analysis methods given in this paper are the methods proposed by others, and these methods are used to simulate and analyze the four networks. What is the innovation of doing this ? What is the significance of the conclusion ? Do these networks have prototypes ? Is it a transportation network or a computer network ? 4.Among the four networks, there are 49 nodes in the WS and BA networks, and 48 nodes in the ER and TN networks. Is it meaningful to analyze the number of nodes differently ? All the pictures in the text are very poor in clarity, and some of them are not clear at all. 5.Resilience is not clearly explained, just the size of N, BETA, etc? 6.Innovation and research significance Please be sure to show clearly in the important position of abstracts and papers. Reviewer #3: The manuscripts aims at comparing the resilience of four network topologies, and to investigate the main factors influencing it. The idea is interesting, but its development should be described, presented and discussed much better, to fully appreciate the results and check for the correctedness of the methods. General comments: - The novelty and research questions should be explained better, as well as the connections between the first part ("forward" investigation of the effect of various parameters on resilience scores) and the second one (fitting and assessment of sensitivity to parameters, using ML), which currently look like two separate halves. - The whole part regarding fitting and the use of ML should be better explained: the research question is not entirely clear, the data used and methods are also very shallowly described, and it is not clear how the investigation was conducted. I can perceive some direction, but the presentation of methods and results should be drastically improved. - Although the language is overall ok, there are too many typos, grammar, syntax and punctuation mistakes; I suggest revising the text very carefully, many with the help of a native speaker or someone fluent in English, as it is not the role of a reviewer to mark all language problems that hinder the readability of the manuscript. Specific comments: ABSTRACT - "The control variable method": do you mean, simply changing one parameter at a time? Check also in the text - What does "stable resilience changes" mean? - RF and GBM models are not introduced - "stability" what do you mean? - "Finally, an importance analysis of the factors influencing resilience is conducted using RF model show that the tolerance parameter has the most significant impact on resilience, indicate that adjusting node capacity is more cost-effective in enhancing network resilience. " Not entirely clear, can be phrased better INTRODUCTION - "the Swiss mathematician Euler transformed it": what does "it" refer to? - "be primarily classified into four topological forms": Others exist (i.e., all to all, fixed-degree, lattice, etc). If you focus on those, just say they're widely observed in many case studies, or justify the choice - "degree": average degree? In-degree?... - "of edges linked to it": what does "it" refer to? - "However, in the complex network, the network structure is undergoing changes, as well as the network topology.": not clear - "the analysis of resilience in different network structures was rarely.": not clear - "However, the resilience of complex networks with different networks and average degrees against cascading failure still needs to be further investigated to understand the patterns of variation in different types of network structures and mitigate the various losses caused by cascading failures.": not clear what is the gap in the literature that you are trying to address - "In this paper, a resilience assessment model for cascading failure scenarios is proposed, incorporating both the total number of nodes and the average degree, the simulation process and algorithm are designed to evaluate node failure events." Not clear what the research question is - "comparison, the importance analysis of the factors influencing resilience are conducted using the RF model.": not clear; RF model never introduced - " And in this section": which section? MATERIAL AND METHODS - "The relationship between average degree, network structure, and resilience is thoroughly analyzed. " Isn't it for the results? - "an imbalance between supply and demand. " Here and later, the authors mix general results on network and specific requirements from supply chains or transport networks. It is very confusing, please revise all instances. Other examples: "significantly impacting transportation safety and efficiency, and causing substantial financial losses.", "Business relationships", and more - Load I_i: I would have expected L_i, also given the "C-L" model - In the table and in general, do not use "the" to name variables and parameters (and, especially, *not* in the axes labels of the figures; use symbols instead!) - Node v_i: what is it? - Eq 1: where does it come from, and how does it fit in the text? - Eq 2: is F instead F_i? - "(or flow)": what is it? - "distance": according to which metric? how defined? - "Then there exists several adjacency matrices: " How used? How does this "en passant" remark fit into the text? - Eq. 3: sum over i up to N? - "failed node itself, and apparently": why "apparently"? SIMULATIONS - "existing research and historical experience": Not clear. If you are based on literature, cite it; otherwise, explain - q_ij = q_ji = 30: why? - "The distance between node i and node j in the four networks randomly generated, normally distributed and...": not clear - "Ii = 10~80, follow a normal distribution." not clear - "characterized by a rapid initial rise and subsequently becomes more gradual.": why not including the fitting immediately here, instead of first verbally describing what is seen and then performing the fit separately? - "degree of fluctuations": what does it mean? RESILIENCE PREDICTION TO CASCADING FAILURE - Why "prediction"? The first part is simply an interpolation, you are not predicting anything - SVM, RF and GBM not introduced nor defined - "simulation experimental data": are they simulated or experimental? - "an poly": what is it? - Error! Reference source not found! - Fig 14 is a dramatic overfitting of a very complex polynomial. Revise and correct - "According to the previous section, the distributions of the variable data β, k and N do not align with a normal distribution.": how would that be evident? And why does it matter for the Spearman coefficient, which looks for non-linear monotonous relationships? - "Correlation between two variables": Defined how? Each "variable" is in principle independent of the others; if you hypothesise they are not, explain how you assess this - "Monotonic equations": Just put the formula - "If the absolute value of the Spearman correlation coefficient between two variables exceeds 0.80, it indicates a mutual dependence": no, this is just an arbitrary choice - "accuracy and stability of the model.": what is "stability"? defined how? of which model? - "simulated data (R, β, k, N)": not clear what you do and mean - "impact the precision of resilience forecasts.": the goal was never explained (and it should be done explicitly and clearly) - " the mean and dividing by the standard deviation. ": of what? How calculated and extracted? - As written above, the rest of the section should be properly explained and clearly stated, so that readers can appreciate all methods and reproduce the results; sharing code may also enable reproducibility. Reviewer #4: The introduction is quite informative but, in my understanding, slightly repetitive in character and can be made more concise. Several parts of the introduction are closer to a lengthy literature review rather than a tight set of circumstances for the study, which creates a confused line of division between contextual setting and critical evaluation of existing research. Furthermore, the objective of study, in which explaining what the paper does uniquely compared to previous studies, somehow it appears later in the section. In my suggestion, it should be emphasized earlier to guide the reader more effectively. Further, there are also grammatical issues that detract from the academic tone, such as subject-verb agreement errors in phrases like "the tree network exhibit," which need to be addressed for clarity and accuracy. On the other hand, one major structural issue of this paper, is that there is no dedicated literature review section. Instead, related work is woven into the introduction, and it is difficult to separate the authors' own work from their synthesis of existing research due to interpolation. Therefore, in this case, the earlier works are mostly summarized but not critically discussed. Meanwhile, theoretical or methodological lacunas in the area are hinted at vaguely, with no adequate critique or evidence whatsoever. These things will undermine the rationale for the current study and blurs the originality of the research questions pursued. Even if the methodology part does provide several technical details like equations and parameters for simulation, the description is not always obvious everywhere, and that might prove difficult for less-advanced readers to understand. For example, several figures like Fig 3 and Fig 4 are stated but there is no explicit discussion or description within the paper to show its function or role, and how those things can help support or validate the methodology. I guess all of them is under-explored. In addition, central assumptions such as the unbounded link capacities or equal load redistribution also be introduced without sufficient explanation on how they might limit the external validity of the findings. Regarding data collection, the paper relies solely on simulated data generated by simulation, with once again, little explanation provided for selecting specific ranges of parameters such as for node numbers, tolerance parameters, and mean degrees. Furthermore, the effort does not take simulation robustness into account as there is no statement on how many runs were made, whether the results are the same over different runs, or to what extent the variability exists. Meanwhile, the external data or world data against which to compare it does not exist at all, limiting the generalizability of the conclusions and raising suspicion regarding the empirical underpinnings of the research. Moreover, despite abundance in visual presentation in the result section, it is plagued with redundancy of textual description. A lot of the discussion repeats graphical results without additional examination, and some figure legends or supporting text are too descriptive and not interpretive. Most importantly, there is no use of statistical tests or confidence limits to validate the trends presented, which also be applied to check the data, in the end contaminates the scientific integrity of the results. Also, there are errors existed such as broken references like "Error! Reference source not found" that reflect poor proofreading and editorial efforts, detracting from the professionalism of the paper. On the other hand, the conclusion predominantly recapitulates earlier findings without offering a more sophisticated theoretical framework for interpreting the implications. Although the paper states a discussion on future work, the suggestions are still ambiguous and can be expanded with more precise directions, for example, applying real network data in real-time or analyzing interdependent multi-layer networks. Furthermore, statements like "adjusting node capacity is cheaper" would also be better if more information on how such capacity adjustments can actually be implemented within real-world network infrastructures, along with the possible trade-offs, technical constraints or economic considerations involved is stated. Lastly, even though the use of machine learning models like SVM, RF or GBM increase the study's value, it is better for the author to explain on why these specific models were selected. The section on hyperparameter tuning, though included does not have very detailed discussion, and once again, there is no external validation or cross-validation across more than one dataset is provided, which lowers the validity and generalizability of the predictive models developed. ********** 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 Reviewer #3: No Reviewer #4: 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 |
|
Dear Dr. Liu, 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.
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.
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: https://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, Babak Aslani Academic Editor PLOS ONE Journal Requirements: If the reviewer comments include a recommendation to cite specific previously published works, please review and evaluate these publications to determine whether they are relevant and should be cited. There is no requirement to cite these works unless the editor has indicated otherwise. [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions Comments to the Author Reviewer #3: (No Response) Reviewer #5: (No Response) Reviewer #6: (No Response) Reviewer #7: All comments have been addressed ********** 2. Is the manuscript technically sound, and do the data support the conclusions??> Reviewer #3: Yes Reviewer #5: Partly Reviewer #6: (No Response) Reviewer #7: (No Response) ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #3: Yes Reviewer #5: (No Response) Reviewer #6: (No Response) Reviewer #7: (No Response) ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #3: No Reviewer #5: No Reviewer #6: (No Response) Reviewer #7: (No Response) ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #3: Yes Reviewer #5: Yes Reviewer #6: (No Response) Reviewer #7: (No Response) ********** Reviewer #3: I commend the authors for the big effort in addressing the comments from the previous round of reviews. I find that the manuscript, undergoing such extensive editing, has now gained more rigor and insights. Nonetheless, a few more points should still be cleared. ABSTRACT: You introduce several acronyms (DC, CC, ER...) but never define them in the abstract. Please do so. LIT REV: Since you now provide a more extensive literature review, you may also want to include Artime et al "Robustness and resilience of complex networks" for a recent review on network resilience, and Proverbio et al "Bridging Robustness and Resilience for Dynamical Systems in Nature" for definitions for dynamical systems UNCLEAR THINGS: - current load of 9 updated from F9 to F9’ (∆F5→9 + F9): what does the content of the parenthesis mean? Is that a equal? Please explain better and be more formal. Moreover, you describe F9' as overload, but isn't the overload just \DeltaF9, and F9' the new load? - In Eq. (6), is "e" the eigenvector corresponding to the largest eigenvalue? - Step 2 of methods: not clear how the various equations talk with each other, if they are connected and how they are used (e.g., where does M goes?) explain better - "specifically safeguarding the top 10% of nodes." What do you mean? not clear - Eq 20-23 not clear; also, calling the variables this way doesn't help readers - "Following prior studies and to control e": which prior studies? - "10 independent simulation repetitions to ensure statistical reliability. ": support (10 is little to "ensure") TEXT: - There are several instances of parenthesis attached to previous or subsequent words, or open parenthesis that are not closed (e.g. Methods, first section, 9 lines below title). Please revise them all. - A few typos still remain (load -> loads, exist->exists ...), please check the text carefully, paying attention to singulars/plurals etc. - Some sentences don't sound right, such as "In this paper, we INTRODUCE the "C-L" model proposed by Motter and". Maybe you use it, since it was already introduced? - Check "Error! Reference source not found." - Beware of fonts of formulae, and that all variables and metrics are consistent (e.g., use italics of math environment in the same way for the same variables across the text). Same goes for apices and pedices, to be checked throughout. And also \ni in Eq (16): it already identified nodes, use other letters - "aligns with discoveries of universal resilience patterns": I would use proposals/suggestions/hypotheses instead of "discoveries", as Gao et al propose to lump under a common framework several instances of models, but fold bifurcations date back many more decades, and anyway they are not universal Reviewer #5: This manuscript investigates the resilience of infrastructure networks to cascading failures, emphasizing the role of network topology in shaping failure propagation. The authors combine traditional network centrality metrics (degree, closeness, eigenvector centrality), a proposed “functional stability” measure, and a “cascading failure scale” to quantify resilience. Simulations are performed on four canonical network models: Erdős-Rényi (ER), Barabási-Albert (BA), Watts-Strogatz (WS), and hierarchical trees. The study aims to derive general insights into how topological properties affect the resilience of networks. Weaknesses and Concerns Limited Novelty: The main concern lies in the lack of novelty in both the methodology and results. The connection between network topology and resilience to cascading failures is well-established in the literature. The combination of classical centrality measures and failure impact into a composite resilience score is not conceptually new, and no theoretical framework or model innovation is introduced. Insufficient Engagement with Literature: The manuscript fails to engage with key existing work. Most notably, the recent and comprehensive review Artime et al., “Robustness and resilience of complex networks”, Nature Reviews Physics (2024) is not cited. This review outlines a rich landscape of resilience research, including structural variations, multilayer networks, adaptive dynamics, and modern modeling tools, none of which are discussed here. Simplistic Model Space: The analysis is restricted to four canonical network topologies (ER, BA, WS, Tree). While these are foundational, much of the recent research in the field focuses on more realistic structures: modular, core-periphery, hierarchical, assortative/disassortative, temporal, and multilayer networks. The exclusion of these significantly limits the generalizability of the conclusions. Known Results Revisited Without New Insight: Many of the findings (e.g., BA networks being robust to random failure but vulnerable to targeted attacks) are textbook-level results that have been known since the early 2000s. The paper does not offer new mechanistic understanding or theoretical contributions. Presentation and Structure: The manuscript includes 17 figures, many of which are redundant or could be grouped for clarity. This makes the paper difficult to follow. A discussion section is lacking. The implications of the findings, their limitations, and potential extensions are not critically assessed. The “CR-based node ranking” is introduced in the abstract but not formally defined in the introduction or methods. This leads to confusion about what exactly is being measured and how. Given the above concerns — especially the limited novelty and lack of engagement with recent literature — I recommend major revision or rejection, depending on the journal’s threshold for conceptual contributions. Reviewer #6: 1.There are still numerous typographical errors in the manuscript. For example, in the first paragraph below Figure 1, where the network model is defined, "V" should represent the node set. Additionally, the references in the first paragraph below Equation 1 are not displayed correctly. 2.Please ensure that the meaning of all mathematical symbols is clearly explained throughout the paper. For instance, what does "F" represent in Equation 1? Furthermore, the formatting of equations is inconsistent across the manuscript. 3.In Figure 3, it is claimed that a comprehensive evaluation metric was constructed, but only separate individual metrics are presented. It seems that the actual construction of a composite index has not been achieved. 4.In the numerical experiments, it is recommended to include simulations on real-world infrastructure networks to enhance the persuasiveness of the results. Reviewer #7: (No Response) ********** 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 Reviewer #5: No Reviewer #6: No Reviewer #7: 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 2 |
|
Dear Dr. Liu,
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: https://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, Babak Aslani, Ph.D. Academic Editor PLOS ONE Journal Requirements: If the reviewer comments include a recommendation to cite specific previously published works, please review and evaluate these publications to determine whether they are relevant and should be cited. There is no requirement to cite these works unless the editor has indicated otherwise. Please review your reference list to ensure that it is complete and correct. If you have cited papers that have been retracted, please include the rationale for doing so in the manuscript text, or remove these references and replace them with relevant current references. Any changes to the reference list should be mentioned in the rebuttal letter that accompanies your revised manuscript. If you need to cite a retracted article, indicate the article’s retracted status in the References list and also include a citation and full reference for the retraction notice. [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions Comments to the Author Reviewer #3: (No Response) Reviewer #7: (No Response) ********** 2. Is the manuscript technically sound, and do the data support the conclusions??> Reviewer #3: Yes Reviewer #7: Yes ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #3: Yes Reviewer #7: No ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #3: No Reviewer #7: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #3: Yes Reviewer #7: Yes ********** Reviewer #3: The authors have made a commendable effort to address the reviewers' comments, by reshaping the manuscript almost completely. Actuallly, since they also mmoved the focus from a simulation-driven theoretical exploration to an application-oriented technical contribution, they may have submitted it as a new manuscript to address reviewers with greater knowledge on these different angle. However, I could evaluate it finding big improvements and not much to additionally review. A few minor points are: - Sec. "Mechanisms of cascading failure propagation", "As Fig.1 shows, when node i (i=1,2, …, n)"... hare and later: do you actually refer to Fig. 2? - Below Eq. 15: My PDF viewer cannot read the sybol after \beta: what is that? - Table 3: p_value of what? - In general, I would suggest to mild down the tone of the findings and of the use of GraphSAGE: althugh it slightly improved with comparison to other methods such as GCN, the difference is not tremendous, both in the identification of critical nodes and in computing time (it is x4, not orders of magnitude). It sufficees to present the findings without sliping into boastful language. - Section "efffects of \beta..": many variables are writeen with a strange "_" in the pedix. Revise? - Not entirely clear how the found fixed allocation ratio of 2:1 between w_sr and w_cs translates into "universal resilience patterns". It is an interesting finding, but Gao et al mostly considered bifurcation-driven failures, which I don't see how they connect with the case here. Can you clarify? Is this remark necessary? Reviewer #7: The revised version shows substantial improvements over the original submission, particularly with the addition of a real-world USAir97 case study and significant presentation cleanup. However, fundamental concerns regarding theoretical novelty, statistical rigor, scalability, and reproducibility remain inadequately addressed. In order to improve your manuscript some revisions are required: 1. Correct the cascading failure model: Add normalization factor to Eq. 2: ΔF_i->j = (load to distribute) × (w_ij / Σ_k w_ik). Current formulation violates load conservation. 2. Strengthen statistical rigor: Replace implausible p-values with appropriate effect sizes (Cohen's d) and bootstrapped significance, Add ablation studies for each component (PCA, entropy, \beta), Conduct sensitivity analysis on resilience metric weights. 3. Scalability: Reviewer #5 mentioned multilayer/hierarchical networks – the authors added USAir97 but did not address computational scalability for large networks or complex topologies. Address this point. 4. Reproducibility. Provide full reproducibility package:Public repository with all code, hyperparameters, and preprocessing scripts, deposit raw simulation outputs in a public repository, Include random seeds, software versions (PyTorch). 5. Taxonomy: the manuscript does not position itself within the resilience taxonomy framework Artime proposes, missing opportunity for theoretical grounding. Address this point. ********** 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 Reviewer #7: 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.] To ensure your figures meet our technical requirements, please review our figure guidelines: https://journals.plos.org/plosone/s/figures You may also use PLOS’s free figure tool, NAAS, to help you prepare publication quality figures: https://journals.plos.org/plosone/s/figures#loc-tools-for-figure-preparation. NAAS will assess whether your figures meet our technical requirements by comparing each figure against our figure specifications. |
| Revision 3 |
|
The submitted revised paper has already answered all the previous comments. Please make sure to address the final minor suggestions from the reviewers. 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.
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: https://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, Babak Aslani, PhD Academic Editor PLOS One Journal Requirements: If the reviewer comments include a recommendation to cite specific previously published works, please review and evaluate these publications to determine whether they are relevant and should be cited. There is no requirement to cite these works unless the editor has indicated otherwise. Please review your reference list to ensure that it is complete and correct. If you have cited papers that have been retracted, please include the rationale for doing so in the manuscript text, or remove these references and replace them with relevant current references. Any changes to the reference list should be mentioned in the rebuttal letter that accompanies your revised manuscript. If you need to cite a retracted article, indicate the article’s retracted status in the References list and also include a citation and full reference for the retraction notice. [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions Comments to the Author Reviewer #3: (No Response) Reviewer #7: All comments have been addressed ********** 2. Is the manuscript technically sound, and do the data support the conclusions??> Reviewer #3: Yes Reviewer #7: Yes ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #3: Yes Reviewer #7: Yes ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #3: Yes Reviewer #7: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #3: Yes Reviewer #7: Yes ********** Reviewer #3: I commend the authors' effort to address my previous comments, which they did in full. I now feel that the paper has been significantly strengthened and fully shows its merits. I only have a couple of additional suggestions to make the reading experience more fluent and easier for people who are not fully proficient with all the details: - The abstract is very technical, and the results are there presented with little context and significance I would suggest to be clear and accessible to multidisciplinary readerships. Also, "GraphSAGE outperforms peers": do you mean it outperforms alternative DL models? and "PCS enhances discriminative power" of what? - Page 14 and 15: Table S1 is included as text, but it is not clear which information it may contain. Please give a quick reference as of why a reader should look it up. - NDCG@K and F1@K: I suggest displaying their naming in fulll, and not just the acronym, the first time they are introduced - A"s illustrated in Fig. 9 (Tables S8 and S9)" please better specify how the tables can be useful and their relationship with the figures Reviewer #7: (No Response) ********** 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 Reviewer #7: 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.] To ensure your figures meet our technical requirements, please review our figure guidelines: https://journals.plos.org/plosone/s/figures You may also use PLOS’s free figure tool, NAAS, to help you prepare publication quality figures: https://journals.plos.org/plosone/s/figures#loc-tools-for-figure-preparation. NAAS will assess whether your figures meet our technical requirements by comparing each figure against our figure specifications. |
| Revision 4 |
|
Critical Node Identification and Resilience Analysis against Cascading Failures PONE-D-25-14454R4 Dear Dr. Liu, 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 will be generated when your article is formally accepted. Please note, if your institution has a publishing partnership with PLOS and your article meets the relevant criteria, all or part of your publication costs will be covered. Please make sure your user information is up-to-date by logging into Editorial Manager at Editorial Manager® and clicking the ‘Update My Information' link at the top of the page. For questions related to billing, please contact billing support . 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, Babak Aslani, PhD Academic Editor PLOS One Additional Editor Comments (optional): Reviewers' comments: Reviewer's Responses to Questions Comments to the Author Reviewer #3: All comments have been addressed ********** 2. Is the manuscript technically sound, and do the data support the conclusions??> Reviewer #3: Yes ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #3: Yes ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #3: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #3: Yes ********** Reviewer #3: (No Response) ********** 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 |
|
PONE-D-25-14454R4 PLOS One Dear Dr. Liu, I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS One. Congratulations! Your manuscript is now being handed over to our production team. At this stage, our production department will prepare your paper for publication. This includes ensuring the following: * All references, tables, and figures are properly cited * All relevant supporting information is included in the manuscript submission, * There are no issues that prevent the paper from being properly typeset You will receive further instructions from the production team, including instructions on how to review your proof when it is ready. Please keep in mind that we are working through a large volume of accepted articles, so please give us a few days to review your paper and let you know the next and final steps. Lastly, 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. You will receive an invoice from PLOS for your publication fee after your manuscript has reached the completed accept phase. If you receive an email requesting payment before acceptance or for any other service, this may be a phishing scheme. Learn how to identify phishing emails and protect your accounts at https://explore.plos.org/phishing. If we can help with anything else, please email us at customercare@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. Babak Aslani 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 .