2019_10_23 - pysat/pysat GitHub Wiki
Agenda: Angeline (notes), Jeff (chair), Russell, and Asher in attendance.
- Big Picture
- HDEE updates:
- Jonathon Smith was selected for adding ground based instruments to pysat
- Jeff Klenzing was on a proposal that was selected related to GEMINI
- 2.1.0 vs 3.0.0
- Jeff added separate development branches for the 2.X and 3.0 releases
- Logging (2.1 or 3.0?)
- What happens the first time someone runs pysat? <- use
printhere instead oflogging
- What happens the first time someone runs pysat? <- use
- Setting default directory
- How and when should this be set? The first time
pysatis run or the first time data is downloaded? - We need to throw an error if people try to download data when a default directory has not been set.
- Should require some changes in Travis-CI.
- There are bugs when hidden files haven't been created yet, but are needed.
- How and when should this be set? The first time
- HDEE updates:
- The Road to 2.1.0
- Goals
- Push out bug fixes for multiple instruments
- Flag everything with Deprecation Warnings to alert community to changes for 3.0.0
- Bugfixes in metadata/attributes?
- Metadata access (#274 / #311) in 2.1.0? Yes
- Metadata keep (#275 / #314) in 2.1.0? Yes
- Netcdf meta (#276 / #302) to 3.0.0? Changes attribute name <- Keep in 2.1.0 for now.
- Import pysatSeasons and pysatModelUtils? No, just add deprecation warnings.
- Extent of Deprecation Warnings? Have import of model_utils issue a deprecation warning and test that.
- Instrument updates - #123 and #183 (send to 2.2), #292 to 3.0.0 (also to 2.2)?
- Goals
- The Road to 3.0.0
- Instrument Independence
- Remove ssnl and model_utils? Yes
- File tracking (#48)?
- Monthly / yearly data (#58)?
- Scipy NaN circular stats have been merged into scipy and the next release will be sometime in December.
Next meeting is 13 November 2019, ideally we will have released 2.1.0 at or before this date.