As previously implemented, dcc.Loading did not work nicely with the long callback, so #203 currently just removes it.
We should find a way to add it back. The nicest would be a bar that actually reports the current progress (see "Example 4: Progress Bar" on https://dash.plotly.com/long-callbacks ).
If it's difficult to get the current progress of the computation out of the posterior object, this bar need only report an estimate of the progress based on an estimate of the runtime derived from the number of serial interval samples and time points and the expected magnitude of R_t.
If there's no easy way to do the bar, a standard loading animation would be fine too.
As previously implemented, dcc.Loading did not work nicely with the long callback, so #203 currently just removes it. We should find a way to add it back. The nicest would be a bar that actually reports the current progress (see "Example 4: Progress Bar" on https://dash.plotly.com/long-callbacks ). If it's difficult to get the current progress of the computation out of the posterior object, this bar need only report an estimate of the progress based on an estimate of the runtime derived from the number of serial interval samples and time points and the expected magnitude of R_t. If there's no easy way to do the bar, a standard loading animation would be fine too.