Peer Review History
| Original SubmissionApril 22, 2025 |
|---|
|
Dear Dr. Coffey, 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 Jul 13 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, Jian Wu, M.D, Ph.D Academic Editor PLOS ONE Journal Requirements: 1. When submitting your revision, we need you to address these additional requirements.-->--> -->-->Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at -->-->https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and -->-->https://journals.plos.org/plosone/s/file?id=ba62/PLOSOne_formatting_sample_title_authors_affiliations.pdf-->--> -->-->2. We noticed you have some minor occurrence of overlapping text with the following previous publication(s), which needs to be addressed:-->--> -->-->https://ashpublications.org/blood/article/144/Supplement%201/1907/532986/Novel-T-Cell-Receptor-Signature-Linked-to-Plasma-->--> -->-->In your revision ensure you cite all your sources (including your own works), and quote or rephrase any duplicated text outside the methods section. Further consideration is dependent on these concerns being addressed.-->--> -->-->3. Thank you for uploading your study's underlying data set. Unfortunately, the repository you have noted in your Data Availability statement does not qualify as an acceptable data repository according to PLOS's standards.-->--> -->-->At this time, please upload the minimal data set necessary to replicate your study's findings to a stable, public repository (such as figshare or Dryad) and provide us with the relevant URLs, DOIs, or accession numbers that may be used to access these data. For a list of recommended repositories and additional information on PLOS standards for data deposition, please see https://journals.plos.org/plosone/s/recommended-repositories.-->--> -->-->4. When completing the data availability statement of the submission form, you indicated that you will make your data available on acceptance. We strongly recommend all authors decide on a data sharing plan before acceptance, as the process can be lengthy and hold up publication timelines. Please note that, though access restrictions are acceptable now, your entire data will need to be made freely accessible if your manuscript is accepted for publication. This policy applies to all data except where public deposition would breach compliance with the protocol approved by your research ethics board. If you are unable to adhere to our open data policy, please kindly revise your statement to explain your reasoning and we will seek the editor's input on an exemption. Please be assured that, once you have provided your new statement, the assessment of your exemption will not hold up the peer review process.-->--> -->-->5. We note that there is identifying data in the Supporting Information files “Supplemental Table 1 to Table 3”. Due to the inclusion of these potentially identifying data, we have removed this file from your file inventory. Prior to sharing human research participant data, authors should consult with an ethics committee to ensure data are shared in accordance with participant consent and all applicable local laws.-->--> -->-->Data sharing should never compromise participant privacy. It is therefore not appropriate to publicly share personally identifiable data on human research participants. The following are examples of data that should not be shared:-->--> -->-->-Name, initials, physical address-->-->-Ages more specific than whole numbers-->-->-Internet protocol (IP) address-->-->-Specific dates (birth dates, death dates, examination dates, etc.)-->-->-Contact information such as phone number or email address-->-->-Location data-->-->-ID numbers that seem specific (long numbers, include initials, titled “Hospital ID”) rather than random (small numbers in numerical order)-->--> -->-->Data that are not directly identifying may also be inappropriate to share, as in combination they can become identifying. For example, data collected from a small group of participants, vulnerable populations, or private groups should not be shared if they involve indirect identifiers (such as sex, ethnicity, location, etc.) that may risk the identification of study participants.-->--> -->-->Additional guidance on preparing raw data for publication can be found in our Data Policy (https://journals.plos.org/plosone/s/data-availability#loc-human-research-participant-data-and-other-sensitive-data) and in the following article: http://www.bmj.com/content/340/bmj.c181.long.-->--> -->-->Please remove or anonymize all personal information (<specific identifying information in file to be removed>), ensure that the data shared are in accordance with participant consent, and re-upload a fully anonymized data set. Please note that spreadsheet columns with personal information must be removed and not hidden as all hidden columns will appear in the published file.-->--> -->-->6. Please include captions for your Supporting Information files at the end of your manuscript, and update any in-text citations to match accordingly. Please see our Supporting Information guidelines for more information: http://journals.plos.org/plosone/s/supporting-information.-->?> [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: No Reviewer #2: Partly Reviewer #3: Partly ********** 2. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #1: No Reviewer #2: Yes Reviewer #3: No ********** 3. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #1: No 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 study provides a detailed and large-scale analysis of TCR repertoire diversity in plasma cell dyscrasias, including MGUS, SMM, and MM, compared to healthy controls. The use of high-throughput sequencing and machine learning adds robustness to the findings. However, the study can be improved with the following aspects: 1. The abundant different TCR clusters between healthy and patients comes only from machine learning (ML)-identified clusters, which are not functionally validated. The title to reflect the ML findings more accurately. 2. Line 39 and lines 122-123: The rationale for focusing on TCRß is not explicitly justified, the authors can briefly explain why TCRß sequencing was prioritized (e.g., technical feasibility, prior literature). 3. Lines 115, 176, 230-231: The authors claim that the age of the healthy group was younger than the patient groups (MGUS/SMM/MM), please provide the median ages for all groups and discuss whether age-matching was attempted. 4. In the main manuscript, the authors claimed that their TCRB sequencing data are available through ImmuneACCESS (e.g., lines 127-128, lines 160-161), but no accession numbers are provided. It will be better if they can provide a specific access accession code. 5. It will be better to standardize the format of the numbers in the main manuscript. e.g., line 213, change “1 240 017” to “1,240,017”. 6. Line 228-229: The manuscript identified "differentially abundant TCRB clusters" only based on p-value. Is there any other parameters that are important for this identification in Supplementary Table 3? e.g, “Importance” or fold-change? 7. Lines 245-247: The authors identified 111 (out of 507 clusters) “CDR3β amino acid sequences associated with T cell specificities for various microbial and human antigens or associated with various pathologic conditions”. Figure 4C should be discussed in detail in the main manuscript. 8. The study does not explain why TCR clusters differ between healthy and disease groups if diversity is similar. Are these clusters tumor-reactive, by stander expansions, or noise? 9. Validate top clusters experimentally (e.g., TCR transfection + antigen screening). The manuscript is well-written and presents important findings. Addressing the above points would significantly strengthen its impact. The study lays a strong foundation for future research into TCR-based diagnostics or therapeutics in plasma cell dyscrasias. Reviewer #2: The manuscript presents an extensive T-cell–receptor (TCR) repertoire analysis across the plasma-cell-dyscrasia continuum and introduces a convergent-clustering with machine-learning (ML) pipeline that reportedly distinguishes patients from healthy donors. The topic is important and, in principle, within PLOS ONE’s scope. However, several methodological and interpretative weaknesses currently prevent me from recommending acceptance. Addressing the issues below should be feasible without re-designing the study, but will require substantial re-analysis and clarification. 1. Differential-abundance screening uses a two-sided Fisher test with α = 0.001 but no FDR control. With 1.24 M tests, ~1 240 false-positive clusters are expected by chance. Re-run the analysis with FDR correction and report the number of clusters that remain significant. Retrain the ML models with this revised feature set. 2. AUROC = 0.84 is based on a single 70/30 random split drawn from the same sequencing batches. No confidence interval (CI) is provided; external generalisability is unknown. Please: (a) Implement repeated stratified hold-outs (e.g., 5 × 20 %) or provide an independent validation cohort. (b) Report AUROC, accuracy, sensitivity, specificity, and Kappa with 95 % CIs. (c) Compare the best model to the others with a statistical test (e.g., DeLong). 3. Provide an enrichment analysis comparing antigen types in disease-enriched vs healthy-enriched clusters. If no significant bias emerges, tone down the claim that the 111/507 clusters containing database-matched CDR3βs “likely reflect differential antigen recognition.”. 4. Except for the R packages and their versions, please also clarify the executable workflow or script directory with hyperparameters. In summary, this study has clear potential. Addressing the above issues and documenting the full reproducibility pipeline should bring the manuscript up to the “methodologically sound” standard required for publication. Reviewer #3: Major Comments and Suggestions: 1. The authors concluded that TCR repertoire diversity did not correlate with disease stage or response to treatment. While this is clearly supported by the multivariate models, the clinical interpretation of this finding is underdeveloped. Please expand on what these null results imply for the understanding of immune surveillance and disease progression. 2. The machine learning framework was well-structured, but critical details need to be clarified, such as how feature selection was handled before model training? What measures were taken to prevent data leakage between training and test sets? Was age included as a covariate in the model, or controlled for via stratification? 3. Although the ROC AUC of 0.84 was promising, a confusion matrix or metrics such as sensitivity/specificity should be included for interpretability. 4. While amino acid properties and antigen database searches were performed, the biological implications remain speculative. The authors stated that distinct clusters differ between patients and healthy controls, but most of these did not map to known antigens. The authors could consider discussing potential causes of this divergence (e.g., subclinical infections, age, vaccination history). 5. Age was accounted for in diversity analyses via multivariate regression and age-exclusion criteria. However, it’s unclear whether machine learning and clustering analyses were fully adjusted for age, which is a known confounder in TCR studies. Please clarify this point or conduct an age-matched subgroup analysis. ********** 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 1 |
|
Dear Dr. Coffey, 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 Sep 21 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, Jian Wu, M.D, Ph.D Academic Editor PLOS ONE Journal Requirements: 1. 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 #1: (No Response) 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: No Reviewer #2: Yes Reviewer #3: Partly ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: No ********** 4. Have the authors made all data underlying the findings in their manuscript fully available??> The PLOS Data policy Reviewer #1: No Reviewer #2: Yes 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: This manuscript presents an analysis of the peripheral blood T-cell receptor (TCR) β-chain repertoire in patients with monoclonal gammopathy of undetermined significance (MGUS), multiple myeloma (MM), and healthy controls (HC), using high-throughput sequencing. The authors identify distinct TCR repertoire features across groups, including differences in clonal expansion, public/shared clones, and CDR3 amino acid usage. The study offers a novel perspective on the immune microenvironment in plasma cell dyscrasias and highlights the potential utility of TCR repertoire profiling in disease stratification. However, there are several significant concerns related to cohort characterization, data interpretation, and methodological clarity that must be addressed before the manuscript can be considered for publication. 1. The manuscript lacks key clinical details about the MGUS and MM cohorts. It is not specified whether patients were treatment-naïve, or if any had received prior immunosuppressive therapy. Since TCR diversity is highly sensitive to immune status, such information is crucial for data interpretation. 2. Additionally, information on infection or inflammatory status should be included, as these factors can influence TCR repertoire features independently of disease state. 3. The study includes only 10 healthy controls, 8 MGUS, and 12 MM patients. The small cohort size limits the robustness and generalizability of the findings, especially for analyses of public clone distribution and amino acid bias. 4. The authors are encouraged to incorporate effect size metrics, confidence intervals, or bootstrapping to enhance statistical reliability. 5. The criteria used to define “clonal expansion,” “shared clones,” and “public clones” are not clearly described. For example, what frequency threshold is used to identify expanded clones? 6. Please provide a consistent and detailed definition of these terms in the Methods section and ensure they are applied uniformly throughout the analysis. 7. The study lacks any form of validation—either technical replicates or an independent validation cohort. The reproducibility of the sequencing data should be addressed, potentially through read saturation plots or duplicate library controls. 8. Figures are generally informative, but legends could be improved. For example, Figures 2 and 4 require clearer color legends and more descriptive axis labeling. 9. Figure 5 would benefit from including statistical annotations (e.g., asterisks for p-values) to indicate the significance of amino acid usage differences. 10. The manuscript briefly mentions clonal expansion and public clones but does not explore underlying mechanisms or implications. Are these changes driven by specific antigens? Is there evidence for immune exhaustion or senescence in MGUS/MM? 11. A more detailed discussion of how repertoire features may reflect tumor-immune interactions would be valuable. 12. The manuscript is generally well written but could benefit from some minor language polishing. Some expressions (e.g., “suggests a trend”) should be supported by statistical evidence or removed. 13. Gene and protein names should follow standard formatting conventions throughout. Reviewer #2: I appreciate the authors’ comprehensive responses to the first-round comments. The revised version is improved in clarity, methodological rigor, and scientific presentation. The study presents a valuable analysis of the TCRB repertoire in plasma cell dyscrasias, with integration of immune repertoire sequencing, machine learning-based classification, and antigen annotation. The distinction between global TCR diversity and cluster-level features appropriately highlights the complexity of T-cell biology in this disease context. While I support the publication of this work, I have a few minor comments and suggestions as outlined below. 1. The MRD results are mentioned briefly. Does MRD status correlate with any TCR feature? 2. Line 259-261: The overlap analysis is interesting but lacks interpretation. Is this overlap more or less than expected by chance? 3. Line 266: How were variable importance scores interpreted across different models? Did top clusters in different models overlap significantly? 4. Please emphasize more clearly that differentially abundant clusters were identified despite no difference in total diversity, which strengthens the idea that qualitative rather than quantitative TCR features matter. 5. The limitation that many sequences did not map to known antigens may reflect gaps in current databases, not necessarily lack of disease relevance. Reviewer #3: 1. Validation of Clustering Results a. The current manuscript does not report how stable or robust the clustering results are. The authors didn’t clarify whether they ran the clustering multiple times to assess consistency. b. No silhouette score, Davies–Bouldin index, or other clustering quality metric is reported to justify the choice of the number of clusters. 2. Sample Size and Overfitting a. The ML models (especially clustering) are susceptible to overfitting, particularly with limited samples. It’s unclear whether the authors used methods to address this (e.g., bootstrapping, downsampling, or dimensionality selection tuning). 3. Biological Interpretation of Clusters a. Some clusters are interpreted as being specific to disease state in their current manuscript, but this is not rigorously tested. A formal statistical test comparing cluster membership distributions across disease vs. healthy controls is needed. b. Additionally, reporting effect sizes and confidence intervals would strengthen the inferences. 4. Lack of Integration with Clinical Data a. Their study would benefit from correlating clusters or clonality features with available clinical parameters (e.g., disease stage, treatment status), if accessible. 5. Multiple Testing Correction a. No indication is given that corrections for multiple hypothesis testing were applied, despite numerous comparisons. This should be addressed in their next round. ********** 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 |
|
Machine learning reveals distinct T-cell receptor clusters in plasma cell dyscrasias compared to healthy controls PONE-D-25-19122R2 Dear Dr. Coffey, 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, Jian Wu, M.D, Ph.D Academic Editor PLOS ONE Additional Editor Comments (optional): The author addressed all the comments and the manuscript was much improved. Reviewers' comments: Reviewer's Responses to Questions Comments to the Author Reviewer #2: All comments have been addressed Reviewer #3: All comments have been addressed ********** 2. Is the manuscript technically sound, and do the data support the conclusions??> Reviewer #2: Yes Reviewer #3: Yes ********** 3. Has the statistical analysis been performed appropriately and rigorously? -->?> 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 #2: Yes Reviewer #3: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English??> Reviewer #2: Yes Reviewer #3: Yes ********** Reviewer #2: The authors have fully addressed all prior reviewer concerns. The revised manuscript is clear, rigorous, and reproducible, with well-presented figures and transparent methodology. I find no outstanding issues. So, I recommend acceptance in its current form. Reviewer #3: All previous statistical concerns have been properly addressed by authors properly. No further questions. ********** 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 #2: No Reviewer #3: No ********** |
| Formally Accepted |
|
PONE-D-25-19122R2 PLOS ONE Dear Dr. Coffey, 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. Jian Wu 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 .