Submission Preparation ChecklistAs 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 descriptive text as PDF, including installation instructions. Please use the style files on Github to prepare your submission.
- The source code with a makefile or similar.
- A copyright statement for the code and an Open Source License.
- Instructions/scripts to reproduce results in the article
Regular ArticlesIn this section, we publish well-structured pieces of application software together with an accompanying article describing the functionality, mathematical foundation, and providing example results. They are based on one of the libraries listed in the section on editorial policies. They have been tested to run and produce at least part of the results in the article.
Short CommunicationsShort communications provide information about updates to codes that were described in a previous article. These could be for instance adaptations to new library versions, or the use of a more advanced component in part of the code. These submissions should contain the complete and self-contained updated revision of the code they refer to, accompanied by an article outlining the changes and their purpose. Technical requirements are the same as for regular submissions, but novelty requirements are not as strict. Nevertheless, the update must be a significant improvement. Depending on the nature of the update, the editor might abbreviate the peer review process.
Library IntroductionsThese are short communications or regular articles introducing a new software library for public use. Articles in the Archive of Numerical Software can be based on such a library, and an introduction or an introduction of the features of a new version will help authors referencing the library. In order to be added, a software library must meet the following criteria:
- Quality manifested in a well-documented user interface, correctness of implementation, and the use of modern software practices such as regular testing. Object-oriented code is welcome, but not necessary.
- Availability under an OSI approved Open Source license.
- Accessibility in the sense that the library does not require excessively many or unusual software to be installed and that configuration and installation can be performed in few and easy steps.
- Utility such that the scope of the library is sufficiently wide and its use results in considerably shorter or better structured application programs.
- An existing user base that extends beyond the institution that created the software.
Copyright NoticeAuthors who publish with this journal agree to the following terms:
- Authors retain copyright and grant the journal right of first publication with the descriptive part of the work simultaneously licensed under a Creative Commons Attribution License that allows others to share the work with an acknowledgment of the work's authorship and initial publication in this journal. The code part of the work is licensed under a suitable OSI approved Open Source license.
- Authors are able to enter into separate, additional contractual arrangements for the non-exclusive distribution of the journal's published version of the work (e.g., post it to an institutional repository or publish it in a book), with an acknowledgment of its initial publication in this journal.
- Authors are permitted and encouraged to post their work online (e.g., in institutional repositories or on their website) prior to and during the submission process, as it can lead to productive exchanges, as well as earlier and greater citation of published work.