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

Seeding issue related to continuation resumes when lots of seeding removed #114

Closed
saraloo opened this issue Oct 30, 2023 · 4 comments
Closed
Assignees
Labels
medium priority Medium priority. submission Concerns the submission framework.

Comments

@saraloo
Copy link
Contributor

saraloo commented Oct 30, 2023

EDIT: MOVED OVERVIEW TO HopkinsIDD/COVID19_USA#14

Project aims are to compare the effect of punctuated variant emergence vs our continuous immune ladder evolution structure on projections.

Overall plan

  • Refit Round 17 phases with all the fixed boundary issues etc that were possibly there during when we ran it
  • Run variant structure for calibration period and projection period
  • Run variant structure until after omicron, then run immune ladder structure

Work is in: https://github.com/HopkinsIDD/COVID19_USA/tree/evol-projection

@saraloo saraloo added medium priority Medium priority. submission Concerns the submission framework. labels Oct 30, 2023
@saraloo saraloo self-assigned this Oct 30, 2023
@saraloo
Copy link
Contributor Author

saraloo commented Oct 30, 2023

Current issues with run

To run a continuation resume from 2020, adding seeding of new variants, there are errors I can't figure out.

Process now with continuation resume is:

  • Seir from resume location is used
  • values in seir at date = start date of new config are used as new init values. If there are new compartments you can include these as 0 with allow_missing_compartments: True
  • parameters etc resumed
  • seeding is resumed
    -- if you want to add new variants, create_added_seeding.R can add new seeding values to the resumed global file (eg I add alpha, delta and omicron seeding)
    -- you can add options like: stop perturbation of initial seeding (eg don't refit WILD seeding again)
  • at every date in the simulation, flepimop checks if there is seeding and does the normal seeding process

Something here isn't working when I try to run a continuation resume Phase 2 from Phase 1. Config is: https://github.com/HopkinsIDD/COVID19_USA/blob/evol-projection/config_SMH_R17_noBoo_lowIE_phase2_blk1_test.yml

My seeding section looks like:

seeding:
  variant_filename: data/variant/variant_props_R17_phase2.csv
  seeding_compartments:
    ALPHA:
      source_compartment: ["S", "unvaccinated", "WILD", "age18to64"]
      destination_compartment: ["E", "unvaccinated", "ALPHA", "age18to64"]
    DELTA:
      source_compartment: ["S", "unvaccinated", "WILD", "age18to64"]
      destination_compartment: ["E", "unvaccinated", "DELTA", "age18to64"]
    OMICRON:
      source_compartment: ["S", "unvaccinated", "WILD", "age18to64"]
      destination_compartment: ["E", "unvaccinated", "OMICRON", "age18to64"]
  method: FolderDraw
  seeding_file_type: seed
  lambda_file: data/seeding_territories_R17_phase2.csv
  date_sd: 3
  amount_sd: 0
  added_seeding:
    added_lambda_file: data/seeding_territories_R17_phase2_added.csv
    fix_original_seeding: TRUE
    fix_added_seeding: FALSE

Seeding looks like it is working, but for some reason it looks like it is seeding the wrong variant? The curves here are from an seir file, and the black points are seeded amounts by variant.
image (4)

Is there anything in flepimop that looks for the index of a compartment or strata rather than by name?

@saraloo
Copy link
Contributor Author

saraloo commented Nov 3, 2023

Copying from slack from @jcblemai :
it turns out it was a nasty bug in gempyor:

  • this bug has been present for more than 1y
  • affects runs where there is seeding before the config t_start .
    • Seeding before t_start is discarded with a message (e.g CRITICAL:root:Seeding ignored 357 rows because they were before the start of the simulation. ). This is normal behavior
    • but because of this bug, it shifted the timing of the (not discarded) seeding (which becomes really off, depending on the # of discarded seeding rows)
    • probably most of our runs are fine because we mostly used create_seeding.R which does not seed before start_date
      • but some latter runs, that are resumed from older runs & use initial conditions could be affected. I could not remember any with a start_date change that could be affected.
      • Sara's run had hundreds of rows ignored which completely shifted the timing of the seeding runs.
        Waiting for a real fix in both main and breaking-improvment, a quickfix for main is available here (PR HopkinsIDD/flepiMoP#121).

shauntruelove added a commit that referenced this issue Nov 3, 2023
@saraloo saraloo changed the title Project: exploring the effect of punctuated vs continual evolution on projections Seeding issue related to continuation resumes when lots of seeding removed Nov 17, 2023
@saraloo saraloo closed this as completed Nov 17, 2023
@jcblemai
Copy link
Collaborator

reopen because not fix in breaking-improvment

@jcblemai jcblemai reopened this Nov 17, 2023
@jcblemai
Copy link
Collaborator

in fact another issue in #122 , so this one can be closed

jcblemai pushed a commit that referenced this issue Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
medium priority Medium priority. submission Concerns the submission framework.
Projects
None yet
Development

No branches or pull requests

2 participants