As part of the submission process, authors are required to check off their submission's compliance with all of the following items, and submissions may be returned to authors that do not adhere to these guidelines.
- The submission has not been previously published, nor is it before another journal for consideration (or an explanation has been provided in Comments to the Editor).
- The submission file is in pdf.
- Where available, URLs for the references have been provided.
- The text is single-spaced; uses a 12-point font; employs italics, rather than underlining; and all illustrations, figures, and tables are placed within the text at the appropriate points, rather than at the end.
- The text adheres to the stylistic and bibliographic requirements outlined in the Author Guidelines, which is found in About the Journal.
Please mail your submission to dano(at)columbia.edu
Instructions for code submission
Please, put everything that is necessary to reproduce your results together:
- all code, libraries, etc.
- all necessary instances and data
- script files that reproduces the figures/tables from the article
- a README that explain how to do this
We are aware that often software is available on the Internet. But it is not the job of the Technical Editor to find out which version of the software fits to your submitted code. Or why the later version of some package produces different results. Please, put everything together that is needed in a suitable combination. Make it as easy as possible for the TE to reproduce your results.
For system standard or commercial libraries, which cannot be distributed with your source code, please make a list at the start of the README specifying all external software packages that are needed. In particular list all additional MATLAB packages that are required. And all special system services that are needed, like, e.g. MPI.
Please, try to make the software as portable as possible, reducing dependencies to particulars of your personal environment as much as possible.
If you use randomized algorithms, please add the possibility (e.g. a command line switch) to explicitly set the seed for the random number generator and supply the seed used in your scripts.
The procedure for the Code Review is as follows
After submission, one of our code worker will unpack your software, look at the README, check that we have everything available, and start the supplied scripts. This should reproduce your tables/figures. With a minimum of effort on our side if possible. We will not debug your software.
At this point the following questions should be answered with yes.
- Does everything compile/work as promised, i.e. is it possible to run this code without major hassle?
- Is everything there (precise test instances etc.) ?
- Can the results given in the paper (partly) be reproduced ?
Once this is achieved the software will be passed to the Technical Editor who will have a look at the code in more detail an prepare a referee report on the software. The questions he investigates are among others:
- Does the code look trustworthy/correct
- Does the description in the article match the implementation
- How useful is the code to others
This is a lot of work. Please help us, by providing a submission that makes it easy to answer these questions.