INFORMS Journal On Computing Skills

Use when the method choice, baselines, and computational-experiment design need alignment for an INFORMS Journal on Computing (IJOC) manuscript — before the experiments are run at scale. Designs a fair, reproducible experimental protocol; it does not write the algorithm proofs (see ijoc-theory-development).

Use when drafting the response to an INFORMS Journal on Computing (IJOC) decision letter — turning referee objections (especially about experiments and reproducibility) into a point-by-point response with re-run evidence. Builds the rebuttal and revision plan; it does not run new analysis on its own (route to ijoc-data-analysis).

Use when deciding which ijoc-* sub-skill to invoke next, or when sequencing a manuscript from idea through rebuttal for an INFORMS Journal on Computing (IJOC) submission. Routes — it does not replace — the specialized skills.

Use when running the final pre-submission preflight for an INFORMS Journal on Computing (IJOC) submission via ScholarOne — page limit, LaTeX template, single-blind rules, technical-area choice, and the GitHub code/data deposit. Final checks; it does not draft content.

Use when running and reporting the computational experiments — and assembling the reproducible code/data deposit — for an INFORMS Journal on Computing (IJOC) manuscript. Turns a designed protocol (see ijoc-methods) into defensible, reproducible results; it does not redesign the experiment.

Use when the prose, abstract, or introduction of an INFORMS Journal on Computing (IJOC) manuscript buries the computational advance or misreads the house voice. Makes the method land for an OR-meets-CS readership; it does not change the underlying results.

Use when calibrating expectations for the INFORMS Journal on Computing (IJOC) review cycle — the Area-Editor desk-reject gate, the undisclosed associate editor, single-blind reviewing, decision types, and whether a sibling journal fits better. Sets expectations and strategy; it does not draft the rebuttal (see ijoc-rebuttal).

Use when the computational exhibits — performance profiles, runtime-vs-size plots, and results tables — are dense, misleading, or do not answer the question for an INFORMS Journal on Computing (IJOC) manuscript. Designs exhibits that make the computational claim legible; it does not generate the underlying results.

Use when deciding whether a project is computing-first enough for an INFORMS Journal on Computing (IJOC) submission and which of its 10 technical areas fits. Scopes the contribution to the OR↔computing interface; it does not invent results or citations.

Use when the algorithm or model formulation, its correctness, and its theoretical guarantees are the bottleneck for an INFORMS Journal on Computing (IJOC) manuscript. Pins down formulation, complexity, and what the method provably does before experiments are finalized; it does not run the experiments.

Use when the one-sentence computational/methodological claim of an INFORMS Journal on Computing (IJOC) manuscript is not sharp, or the contribution reads as application rather than computing. Sharpens the "what is new and by how much"; it does not run the experiments that back it.

Use when staking the computational/methodological contribution of an INFORMS Journal on Computing (IJOC) manuscript against OR/MS and CS prior art. Positions the advance relative to the right baselines and the right frontier; it does not invent citations.