Skip to content

Commit 5fb12ca

Browse files
authored
Update README.md
1 parent 851fa8d commit 5fb12ca

File tree

1 file changed

+47
-2
lines changed

1 file changed

+47
-2
lines changed

dev-meetings/2025/2025-08-22/README.md

Lines changed: 47 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,53 @@
11
# Gammapy Developer Meeting
22
* Friday, August 22, 2025, at 2 pm (CET)
3-
* Gammapy Developer Meeting on Zoom (direct link on Slack)
3+
* Gammapy Developer Meeting on Zoom (direct link on Slack)
4+
5+
Attendees: Régis Terrier (RT), Bruno Khélifi (KF), Atreyee Sinha (AS), Tomas Byland (TB), Kirsty Feijen (KF), Axel Donath (AD)
6+
47
# Agenda
58

9+
Discussion on testing of gammapy 2.0rc1. AS has had the opportunity to browse the docs and run some analysis.
10+
- No immediate issues seen.
11+
- BK says that binder for some tutorial is not working. Made a test on the dev doc.
12+
13+
14+
RT ran the benchmarks/validations and most of them look relatively consistent.
15+
- one extra data point in the crab/plots_flux-points-1d.png (BK: extra point is outside the energy range of the model, could it be a mask fit?)
16+
- appears that this relates to having the upper limit vs not. Value previously was nan and now it is 8e-17. It could be to do with the change by Quentin.
17+
- RT: doing better with the upper limits but it still needs work
18+
- now we have a result for the lightcurve (which previously we had a plotting issue)
19+
- RT: looks like we are okay with the validations we we will merge this
20+
21+
22+
We should add some further information to the release notes (RT).
23+
24+
#6095 can be added in for v2.0 - KF just some simple adjustments to the docs. By adding plt.show it avoid having the axes being returned in the tutorials as well.
25+
26+
#6106 was merged to avoid the warning in the analysis-3d tutorial. RT is should be fine because we only use this in one instance, so a simple fix is prefered. We don't gain enough to create our own method (AS)
27+
28+
29+
#6108 should be postponed to v2.1
30+
31+
#6105 is the last thing for v2.0. We merged this as it is a small note about sherpa (RT,AS).
32+
33+
Discussion about the requirement file for the pip installation (BK, #6091).
34+
- Need to decide if we do this or not (RT). We had recent questions about astropy7.1 being installed and things being broken, also similarly with matplotlib, so it could be useful to have this file (RT).
35+
- Need to decide where we could put this info in the docs if we decide to add it (RT). It can be mentioned in the getting-started with the pip install (AS). We should kept it simplictic there but rather add something to the "Using pip" section (RT). It makes sense to have it in this section (KF).
36+
- It doesn't show that you should create an env and then install, so we could show the uses how to do that (RT).
37+
- Should we really include this, it seems to make more effort for us to maintain this (AD). By now the convention is log files to have a reproducable env (AD). We don't want a reproducable env, we would like the user to install without incompatibilities (RT).
38+
- It is unclear whether is worth doing this because really a "pip install gammapy[all]" should work for all, and we should have the setup.cfg better setup to work for that (AD). The same could also be said for the use of conda. Don't see how future versions wont break if we use this method with setup.cfg (RT).
39+
- In the end, if we keep the requirements.txt as the same as the conda env file then we could go ahead as this is a small effort (AD). Recommend to stay as is for now, but gradually move towards using pixie and uv (AD).
40+
- We should create a discussion on this
41+
42+
We don't need a second release candidate. We can go ahead now that everything is okay.
43+
44+
Binder is not working (BK). It could be because they do not work on the dev or pre-releases (RT, AD). We should be able to get it working for each version, by default defining an env that uses the dev version, then adjust as needed, on release change it to the version and add the tags (AD).
45+
46+
47+
We should announce a user call in line with v2.0 around mid September (AS, RT). Could include the new MCMC and bayesian, and also the new Fermi analysis, we can ask Fabio and Quentin for that (AS). After September 22nd.
48+
49+
50+
651
### PRs opened last week (less than 8 days ago):
752
* [#6102](https://github.com/gammapy/gammapy/pull/6102) jfactory integral calculation description - Kirsty Feijen
853
* [#6097](https://github.com/gammapy/gammapy/pull/6097) Update release.rst after 2.0 release - Atreyee Sinha
@@ -42,4 +87,4 @@
4287
### issues opened last week (less than 8 days ago):
4388
* [#6091](https://github.com/gammapy/gammapy/issues/6091) Post 2.0rc1 update and remaining PRs - Bruno Khélifi
4489

45-
report created at 22/08/2025, 07:22:54
90+
report created at 22/08/2025, 07:22:54

0 commit comments

Comments
 (0)