AusClimateService / AusClimateService/npcp
AGCD/AWRA time alignment
- Dominant language
- Jupyter Notebook
- Stars
- 2
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
From the AWRA v7 [technical report](https://awo.bom.gov.au/assets/notes/publications/AWRA-Lv7_Model_Description_Report.pdf) (page 9):
The following notation is used for the climate forcing in the AWRA report:
- ππ Daily gross precipitation to 9am local time (mm)
- πΎπ Daily downwelling shortwave (solar) radiation midnight to midnight (MJ mβ2 dβ1),
- π’2 Wind speed at a height of 2 m to 9am (m/s)
- ππ Actual vapour pressure (Pa)
- ππππ Daily minimum air temperature to 9am local time (Β°C), and
- ππππ₯ Daily maximum air temperature from 9am local time (Β°C)
AWRA-L calculates the water balance between 9 am of the day before to 9 am of its timestamp, predominantly to align with the observational (AGCD) period of rainfall. However, the (AGCD) minimum and maximum temperature of a given date corresponds to two differing 24-hour periods (the minimum value corresponds to the 24 hours before 9 am and the maximum temperature corresponds to the 24 hours after 9 am). Further, the solar measurements are the average values from midnight to midnight for a given date, with daylight predominantly aligning with the 24 hours ending 9am the following day. The actual vapour pressure is measured at 9 am and 3 pm, and we use a weighted average of these values to correspond to the day following 9am. As a result, when the AWRA system reads in the input data files times are shifted as follows to represent the 24 hours to 9am used to timestamp AWRA-L outputs:
β’ ππ β as is (dated same as AWRA-L outputs)
β’ πΎπ β shift forwards 1 day
β’ ππππ₯ β shifted forwards 1 day
β’ ππππ β as is (dated same as AWRA-L outputs)
β’ π’2 β as is (dated same as AWRA-L outputs)
β’ ππ β shifted forwards 1 day
The shifting of ππππ₯ and πΎπ was implemented for the first time in AWRA-L v7 to fit with the 9 am to 9 am day.
UPSHOT: We should use these time shift when working with both AGCD and AWRA data files.
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are identified. Start by locating the notebooks or input-reading code that handles AGCD and AWRA data, then trace how each forcing variable is timestamped. Done means both data sources consistently apply the documented shifts for Kd, Tmax, and pe while leaving Pg, Tmin, and u2 unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- jupyter-notebook
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100