Hi,
I'm working through the JOSS review. One of the review checklist items includes:
- Installation instructions: Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.
A couple of things to note here.
First, the README and DESCRIPTION do not explicitly state you need SWAT or SWAT+ executable files. I'd include this in the README with a link to the respective downloads for each OS. In the DESCRIPTION, this requirement should be included in the SystemRequirements field. (See https://r-pkgs.org/description.html#other-fields).
Second, it isn't realistic to automate including SWAT with the package given CRAN packaging constraints. But, I think a function to download and copy a SWAT/SWAT+ executable to the project folder would be useful. The function should return the file path, then this can be provided as the SWAT executable file path argument in runSWATpar().
The first item should be fixed (IMO), but the second item is just a suggestion.
EDIT: Reference JOSS Review thread:
openjournals/joss-reviews#6797
Hi,
I'm working through the JOSS review. One of the review checklist items includes:
A couple of things to note here.
First, the
READMEandDESCRIPTIONdo not explicitly state you need SWAT or SWAT+ executable files. I'd include this in the README with a link to the respective downloads for each OS. In theDESCRIPTION, this requirement should be included in theSystemRequirementsfield. (See https://r-pkgs.org/description.html#other-fields).Second, it isn't realistic to automate including SWAT with the package given CRAN packaging constraints. But, I think a function to download and copy a SWAT/SWAT+ executable to the project folder would be useful. The function should return the file path, then this can be provided as the SWAT executable file path argument in
runSWATpar().The first item should be fixed (IMO), but the second item is just a suggestion.
EDIT: Reference JOSS Review thread:
openjournals/joss-reviews#6797