PacFIN.BDS.Extraction() (with a help man page) extracts BDS data from PacFIN's Comprehensive_BDS_Comm table.
The old BDS tables were made wider with extra ages for the same fish, from readers one, two, and three moved to their own columns. To stick with a more raw data format, this is not done here and hence the default for the argument to add columns with legacy names is set to FALSE (there would have to be another table to fully match the old BDS table).
To compare the number of unique fish from the old BDS table to the new Comp_BDS, I tabulated the number of non-missing ages for unique fish [ paste(SAMPLE_NO, CLUSTER_NO, FISH_NO) ] by agency and year.
We are not concerned with a final age since NWFSC uses an aging error matrix, but for other users of PacFIN BDS data, I also looked at the number of final ages vs the number of first reads, both from the Comprehensive_BDS table .
In the Canary rockfish tables below, 'Year is sample year, 'legacyAge' is for ages from the old BDS table, compAgeFinal is the final age from the Comp_BDS table, and comAge is the first read from the Comp_BDS table. Note that the ages from a sample year could have aged at a later time.
For WA, there are more ages of unique fish in 1982 for the old table than in Comp_BDS:
Besides Canary, I have looked at the ages for Dover, Sablefish, Darkblotched, and Yellowtail. Of those looked at, only Dover in CA has a major issue, with all the ages before 1990 only being in the old BDS tables and not the Comp_BDS:
At least the issue for Dover in CA is an all year or month issue. A major mixture within a month would be more of a problem as it appears that the sample number in the Comp_BDS has been changed from the old BDS tables. (Minor issues were 30 missing ages in Comp_BDS for Sablefish in 2010 and 49 ages missing in Comp_BDS in 1987 for Yellowtail, both of those were in OR.)
Looking at the surface reads and break and burn ages on the same fish in WA in the early 80's, we see that no final age is given. Below are two examples. Because of this issue, Canary Comp_BDS has around 600 more unique fish single ages from the first reader than in final ages.
BDS_ID SAMPLE_ID SAMPLE_YEAR AGENCY_CODE SAMPLE_NUMBER FISH_SEQUENCE_NUMBER AGE_SEQUENCE_NUMBER AGE_METHOD_CODE AGE_IN_YEARS FINAL_FISH_AGE_IN_YEARS
21644 1001602 63325863 1980 W 20804101260004 4 1 S 19 NA
21645 1001603 63325863 1980 W 20804101260004 4 2 B 26 NA
BDS_ID SAMPLE_ID SAMPLE_YEAR AGENCY_CODE SAMPLE_NUMBER FISH_SEQUENCE_NUMBER AGE_SEQUENCE_NUMBER AGE_METHOD_CODE AGE_IN_YEARS FINAL_FISH_AGE_IN_YEARS
21646 1001733 63325863 1980 W 20804101260004 5 1 S 20 NA
21647 1001734 63325863 1980 W 20804101260004 5 2 B 41 NA
Since break and burn is accepted to be the superior method, the B&B final age could be filled in and the surface final age left as NA. With both left as NA, the final ages have fewer ages for WA.
PacFIN.BDS.Extraction() (with a help man page) extracts BDS data from PacFIN's Comprehensive_BDS_Comm table.
The old BDS tables were made wider with extra ages for the same fish, from readers one, two, and three moved to their own columns. To stick with a more raw data format, this is not done here and hence the default for the argument to add columns with legacy names is set to FALSE (there would have to be another table to fully match the old BDS table).
To compare the number of unique fish from the old BDS table to the new Comp_BDS, I tabulated the number of non-missing ages for unique fish [ paste(SAMPLE_NO, CLUSTER_NO, FISH_NO) ] by agency and year.
We are not concerned with a final age since NWFSC uses an aging error matrix, but for other users of PacFIN BDS data, I also looked at the number of final ages vs the number of first reads, both from the Comprehensive_BDS table .
In the Canary rockfish tables below, 'Year is sample year, 'legacyAge' is for ages from the old BDS table, compAgeFinal is the final age from the Comp_BDS table, and comAge is the first read from the Comp_BDS table. Note that the ages from a sample year could have aged at a later time.
For WA, there are more ages of unique fish in 1982 for the old table than in Comp_BDS:
Here is the WA - 1982 breakdown by month:
For OR, the Comp_BDS has equal or more ages of unique fish:
CA is all good for Canary (but see Dover below):
Besides Canary, I have looked at the ages for Dover, Sablefish, Darkblotched, and Yellowtail. Of those looked at, only Dover in CA has a major issue, with all the ages before 1990 only being in the old BDS tables and not the Comp_BDS:
There is a mixture in 1990 and here is the breakdown by month:
At least the issue for Dover in CA is an all year or month issue. A major mixture within a month would be more of a problem as it appears that the sample number in the Comp_BDS has been changed from the old BDS tables. (Minor issues were 30 missing ages in Comp_BDS for Sablefish in 2010 and 49 ages missing in Comp_BDS in 1987 for Yellowtail, both of those were in OR.)
Looking at the surface reads and break and burn ages on the same fish in WA in the early 80's, we see that no final age is given. Below are two examples. Because of this issue, Canary Comp_BDS has around 600 more unique fish single ages from the first reader than in final ages.
Since break and burn is accepted to be the superior method, the B&B final age could be filled in and the surface final age left as NA. With both left as NA, the final ages have fewer ages for WA.