-
Notifications
You must be signed in to change notification settings - Fork 9
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
Document units in FIMS #591
Document units in FIMS #591
Conversation
Instructions for code reviewerHello reviewer, thanks for taking the time to review this PR!
Checklist
|
These commits help with the documentation in the vignette but #561 refers to the fact that there is a unit column in data_mile1 that is not filled out for all entries and that is not addressed. |
@kellijohnson-NOAA, I've updated the unit column in data_mile1, but I think issue #561 needs further discussion & work if we want to document units alongside the code (see my comment here). Should I open a pull request to merge the changes I've made so far or would it be preferable to wait until we've reached decisions on where to document units alongside code? |
@Bai-Li-NOAA do you mind if I make one change to this PR and one addition? |
@kellijohnson-NOAA. No, I don't mind at all. Please feel free to make any changes. |
Thanks @Bai-Li-NOAA I pushed one small change and an addition. The addition is going to conflict with the other open PR but it is pretty minor so I am willing to deal with the conflicts. |
Thanks @Bai-Li-NOAA and @kellijohnson-NOAA for working on this. The index units are listed as "mt", but since we have a catchability parameter available, isn't it equally possible to use any other units (or unknown units) as long as the index is assumed proportional to biomass? Related to that, it looks like our model specification says (incorrectly I think) that "survey is in number": |
@Bai-Li-NOAA I was able to rebase this branch with the main branch without any conflicts. Would you like me to force push the rebase? |
Force push the rebase sounds good. Thanks, @kellijohnson-NOAA. I will reopen the pull request after that. @iantaylor-NOAA , good catch. The unit from the model specification chapter is incorrect. |
a5ed712
to
4a995c3
Compare
6e0714d
to
9174dfe
Compare
9174dfe
to
9d42868
Compare
@Bai-Li-NOAA, can you reassign this to another reviewer? I won't have time to look at this until the end of next week. |
@Andrea-Havron-NOAA, thanks for letting me know. I will find another reviewer for the pull request. @iantaylor-NOAA, would you be available to review the pull request? You've made some helpful suggestions on it in the past. If you're busy, no worries. I'll continue looking for another reviewer. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks @Bai-Li-NOAA for making these improvements.
The one question that this PR raises for me is whether there's a way to make the tests more modular. That is, the new "agecomp in proportion works" test added to test-integration-fims-estimation.R has a lot of redundancy with the existing "estimation test of fims". We want to make sure proportions still pass all the same checks but the duplicate code would be harder to maintain than if there's some way to wrap it in a function without losing the ability to get detailed output from each element of the test. Having said that, I don't think it makes sense to spend more time on this now, rather to think about the issue for future revisions to the tests.
- document units in code snippets of the fims-demo vignette - add units to output figures in the fims-demo vignette and add a spawning biomass comparison figure - add an R test to confirm that age composition intput can be in numbers or proportions - add units for index_data and age_data in data_mile1.R Co-authored-by: Kelli Johnson <kelli.johnson@noaa.gov>
9d42868
to
0c5f2da
Compare
What is the feature?
This PR addresses issue #561 and documents units in FIMS
How have you implemented the solution?
Does the PR impact any other area of the project?
No
How to test this change
No changes to the core code base
Developer pre-PR checklist