|
1 | 1 | # Gammapy Developer Meeting |
2 | | - * Friday, August 29, 2025, at 2 pm (CET) |
| 2 | + * Friday, August 29, 2025, at 2 pm (CET) approx. 14:05-15:17 |
3 | 3 | * Gammapy Developer Meeting on Zoom (direct link on Slack) |
| 4 | + |
| 5 | +Attendees: Leander Schlegel (LS), Tomas Bylund (TB), Aritra Gupta (AG), Régis Terrier (RT), Daniel Morcuende (DM), Kirsty Feijen (KF), Atreyee Sinha (AS), Mattias Fuessling (MF) |
| 6 | + |
4 | 7 | # Agenda |
5 | 8 | ## General information |
6 | 9 |
|
| 10 | +### v2.0 release status |
| 11 | +RT reports: |
| 12 | +Release made last Tuesday (August 26), AS made most of the work. |
| 13 | + |
| 14 | +Overall went fine. Validation and benchmarks scripts used for the released version were also tagged. |
| 15 | + |
| 16 | +The instructions for making the final full release did not contain the step where `dev/prepare-release.py` is run, and consequently some metadata for the release is incomplete. |
| 17 | + |
| 18 | +The automatic adding of the new version to Zenodo failed, so will have to be done manually. |
| 19 | +Bruno has done this before and back then contacted Zenodo team for this. |
| 20 | + |
| 21 | +RT: Has someone already installed and checked that everything is okay with release? |
| 22 | + |
| 23 | +DM confirms for mamba. |
| 24 | + |
| 25 | +RT: All steps are now checked and we should announce the new version. |
| 26 | + |
| 27 | +AS: Should make sure mails are sent to VERITAS, MAGIC, HAWC, SWGO, need to find people who can send to their mailing lists. |
| 28 | + |
| 29 | +RT: Have to prepare text for announcement mails. After mails are sent, there should be celebrations. |
| 30 | + |
| 31 | +### Reflections on the new release |
| 32 | +RT: It was a long time to make this release, probably the roadmap was too ambitious. |
| 33 | + |
| 34 | +AS: Gabriel Emery was missed for the contributor list somehow, but he is in the author list. Unclear how this happened. Is it worth to update the docs to ensure he is included? |
| 35 | +RT: Probably not before next bugfix as manually rebuilding the docs is complicated, as it will be fixed soon probably in any case. |
| 36 | + |
| 37 | +### Introduction of AG: |
| 38 | + |
| 39 | +AG introduces themselves: Research on phenomenology of dark matter (theory), accretion od DM in compact objects (neutron stars, white dwarfs). Aim to understand and help on DM frontier with gammapy. |
| 40 | + |
| 41 | + |
| 42 | +-Theory background: |
| 43 | +In models, DM could be thermalized or non-thermalized. Dark sector with 1 particle, major portion of DM today is non-rel/cold. DM models provide: Velocity averaged annihilation cross-section for annihilation of DM and DM mass. The DM annihilates into standard particles, that go into pions and finally gamma rays. Different models exist (e.g. with dark sector). Possible that no annihilation at threshold is expected, missing in most codes today. |
| 44 | + |
| 45 | +-Possible observations: Diffuse flux or smoking gun signatures in form of lines. Line signatures require good calculation of background, but models that provide line predictions are interesting. |
| 46 | +In non-thermal DM we can not rely on direct detection. Line sig. and diffuse photon flux give opportunity for DM frontier (???) |
| 47 | + |
| 48 | +We did work which predicts neutrino line, it would be very interesting to see how to work on it from observation side. |
| 49 | + |
| 50 | +Would like to help with these points for DM. |
| 51 | + |
| 52 | +RT: Very interesting view. We include some tables that have part of the channels. Question if we should provide models directly in Gammapy or simply create an interface into which theorists could insert their models. |
| 53 | +View as developer: We have had contributions for DM at points, but difficult to get a team in the long run set on DM |
| 54 | +Dark matter analysis could also be interesting topic for a User call, could try to have one before the end of the year. |
| 55 | + |
| 56 | +AS: I'm sure there will be enough people interested. |
| 57 | + |
| 58 | +RT: We have number of feature requests related to DM (e.g. #5734, #5359, #4776). Main question is how to organize, what should be there, how to connect with external things like new models. Maybe we could create parent-discussion to gather all this. |
| 59 | + |
| 60 | +AS: We create a new project for DM? |
| 61 | + |
| 62 | +RT: Yes is good idea, just not clear how to organize in the moment/what to put in. Some things connected to modelling, some to analysis, estimators. |
| 63 | + |
| 64 | +AG: Brainstorming: We could ask users, if thermal or non thermal models, heavy, light DM. Theoretical parameters would then be input to our code, that predicts fluxes. In every case different input needed. With this we take out the theory parts for the observational/experimental side of the code. |
| 65 | + |
| 66 | +RT: Not sure if/how to implement in gammapy option dependent on some parameters. But should define how to interface codes, could be simpler way to work. Maintaining on long term for DM models we probably can not do. |
| 67 | +Then model production would be left to dedicated codes, but we agree how to interface with Gammapy. |
| 68 | +Let's organize user-call on this and contact people, who contributed on this in the past. |
| 69 | + |
| 70 | +AS: Next user-call probably in November. |
| 71 | + |
| 72 | +RT: Should be okay, more important, that most people related to it are around. |
| 73 | + |
| 74 | +AG: I can take a look at open issues and try to fix them. |
| 75 | + |
| 76 | +### Organising the development cycle |
| 77 | +RT: Try to establish main projects that drive the timing of the release cycle. |
| 78 | +We could discuss among all devs. |
| 79 | +Need to think more carefully about how to set milestones for PRs and issues, there has been tendency to simply bump things to next available milestone but this means no prioritization is being done. Should start to put things into wishlist by default and only milestone things after performing a prioritization. Should go through features in next dev call to discuss. Will put most into wishlist. |
| 80 | + |
| 81 | +MF: Congratulations to Gammapy 2.0! We will give you room to present this release in depth at October CTAO-meeting and hope some of you that worked hard on it, can be there. |
| 82 | +Should make sure this leads to a proper release of the Science Analysis Tools, which would be a major milestone for the Science tools work package. |
| 83 | +Reminds us that the SAT is supposed to serve for the science data challenge, in particular Gammapy 2.1 will be used to generate the simulation for the SDC, and so it is important to check ahead of time that all features needed for the SDC are present in Gammapy. We will discuss with David Green next week about the list of science cases in order to give input for the planning of release 2.1 during the first weeks of the new development cycle. |
| 84 | + |
| 85 | +### Next user call |
| 86 | +AS: Can I announce 22.9 for the next User-Call? I asked QR and FP. |
| 87 | + |
| 88 | +RT: Yes, perfect. |
| 89 | + |
| 90 | +RT: Thats all for today, thank you and have a nice week. |
| 91 | + |
7 | 92 | ## Open issues |
8 | 93 |
|
9 | 94 | ## Bugs |
|
21 | 106 |
|
22 | 107 | ### MWL |
23 | 108 |
|
24 | | -## Any other buisiness |
| 109 | +## Any other business |
25 | 110 |
|
26 | 111 | # Automatic activity report |
27 | 112 |
|
|
0 commit comments