Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JOSS Review Meta-Response #66

Merged
merged 26 commits into from
Apr 10, 2024
Merged

JOSS Review Meta-Response #66

merged 26 commits into from
Apr 10, 2024

Conversation

crvernon
Copy link
Contributor

Addresses the JOSS paper review responses in: openjournals/joss-reviews#6325

Issues addressed:
Resolves #43
Resolves #44
Resolves #47
Resolves #48
Resolves #49
Resolves #50
Resolves #51
Resolves #52
Resolves #54
Resolves #55
Resolves #56
Resolves #57
Resolves #58
Resolves #59
Resolves #60
Resolves #61
Resolves #62
Resolves #63
Resolves #64

Associated PRs:
#45
#46
#53
#65

@rg727
Copy link
Collaborator

rg727 commented Apr 10, 2024

Finished addressing the first round of JOSS reviews

@rg727 rg727 closed this Apr 10, 2024
@rg727 rg727 reopened this Apr 10, 2024
@rg727 rg727 merged commit 75d0ba2 into main Apr 10, 2024
9 checks passed
@crvernon crvernon mentioned this pull request Apr 10, 2024
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

A few public functions do not appear to have docstrings: hmm_multisite_sample, hmm_multisite_fit. I guess there are more. You can find these by pip install ruff, navigate to directory, ruff . --select D100. I don't think you have to go too far in this, as it is probably not the responsibility of to fully train a user in StateMod, but since I think there is an implication that is a portal to new users of StateMod, a little more help explaining its principles in the notebooks would be appreciated. I understand you are all probably experts in it so it is probably difficulty to identify what is implicit and what is not, so I will just list things I would appreciate explaining under this task as I identify them Maybe I am impatient but I wonder if you could use a shorter selection of dates in your quickstart notebooks, perhaps just select an interesting decade (or even better a year!)? 20-30 mins doesn't feel like a particularly quick start. Edit: in fact I wonder if changing the dates would be a helpful statemodify functionality (and the ability to change any of the .ctl parameters at runtime) To avoid potential other issues like this, I think it would be sensible for your testing in automation to run on windows and macos. You would only need to add windows-latest and macos-latest into .github/workflows/build.yml. Edit: having started the notebooks I can see that StateMod is compiled for linux and mingw/cygwin, so I can see why you'd only test ubuntu, that said - considering there was only one error on my windows machine, it probably won't hurt and ensures that potential future versions of StateMod will be compatible. Path error in test, I think due to my using a windows machine. Should be fixable by using os.path.join in COMP_FILE under TestModify. Though you may want to consider using pathlib throughout for a more convenient long term handling of file paths than os.
2 participants