-
Notifications
You must be signed in to change notification settings - Fork 1
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
Add anomaly time series #129
Comments
Yes, calculating this should be relatively simple, but the question is how we're going to implement it in terms of an interface. I don't think we'll be able to implement it in the form of a button/dropdown menu to change between the regular view and the anomaly. That's because there is not a full overlap in the legends between the two views. I think we'll need to create a separate tool for this. |
I see your point. Could a solution be to add a button on the original interface that switched to another tool page with a similar layout? That is, a button that works as a URL link to a different page. In this way, we could keep it simple with only the daily and monthly entrances. But with the buttons to switch between absolute and anomaly plots. Maybe this does not make sense or is not possible... |
Notes from last meeting: try to implement the anomaly view inside the existing tools for daily and monthly time series by using a dropdown/selection tool. |
Anomaly plots have now been added for daily plots in #148. Monthly anomalies are TBD. |
In the anomaly plot, the Hover tool:
|
While testing the monthly anomaly plots, we realized C3S and others usually show the Relative Anomaly (%) not the Anomaly. Anomaly [km^2]= Value - MonthlyMean Relative Anomaly [%] = 100 * (Value - MonthlyMean) / MonthlyMean We can thus develop 3 types of graphs: 1) Absolute values, 2) Anomalies, 3) Relative Anomalies. This is valid for daily and monthly plots. |
For next development, it would be very useful to add the option of showing anomaly wrt 1981-2010 (or 1919-2020). It should be relatively "straight forward" I think ...(?)
The text was updated successfully, but these errors were encountered: