Peer Review History
| Original SubmissionSeptember 5, 2025 |
|---|
|
PONE-D-25-48123Double-Pooling Optimization of Ride-hailing Orders Based on ST-GNN and Path OptimizationPLOS ONE Dear Dr. Xing, 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 Nov 07 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. 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: 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, Guangyin Jin Academic Editor PLOS ONE Journal Requirements: When submitting your revision, we need you to address these additional requirements. 1. Please ensure that your manuscript meets PLOS ONE's style requirements, including those for file naming. The PLOS ONE style templates can be found at https://journals.plos.org/plosone/s/file?id=wjVg/PLOSOne_formatting_sample_main_body.pdf and 2. Please note that PLOS One has specific guidelines on code sharing for submissions in which author-generated code underpins the findings in the manuscript. In these cases, we expect all author-generated code to be made available without restrictions upon publication of the work. Please review our guidelines at https://journals.plos.org/plosone/s/materials-and-software-sharing#loc-sharing-code and ensure that your code is shared in a way that follows best practice and facilitates reproducibility and reuse. 3. We note you have included a table to which you do not refer in the text of your manuscript. Please ensure that you refer to Tables 1, 2 and 3 in your text; if accepted, production will need this reference to link the reader to the Table. 4. Thank you for stating the following financial disclosure: “This work was supported by the Industrialization Cultivation Project of the Jilin Provincial Department of Education [Grant Number JJKH20230306CY].” Please state what role the funders took in the study. If the funders had no role, please state: "The funders had no role in study design, data collection and analysis, decision to publish, or preparation of the manuscript." If this statement is not correct you must amend it as needed. Please include this amended Role of Funder statement in your cover letter; we will change the online submission form on your behalf. 5. Please note that your Data Availability Statement is currently missing direct link to access each database. If your manuscript is accepted for publication, you will be asked to provide these details on a very short timeline. We therefore suggest that you provide this information now, though we will not hold up the peer review process if you are unable. 6. 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? 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: Partly ********** 2. Has the statistical analysis been performed appropriately and rigorously? Reviewer #1: Yes Reviewer #2: No ********** 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: 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: 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: 1.The core of the paper lies in how the ST-GNN embedding modifies edge weights before entering the “modified Dijkstra” module, but the manuscript lacks an explicit mathematical definition and pseudocode. Please provide an edge-weight mapping of the form we∗(t)=α westatic+γ f(zt,ae,…)w_e^{*}(t)=\alpha\,w^{\text{static}}_e+\gamma\,f(\mathbf{z}_t,\mathbf{a}_e,\ldots)we∗(t)=αwestatic+γf(zt,ae,…), list all learnable parameters, describe normalization/stabilization procedures, and include complete online inference pseudocode with time complexity O(⋅)O(\cdot)O(⋅). 2.The training objective is only described vaguely (“use spatio-temporal embeddings to estimate pairing probability; minimize the deviation between predicted detour rate and the historical optimal path”), but the “historical optimal path” is not defined. Please formalize how labels are generated and how the loss is constructed: Is the historical optimal path a static shortest path, a shortest travel-time path under historical median speeds, and does it incorporate signals/congestion factors? 3.In Table 1 you compare “ST-GNN + Floyd/A*/modified Dijkstra.” If these methods use different edge weights (i.e., not the same dynamic cost definition), the comparison is not fair. Please standardize and disclose the cost function, tuning protocol, and stopping criteria across all solvers. 4. The manuscript states that features are built from the entire November 2016 data, while testing uses Nov 28–30 (5,460 trips). If ST-GNN training also uses dynamics from those test days, you must demonstrate there is no information leakage (e.g., a strict left-closed/right-open rolling window; no use of future traffic states). Please specify train/validation/test temporal splits, spatial partitioning, and any cross-validation strategy. 5. The unit carbon factor is fixed at β=0.2 kg/km\beta=0.2\ \text{kg/km}β=0.2 kg/km, which ignores the effect of speed/idling/congestion on CO₂. I suggest: a) Cite authoritative emission factors or define a speed-dependent β(v)\beta(v)β(v), and provide a sensitivity analysis; b) In the case study, demonstrate the robustness of the chosen optimal path when β\betaβ varies. 6. In the ADR formula the denominator M×2M\times 2M×2 implicitly assumes “two orders per pair,” yet MMM is used to indicate both “number of pairs” and “number of samples,” which is confusing. Please unify the notation as PPP pairs and 2P2P2P orders, and provide a worked example. 7. Replace “Tyson polygon” with “Thiessen (Voronoi) polygons”, and on first use provide the mathematical definition and construction details (adjacency rule, prohibition of edge crossing). 8. Terminology unification: choose a single term among carpooling / ride-pooling / ride-sharing; in the title, standardize “Double-Pooling/dual-pool/two-order pooling” to “two-passenger ride-pooling.” 9. Units and formatting: use kg CO2_22 (with a space before the unit). In Table 1, use the column header “Average carbon emission reduction per order (kg CO2_22)”. 10. Maps/route figures: add a scale bar, north arrow, and basemap attribution; for Figs. 8/9, annotate time windows and constraint feasibility. 11. Tone and references: remove promotional language and replace with verifiable statements; ensure journal titles and publication years are formatted and reported consistently. Reviewer #2: This paper proposes a dual-optimization approach for ride-sharing order matching that combines a spatio-temporal graph neural network (ST-GNN) with an improved Dijkstra algorithm. The authors use Tyson polygons for spatial division of Chengdu's urban area and apply multi-head graph attention networks with Transformer encoders to capture spatio-temporal dependencies. Testing on Didi order data from November 2016, the method achieves an 86.6% matching success rate with 0.34kg CO2 reduction per order. While the integration of graph neural networks with ride-sharing optimization presents an interesting direction, several fundamental issues need addressing before this work can make a solid contribution to the field. 1. The ST-GNN architecture description lacks mathematical formulation and technical depth. Section 3's "The ST-GNN model framework" provides only high-level descriptions without explaining the specific layer configurations, loss functions, or training procedures. For instance, how exactly does the "gated mechanism" in Step 6 balance spatial and temporal features? What objective function guides the model training? The paper mentions generating a "128-dimensional spatio-temporal embedding vector" but never explains how this dimensionality was chosen or validated. This vagueness makes the work difficult to reproduce or properly evaluate. 2. The comparison is limited to combining ST-GNN with only three path-finding algorithms (Floyd, A*, modified Dijkstra), which doesn't demonstrate the ST-GNN's actual contribution versus traditional ride-sharing methods. Where are comparisons with established ride-sharing algorithms like those by Alonso-Mora et al. (2017) on dynamic vehicle routing, or Ma et al. (2013) on T-Share? The authors cite several ride-sharing papers in the introduction but never compare against them experimentally. Additionally, testing on only 5,460 orders from three days is insufficient to validate a method intended for large-scale deployment. 3. Table 1's results lack any statistical significance testing, confidence intervals, or standard deviations across multiple runs. Did the authors perform cross-validation? How sensitive are results to different data splits or time periods? The claimed improvements (86.6% vs 85.1% matching rate) could easily fall within statistical noise. Without proper statistical analysis, readers cannot assess whether the reported improvements are meaningful or merely random variations. 4. The paper provides no discussion of computational complexity or scalability. What are the time and space complexities of the proposed approach? How does runtime scale with the number of orders, graph nodes, or time windows? For a real-time ride-sharing system, these considerations are crucial. The authors mention "ensuring computational efficiency" but provide no actual runtime measurements or complexity analysis. 5. The abstract is overly dense with technical details while the introduction fails to clearly position the work within existing literature. Section 2 jumps between problem definition and methodology without clear transitions. The conclusion merely restates results without discussing limitations or future work. Consider restructuring to follow a clearer narrative: problem → existing solutions → gaps → proposed method → validation. 6. Figures 4-6 showing clustering and Tyson polygons lack scale bars and proper legends. Figure 1's system architecture diagram uses vague terms like "Feature fusion layer" without explaining what features are being fused or how. Figure 8 and 9 comparing independent versus pooled paths need clearer visualization - perhaps showing the actual routes on a map rather than abstract node connections. 7. Why use Tyson polygons over grid-based or administrative boundary divisions? The authors claim Tyson polygons better represent "real demand distribution" but provide no comparative analysis. Similarly, the choice of 30-minute time windows, 500-meter clustering radius, and other parameters appears arbitrary without sensitivity analysis or justification. 8. The carbon reduction calculation uses a simple linear factor (β = 0.2kg/km) without considering vehicle types, traffic conditions, or actual emission patterns. Real-world emissions vary significantly based on speed, acceleration patterns, and vehicle occupancy. This oversimplification undermines the environmental claims. 9. The manuscript contains numerous grammatical errors and awkward phrases. Examples include "Through spatio-temporal perception modeling" (missing subject), "AmAP POI data" (likely meant "Amap"), and inconsistent terminology (sometimes "carpool," sometimes "carpooling," sometimes "ridesharing"). These issues detract from the technical content and suggest insufficient proofreading. 10. The paper lacks crucial details for reproducibility. What framework was used for the GNN implementation? How were hyperparameters selected? What hardware was used for experiments? The GitHub repository or code availability is not mentioned, making it impossible to verify results or build upon this work. ********** 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: No Reviewer #2: No ********** [NOTE: If reviewer comments were submitted as an attachment file, they will be attached to this email and accessible via the submission site. Please log into your account, locate the manuscript record, and check for the action link "View Attachments". If this link does not appear, there are no attachment files.] While revising your submission, please upload your figure files to the Preflight Analysis and Conversion Engine (PACE) digital diagnostic tool, https://pacev2.apexcovantage.com/. PACE helps ensure that figures meet PLOS requirements. To use PACE, you must first register as a user. Registration is free. Then, login and navigate to the UPLOAD tab, where you will find detailed instructions on how to use the tool. If you encounter any issues or have any questions when using PACE, please email PLOS at figures@plos.org. Please note that Supporting Information files do not need this step. |
| Revision 1 |
|
Optimization of Two-Passenger Ride-Pooling Orders Based on ST-GNN and Path Optimization PONE-D-25-48123R1 Dear Dr. Xing, 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, Guangyin Jin Academic Editor PLOS ONE Additional Editor Comments (optional): 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: 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 ********** 3. Has the statistical analysis been performed appropriately and rigorously? Reviewer #1: (No Response) Reviewer #2: 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 ********** 5. Is the manuscript presented in an intelligible fashion and written in standard English? PLOS ONE does not copyedit accepted manuscripts, so the language in submitted articles must be clear, correct, and unambiguous. Any typographical or grammatical errors should be corrected at revision, so please note any specific errors here. Reviewer #1: Yes Reviewer #2: Yes ********** 6. Review Comments to the Author Please use the space provided to explain your answers to the questions above. 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: No other concerns. Reviewer #2: This manuscript proposes a dual-optimization framework for two-passenger ride-pooling. The authors construct a demand-adaptive urban graph using Voronoi polygons and employ a spatio-temporal GNN (ST-GNN) to learn embeddings. These embeddings inform both order matching and a multi-objective path optimization algorithm. Validated on a real-world dataset, the method demonstrates strong performance in matching success, detour reduction, and carbon savings, offering a practical solution for shared mobility. The authors have done a commendable job of addressing the previous round of feedback, and the manuscript is significantly stronger as a result. The additions clarifying the methodology, such as the explicit edge weight formulation (Eq. 1), the loss function (Eq. 5), and the data splitting strategy, have greatly improved the paper's rigor. I have just a couple of minor suggestions for final polishing. 1. I was pleased to see the addition of the "Limitations and Future Work" section, which properly addresses the fixed carbon emission factor. The authors are correct that this is a common simplification. As they move forward with this research, I would suggest they consider not just a speed-dependent factor, but also factors related to vehicle acceleration and idling, which are significant contributors to emissions in congested urban environments. This would be a strong next step for refining the environmental optimization aspect. 2. The enhanced description of the ST-GNN model framework is much clearer. I noted the use of Transformer encoder layers for temporal modeling. While the paper mentions this captures "long-range dependencies," a brief justification for this choice over more traditional recurrent architectures (like LSTMs or GRUs) would be beneficial, perhaps just a sentence in the methodology section. It is not a major issue, as the results stand, but it would help readers understand the design choice, especially given that recurrent networks are also common in this domain. ********** 7. PLOS authors have the option to publish the peer review history of their article (what does this mean?). If published, this will include your full peer review and any attached files. If you choose “no”, your identity will remain anonymous but your review may still be made public. Do you want your identity to be public for this peer review? For information about this choice, including consent withdrawal, please see our Privacy Policy. Reviewer #1: No Reviewer #2: No ********** |
| Formally Accepted |
|
PONE-D-25-48123R1 PLOS ONE Dear Dr. Xing, 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. Guangyin Jin 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 .