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
We'd like to shift the plan2adapt baseline climatology from 1961-1990 to 1971 - 2000. PCIC's standard baseline climatology is now 1971-2000. The percentileanomaly API lets the user specify whatever baseline they want as long as that baseline is present in the stored queries, and we have a full set of 1971-2000 anusplin data, so the main issue is changing what baseline we have stored queries for.
I think the smoothest way to do this would be to modify the stored query script to allow it to store results for both baselines. Then we'd have a period where the backend could provide either baseline upon request, and we could seamlessly switch the front end whenever it made sense to.
The text was updated successfully, but these errors were encountered:
We'd like to shift the plan2adapt baseline climatology from 1961-1990 to 1971 - 2000. PCIC's standard baseline climatology is now 1971-2000. The
percentileanomaly
API lets the user specify whatever baseline they want as long as that baseline is present in the stored queries, and we have a full set of 1971-2000 anusplin data, so the main issue is changing what baseline we have stored queries for.I think the smoothest way to do this would be to modify the stored query script to allow it to store results for both baselines. Then we'd have a period where the backend could provide either baseline upon request, and we could seamlessly switch the front end whenever it made sense to.
The text was updated successfully, but these errors were encountered: