Sharing Parameter Blocks - Part 2

[ConradSelig]

I decided it would likely be a good idea to split this ticket into another part so the code I've already written for importing and exporting functions can be tested.

This ticket will serve to track other parameter blocks such as controls and disease blocks.

@missyschoenbaum What blocks exactly do you want exported? Here is what I'm thinking:

• Disease
  • Progression ( Disease Progression / Assign Progression)
  • Spread ( Disease Spread)
• Controls
  • Protocol (Control Protocol / Assign Protocols)
  • Vaccination ( Vaccination Triggers / Vaccination Rings / Vaccination Global)
  • Destruction (Destruction Global)
  • Zones (Zones / Zone Effects / Assign Effects)

Note: All of these blocks, somewhere, use either a relational function or a probability density function. We import/export the functions each block uses with that block and use the code (minimal modifications will have to be made for importing) written in part 1 to do it.

There are a few settings elsewhere in the program, but I believe those can or should always be set by hand.

[missyschoenbaum]

It may take me a while to think on this. I don't think we need to export any assigns, as that should always be a thoughtful and purposeful task. I'm also wondering if we shouldn't just export what is hard to rebuild, like the functions, and we have already done that.

[ConradSelig]

Liesel confirmed in today's meeting that we should not pursue additional parameter block exporting/importing. Closing this ticket.