pyDARN Dev Ops Meeting April 15, 2021
Date: April 15, 2021
Attendees:
- Marina Schmidt (Lead Developer)
- Carley Martin (Scientist and developer)
- Daniel Billett (Scientist and developer)
- Devin Huyghebeart (Scientist and tester)
- Emma Bland (Scientist, DAWG Chair, tester)
- Pasha Ponermeranko (Scientist)
- Shane Coyle (Scientist, Developer)
No comment- keep as is
- rxrise is dependent on the PI to update hardware files. RST fills in this value that may be unreliable as we don't know why this is the case. pyDARN will use the hardware file rxrise.
- frang should be the center of the gate but is coded as the edge of the grate and measured at the front of the gate at SuperDARN Canada. Further work needs to be done before confidently defining this. For now pyDARN will follow the coded way in RST, edge of the gate.
- 2.1 branch is to be open for review by May 14
- The goal is to have 2.1 released before the workshop
- 3.0 will include cartopy that Shane Coyle from VT has been working on as it requires a bigger install dependency
Concern on hard-coding the numbers in as they may change. The change is very unlikely and this a temp fix while DSWG is currently on hold to standardizing hardware files. Currently, the issue is the hardware files are not consistent on the number of range gates as this depends on the mode. SuperDARN Canada radars use 15 km mode and other use 45 km for filling in this value. Thus this causes an issue with generating the FOV for grid plotting and convection maps. Because GRID and MAP files do not contain nrang and rsep values the FOV can not be displayed as the data file contains. Thus hard coded 45 km nrang values are in the SupeDARNRadars radars table to allow a check to be done if the user asks for too many range gates and so a general FOV can be done up for other types of plots.