You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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)
can-ft-catch-by-month (data until 2019)
can-ss-catch-by-month (data until 2019)
catch_per_country (data until 2018)
catches (data until 2017)
landings-tac-history (data until 2019)
us-cp-catch-by-month (data until 2019)
us-ms-catch-by-month (data until 2019)
us-research-catch-by-month (data until 2018)
us-shore-catch-by-month (data until 2019)
The text was updated successfully, but these errors were encountered:
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).
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.
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)
The text was updated successfully, but these errors were encountered: