link: https://hackmd.io/@bsipocz/numpy2_bof
Give us feedback on the release of NumPy 2.0! Please tell us things that you think we did well and things we did wrong or could have done better.
Notes
changes in packagingDealing with numpy.distutils removal
Comparison example project with meson-python
deep water with meson co-aligning with numpy 2.0
🔧 More meson-python docs!
CI issues due to dependencies not rebuilding with NumPy 2.0
Monday
Summary of state of IVOA/CSP/TCG
Couple of mentions of new astroquery modules that I was not aware of (e.g. SKA)
CSP activities may be of interest of the group (Vandana is part of the committee). Typical topics:Basically all lessons leared and difficulties we run into with the archives/data providers could be propoagated back through this group.
Typical topics of discussions from previous interopsbig data accessVO friendly parquet
cloud usage inclusion in e.g. SIA results
wider TAP adoption
Heliophysics API
Projects (if moved, keep the location updated)
Package
Room
Contact person
link to repo, other info: keep it short
in person interest add +
fastplotlib
201 slack: #fastplotlib-sprint
Kushal Kolar, Caitlin Lewis
Matt Craig changed 2 years agoEdit mode Like Bookmark
Package
Room
Contact person
link to repo, other info: keep it short
in person interest add +
cadCAD: Dynamical Systems Simulation in Python
211
Emanuel Lima
cadCAD
Dave Clements changed 3 years agoView mode Like Bookmark
Generic comments
Link often to "upstream" resources. Whether it is stats resources or programming or tutorials. Maybe add a section at the bottom/top of all the notebooks?
Some packages have steeper learning curves than others. Definitely link to their "getting started" tutorials, e.g. pymc3, but also we should link to scikit-learn's MOOC and the numpy tutorials, Jake's book, rather than try to cover all that material on our own.
chapter1 -- Introduction
datasets
Datasets are described when used in later notebooks, if repetition is preferred, a notebook going through all the datasets
Org
[x] Delete/disable org-wide Travis CI app (need org admin access) : Matt Craig sent announcement; Erik Tollerud will disable in Jan 2021.
[x] Will this really automatically prevent Travis CI from running in all the repos in the org?
[x] What if we decided to re-enable Travis CI but only for certain repos? (Unlikely to happen at this point but what about older core releases?)
Core
[ ] astropy (core)
P. L. Lim changed 4 years agoEdit mode Like Bookmark
2021-02-04
Plan:
write astroquery dev section 6.4, section 6.7, verbatim from paper can be then removed
triage m-dwarf selection section 3.1
2012-02-09
plan:
extend the draft points to full text for common API and CD/CI sections, 6.2 & 6.3, finish 6.4