Data pulls for model-based estimates

[Duane-Stevenson-NOAA]

It would be GREAT if this package included the functionality to replicate the data pulls for model-based survey data products. These are currently created using sumfish, which many staff members cannot get to reliably work. This means that data pulls for these time-sensitive products may be unnecessarily delayed by limited staff availability and access.

An example of a data pull script is here, and an example of a formatted data file here. If we can replicate these data files, in this format, it will reduce the pressure on the few staff that can currently provide these data sets.

[zoyafuso-NOAA]

Hi Duane,

Apologies for not responding to this at the time, I need to configure GitHub to ping me when an issue comes up here. I totally agree and this is one of the potential future applications of the gapindex package along with the design-based index products.

The update here is that this can be done for the GOA model-index data pulls, as the data pulling is fairly straightforward. I've done some initial bridging with the output from gapindex::get_data() and gapindex::calc_cpue() for the GOA VAST data inputs for the 2023 requests and they match.

Bering Sea data pulls from that script you attached are a little bit more involved and I need to review that script and the sumfish repo so I can configure gapindex to replicate those data pulls for both the index and age-comp VAST data inputs.

I am creating three tasks for me that I will prioritize for this fall/winter. If successful maybe I can convince Cecilia/Lewis to integrate gapindex into the 2024 ModSquad workflow.

• [ ] Bridge GOA VAST index data pulls with gapindex.
• [ ] Bridge EBS/NBS VAST index data pulls with gapindex.
• [ ] Bridge EBS/NBS VAST agecomp data pulls with gapindex.

Thanks, Zack

[Duane-Stevenson-NOAA]

Thank you, Zack. I have spoken with Jason about this, and he is willing to help with the development of this package. He could be a great resource, and I encourage you and whoever else is working on this aspect of the package to reach out to him for input.

Duane

On Wed, May 10, 2023 at 11:34 AM zoyafuso-NOAA @.***> wrote:

Hi Duane,

Apologies for not responding to this at the time, I need to configure GitHub to ping me when an issue comes up here. I totally agree and this is one of the potential future applications of the gapindex package along with the design-based index products.

The update here is that this can be done for the GOA model-index data pulls, as the data pulling is fairly straightforward. I've done some initial bridging with the output from gapindex::get_data() and gapindex::calc_cpue() for the GOA VAST data inputs for the 2023 requests and they match.

Bering Sea data pulls from that script you attached are a little bit more involved and I need to review that script and the sumfish repo so I can configure gapindex to replicate those data pulls for both the index and age-comp VAST data inputs.

I am creating three tasks for me that I will prioritize for this fall/winter. If successful maybe I can convince Cecilia/Lewis to integrate gapindex into the 2024 ModSquad workflow.

• Bridge GOA VAST index data pulls with gapindex.
• Bridge EBS/NBS VAST index data pulls with gapindex.
• Bridge EBS/NBS VAST agecomp data pulls with gapindex.

Thanks, Zack

— Reply to this email directly, view it on GitHub https://github.com/afsc-gap-products/gapindex/issues/22#issuecomment-1542636722, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANKDWAVMP45NXJ53MMN32T3XFPNTFANCNFSM6AAAAAAV3DGVWQ . You are receiving this because you authored the thread.Message ID: @.***>

-- Duane Stevenson, Ph.D. Supervisory Fish Biologist Groundfish Assessment Program NMFS, Alaska Fisheries Science Center

[zoyafuso-NOAA]

This will be a modsquad goal for our hindcast season so I will close this issue.