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

Inconsistency in CSV File Years for MSE: Seeking Clarification for the Year 2018 (pacifichakemse/inst/extdata/csv-data) #14

Open
sacurin opened this issue Feb 22, 2024 · 2 comments

Comments

@sacurin
Copy link

sacurin commented Feb 22, 2024

Does anyone know why the CSV files used in MSE don't have the same length of years?
For example, for the year 2018 (pacifichakemse/inst/extdata/csv-data)

  1. can-ft-catch-by-month (data until 2019)
  2. can-ss-catch-by-month (data until 2019)
  3. catch_per_country (data until 2018)
  4. catches (data until 2017)
  5. landings-tac-history (data until 2019)
  6. us-cp-catch-by-month (data until 2019)
  7. us-ms-catch-by-month (data until 2019)
  8. us-research-catch-by-month (data until 2018)
  9. us-shore-catch-by-month (data until 2019)
@aaronmberger-nwfsc
Copy link

My guess is that the incomplete ones are simple aggregations of the other complete ones (e.g., catch_per_country is the sum across months for each fleet in a country). And somewhere during development, those aggregation files were perhaps not used and thus not updated (i.e., catch by month and fleet was just used as the 'raw' data).

@kristinmarshall-NOAA
Copy link
Contributor

Aaron's guess makes sense to me. It seems like the 2019 observations wouldn't actually be used in the code. But that is something we can track down in the load and run functions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants