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

Special Project Data for Washington #66

Open
chantelwetzel-noaa opened this issue Jul 16, 2021 · 0 comments
Open

Special Project Data for Washington #66

chantelwetzel-noaa opened this issue Jul 16, 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: bug
Milestone

Comments

@chantelwetzel-noaa
Copy link
Contributor

Data was using PacFIN data to explore the sampling distribution of lingcod ages relative to the lengths. The data he was using was not pulled using the PacFIN bds pull function from the main branch of this package; however, WDFW pointed out something that I want to make sure we double check. Apparently identifying all Washington special samples requires checking more than one column in PacFIN. Lisa Hillier (WDFW) writes:

"Based on the spreadsheet from Jim this morning, it looks like the WA data from 2016-2019 includes special project samples that should not be included as comm. fishery samples. Special projects are coded as Market samples for WA (this may be the issue if the data is filtered based on this category) but should be filtered based on special_project_name too."

I am opening an issue here as a reminder to double check our pulling and cleaning processes to ensure that all WDFW special samples are being removed from the bds data.

@kellijohnson-NOAA kellijohnson-NOAA added type: bug 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: bug
Projects
None yet
Development

No branches or pull requests

2 participants