Peer Review History
| Original SubmissionJanuary 10, 2026 |
|---|
|
Dear Dr. Tareq, 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 Mar 28 2026 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, Sheikh Arslan Sehgal, PhD 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. Please include your tables as part of your main manuscript and remove the individual files. Please note that supplementary tables (should remain/ be uploaded) as separate "supporting information" files. 4. Please include a caption for figure 2 5. 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 1. Is the manuscript technically sound, and do the data support the conclusions? Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: Yes ********** 2. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #1: Yes Reviewer #2: N/A Reviewer #3: Yes ********** 3. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #1: Yes Reviewer #2: No Reviewer #3: Yes ********** 4. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: Yes ********** Reviewer #1: The manuscript addresses an important public-health problem by proposing a computationally designed multi-epitope vaccine candidate against Human Metapneumovirus (HMPV) using reverse vaccinology and pan-genomic analysis. While the study follows a commonly accepted immunoinformatics pipeline, the work lacks sufficient methodological justification, benchmarking, and biological validation. Several conclusions are overstated relative to the in silico evidence provided. Substantial revisions are required before the manuscript can be considered for publication. While the manuscript addresses an important topic, significant improvements in technical rigor, interpretative caution, and language quality are required before it can be considered for publication. 1.The study relies entirely on in silico predictions, yet several conclusions imply biological efficacy; this overinterpretation must be corrected throughout. 2.The pan-genomic dataset size and diversity are insufficiently justified, raising concerns about the representativeness of conserved epitopes. 3.The manuscript does not clearly distinguish between filtering criteria and true validation, particularly for epitope selection and docking results. 4.The immunoinformatics pipeline largely follows previously published workflows without demonstrating substantial methodological novelty. 5.No benchmarking against experimentally validated HMPV epitopes or vaccine candidates is provided. 6.Epitope conservation is evaluated at the protein level rather than at the allele-specific epitope level, which limits robustness claims. 7.The population coverage analysis assumes uniform HLA expression and immune responsiveness, which oversimplifies real population heterogeneity. 8.The use of immune simulation tools is treated as functional validation, despite known limitations of such models. 9.Docking studies with immune receptors (e.g., TLRs) are conceptually misinterpreted as evidence of immunogenicity. 10.The vaccine construct design lacks comparative assessment with alternative linker or adjuvant configurations. 11.The manuscript does not address epitope competition, immunodominance, or antigen processing constraints. 12.Structural modeling results are presented without confidence scores or error estimation. 13.The absence of sensitivity analysis for prediction thresholds weakens the reliability of the pipeline. 14.Claims of “broad protection” are not supported by functional or epidemiological data. 15.The discussion does not adequately acknowledge false-positive rates inherent to epitope prediction tools. 16.No attempt is made to evaluate potential cross-reactivity or autoimmunity risks. 17.The manuscript lacks a clear translational roadmap bridging computational prediction to experimental validation. 18.Several figures are descriptive but do not add mechanistic insight. 19.Statistical rigor is limited; many results are reported without comparative baselines. 20.Overall, the manuscript would benefit from a more critical, hypothesis-driven narrative rather than a pipeline-driven presentation. Abstract and Title The abstract provides a clear overview of the workflow but overstates the readiness of the vaccine candidate. Claims suggesting effectiveness, protection, or immunogenicity should be softened to “predicted” or “potential”. Quantitative results (e.g., binding affinities, population coverage) are reported without uncertainty or limitations. The abstract should explicitly state that no experimental validation was performed. The title is descriptive and appropriate. However, the phrase “Computational prediction of a vaccine candidate” should be emphasized throughout the manuscript to avoid implying experimental validation. Consider clarifying whether the pan-genomic analysis is based on complete global HMPV diversity or a limited dataset. Introduction The background on HMPV epidemiology and clinical relevance is adequate. The rationale for selecting multi-epitope vaccine design is appropriate but largely generic and not well differentiated from previous studies. The novelty of combining reverse vaccinology with pan-genomic analysis is claimed but not critically compared with existing HMPV vaccine design studies. The introduction would benefit from a clear statement of unmet gaps in current HMPV vaccine research that this study aims to address by citing recently published articles. For instance the following articles are worthy to read and cite. 10.15586/aei.v53i6.1475, 10.15586/aei.v53i6.1492, 10.15586/aei.v54i1.1504, 10.15586/aei.v54i1.1519, 10.3389/fmicb.2022.96028, 10.3390/biomedicines11041041 Materials and Methods Genome Retrieval and Pan-Genomic Analysis The criteria for genome selection (strain diversity, geographic representation, completeness) are insufficiently described. No justification is provided for the number of genomes used in the pan-genome analysis. The classification of core, accessory, and unique genes should be supported by reproducibility metrics or thresholds. Antigen Selection and Reverse Vaccinology Protein selection criteria (e.g., subcellular localization, antigenicity cutoffs) appear arbitrary and are not adequately justified. The exclusion of potentially relevant proteins is not discussed. The study does not assess protein conservation at the epitope level, which is critical for vaccine robustness. Epitope Prediction Multiple epitope prediction tools are used, but no benchmarking or consensus rationale is provided. The choice of thresholds for epitope selection lacks justification. B-cell epitope prediction is treated superficially, despite its importance in vaccine design. Epitope redundancy and overlap are not adequately addressed. Population Coverage Analysis While global HLA coverage is claimed, the manuscript does not clearly state which populations are underrepresented. The analysis assumes equal HLA expression and immune responsiveness, which oversimplifies real-world variability. Results should be interpreted with greater caution. Vaccine Construct Design Linker selection and adjuvant choice are not sufficiently justified with references or comparative analysis. The potential impact of linker sequences on epitope processing and presentation is not discussed. No alternative construct designs are evaluated. Structural Modeling and Docking Structural predictions are presented without confidence metrics such as model reliability or alignment scores. Docking with immune receptors (e.g., TLRs) is treated as validation, which is conceptually incorrect. Docking results are not compared against known ligand–receptor complexes. Immune Simulation Immune simulation results are descriptive but lack biological grounding. The limitations of in silico immune simulators are not acknowledged. Simulation outputs are interpreted too literally as indicators of real immune protection. Results Results largely mirror the computational workflow without critical analysis. Many results are reported without statistical context or comparative baselines. Figures are descriptive but do not provide mechanistic insight. The distinction between filtering steps and true validation is often blurred. Discussion The discussion reiterates results rather than critically interpreting them. Limitations of immunoinformatics-only vaccine design are insufficiently acknowledged. No comparison is made with existing HMPV vaccine candidates or experimental studies. Translational implications are overstated given the absence of experimental validation. Potential challenges such as epitope competition, immune dominance, and vaccine delivery are not discussed. Conclusion The conclusion summarizes the workflow but overstates confidence in the proposed vaccine candidate. Statements implying vaccine efficacy or readiness for clinical development should be removed or softened. The conclusion should clearly outline next experimental steps, such as in vitro immunogenicity and in vivo validation. Grammatical, Typographical Mistakes 1.Inconsistent use of American vs British spelling (e.g., “modeling” vs “modelling”). 2.Overuse of assertive verbs such as “demonstrates,” “confirms,” and “proves” in a computational-only study. 3.Frequent missing articles (“a,” “an,” “the”) before technical nouns. 4.Subject–verb agreement errors (e.g., “results shows” instead of “results show”). 5.Long, complex sentences that should be split for clarity. 6.Inconsistent abbreviation formatting; some abbreviations are used before definition. 7.Inconsistent capitalization of technical terms and algorithm names. 8.Redundant phrasing such as “it is important to note that,” which can be removed. 9.Minor spelling errors introduced by PDF line breaks. 10.Inconsistent hyphenation (e.g., “multi epitope” vs “multi-epitope”). 11.Incorrect pluralization (e.g., “epitope was selected” when referring to multiple epitopes). 12.Extra spaces before punctuation marks in several places. 13.Mixed verb tenses within the same paragraph. 14.Ambiguous pronoun references (“this,” “which”) with unclear antecedents. 15.Inconsistent formatting of symbols and units. Reviewer #2: 1.Abstract: Reduce methodologies and focus on the findings. 2.Introduction: Too lengthy. Outbreak HMPV after SARS-CoV and possible similarities in the mode of pathogenesis including host-virus interactions in terms of TLR activation (author may follow and include: https://doi.org/10.1016/j.cytogfr.2024.10.001; https://doi.org/10.1016/j.ijbiomac.2024.137836) 3.Results and Discussion: Too lengthy. A scheme may be added for better understanding. What were the immunological basis of selecting the antigens used for vaccine construction? What are the molecular functions mediated by these in HMPV which could be hampered by vaccination? TLR4 is appearing to be a key target, and therefore a thorough discussion on the roles of TLR4 in inducing innate immune response to viruses and other microbes need to be included (author may follow and include: https://doi.org/10.1016/j.bjid.2015.10.011 https://doi.org/10.1111/sji.12771; https://doi.org/10.1016/j.cytogfr.2024.10.001; https://doi.org/10.1016/j.ijbiomac.2024.137836; ) 4.Discussion: The potential of reverse vaccinology and immuno-informatics approaches in designing vaccines for therapeutic use in different diseases caused from virus to bacteria to parasite and even against cancer-causing pathogen should be discussed and author may follow these important findings. (https://doi.org/10.1016/j.intimp.2024.112120; https://doi.org/10.1016/j.meegid.2022.105237; https://doi.org/10.3390/vaccines11030525 https://doi.org/10.1016/j.meegid.2020.104633 https://doi.org/10.1016/j.heliyon.2024.e36154; ;; https://doi.org/10.1016/j.molliq.2022.118633). https://doi.org/10.1016/j.meegid.2020.104633 (https://doi.org/10.1016/j.heliyon.2024.e36154) (https://doi.org/10.1016/j.xpro.2025.103671). Reviewer #3: Manuscript Title:Computational prediction of a multi-epitope Human Metapneumovirus vaccine candidate through integrated reverse vaccinology and pan-genomic approaches Comment:Major Revision Manuscript ID :PONE-D-25-68286 The study entitled “Computational prediction of a multi-epitope Human Metapneumovirus vaccine candidate through integrated reverse vaccinology and pan-genomic approaches” used bioinformatics to design a multi-epitope Human Metapneumovirus vaccine candidate, evaluating antigenicity, immune responses, structural stability, and cloning feasibility for future experimental validation. Therefore, this study can be recommended for publication if the following comments are addressed. 1.It is not clear how diverse and representative the HMPV sequence dataset was. The authors should clarify whether multiple strains from different geographical regions and time periods were included, and how this diversity might influence epitope selection. 2.Although three proteins (Protein 1, Protein 2, and Protein 3) were shortlisted, the criteria used to prioritize these proteins are not explained. The authors should explain the criteria. 3.Were all the predicted epitopes conserved across all the strains? 4.The authors should check whether the selected epitopes were homologous to the human proteome or not. 5.There appears to be an inconsistency between docking and molecular dynamics results: Protein 1 showed stronger receptor binding, whereas Protein 2 was selected as the final candidate due to better structural stability. The authors should clearly explain this. 6.The authors are advised to perform discontinuous epitope prediction. 7.In silico experiments i.e. Molecular docking and Immune simulation of selected vaccine construct do require a control (positive and/or negative) to emphasize that HMPV_V2 is better binder and inducer of immune response. Control can be chosen from an existing experimentally verified construct/epitope or a randomly generated construct for comparison. Further, high binding energies (in docking experiments) in comparison to no reference do not make sense. 8.The discussion section is not satisfactory. The authors should use other studies that have been done in this field in this section and compare their results with the results of those studies. It is suggested that you use the following studies in this section: https://doi.org/10.1016/j.biologicals.2024.101782 https://doi.org/10.1007/s13205-024-04022-6 https://doi.org/10.1016/j.vacun.2024.04.003 https://doi.org/10.1007/s12026-023-09403-2 https://doi.org/10.3390/v14112504 https://doi.org/10.1016/j.jtbi.2016.04.009 9.The manuscript has many typographical and grammatical errors. Please improve the manuscript by someone who is a native English speaker. ********** 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 ********** [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 1 |
|
Dear Dr. Tareq, 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 04 2026 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. As the corresponding author, your ORCID iD is verified in the submission system and will appear in the published article. PLOS supports the use of ORCID, and we encourage all coauthors to register for an ORCID iD and use it as well. Please encourage your coauthors to verify their ORCID iD within the submission system before final acceptance, as unverified ORCID iDs will not appear in the published article. Only the individual author can complete the verification step; PLOS staff cannot verify ORCID iDs on behalf of authors. We look forward to receiving your revised manuscript. Kind regards, Haitham Mohamed Amer, 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. Reviewers' comments: Reviewer's Responses to Questions Comments to the Author Reviewer #1: All comments have been addressed Reviewer #2: All comments have been addressed Reviewer #3: (No Response) ********** 2. Is the manuscript technically sound, and do the data support the conclusions??> Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: Yes ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: Yes ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #1: Yes Reviewer #2: No Reviewer #3: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: Yes ********** Reviewer #1: The manuscript has been revised and the authors have responded to all my comments. I would recommend this manuscript for publication Reviewer #2: Authors have addressed all the concerns raised by me, revised the manuscript and the revised forms look more improved. Reviewer #3: The study entitled “Computational prediction of a multi-epitope Human Metapneumovirus vaccine candidate through integrated reverse vaccinology and pan-genomic approaches” designed a multi-epitope HMPV vaccine candidate using pan-genomics and immunoinformatics to predict immunogenicity and stability. Therefore, this study can be recommended for publication if the following comments are addressed. 1. Does the dataset include balanced representation of all HMPV sub-lineages, or are some groups overrepresented? How was genetic variability within each lineage quantified to ensure comprehensive epitope coverage? 2. What Were proteins selected based only on conservation, or also on subcellular localization and antigen exposure? How was accessibility to host immune surveillance (e.g., membrane/extracellular presence) validated? 3. What is the known accuracy or error rate of tools like IEDB, BCpred, or VaxiJen in similar studies? How were false positives minimized or validated through multi-tool or threshold-based filtering? 4. Are certain HLA alleles disproportionately responsible for the predicted binding affinity? How does this bias affect vaccine effectiveness across genetically diverse populations? 5. What model underlies the immune simulation tool? 6. Do any predicted epitopes share sequence or structural similarity with human proteins? 7. What was the total pool of predicted epitopes before applying filtering criteria? 8. How stringent was the selection process, and what proportion of candidates were retained? 9. The manuscript has many typographical and grammatical errors. Please improve the manuscript by someone who is a native English speaker. 10. The discussion section is not satisfactory. The authors should use other studies that have been done in this field in this section and compare their results with the results of those studies. It is suggested that you use the following studies in this section: https://doi.org/10.1016/j.biologicals.2024.101782 https://doi.org/10.1007/s13205-024-04022-6 https://doi.org/10.1016/j.vacun.2024.04.003 https://doi.org/10.1007/s12026-023-09403-2 https://doi.org/10.3390/v14112504 https://doi.org/10.1016/j.jtbi.2016.04.009 ********** 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 ********** [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. Md Tareq, 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. As the corresponding author, your ORCID iD is verified in the submission system and will appear in the published article. PLOS supports the use of ORCID, and we encourage all coauthors to register for an ORCID iD and use it as well. Please encourage your coauthors to verify their ORCID iD within the submission system before final acceptance, as unverified ORCID iDs will not appear in the published article. Only the individual author can complete the verification step; PLOS staff cannot verify ORCID iDs on behalf of authors. We look forward to receiving your revised manuscript. Kind regards, Haitham Mohamed Amer, 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. Reviewers' comments: Reviewer's Responses to Questions Comments to the Author Reviewer #4: (No Response) Reviewer #5: All comments have been addressed ********** 2. Is the manuscript technically sound, and do the data support the conclusions??> Reviewer #4: No Reviewer #5: No ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #4: N/A Reviewer #5: Yes ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #4: Yes Reviewer #5: No ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #4: No Reviewer #5: No ********** Reviewer #4: The study addresses an important topic and contains promising material, but there are multiple methodological and interpretive weaknesses that must be addressed before this can be considered a full research contribution. Below I summarize the main concerns and provide actionable suggestions the authors should implement or justify explicitly. 1. Please revise the citation formatting throughout the manuscript. In several instances where multiple references are cited to support the same statement, the references are presented in separate adjacent brackets (e.g., [1] [2] [3]). According to standard scientific writing and the journal's formatting guidelines, these citations should be consolidated into a single bracket (e.g., [1–3]). Please ensure consistency in citation formatting throughout the manuscript. 2. Authors should provide a rationale for the choice of linkers and adjuvant. 3. The authors should explain the methodology in more detail. 4. Authors should assess the solubility of the vaccine construct. 5. Authors should perform disulfide engineering of the vaccine structure. 6. Authors should predict discontinuous B-cell epitopes on the 3D structure of the vaccine. 7. Authors should perform codon optimization and in silico cloning of the vaccine construct. 8. The authors should perform the imine response simulator in response to three doses of the vaccine. 9. Please provide the MM-PBSA calculations of the simulated trajectory. 10. The manuscript has spelling and grammatical errors that need to be proofread and corrected. 11. The authors are suggested to add insights from clinical research to which relates the study with real-world relevance. 12. The manuscript is very grammatically poor and a native speaker should rewrite it. 13. To enrich your study, please refer to other studies on vaccine design of other microorganisms. In this case, it is recommended that you use and cite to the following studies. https://doi.org/10.1186/s12985-026-03099-0 https://doi.org/10.1371/journal.pone.0335147 https://doi.org/10.1186/s12985-026-03072-x Reviewer #5: This manuscript addresses an important and timely topic — the development of an in silico multi-epitope vaccine candidate against HMPV. The pan-genomic approach used to identify core proteins is a methodologically interesting contribution. However, as detailed above, the manuscript suffers from several critical deficiencies that must be resolved before it can be considered for publication in PLOS ONE. The authors are strongly encouraged to conduct a rigorous revision that addresses all points raised. The scientific potential of this work can only be realized with substantially greater methodological transparency, analytical precision, and engagement with the current literature. 1. Throughout the manuscript, target proteins are referred with no accession numbers, gene names, or functional annotations provided. This is a fundamental failure of scientific transparency and reproducibility. The reader cannot determine what the vaccine actually targets. All three proteins must be explicitly identified with their NCBI accession numbers and known biological functions in the Results section. 2. The Abstract and Results section describe the maximum RMSD of HMPV-V2 as 8.213 Å as evidence of "exceptional structural integrity" and "low RMSD." This interpretation is scientifically incorrect. An RMSD of 8.213 Å represents substantial conformational deviation in a protein-receptor complex. For context, RMSD values below 2–3 Å are generally considered indicative of stable MD simulation trajectories. The authors appear to use the term "low" only in comparison to HMPV-V1 (14.352 Å) and HMPV-V3 (22.291 Å), which is a relative rather than an absolute criterion. The manuscript must either provide a proper justification for this interpretive choice or revise the characterization of HMPV-V2's stability. Critically, for comparison, Ehsasatvatan et al. (2025, BMC Infectious Diseases) reported average RMSD values of 0.40 nm (4.0 Å) for their vaccine-TLR4 complex — a far more modest deviation under a 50 ns simulation. The RMSD values of the current manuscript require scientific justification. 3. Lines 565–571 of the Discussion contain a clear internal contradiction: the text states that "Protein 1 of the construct maintains a robust and stable binding affinity to TLR4" while simultaneously attributing minimal RMSD/RMSF fluctuations to "Protein 2." Since HMPV-V2 was selected as the lead candidate, these references are ambiguous and contradictory. This section must be rewritten with precise and consistent nomenclature. 4. According to Table 4 of the manuscript, HMPV-V3 demonstrates superior structural quality metrics: the highest Ramachandran favored region (93.5% vs. 87.7% for HMPV-V2) and the highest ERRAT score (88.796 vs. 87.57). Despite this, HMPV-V2 is selected as the lead candidate without a transparent quantitative scoring framework. No multi-criteria decision analysis or weighted scoring table is provided. The authors must either present a formal justification that accounts for all comparative metrics or acknowledge this limitation explicitly. 5. Line 499 states "We conducted a 100-millisecond molecular dynamics (MD) simulation," while lines 291, 506 and elsewhere consistently state "100-nanosecond." A 100 ms and a 100 ns simulation differ by four orders of magnitude and represent entirely different computational analyses. This is a critical factual inconsistency that must be corrected throughout the manuscript. Figure 7 contradicts the stated simulation duration. The X-axis of Figure 7 (RMSD plot) extends only to 20 nanoseconds, not 100 nanoseconds as stated in the Methods (line 291) and Results (line 506). This is a fundamental inconsistency: either the figure was generated from a truncated or different simulation run than what is described in the text, or the reported simulation duration is incorrect. The authors must clarify and reconcile this discrepancy. If the actual simulation was 20 ns, all claims based on "100 ns stability" are invalid and must be revised accordingly. Similarly, Figure 9 (SSE analysis) also shows a time axis extending only to 20 ns, further confirming this inconsistency. Incomplete MD simulation analysis — key descriptors are absent from the manuscript. The authors state in the Methods section (lines 304–308) that the following MD descriptors were considered for assessing stability: Protein-Ligand Interactions (P-L), Molecular Surface Area (MolSA), Solvent-Accessible Surface Area (SASA), Polar Surface Area (PSA), and Intermolecular Hydrogen Bonds. However, none of the corresponding plots or quantitative data for SASA, MolSA, PSA, radial distribution function (g(r)), or hydrogen bond count/occupancy are presented anywhere in the manuscript or supplementary materials. Only RMSD, RMSF, and SSE are reported. This represents a significant gap between the stated methodology and actual reported results. Specifically: • SASA plots are essential for evaluating solvent exposure and the hydrophilic/hydrophobic balance of the vaccine-receptor interface during the simulation. • Intermolecular hydrogen bond analysis is critical for quantifying the stability of specific interactions at the binding interface and is standard practice in MD-based vaccine studies. • MolSA and PSA provide complementary information about the compactness of the complex over time. The authors must present all aforementioned analyses with appropriate figures and quantitative discussion in the Results and Discussion sections. 6. Lines 586–588 describe reference [76] as "Al-Khafaji et al. (2024) on a Staphylococcus aureus vaccine." However, Reference 76 in the bibliography (Biswas et al., 2024, Biologicals) is a study on human cytomegalovirus (CMV), not S. aureus. This is a clear citation error that was not corrected from the previous revision. All references cited in the Discussion must be verified against their actual content. 7. The authors disclosed in the response letter that 1,250 MHC-I, 1,875 MHC-II, and 980 B-cell epitopes were initially predicted, leading to a final selection of 15 (0.4% retention rate). This information is essential for evaluating the rigor of the selection process but is absent from the manuscript body. It must be incorporated into the Methods and/or Results section. 8. Roary (version 3.13.0) is a pan-genome pipeline originally developed for bacterial genomes. Its applicability to viral pan-genome analysis — particularly for RNA viruses like HMPV — has not been validated in the literature. The authors provide no justification for this methodological choice. A detailed explanation or citation of precedent studies using Roary for viral pan-genomics must be provided, or an alternative validated tool should be used. 9. Line 478 states: "For a respiratory virus like HMPV, a Th1 response is the only way to achieve viral clearance." This is an overstatement that is not supported by immunological evidence. Th2-mediated humoral responses, particularly neutralizing antibody production, also play a significant role in controlling respiratory viral infections. This sentence must be revised to reflect the current understanding of balanced Th1/Th2 immunity in HMPV clearance. 10. Reference 11 is listed as: "human-metapneumovirus-evolution-and-interaction-with-the-innate-i @ share.google. Available: https://share.google/...". A Google Share link does not constitute a citable scientific reference. This citation must be replaced with the original peer-reviewed publication. 11. The complete amino acid sequence of the lead candidate HMPV-V2 (including adjuvant, linkers, and all epitope components) is not provided in the manuscript or supplementary materials. This information is essential for reproducibility and is standard practice in immunoinformatics publications. It must be added as supplementary material. 12. The authors use ProtParam's instability index (<40) to conclude that all vaccine constructs are "stable." It should be noted that this index was developed for in vitro conditions and does not accurately predict in vivo stability under physiological conditions. The text should be qualified accordingly to avoid overclaiming. 13. A significant deficiency of the Discussion section is the absence of a comparison with directly relevant, recently published immunoinformatics studies on HMPV vaccines. The authors are required to engage with the following key studies: Ehsasatvatan et al. (BMC Infectious Diseases, 2025) Naji et al. (Scientific Reports, 2025) Fardad et al. (VirusDisease, Springer, 2025) 14. Despite the authors' claim that professional language editing was performed, the following errors remain in the revised manuscript: • Line 61: "HMPV belongs the Pneumoviridae family" → should read "HMPV belongs to the Pneumoviridae family" • Line 65: "HMPV is now very well recognized as leading etiologic agent" → missing article: "as a leading etiologic agent" • Line 75: "respiratory microrganisms" → spelling error: "microorganisms" • Line 191: "screened for allergenicity, allergenicity and toxicity" → word "allergenicity" is repeated; likely should be "antigenicity, allergenicity and toxicity" • Line 380: "immugenicity booster" → spelling error: "immunogenicity" • Line 453: "Fig 5 also shows the complex files.Tablefiles. Table 5." → apparent copy-paste merge error: "Fig 5 also shows the complex files. Table 5." The manuscript requires a thorough, genuine language review by a professional editor or a native English speaker with scientific background before resubmission. ********** 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 #4: No Reviewer #5: No ********** |
| Revision 3 |
|
Computational prediction of a multi-epitope Human Metapneumovirus vaccine candidate through integrated reverse vaccinology and pan-genomic approaches PONE-D-25-68286R3 Dear Dr. Islam Tareq, 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, Haitham Mohamed Amer, PhD Academic Editor PLOS One Reviewers' comments: Reviewer's Responses to Questions Comments to the Author Reviewer #4: All comments have been addressed Reviewer #5: All comments have been addressed ********** 2. Is the manuscript technically sound, and do the data support the conclusions??> Reviewer #4: Yes Reviewer #5: Yes ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #4: N/A Reviewer #5: Yes ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #4: Yes Reviewer #5: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #4: Yes Reviewer #5: Yes ********** Reviewer #4: The authors have carefully and accurately incorporated all comments into the manuscript, and the article is eligible for publication in this journal. Reviewer #5: (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 #4: No Reviewer #5: No ********** |
| Formally Accepted |
|
PONE-D-25-68286R3 PLOS One Dear Dr. Tareq, 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. Haitham Mohamed Amer 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 .