-
Notifications
You must be signed in to change notification settings - Fork 33
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
Detect accumulation frequency #898
Comments
I would rather be in favour of letting the user control this as has been suggested in #867 (comment) and #867 (comment). As we've discussed in the linked issue, this only works well if the accumulation pattern is regular. If it's not, what do we do? I wonder if we want to do the forecast accumulation in the modelling step or as a post-processing step? For example, we could generate daily forecasts and have a post-processing function that accumulates the data in any pattern using a setup similar to what fill_missing() does. There might be some computational issues but might be worth exploring. |
I like the idea of telling people if it has happened and how to override it |
I like this idea a lot but it would require a lot of work to reduce the pipeline like nature of the output or to get people used to more steps at least |
Nothing (i.e. the current default)? |
I agree it's a nice idea - in addition to this there's also the issue that currently in the model observation noise is applied after accumulation. |
As in this is a model fault or makes this hard? I am not sure its a model fault but a choice? |
I'm not sure we'll be able to fit otherwise as the observation noise defines the likelihood and thus can only apply when there are observations. |
I think you could do it but not in any clean or reasonable way |
I believe this has been addressed in #901 and should be closed? |
It was done for forecasts but not yet for |
We could do that if all the gaps are equal. Same with the
initial_accumulate
argument.Originally posted by @seabbs and @sbfnk in #867 (comment)
The text was updated successfully, but these errors were encountered: