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

Best way to split data at 40 10' management line #60

Open
kellijohnson-NOAA opened this issue Mar 8, 2021 · 3 comments
Open

Best way to split data at 40 10' management line #60

kellijohnson-NOAA opened this issue Mar 8, 2021 · 3 comments
Labels
priority: low The lowest level priority, i.e., not urgent. status: help wanted Help is needed topic: code Related to R code within this package type: enhancement
Milestone

Comments

@kellijohnson-NOAA
Copy link
Contributor

Anyone have advice on how to split data from PacFIN at the 40 10' management line? @iantaylor-NOAA suggested those who worked on data from China rockfish might have insight? @John-R-Wallace-NOAA do you have ideas. I would think that the method here would be standard across almost all species and we could implement some code.

@kellijohnson-NOAA kellijohnson-NOAA added the status: question Questions about the issue need answered label Mar 8, 2021
@iantaylor-NOAA
Copy link
Contributor

iantaylor-NOAA commented Mar 8, 2021

@chantelwetzel-noaa just reminded me in a discussion about splitting the WCGOP data on this boundary that the 2017 Yellowtail Rockfish assessment was also split at 40°10', so perhaps @andi-stephens-NOAA remembers what approach was used.

Species with splits at 40°10'

  • china rockfish
  • yellowtail rockfish
  • lingcod (2021)

@andi-stephens-NOAA
Copy link
Contributor

andi-stephens-NOAA commented Mar 8, 2021 via email

@kellijohnson-NOAA
Copy link
Contributor Author

kellijohnson-NOAA commented Mar 16, 2021

Thanks to @melissamonk-NOAA for bringing to our attention that the ports specified by calcom that form port group complexes can be used to split the data.

Shelter Cove can act as the delineation here. For the catch data, the column is PORT_NAME; and for the bds data, the column is AGENCY_PORT_CODE, which provides cryptic groups that can be linked to actual port names here. For the latter, we care about low 200 level ports.

image

Next steps include the following:

@kellijohnson-NOAA kellijohnson-NOAA added type: enhancement and removed status: question Questions about the issue need answered labels Mar 16, 2021
@kellijohnson-NOAA kellijohnson-NOAA added this to the year_2021 milestone Mar 16, 2021
@kellijohnson-NOAA kellijohnson-NOAA added status: help wanted Help is needed topic: code Related to R code within this package priority: low The lowest level priority, i.e., not urgent. labels May 4, 2022
@kellijohnson-NOAA kellijohnson-NOAA modified the milestones: year_2021, year_2022 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: low The lowest level priority, i.e., not urgent. 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

3 participants