From Cornell University Computational Optimization Open Textbook - Optimization Wiki
Jump to navigation
Jump to search
- Theory, methodology, and/or algorithmic discussions
- The Lagrangian variables associated with equality constraints h(x) are unbounded but the Lagrangian dual problem states them as non-negative. Please fix the same.
- At least one numerical example
- Please update the dual objective function and domain of dual variables accordingly.
- An introduction of the topic
- Place references after the period at the end of each sentence. This goes for all the sections in the wiki.
- Theory, methodology, and/or algorithmic discussions
- The inline notations (`x1`, `s1`) should also be typed using LaTex.
- Theory, methodology, and/or algorithmic discussions
- Rephrase “Cut the relevant information and conditions in the portfolio optimization, as well as the final requirements into the relevant variables, constraints and linear functions of the linear programming problem.”
- At least one numerical example
- Fix misspelling “dolling decision variables”.
- Need some commas here (second sentence hard to read).
- Remove white space between end of sentences and reference numbers.
- Theory, methodology, and/or algorithmic discussions
- Some normal text was expressed as equation.
- Theory, methodology, and/or algorithmic discussions
- Acquisition function figure could be made larger and clearer to improve readability.
- References should be properly formatted, not just hyperlinks. Refer to the link below for an example: https://optimization.cbe.cornell.edu/index.php?title=Quantum_computing_for_optimization (#2 is still incorrectly formatt
- Theory, methodology, and/or algorithmic discussions
- All equations need to be better formatted.
- Please properly format pseudocode.
- Consider adding future research directions
- Theory, methodology, and/or algorithmic discussions
- Avoid inserting inline citations after words like “This article..” as it is a bit informal. This could be rephrased or changed to something like “According to author,^[2] …” with author name inserted.
- An introduction of the topic:
- Please consider correcting a few grammatical errors: “Optimal path”, “cross country”, missing period at end of first paragraph, other random capitalizations, etc.
- There are no citations in the introduction. Please cite every source.
- Theory, methodology, and/or algorithmic discussions
- Please add the mathematical description of the algorithm. (Insufficient)
- Please fix grammatical and spelling errors as (“from current position to the goal”, “There are a lot of discussions”, etc). Also, many hyphens are missing as “non playable”.
- At least one numerical example
- The numerical example does not show the full computations the algorithm performs. Please show the computation on a smaller example.
- Theory, methodology, and/or algorithmic discussions
- Since this Wiki focuses on jobshop scheduling, at least two methods are expected. Branch and bound is a general MILP technique, so, it is recommended to add a tailored technique that can only solve specific jobshop scheduling problems. Solving the numerical example with this technique is not necessary.
- Theory, methodology, and/or algorithmic discussions
- Add a mathematical description of the problem and a pseudocode/flowchart for the Lemke-Howson algorithm.
- Rephrase “This algorithm utilizes iterated pivoting much like the simplex algorithm used in the simplex algorithm used in linear programming”.
- Formatting (incomplete).
- Incorrect reference style.
- An introduction of the topic
- Avoid pronouns such as “we”. This goes for all other sections as well.
- Theory, methodology, and/or algorithmic discussions
- Organization of ideas in this section needs work.
- Please format the algorithm in proper algorithmic pseudocode format.
- Theory, methodology, and/or algorithmic discussions
- “Minimize” and “subject to” should be “min” and “s.t.” in MathType (inconsistent formatting)
- At least one numerical example
- Fix typo “while minimize” to “while minimizing”.
- Theory, methodology, and/or algorithmic discussions
- Avoid pronouns such as “we” (all sections).
- At least one numerical example
- A numerical example is simply "numerical" and does not need any application context (similar to those numerical problems in HW assignments). There is an Application section where you discuss the applications.
- These variables should be defined before the conclusion section, they are out of place here.
- Include hyperlinks to references if possible.
- Theory, methodology, and/or algorithmic discussions
- Need discussion about the concept of “central path” and the notion of self concordance
- Please consider proper formatting of the algorithm as pseudocode. Algorithms also must be accompanied with high level summary and discussion on its most important high level ideas.
- Fix typo “optimisation”.
- Theory, methodology, and/or algorithmic discussions
- References are not linked or expressed correctly. Please consider having the references as this Wiki template, https://optimization.cbe.cornell.edu/index.php?title=Quantum_computing_for_optimization
- At least one numerical example
- Please add a few sentences to show the transition from problem to solution.
- The solution technique should be clearly presented, and solved "step-by-step".
- Please follow the standard reference style - the current format is incorrect.
- At least one numerical example
- Please show a step-by-step solution in the example. The solution is incomplete. The Numerical Example section needs a "step-by-step" calculation process and a clear presentation of each step's results. (again, similar to the way of solving an HW problem).
- This example does not follow the MINLP structure discussed in the above section since binary variables are missing. Branch and bound may not be appropriate for such problems. Please provide an appropriate numerical example and solve it according to the above comments.
- Too few references overall, you should aggregate information from multiple sources. A quick Google scholar search could provide relevant references.
- Please follow the standard reference style - the current format is incorrect