Trusted, Bureaucrats
4,223
edits
Changes
Jump to navigation
Jump to search
m
* New relax users often ask for a demo data set to test out the software with. This is totally unnecessary and is only needed to sooth the uncertainty of the software user.
* Simply bundle a data set and a functional relax script.
* I have recently created There is a git repository for this (e.g. at https://sourceforge.net/p/nmr-relax/relax-demo/ci/master/tree/).
It is essential that step 1) is completed first. Then the developer knows that their task is complete once the test passes. Most of this development would be based on mimicking what is already in place in relax. There are many different analysis types contributed by many different people, and development by copying/mimicking is highly recommended. It is also good to have complete test coverage added at step 8), as this ensures that the analysis will be robust and never break as relax is further developed. That future-proofs the code. I have uploaded the relax git repositories to SourceForge, github, gitlab, and bitbucket (and hopefully soon to Savannah) so that the software should survive for decades to come, independent of my presence.
== Speed ==
