You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Interesting new case for the trigger report: how do we compute and communicate performance for observational triggers that can activate on a frequent basis? In Malawi, that would be daily. (In Niger that was only once.)
In this case because it's once monthly, we're treating it like a predictive trigger. Maybe there is a parallel with sudden-onset triggers here.
In this case, we actually only look at it in September, not earlier, but were calculating the performance to see when we might want to set our activation timepoints. That was just a comment that accidentally was left in the code, so actually the same as Niger here. Interesting thought, though. I think we could treat it like a predictive trigger if we are doing something like monthly (so as in Niger, you could look at the individual trigger points). However, clearly impossible for daily triggers. Some interested ideas could be there for plots maybe of likelihoods across the observation period, maybe?
Basically, there could be some interesting stuff for Malawi in terms of reporting likelihood of activation across the entire observational period.
The text was updated successfully, but these errors were encountered:
Pulling these from interesting comments Josée left about the trigger report if the observational trigger has multiple activation timepoints.
@joseepoirier
@caldwellst
Basically, there could be some interesting stuff for Malawi in terms of reporting likelihood of activation across the entire observational period.
The text was updated successfully, but these errors were encountered: