Closed wimvanderbauwhede closed 3 years ago
Statement of need I think that this had already been addressed in https://github.com/openjournals/joss-reviews/issues/2950#issuecomment-761789660 but let us know if this not the case.
Automated Tests We have a series of automated regression and compile tests that are run at every commit -- https://github.com/uDALES/u-dales/tree/master/tests
Functionality I am not sure what is meant by this exactly -- I do not think there are any specific claims made that need to be checked but @tomgrylls may have more to say about this.
Thanks both - I have added to the documentation and created a PR (#140).
@dmey I will first request a review from you and another uDALES team member to make sure we are happy with these additions before then confirming that it satisfies the checklist as discussed above.
OK, happy to close this issue.
The Review checklist at https://github.com/openjournals/joss-reviews/issues/3055 has a few items that I can't tick at the moment because I can't find the info in the docs, so if you could please point me to it:
"Documentation A statement of need: Does the paper have a section titled 'Statement of Need' that clearly states what problems the software is designed to solve and who the target audience is?"
"Automated tests: Are there automated tests or manual steps described so that the functionality of the software can be verified?"
"Functionality [...] Functionality: Have the functional claims of the software been confirmed? Performance: If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)"