Mathematical Programming Computation


Mathematical Programming Computation: Information for Authors



1. Manuscript

Only articles written in the English language will be considered for publication. There is no pre-set page limit on articles, but the journal encourages authors to be concise. The length of the manuscript will be taken into consideration in the review process. Authors should aim to present summaries of computational tests, rather than long tables of individual results. Detailed tables and log files can be included in supplementary material to be made available on the journal's web site.

Articles should give a general description of the software, its scope, and the algorithms used. Rather than long descriptions of well-known algorithms, authors are encouraged to give details that deviate from the known state-of-the-art on specific design decisions and their consequences and implementation details.

2. Software

Computer codes must be accompanied by a clear description of the environment in which they are expected to be built, including instructions on how to obtain any required third-party packages. Clear and easy to follow instructions must be given on how to build and run the author's software, and how to use it to recompute any computational results given in the article.

3. Submission

Starting December 1, 2008, research articles can be submitted in Adobe PDF format through the journal's web page. Software and supplementary material can also be submitted through the web-based system. Software should be delivered as a zip or gzipped-tar archive file that unpacks into a directory, reflecting the name of the software. Prior to December 1, 2008, articles and supplementary material should be submitted to William Cook (Editor-in-Chief) at mpc@isye.gatech.edu.

4. Review

Articles within the scope of the journal will receive a rigorous review. The journal intends to have standards of quality similar to those of Mathematical Programming Series A and B (MPA and MPB) and other top research journals. The editorial board will strive to have papers reviewed within a four-month period. This target will be extended in cases of exceptionally long or difficult manuscripts.

The review of articles describing software will include an evaluation of the computer code received with the submitted manuscript. The criteria used in the software review include the following points.
  • The innovation, breadth, and depth of the contribution.
  • An evaluation of the progress in performance and features compared with existing software.
  • The conditions under which the software is available. See (6) below.
  • The availability and quality of user documentation.
  • The accessibility of the computer code; the ease with which a developer can make modifications.
5. Online Supplementary Material

As part of the review process, a public report on computational tests carried out by the editorial board may be produced. This report will be made public as supplementary material to document the replication of results from the research article, and to describe any additional tests that were made.

6. Evaluating Software Availability

The availability of accompanying software is evaluated in three categories. In each case, the lower the score the better.

License of the Code
  • Open-source software.
  • Source code available for academic use.
  • Source code available with major restrictions.
  • Only binary code available.
  • Binary code only available to the reviewers.
Distribution of the Code
  • Open-source software.
  • Software available from a web site.
  • Software only available from author on request.
License and Availability of any Required Third-party Packages
  • Open-source software.
  • No additional package needed.
  • Only freely available open-source packages needed.
  • Additional packages as source code.
  • Additional packages freely available in binary form.
  • Commercial packages needed.
  • Packages needed that were supplied by the author to the reviewers and are not available to readers, that is, software cannot be built by readers.