|
2 | 2 | * Friday, June 20, 2025, at 2 pm (CET) |
3 | 3 | * Gammapy Developer Meeting on Zoom (direct link on Slack) |
4 | 4 |
|
| 5 | +## Participants |
| 6 | +(Zoom display names, zoom chosen order) |
| 7 | +Bruno Khelifi, Tomas Bylund, Natthan Pigoux, Quentin Remy, Atreyee Sinha, Fabio Pintore, Daniel Morcuende, Kirsty Feijen, Fabio Acero, Hanna Stapel, Axel Donath, Jean-Philippe Lenain, Régis Terrier, Samantha Wong. |
| 8 | + |
5 | 9 | # Agenda |
6 | 10 |
|
7 | 11 | ### SAT IKC latest news |
|
21 | 25 | - MWL |
22 | 26 | - AoB |
23 | 27 |
|
| 28 | +### Documentation |
| 29 | +* There were a number of PRs opened (some merged) in a general clean up of the documentation |
| 30 | +* We should make a decision on the following: |
| 31 | + * Proposal for re-ordering the tutorials [#5796](https://github.com/gammapy/gammapy/issues/5796) |
| 32 | + * Removing the setup in every tutorial [#5816](https://github.com/gammapy/gammapy/issues/5816) |
| 33 | + |
| 34 | +### Features |
| 35 | +* How to support the default plot labels [#5894](https://github.com/gammapy/gammapy/pull/5894) |
| 36 | +* How to correctly test the stacking functionality for LightCurveEstimator [#5898](https://github.com/gammapy/gammapy/pull/5898) |
| 37 | + |
| 38 | +# Minutes |
| 39 | +## SAT IKC latest news |
| 40 | +* Bruno presented news about the CTAO Science Analysis Tools project. |
| 41 | +* Bruno reminded the meeting that the In kind contribution includes two year of bug fixes after the hand-over of the tools. |
| 42 | +* Formally there are 38 FTEs in the project, but by Bruno's count there are currently around 42 FTEs already used up and experience tells us that the work needed is frequently underestimated. |
| 43 | +* Bruno showed a release plan |
| 44 | + |
| 45 | + * SAT release 0 to happen by September 30 in 2025 |
| 46 | + |
| 47 | + * SAT release 1 to happen by January 31 in 2026 |
| 48 | + |
| 49 | + * Final acceptance release to be delivered by end of September 2027 |
| 50 | + |
| 51 | +* Bruno suggests that the release plan should be aligned with the IKC review process |
| 52 | +* Bruno suggests we start working on defining a project dedicated to the maintenance and upgrade of the SAT |
| 53 | +* Bruno warns that there is a coming cost in terms of work on the verification documentation. |
| 54 | +* Bruno provides an overview of work defining the VOD format |
| 55 | + |
| 56 | +### Questions |
| 57 | +* Quentin asked who would provide for the science data challenge, would the Gammapy devs have to provide this? Bruno says this is a good question, not clear how it will work but CTAO will somehow provide support. |
| 58 | +* After a question from Quentin, Daniel clarifies that the SAT will mostly be an import of gammapy that lives in and is managed via gitlab with additional CTAO-specific documentation and possibly some additional functionalities. The plan is being worked out, discussed and will be presented to CTAO Computing. They have to approve it. |
| 59 | +* Atreyee asks if this includes if also the documentation should be hosted on gitlab, Daniel answers yes. |
| 60 | +* Atreyee asks what happens with user questions. Daniel answers that it is not clear at the moment. Bruno remarks that this is a good example of an issue that would be resolved by an IKC agreement covering support and future upgrades. |
| 61 | +* In a discussion following a question Atreyee it is highlighted that there is a risk that the Gammapy version accepted, and required to be supported for 2 years, could end up out of step with the Gammapy LTS releases, requiring the support of two separate LTS releases! Another reason to create a IKC agreement covering support. |
| 62 | +* Atreyee asked a further question I was not able to record |
| 63 | + |
| 64 | +## VERITAS tutorial |
| 65 | +* Samantha presents her draft tutorial showing VERITAS users how to use gammapy to make a real analysis |
| 66 | +* Samantha found she needs to use a local star catalogue file, because queries to Simbad tended to crash; this filed would be hosted in gammapy-data. |
| 67 | +* Still some questions regarding licensing left to be clarified, but Samantha is not expecting any problems and think that it will be resolved today. |
| 68 | +* Regis remarks that it is anyway good practice to not have network lookups in the documentation because that regularly causes CI jobs to fail when the lookups timeout. |
| 69 | +* Samantha reports she is working a bit on getting the VERITAS catalogue uploaded. |
| 70 | +* Atreyee remarks that the star masking part of the tutorial could be moved into a separate function in gammapy utils. |
| 71 | + |
| 72 | +## Bugs overview |
| 73 | +* Fabio reports that the issues regarding linked parameters in sampled models have been understood and PRs resolving them have been merged. |
| 74 | +* Atreyee volunteers to take a look at the open issues and make sure any bugs get assigned |
| 75 | + |
| 76 | +## Documentation overview |
| 77 | +* Kirsty reports that several PRs about documentation have been created, some of which has been merged. |
| 78 | +* In the discussion about whether the tutorials should reordered, Regis stated he thinks the reorder should happen in time for version 2.0 |
| 79 | +* The decision for the new structure is postponed to next week |
| 80 | +* Kirsty asks if the `check_setup()` part of every tutorial really _needs_ to be part of precisely every tutorial. After much discussion the conclusion is it is kept (the `check_setup` command automatically downloads the gammapy data if it is missing). It is further suggested that `gammapy info` could print a message along the lines of "congratulations, everything works". |
| 81 | +* Kirsty highlighted #5922 where `inter_kwargs` are used for two different purposes, which makes it unclear how to document it. |
| 82 | +* Atreyee shows the new tutorial on upper limits. It was concluded that it would be more appropriate to split the tutorial into two different tutorials. |
| 83 | + |
| 84 | +## Project management |
| 85 | +* Regis has created a [project on github for coordinating the work remaining on Gammapy 2.0](https://github.com/orgs/gammapy/projects/30/views/1). He highlights the need to start working on the changelog and the authorlist now. |
| 86 | + |
| 87 | +## Activity report |
| 88 | + |
24 | 89 | ### PRs opened last week (less than 8 days ago): |
25 | 90 | * [#5936](https://github.com/gammapy/gammapy/pull/5936) Update of the user guide documentation of `Modelling and Fitting` - Bruno Khélifi |
26 | 91 | * [#5934](https://github.com/gammapy/gammapy/pull/5934) Estimator documentation: update the n_sigma description - Bruno Khélifi |
|
58 | 123 | * [#5920](https://github.com/gammapy/gammapy/issues/5920) EventList created with default constructor cannot be printed - Tomas Bylund |
59 | 124 | * [#5917](https://github.com/gammapy/gammapy/issues/5917) Remove deprecations for v2.1 - Régis Terrier |
60 | 125 |
|
61 | | - report created at 20/06/2025, 07:24:22 |
62 | | - |
63 | | - |
64 | | - |
65 | | -### Documentation |
66 | | -* There were a number of PRs opened (some merged) in a general clean up of the documentation |
67 | | -* We should make a decision on the following: |
68 | | - * Proposal for re-ordering the tutorials [#5796](https://github.com/gammapy/gammapy/issues/5796) |
69 | | - * Removing the setup in every tutorial [#5816](https://github.com/gammapy/gammapy/issues/5816) |
70 | | - |
71 | | -### Features |
72 | | -* How to support the default plot labels [#5894](https://github.com/gammapy/gammapy/pull/5894) |
73 | | -* How to correctly test the stacking functionality for LightCurveEstimator [#5898](https://github.com/gammapy/gammapy/pull/5898) |
|
0 commit comments