| 45 | | |
| 46 | | |
| 47 | | |
| 48 | | |
| 49 | | |
| | 46 | * Suspected bugs and proposed fixes should be reported back to the original authors to be considered for inclusion in the standard distribution. No independently developed and maintained forks should be created as long as the original authors actively work on the program. |
| | 47 | * The program should normally be redistributed in its entirety. When there are special reasons, an agreement should be sought with the original authors to redistribute only specific parts. This should be arranged such that the redistributed parts remain updated in step with the standard distribution. |
| | 48 | * Any changes in the code must be clearly marked in the source (reason, author, date) and documented. If any modified version is redistributed it should be stated at the point of distribution (download link) that it has been modified and why. |
| | 49 | * If a significant part of the code is used by another program, this should be clearly specified in that program's documentation and stated at its point of distribution. |
| | 50 | * Copyright information and references may not be removed. Copyright-related program messages may not be altered and must be printed even if only a part of the program is used. Adding further messages specifying any modifications is encouraged. |
| 52 | | |
| 53 | | |
| 54 | | |
| 55 | | |
| | 53 | * The main software reference as designated by the program authors should always be cited. |
| | 54 | * In addition, the original literature on which the program is based should be cited to the extent that it is of relevance for a study, applying the same threshold criteria as for other literature. |
| | 55 | * When several programs are combined, they should all be mentioned, commensurate with their importance for the physics study at hand. |
| | 56 | * To make published results reproducible, the exact versions of the codes that were used and any relevant program and parameter modifications should be spelled out. |
