Peer Review History
| Original SubmissionApril 20, 2021 |
|---|
|
PONE-D-21-13064 Genetic divergence in microsatellites but not in mtDNA in sympatric populations of the marbled crab, <pachygrapsus marmoratus=""> (Fabricius, 1787) along the Turkish seas PLOS ONE Dear Dr. Çetin, 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.</pachygrapsus> The study represent interesting populations across a special setting. There are numerous weaknesses with the paper. The presentation of results should be improved, questions made more clear, the specific results interpreted in context of the question and the analyses need to be improved (added in some case). In some cases they have to be reinterpreted or better described. The six main points are the following, but the three reviewers also give many extra points for corrections and adjustments.
Please submit your revised manuscript by Aug 13 2021 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org. When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file. Please include the following items when submitting your revised manuscript:
If you would like to make changes to your financial disclosure, please include your updated statement in your cover letter. Guidelines for resubmitting your figure files are available below the reviewer comments at the end of this letter. If applicable, we recommend that you deposit your laboratory protocols in protocols.io to enhance the reproducibility of your results. Protocols.io assigns your protocol its own identifier (DOI) so that it can be cited independently in the future. For instructions see: http://journals.plos.org/plosone/s/submission-guidelines#loc-laboratory-protocols. Additionally, PLOS ONE offers an option for publishing peer-reviewed Lab Protocol articles, which describe protocols hosted on protocols.io. Read more information on sharing protocols at https://plos.org/protocols?utm_medium=editorial-email&utm_source=authorletters&utm_campaign=protocols. We look forward to receiving your revised manuscript. Kind regards, Arnar Palsson, Ph.D. Academic Editor PLOS ONE Additional Editor Comments: The study represent interesting populations across a special setting. There are numerous weaknesses with the paper. The presentation of results should be improved, questions made more clear, the specific results interpreted in context of the question and the analyses need to be improved (added in some case). In some cases they have to be reinterpreted or better described. The six main points are the following, but the three reviewers also give many extra points for corrections and adjustments. 1. The frequency of mt haplogroups differs by areas, 2. I would argue that the authors should show that there are no signals in higher significant K´s. 3. Present the cytonuclear pattern (microsatellite cluster - mtDNA haplotype combination) to gain further insight into the patterns of admixture in the TSS. 4. Perform isolation with migration (IMA) analyses to test mitochondrial gene flow between clusters 5. Get a native English speaker to help with language, either an academic or certified English copy-editor. 6. Supplementary figures and tables, add titles and more detailed legends and descriptions. 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. In your Methods section, please provide additional information regarding the permits you obtained for the work. Please ensure you have included the full name of the authority that approved the field site access and, if no permits were required, a brief statement explaining why. 3. In your Data Availability statement, you have not specified where the minimal data set underlying the results described in your manuscript can be found. PLOS defines a study's minimal data set as the underlying data used to reach the conclusions drawn in the manuscript and any additional data required to replicate the reported study findings in their entirety. All PLOS journals require that the minimal data set be made fully available. For more information about our data policy, please see http://journals.plos.org/plosone/s/data-availability. Upon re-submitting your revised manuscript, please upload your study’s minimal underlying data set as either Supporting Information files or to a stable, public repository and include the relevant URLs, DOIs, or accession numbers within your revised cover letter. For a list of acceptable repositories, please see http://journals.plos.org/plosone/s/data-availability#loc-recommended-repositories. Any potentially identifying patient information must be fully anonymized. Important: If there are ethical or legal restrictions to sharing your data publicly, please explain these restrictions in detail. Please see our guidelines for more information on what we consider unacceptable restrictions to publicly sharing data: http://journals.plos.org/plosone/s/data-availability#loc-unacceptable-data-access-restrictions. Note that it is not acceptable for the authors to be the sole named individuals responsible for ensuring data access. We will update your Data Availability statement to reflect the information you provide in your cover letter. 4. We note that Figures 1 and 2 in your submission contain map images which may be copyrighted. All PLOS content is published under the Creative Commons Attribution License (CC BY 4.0), which means that the manuscript, images, and Supporting Information files will be freely available online, and any third party is permitted to access, download, copy, distribute, and use these materials in any way, even commercially, with proper attribution. For these reasons, we cannot publish previously copyrighted maps or satellite images created using proprietary data, such as Google software (Google Maps, Street View, and Earth). For more information, see our copyright guidelines: http://journals.plos.org/plosone/s/licenses-and-copyright. We require you to either (1) present written permission from the copyright holder to publish these figures specifically under the CC BY 4.0 license, or (2) remove the figures from your submission:
We recommend that you contact the original copyright holder with the Content Permission Form (http://journals.plos.org/plosone/s/file?id=7c09/content-permission-form.pdf) and the following text: “I request permission for the open-access journal PLOS ONE to publish XXX under the Creative Commons Attribution License (CCAL) CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). Please be aware that this license allows unrestricted use and distribution, even commercially, by third parties. Please reply and provide explicit written permission to publish XXX under a CC BY license and complete the attached form.” Please upload the completed Content Permission Form or other proof of granted permissions as an "Other" file with your submission. In the figure caption of the copyrighted figure, please include the following text: “Reprinted from [ref] under a CC BY license, with permission from [name of publisher], original copyright [original copyright year].”
The following resources for replacing copyrighted map figures may be helpful: USGS National Map Viewer (public domain): http://viewer.nationalmap.gov/viewer/ The Gateway to Astronaut Photography of Earth (public domain): http://eol.jsc.nasa.gov/sseop/clickmap/ Maps at the CIA (public domain): https://www.cia.gov/library/publications/the-world-factbook/index.html and https://www.cia.gov/library/publications/cia-maps-publications/index.html NASA Earth Observatory (public domain): http://earthobservatory.nasa.gov/ Landsat: http://landsat.visibleearth.nasa.gov/ USGS EROS (Earth Resources Observatory and Science (EROS) Center) (public domain): http://eros.usgs.gov/# Natural Earth (public domain): http://www.naturalearthdata.com/ 5. Please include captions for ALL 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? The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented. Reviewer #1: Partly Reviewer #2: Partly Reviewer #3: Partly ********** 2. Has the statistical analysis been performed appropriately and rigorously? Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: Yes ********** 3. Have the authors made all data underlying the findings in their manuscript fully available? The PLOS Data policy requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified. Reviewer #1: Yes Reviewer #2: No Reviewer #3: Yes ********** 4. Is the manuscript presented in an intelligible fashion and written in standard English? PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here. Reviewer #1: Yes Reviewer #2: No Reviewer #3: Yes ********** 5. Review Comments to the Author Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters) Reviewer #1: Comments PLOS ONE The authors analyze microsatellite and mtDNA data from the marbled crab in the Turkeys, Black and Mediterranean Sea. The analysis are restricted to 5 microsatellites and the CO1 region of the mitochondrial DNA. The authors find a genetic difference between the Black and Turkeys Sea on one side and the Mediterranean Sea on the other when looking at the microsatellite data, but not when analyzing the mtDNA data. Overall, I find this study quite interesting, and a presumable need for further knowledge about the crab. It would have been nice to see more independent markers, but I also realize you sometimes work with what you have. But it would be nice to see some SNP data for these crabs in the future. I am not sure to what extend I agree about the overall conclusion of the paper. The author states there is no genetic divergence in the mtDNA across the analyzed range, but there is in the microsatellites. I agree that there is in the microsatellites, and as stated in my comments I believe there is more than the authors present. I however, don’t agree that there is no difference over the range in the mtDNA: looking at the network, it is true that the Black Sea and TSS, not alone posses a haplotype/group. However it is clear that the frequency of haplogroups per area is not the same, and also that some areas don’t have specific haplotypes (e.g. is H4 and H5, with there surrounding haplotypes not present in TSS and the Black Sea). I think this is one point the authors need to consider, and of course if they disagree, I feel a stronger argumentation is warranted in the manuscript. I have tried to add comments in an orderly fashion: 1) The title is very descriptive, but doesn’t sound all that good. 2) Paragraph from 64 to 72 doesn’t read very well. 3) Figure 1. It would be good to mark TSS on this figure. It is nicely done on Figure 2 (same thing could be done in figure 1). I expect that the quality will be better with the final submission. 4) Line 111-113. I to some degree concur with the idea of using markers with higher mutation rate, however, suggesting to use microsatellites is less useful than going directly to more markers, e.g. whole genome shotgun sequencing. 5) Line 125. There is a space missing behind reference number 42. I think there is something missing at the end of that sentence. And the “n” before “populations” is probably a mistake. 6) Line 125-127. It is unclear to me how this is different from what you write in the sentence before? If you mean it can influence the genetic structure towards more differentiation, it would be good to spell out, as it is not clear. 7) Line 133. You don’t end the parentheses starting before “587”. 8) Line 134. When you refer to figure 1 here it would be helpful to include the names of these places on the map. 9) Line 135. There is something weird with the beginning of this line. If PLOS ONE allows I would write “XX et al (37) found”. 10) Line 136-137. For this point to hold, I think you should add in line 132-134 what genomic data was used. I presume it was CO1. 11) Line 140. Perhaps there is a better phrasing than “chaotic genetic patchiness”. 12) Line 154. I guess “A1”, is the first supplementary table, but this should be clearer. Also, it would be nice to do a count, so it’s obvious that there are 32 locations. There is also one point to many after A1. 13) Line 169. You may want to add one line about how they did fragment sizing at Cornell. 14) Line 174-177. You risk introducing a Wahlund effect by mixing potential populations, so an argument for this not happening would be merited somewhere. At the same time, I don’t see anything in the STRUCTURE plot supporting pooling samples in the way you are doing. I do however understand the necessity, I just don’t think that structure supports doing it. 15) Line 192-194. I am not a fan of choosing an optimal K in structure/admixture analysis, as all significant K’s are saying something about the data, and thus you are leaving out potential information. If the authors have not seen it, I would suggest the paper “A tutorial on how not to over-interpret STRUCTURE and ADMIXTURE bar plots”, written by one of the people who have done large amount of work on STRUCTURE (Daniel Falush). As a minimum I would argue that the authors should show that there are no signals in higher significant K´s. 16) Line 210-213. You don’t show the graph? 17) Line 237-238. Looks like you swapped the two last accession numbers? 18) Line 238. It is a little misleading to present it as 926 individuals, as you are effectively only adding 74 sequences – unless you are adding haplotypes multiple times so you are analyzing a total of 926 sequences? I would keep the part that with the 74 CO1 coming from 610, but write it came to a total of 390 individuals or individual sequences, or something along those lines. 19) Line 240. Think there is a point missing after “(70)”. 20) Line 241. You don’t close the parentheses before “e.g. (27)”. 21) Line 253. Sounds like you know that there will be signs of expansion. You could write “to detect potential population explansion” 22) Line 260. Do you mean the 20 populations that you pool the locations into, and what is the subpopulations here? 23) Line 268. Comma after “(S3 Table)” should be moved back one, and then a space. 24) Paragraph starting on line 271. Firstly, see my point 16. Secondly, I would also argue that there are clearly more signals in the PCoA than just two clusters. It is very clear that other samples are also clustering. I think marking more specifically the 20 “populations” is needed here. However, some indication of the 2 major clusters could be nice to keep. 25) Line 281. It is not clear what Table A1 is? 26) Line 282. Can I see from S2 Table that cluster C is fixed for Pm108? I thought S2 was showing proportion of null alleles? 27) Line 283-285. The S1 and S2 Tables I have show nothing about He. I don’t see the He values anywhere, these should be added. 28) Line 288. See my comments else where regarding the STRUCTURE inference. However, I still argue that you need to prove there is no significant meaningful higher structure. 29) Line 295. Again, see my comment about the PCoA elsewhere. But I will again argue you need to add information about all 20 “populations”. 30) Line 305 and other places. It is a bit confusing referring to the SoM and Dardanelles when they are not market on any map, nor in S1 Table. 31) Table 1. Could it be that those low values are due to population mixing (when you go from 32 sampling sites to 20 populations). I realize that the values above the diagonal is ΦST , however you don’t state it. 32) Line 318. As the AMOVA test show more variation within groups than between groups I think this again indicates that more exploration of STRUCTURE and the PCoA is needed. 33) Table 2, 3, 5 and 6, please expand the legend to tell what SS is. 34) Line 337-338. As previous, is it actually 926 sequences you analyzed? 35) Line 356. Are the samples obtain from three different sources? It sounds like that, from your sampling, from Kalken, and then some extra Genebank sequences? 36) Figure 5. It would be good if you could add differences between haplotypes to the figure. 37) Line 361-362. It would be good to add to the table which populations are from the Mediterranean, Black Sea and so fourth. 38) Line 362. It is minor, but is that actually low compared to the length of the analyzed sequence? 39) Line 371. Again, it would be beneficial to add to table 4 which subpopulations are from TSS. 40) Table 4. It doesn’t seem consistent to me what the pop code, population and subpopulation is referring to? 41) Line 385-389. It seems that mtDNA is supporting better 3 clusters than just 2. I’m fine with you comparing them as 20 groups, but from the STRUCTURE plot they are obviously not genetic populations. So you should be careful with the term populations. 42) Line 396. Missing space after the parentheses. 43) Line 398. I don´t see S1 table showing anything about haplotypes? 44) Line 432. It is very hard to follow the location names, when some are not added to the map. 45) Line 440-442. I’m not sure what you are trying to say with this sentence, so if you could clear up what the point is, that would be helpful. 46) Line 444-445. This is very speculative, and not possible to say with this data. I think it’s fine to keep, as it is interesting, but it should at least be stated that you have no possibility of investigating that with this data. 47) Line 450. I’m still not convinced it is just 2 populations, and thus as suggested earlier, this should be analyzed further. 48) Line 453. What recent geneflow wouldn’t affect the microsatellites, but only the mtDNA? 49) Line 475. You need to shortly state what reference 47 was analyzing (species/markers), otherwise it’s hard to understand. 50) Line 521-525. “Been replaced” sounds weird. Rather something along the lines of “have become dominant, due to drift or selection”, or something like it. I don’t know what form the journal want, but you should look over the references as they are not consistent in how you write. E.g. “found by (47)” vs “Paterno et al. (10)”. Location 19 has a much higher proportion of green population than the locations closer to the TSS. How do you explain this if green is just flowing from the black sea, and should thus arguably become less and less dominant the further you go into the Mediterranean? Figure 5. If you can make the labels a bit bigger, it would be helpful to read the location names. The figure would benefit with differences between haplotypes/groups. Supplementary figure 1, I think is missing a legend. Reviewer #2: This study examined the population genetic structure of the marbled rock crab Pachygrapsus marmoratus, focusing on the Turkish Strait System between the Black Sea and the Mediterranean Sea. I think the topic in this study is interesting and important in the population genetics of coastal organisms. However, the manuscript is not well prepared, and thus extremely hard to read and/or understand tables, figures, and arguments proposed by the authors. This is because there are many flaws in the presentation of results, and datasets and analyses are insufficient to support the arguments. I think the English writing should be improved too. I left specific comments on the attached PDF directly. Reviewer #3: The study examined population genetic structure of the marbled rock crab Pachygrapsus marmoratus in the TSS, a transition zone between the Black Sea and Mediterranean Sea using mtDNA and microsatellite markers. Microsatellite data from 5 loci showed marked genetic differentiation with 2 genetic clusters exhibiting differential distribution between the Black Sea and the Mediterranean. Mitochondrial CoI sequences reveal the occurrence of 3 common haplotypes, which while exhibiting low sequence divergence values exhibit geographically different distributions broadly concordant with a genetic break between the Black Sea and the Mediterranean. While the topic is of broad interest to the fields of phylogeography and population genetics with particular attention to admixture zones, I have several comments/clarifications that need to be addressed before the paper is acceptable for publication. Major comments: - Sample information. Suggest to include the information on Basin (Table S1) in Figure 1 perhaps as part of the Figure caption, for easier reference. - l.247 Indicate reason for excluding individuals with STRUCTURE q<0.7 from pairwhise Phi-ST analysis? - l.304. Indicate overall Fst value and associated p-value (microsatellites) to support statement of significant differentiation among sampling sites - L.305. On the Dardanelles samples - indicate population number or code at the first instance for easy reference. The detail for the Dardanelle samples being population #10 was only mentioned later in line 370. - Table 1. For correction, the table caption indicates "nuclear genetic divergence", but it includes Phi-ST values from mitochondrial data - Table 1. Suggestions: (1) Indicate Basin or Group (Black Sea, TSS, Mediterannean etc...) on Table 1 for easier reference and (2) Might be more visually informative to make this into a heatmap (retaining the values for reference). - AMOVA. Table 2 and 3 can be combined in a single table. - l.350. H7 is not geographically restricted to the Black Sea, as it is found in the Mediterranean samples - On genetic structure, it is important to state first whether the mitochondrial data reveal significant genetic structure (Phi ST > 0), before presenting the AMOVA results. Also, what is the overall Phi-ST value and its associated p-value? - l.385. The same two hypothesis of geographic structure tested with microsatellites - AMOVA Tables 5 and 6 can be combined On comparison between microsatellite and mt CoI results: - On line 453, the authors report that microsatellites and mtDNA did not reflect the same degree of divergence in the Mediterranean. What does 'degree of divergence' mean? Are they referring to the Fst and Phi-st values? It will be difficult to compare divergence for different marker types. If anything, what is clear is that there is a broadly concordant pattern of geographic structure revealed by both markers. Marked genetic groups for the microsatellite data is clear (clusters M and C, with differential distributions across the sampled range). For the mtDNA data, yes the sequence divergence may be low (with closely related haplotypes separated by 1-2 bp only), however, their markedly different geographical distributions (H7 predominant in the Black Sea and TSS, H2 and H4 predominent in the Mediterranean and Atlantic) also give rise to a geographic break broadly consistent with the microsatellite data. This is also seen in the AMOVA for both markers (Tables 3, 4, 5 and 6). - I suggest that the authors present the cytonuclear pattern (microsatellite cluster - mtDNA haplotype combination) to gain further insight into the patterns of admixture in the TSS. To what extent do individuals with belonging to different microsatellite clusters share mitochondrial haplotypes? - Suggest to perform isolation with migration (IMA) analyses to test hypotheses regarding mitochondrial gene flow between microsatellite clusters. it might be possible to test hypotheses regarding directionality of mitochondrial gene flow, as well as infer whether there was gene flow after divergence (or none). Minor comments/corrections - l.70 North Sea-Baltic Sea - l.125 connectivity among n populations - l. 154. ... in A1. Do you mean S1 Table? - l.265 "didn't" replace with "did not" ********** 6. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files. If you choose “no”, your identity will remain anonymous but your review may still be made public. Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy. Reviewer #1: Yes: Charles Christian Riis Hansen 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 |
|
PONE-D-21-13064R1Mitonuclear genetic patterns of divergence in the marbled crab, <pachygrapsus marmoratus=""> (Fabricius, 1787) along the Turkish seas</pachygrapsus>PLOS ONE Dear Dr. Çetin, 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. The manuscript is greatly improved and the reviewers were generally pleased with the ammendments. Few minor things remain. Main points. 1. The higher sign in AMOVA with clusters derived from the data is ENTIRELY expected. the data is analyzed for structure, and then the data are analyzed with respect to that structure (circlular). I recommend you drop the Amova on clusters, and only keep the geographic regions and Sampling site anova up in the table. You can test in cross, variance in microsats within clusters defiend from mtDNA – and vice versa. 2. Rev 2 asked for Samova analyses. I say more analyses are not needed (unless you want to give it a go). But you should discuss that doing Samova might be interesting (also on more markers) and the K3-5 heterogeneity shown by the structure analyses, and that possible explanations for these results. Are these non-biological (technical), multiple ancestral populations that mixed, or ecomorphs within species,…etc 3. Check that all figures and tables including for the supplementary is refereed correctly as e.g., the S2 figure is not refereed to in the text. At the same time S1 Fig, S2 Table, and S3 Table was not included in the submission (rev 2). Minor points. New opening line of abstract is better, but the ending is a bit strange. Consider rewriting and switching verbs, “created” seems a bit off. “because secondary contact zones of post-glacial lineages can be created.” Line 84. Add reference “These transition zones are often regions where divergent lineages meet in secondary contact.” Please submit your revised manuscript by Mar 26 2022 11:59PM. If you will need more time than this to complete your revisions, please reply to this message or contact the journal office at plosone@plos.org. When you're ready to submit your revision, log on to https://www.editorialmanager.com/pone/ and select the 'Submissions Needing Revision' folder to locate your manuscript file. Please include the following items when submitting your revised manuscript:
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, Arnar Palsson, Ph.D. Academic Editor PLOS ONE Journal Requirements: 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. Additional Editor Comments: The manuscript is greatly improved and the reviewers were generally pleased with the ammendments. Few minor things remain. Main points. 1. The higher sign in AMOVA with clusters derived from the data is ENTIRELY expected. the data is analyzed for structure, and then the data are analyzed with respect to that structure (circlular). I recommend you drop the Amova on clusters, and only keep the geographic regions and Sampling site anova up in the table. You can test in cross, variance in microsats within clusters defiend from mtDNA – and vice versa. 2. Rev 2 asked for Samova analyses. I say more analyses are not needed (unless you want to give it a go). But you should discuss that doing Samova might be interesting (also on more markers) and the K3-5 heterogeneity shown by the structure analyses, and that possible explanations for these results. Are these non-biological (technical), multiple ancestral populations that mixed, or ecomorphs within species,…etc 3. Check that all figures and tables including for the supplementary is refereed correctly as e.g., the S2 figure is not refereed to in the text. At the same time S1 Fig, S2 Table, and S3 Table was not included in the submission (rev 2). Minor points. New opening line of abstract is better, but the ending is a bit strange. Consider rewriting and switching verbs, “created” seems a bit off. “because secondary contact zones of post-glacial lineages can be created.” Line 84. Add reference “These transition zones are often regions where divergent lineages meet in secondary contact.” [Note: HTML markup is below. Please do not edit.] Reviewers' comments: Reviewer's Responses to Questions Comments to the Author 1. If the authors have adequately addressed your comments raised in a previous round of review and you feel that this manuscript is now acceptable for publication, you may indicate that here to bypass the “Comments to the Author” section, enter your conflict of interest statement in the “Confidential to Editor” section, and submit your "Accept" recommendation. Reviewer #1: All comments have been addressed Reviewer #2: (No Response) Reviewer #3: All comments have been addressed ********** 2. Is the manuscript technically sound, and do the data support the conclusions? The manuscript must describe a technically sound piece of scientific research with data that supports the conclusions. Experiments must have been conducted rigorously, with appropriate controls, replication, and sample sizes. The conclusions must be drawn appropriately based on the data presented. 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 requires authors to make all data underlying the findings described in their manuscript fully available without restriction, with rare exception (please refer to the Data Availability Statement in the manuscript PDF file). The data should be provided as part of the manuscript or its supporting information, or deposited to a public repository. For example, in addition to summary statistics, the data points behind means, medians and variance measures should be available. If there are restrictions on publicly sharing data—e.g. participant privacy or use of data from a third party—those must be specified. Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: Yes ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English? PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here. Reviewer #1: Yes Reviewer #2: Yes Reviewer #3: Yes ********** 6. Review Comments to the Author Please use the space provided to explain your answers to the questions above. You may also include additional comments for the author, including concerns about dual publication, research ethics, or publication ethics. (Please upload your review as an attachment if it exceeds 20,000 characters) Reviewer #1: I’m happy with the amendments the authors have made and want to congratulate the authors on making it this far. As I’m happy with the amendments, I don’t have any more comments, except that the authors need to check that all figures and tables including for the supplementary is refereed correctly as e.g., the S2 figure is not refereed to in the text. At the same time S1 Fig, S2 Table, and S3 Table was not included in the submission. But even so I’m happy with the amendments. Reviewer #2: General I think the manuscript has been considerably improved and my major concerns have been mostly resolved. However, I still have one concern about the results of AMOVA. Major comments: Regarding comments by Reviewer 1 (32) and reply to my previous comment (45): I agree with Reviewer 1. The AMOVA results should be more carefully discussed. I think the AMOVA test showing more variation within groups than between groups implies that the grouping by geographical regions does not sufficiently represent population genetic structure. I therefore recommend you to conduct SAMOVA with sampling site data, not by regions or clusters C/M, since SAMOVA can detect the most plausible grouping by comparing FCT values of different K without information for grouping in advance. I do not agree with your opinion that "SAMOVA won't add anything new to our interpretation." Minor comments: Line 44. SoM is not obvious in Abstract. Please spell out it for the first appearance. Line 126. Mediterranean => the Mediterranean / Gbif => GBIF Line 142. ", [27]" => " [27], " Line 280–282. I think it is also important for Pm79 that numbers of 212 and 214 are almost same in red but 214 dominates in green. Line 494-496. Explaining the similarity of COI sequences by its slow mutation rate may contradict your discussion in Line 438-440 that mtDNA sorts faster. Reviewer #3: The authors have incorporated the comments and suggestions to the manuscript, with the exception of one suggested analysis (IMA), which they have provided justification for (results do not provide meaningful estimates of divergence time because of very wide variation). The manuscript is much improved incorporating all the other comments from the reviewers. ********** 7. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files. If you choose “no”, your identity will remain anonymous but your review may still be made public. Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy. Reviewer #1: Yes: Charles Christian Riis Hansen 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 |
|
Mitonuclear genetic patterns of divergence in the marbled crab, <pachygrapsus marmoratus=""> (Fabricius, 1787) along the Turkish seas PONE-D-21-13064R2</pachygrapsus> Dear Dr. Çetin, We’re pleased to inform you that your manuscript has been judged scientifically suitable for publication and will be formally accepted for publication once it meets all outstanding technical requirements. Within one week, you’ll receive an e-mail detailing the required amendments. When these have been addressed, you’ll receive a formal acceptance letter and your manuscript will be scheduled for publication. An invoice for payment will follow shortly after the formal acceptance. To ensure an efficient process, please log into Editorial Manager at http://www.editorialmanager.com/pone/, click the 'Update My Information' link at the top of the page, and double check that your user information is up-to-date. If you have any billing related questions, please contact our Author Billing department directly at authorbilling@plos.org. If your institution or institutions have a press office, please notify them about your upcoming paper to help maximize its impact. If they’ll be preparing press materials, please inform our press team as soon as possible -- no later than 48 hours after receiving the formal acceptance. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information, please contact onepress@plos.org. Kind regards, Arnar Palsson, Ph.D. Academic Editor PLOS ONE Additional Editor Comments (optional): Reviewers' comments: |
| Formally Accepted |
|
PONE-D-21-13064R2 Mitonuclear genetic patterns of divergence in the marbled crab, Pachygrapsus marmoratus (Fabricius, 1787) along the Turkish seas Dear Dr. Çetin: I'm pleased to inform you that your manuscript has been deemed suitable for publication in PLOS ONE. Congratulations! Your manuscript is now with our production department. If your institution or institutions have a press office, please let them know about your upcoming paper now to help maximize its impact. If they'll be preparing press materials, please inform our press team within the next 48 hours. Your manuscript will remain under strict press embargo until 2 pm Eastern Time on the date of publication. For more information please contact onepress@plos.org. If we can help with anything else, please email us at plosone@plos.org. Thank you for submitting your work to PLOS ONE and supporting open access. Kind regards, PLOS ONE Editorial Office Staff on behalf of Dr. Arnar Palsson 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 .