All reviews of published articles are made public. This includes manuscript files, peer review comments, author rebuttals and revised materials. Note: This was optional for articles submitted before 13 February 2023.
Peer reviewers are encouraged (but not required) to provide their names to the authors when submitting their peer review. If they agree to provide their name, then their personal profile page will reflect a public acknowledgment that they performed a review (even if the article is rejected). If the article is accepted, then reviewers who provided their name will be associated with the article itself.
The reviewers are satisfied with your corrections,
No comment.
No comment.
No comment.
The revised article, as well as the authors' comments, satisfactorily address my concerns from the first review.
The authors have addressed all the reviewers' comments in the revised manuscript.
The authors have addressed all the reviewers' comments in the revised manuscript.
The authors have addressed all the reviewers' comments in the revised manuscript.
The authors have addressed all the reviewers' comments in the revised manuscript.
The two reviewers have made some valid comments and raised a few issues that require your attention. Consequently, I would invite you to revise the paper taking into account their observations.
No comment (see reviewed PDF).
No comment (see reviewed PDF).
No comment (see reviewed PDF).
The paper is well-organized, and the use of the English language is generally good.
In line 84, the authors state that “this is the first prototype workable scheme to address how LaTeX could be used as an input language to perform mathematical programming modeling.” This statement is not necessarily true. I encourage the authors to take a closer look at MOSAICmodeling (www.mosaic-modeling.de), which is a modeling and optimization framework based on a LaTeX-style syntax for inputting algebraic and differential equations. A comparison between MOSAICmodeling and the proposed framework would be helpful in terms of evaluating the advantages of this contribution.
In lines 92-97, 22 references are listed with no further details, which is not very useful for the reader. Also, this seems to be a fairly biased list, with contributions mostly from the process systems engineering (PSE) community and many papers co-authored by the authors of this work. I recommend selecting a more representative set of papers from a wider range of fields, considering that the topic addressed here is of interest to more than just the PSE community.
The proposed approach is sound and it makes natural sense to divide the work process of the parser into three parts: objective function, constraints, and variables. However, I have some questions that I hope the authors could answer in their response or address in the revised manuscript:
1. The authors state that the parser can handle Greek letters. How about variables that consist of a Greek and a Latin letter, e.g. \Delta t?
2. How does the parser handle superscripts? Does the parser differentiate between superscripts and exponents?
3. In the literature, summations are often defined over sets instead of explicit conditions, e.g. \sum\limits_{i \in K} with K being a subset of the full-cardinality set I. Can the parser handle this case?
4. Looking at the example in line 347, it seems to be possible to use subsets for constraint generation. How are these subsets defined as these definitions usually do not explicitly appear in the LaTeX formulation of an optimization model? Is this information possibly directly extracted from the .dat file?
The validity of the proposed approach is nicely demonstrated in an illustrative example. However, some information on the platform’s ability to detect errors in the LaTeX formulation would be useful. For example, in the illustrative parsing example, what happens if in one of the constraints, the user forgot to write one of the two indices of the variable x?
Moreover, I personally would welcome a discussion on the challenges of extending this platform to the nonlinear case.
All text and materials provided via this peer-review history page are made available under a Creative Commons Attribution License, which permits unrestricted use, distribution, and reproduction in any medium, provided the original author and source are credited.