January 26–30, 2026

THREE BIG THINGS THIS WEEK

1. We gave one training session and presented three talks this week at the National Stock Assessment Workshop!

2. A table of capabilities of FIMS compared to other platforms will be put on our website to help communicate to leadership where we are and where we are going. A big thank you to Cole for the inspiration.

3. Matthew is working on #981 to reduce the amount of RAM needed to compile FIMS.

HELPFUL RESOURCES

• FIMS Outreach Activities
• NMFS Open Science Calendar
• Implementation Team Notes
• FIMS FAQs
• NOAA-FIMS Discussions
• GitHub Trainings

FIMS ANNOUNCEMENTS

• Meg and Ian will be doing a training next week on FIMSdiags.
• Please encourage your peers to use the Discussion Board to ask questions about FIMS and propose features so we can talk about them in a public forum.
• If you attended the FIMS Training on Monday, please fill out the survey on Google Cloud Workstations.

UPCOMING EVENTS

PHOTO OF THE WEEK

To add ten years of projections onto your time series you can use FIMS::FIMSFrame() to add -999 to all of your data streams by just adding a single year of -999 for any type with the maximum year that you want to project to. See the code below for an example, which was taken from the projections vignette. Now we need to think carefully about the default uncertainty values for the -999 in each type.

data("data1", package = "FIMS")
years_of_projections <- 10
data1_with_extra_year <- dplyr::add_row(
  data1,
  type = "landings",
  timing = get_end_year(data_4_model) + years_of_projection,
  name = "fleet1",
  value = -999,
  unit = "mt"
) |>
  # Make a FIMSFrame object out of this data frame with the extra row to add all
  # of the other missing years for each data type
  FIMSFrame()