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

add diagnostics related to trips without trip weights and expanded sample sizes #64

Open
iantaylor-NOAA opened this issue Jun 17, 2021 · 0 comments
Labels
priority: high The highest priority level in terms of what needs to be done. status: help wanted Help is needed topic: code Related to R code within this package type: enhancement
Milestone

Comments

@iantaylor-NOAA
Copy link
Contributor

Is your feature request related to a problem? Please describe.
PacFIN data for Lingcod include lots of trips without trip weight, which end up with expansion factor of 1, whereas many trips have a reasonably large expansion, creating a bimodal distribution of expanded sample sizes and spikes in the resulting length compositions. An example of the resulting distribution is posted to pfmc-assessments/lingcod#69.

Describe the solution you'd like
A standard output table of the number of trips by gear/year that have missing trip weight would provide useful information.
@chantelwetzel-noaa also demonstrated that plotting the distribution of Final_Sample_Size by fleet/year is a useful way to see what's going on.

Describe alternatives you've considered
One-off scripts for any given species.

Additional context
Nothing now. Could be added later.

@kellijohnson-NOAA kellijohnson-NOAA added type: enhancement status: help wanted Help is needed topic: code Related to R code within this package priority: high The highest priority level in terms of what needs to be done. labels May 4, 2022
@kellijohnson-NOAA kellijohnson-NOAA added this to the year_2022 milestone May 4, 2022
@kellijohnson-NOAA kellijohnson-NOAA modified the milestones: year_2022, year_2023 May 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: high The highest priority level in terms of what needs to be done. status: help wanted Help is needed topic: code Related to R code within this package type: enhancement
Projects
None yet
Development

No branches or pull requests

2 participants