Open lagerros opened 4 years ago
I created https://github.com/epidemics/covid/issues/395, but yes, we should be fine data-wise as soon as we have a new run (the functionality is there https://github.com/epidemics/epimodel/pull/34 but I need Tomas' approval it's correct).
For 1. - how should it look like? Like an actual table like:
RegionID Active
US 43213
UK 53211
...
rendered on the model page?
Mathijs has some proposal on #391 already. Will that always be 4 options? Could there be more or less? Bigger flexibility is of course making it harder.
And that's going to be static per client and same for all his models or different per each model?
Also, a side note, you Jacob mentioned that the complexity is low, that's IMO a bit underestimated.
Fair, though I meant doesn't require any larger architectural decisions etc(?)
1,2,3 sound good. 4 yes could be more or less. 5 static per client (but different between different clients).
In my view we do not want this and work on this should be stopped
We want to deliver a "custom site" to clients who our pro bono team are doing consulting for, where they can explore the outputs of our modelling work in a similar interface as currently available on the site.
Basically this amounts to the client getting a specific URL, similar to http://epidemicforecasting.org/?channel=david-j&selection=BR that is used to visualised a file of traces uploaded to GCS.
However, on the site we also want to display:
(I think 2. and 3. are bottlenecked by resolving current issues with data format and getting a batch of new simulation runs.)
For 4. and 5., it is fine to assume for the MVP that someone from the modelling team will be able to commit text updates directly to the relevant files (so need to build custom functionality for that).
Finally, assuming that we have the prerequisite input data files using v4 format, there should be an easy way to generate new custom sites as specified above. The workflow for the whole team should look like: