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

[Bug:] Inconsistent inputs for evaluate() functions in the recruitment module #653

Open
Bai-Li-NOAA opened this issue Jul 24, 2024 · 3 comments
Assignees
Labels
kind: bug Something isn't working P3 low priority task theme: code cleanup
Milestone

Comments

@Bai-Li-NOAA
Copy link
Contributor

Describe the bug

The evaluate() function in the Beverton Holt SR class requires phi_0 as the second parameter, while the evaluate() function from the recruitment base class uses ssbzero as the second parameter. Should these parameters be consistent? Additionally, the R test for the Beverton-Holt SR module uses ssb0 as input. Could this be a typo, and should it actually be phi_0

Describe how to reproduce the bug

See links in the description block.

Screenshots

No response

Which OS are you seeing the problem on?

No response

Which browser are you seeing the problem on?

No response

Which version of FIMS are you seeing the problem on?

No response

Additional context

No response

@Bai-Li-NOAA Bai-Li-NOAA added kind: bug Something isn't working status: triage_needed This is not approved for this milestone, do not work on it yet labels Jul 24, 2024
@kellijohnson-NOAA
Copy link
Contributor

Wait until after sprint 2 is done, change during week of Aug. 5th. Should be changed in dev. Code needs to be made consistent in the naming structure. @msupernaw will do this!

@kellijohnson-NOAA kellijohnson-NOAA added P3 low priority task theme: code cleanup and removed status: triage_needed This is not approved for this milestone, do not work on it yet labels Jul 30, 2024
@kellijohnson-NOAA kellijohnson-NOAA added this to the 2 milestone Jul 30, 2024
@kellijohnson-NOAA
Copy link
Contributor

@msupernaw can you do this now that dev_MS is merged into dev?

@msupernaw
Copy link
Contributor

msupernaw commented Oct 10, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind: bug Something isn't working P3 low priority task theme: code cleanup
Projects
None yet
Development

No branches or pull requests

3 participants