Advanced users have customized the Covasim model calibration on the backend. Such users need to be able to upload the full parameter file to have the webapp reflect their exact parameterization. In addition, it would be desirable (although not MVP) for users to be able to customize which parameters appear in the interface, including ones that are part of nested dictionaries.
There is already considerable flexibility for uploading a custom JSON file of parameters. However, the parameter upload for setting the simulation configuration needs to be decoupled from the specification of parameters in the interface, which should be configurable separately.
[ ] Change parameter upload/download to be full sim.pars, not web_pars
[ ] Perform validation on uploaded parameters (e.g., population size)
[ ] Remove the distinction between "sim pars" and "epi pars", and change the layout so the parameter name and box is on the same line (to save space), and just have a single column
[ ] Non-MVP: have an advanced "Access code" feature to increase the time & size limitations? e.g. if you type "custom_OHA" into the box, it will let you run with full population sizes (and maybe customize the options to Oregon).
Advanced users have customized the Covasim model calibration on the backend. Such users need to be able to upload the full parameter file to have the webapp reflect their exact parameterization. In addition, it would be desirable (although not MVP) for users to be able to customize which parameters appear in the interface, including ones that are part of nested dictionaries.
There is already considerable flexibility for uploading a custom JSON file of parameters. However, the parameter upload for setting the simulation configuration needs to be decoupled from the specification of parameters in the interface, which should be configurable separately.
sim.pars, notweb_pars