diff --git a/CoC.html b/CoC.html index 3bb8c42..aa9ce03 100644 --- a/CoC.html +++ b/CoC.html @@ -1,154 +1,76 @@ - - - - - - - - - Gammapy - Contribute - - - - - - - - - - - - -
-
-

Gammapy Community Code of Conduct

-

- -

- Gammapy is committed to fostering an inclusive community. -

- -

- Aside from the actual code, Gammapy is also a community of users and developers. This community is central - to accomplishing anything with the code itself. We welcome anyone who wishes to contribute to the project - and expect everyone in our community to follow this code of conduct when interacting with others. -

- -

As members of the community,

- - - -

- This code of conduct applies to all community situations online and offline, including mailing lists, forums, - social media, conferences, meetings, associated social events, and one-to-one interactions. This Code of - Conduct have been mostly re-used from the Astropy code of conduct. -

- -

-

In order to report any information or issue, please contact the Gammapy Coordination Committee using its - generic email, gammapy-coordination-l@in2p3.fr, or any - member of the Coordination Committee (see its composition here). -

-
-
- - - - - - - - - - + + + + + + + + Gammapy - Contribute + +
+ + + + +
+
+

Gammapy Community Code of Conduct

+

+

+ Gammapy is committed to fostering an inclusive community. +

+

+ Aside from the actual code, Gammapy is also a community of users and developers. This community is central + to accomplishing anything with the code itself. We welcome anyone who wishes to contribute to the project + and expect everyone in our community to follow this code of conduct when interacting with others. +

+

As members of the community,

+ +

+ This code of conduct applies to all community situations online and offline, including mailing lists, forums, + social media, conferences, meetings, associated social events, and one-to-one interactions. This Code of + Conduct have been mostly re-used from the Astropy code of conduct. +

+
+
+
+

In order to report any information or issue, please contact the Gammapy Coordination Committee using its + generic email, gammapy-coordination-l@in2p3.fr, or any + member of the Coordination Committee (see its composition here). +

+
+
+ + + + + \ No newline at end of file diff --git a/about.html b/about.html index d803caf..485192e 100644 --- a/about.html +++ b/about.html @@ -1,219 +1,126 @@ - - - - - - - - - - - - Gammapy - About - - - - - - - - - - - -
- -
-

About

-
- -

- - What is Gammapy? | Publications | Awards and Prizes -

- -
-
-

What is Gammapy?

-

- Gammapy is an open-source Python package for gamma-ray analysis built on Numpy and Astropy. -

-

- It is used as core library for the Science Analysis Tool of Cherenkov Telescope Array (CTA), and can be used to analyse data - from existing gamma-ray telescopes. -

-

- Gammapy is a community-developed, open-source Python package for gamma-ray astronomy. - It is an in-development affiliated package of Astropy that builds on the core scientific - Python stack to provide tools to simulate and analyse the gamma-ray sky for telescopes - such as CTA, H.E.S.S., VERITAS, MAGIC, HAWC and Fermi-LAT. - Gammapy is a place for Python-coding gamma-ray astronomers to share their code and collaborate. - Feature requests and contributions welcome! - Likelihood fitting of the morphology and spectrum of gamma-ray sources (using Sherpa), - including multi-mission joint likelihood analysis and physical SED modeling (using Naima) - is one important feature we’re working on. But Gammapy has a broader scope, we currently - have code e.g. for data handling, background modeling, source detection, easy access to c - ommonly used datasets and catalogs, statistical methods, even simulating Galactic source - populations. -

- - -
-

- When using Gammapy for your publication, please follow the citation scheme presented in the - acknowledgment page in order to support the - Gammapy team. - -

- - + + + + + + Gammapy - About + +
+ + + + +
+
+

About

+
+

+ + What is Gammapy? | Publications | Awards and Prizes +

+
+
+

What is Gammapy?

+

+ Gammapy is an open-source Python package for gamma-ray analysis built on Numpy and Astropy. +

+

+ It is used as core library for the Science Analysis Tool of Cherenkov Telescope Array (CTA), and can be used to analyse data + from existing gamma-ray telescopes. +

+

+ Gammapy is a community-developed, open-source Python package for gamma-ray astronomy. + It is an in-development affiliated package of Astropy that builds on the core scientific + Python stack to provide tools to simulate and analyse the gamma-ray sky for telescopes + such as CTA, H.E.S.S., VERITAS, MAGIC, HAWC and Fermi-LAT. + Gammapy is a place for Python-coding gamma-ray astronomers to share their code and collaborate. + Feature requests and contributions welcome! + Likelihood fitting of the morphology and spectrum of gamma-ray sources (using Sherpa), + including multi-mission joint likelihood analysis and physical SED modeling (using Naima) + is one important feature we’re working on. But Gammapy has a broader scope, we currently + have code e.g. for data handling, background modeling, source detection, easy access to c + ommonly used datasets and catalogs, statistical methods, even simulating Galactic source + populations. +

+
+

+ When using Gammapy for your publication, please follow the citation scheme presented in the + acknowledgment page in order to support the + Gammapy team. +

+ +

+

Publications

-

-

- We provide the following as a standard acknowledgment you can use if there is not - a specific place to cite the paper: -

-

- "This research made use of Gammapy, a community-developed core Python package for - gamma-ray astronomy (Deil C., et al. - 2017)" -

- -

In Presentations

-

If you are giving a presentation or talk featuring work/research that makes - use of Gammapy we would like to ask you to acknowledge Gammapy by using this logo -

Gammapy banner

-

--> - -

-

Publications

-
    -
  • A&A, 678, A157 (2023) - - “Gammapy: A Python package for gamma-ray astronomy ” -
    • -
  • A&A, 632, A72 (2019) - - “Validation of open-source science tools and background model construction in γ-ray astronomy” -
    • -
  • A&A, 625, A10 (2019) - - “Towards open and reproducible multi-instrument analysis in gamma-ray astronomy” -
    • -
  • 2017ICRC...35..766D - - “Gammapy - A prototype for the CTA science tools” -
    • -
  • 2015ICRC…34..789D - - “Gammapy: An open-source Python package for gamma-ray astronomy” -
    • -
- -

The full list of publications using Gammapy can be found with this - - link. -

- -

-

Awards and Prizes

- - - -
-
- -
-
-

© Gammapy project

-
- - - - - - - - - - - - - - - - - - +

+ The full list of publications using Gammapy can be found with this + + link. +

+

+

Awards and Prizes

+ +
+
+ + + + + \ No newline at end of file diff --git a/acknowledging.html b/acknowledging.html index 007a2b3..8c30bcc 100644 --- a/acknowledging.html +++ b/acknowledging.html @@ -1,122 +1,51 @@ - - - - - - - - - - - - Acknowledging or Citing gammapy - - - - - - - - - - - - - - - - - -
+ + + + + + + - - - - - - - - -
-
- -

Acknowledging or Citing gammapy

-
- -

- In publications | In presentations | In projects -

- -

-

In publications

-

- If you use Gammapy for work or research presented in a publication (whether directly, or as a dependency to - another package), we ask you to add two citations to Gammapy: -

- - - -
-
-

In presentations

-

- If you are giving a presentation or talk featuring work/research that makes use of Gammapy, we suggest - using this logo on your title slide: -

- - - -


-
-

In projects

-

- If you are using Gammapy as part of a code project (e.g., affiliated packages), a useful way to acknowledge - your use of Gammapy is with a badge in your README. We suggest this badge: -

- - -

- Which is available at the URL - https://img.shields.io/badge/powered%20by-gammapy-orange.svg?style=flat. -

- -

- If your code is hosted on GitHub, you can place the following in your README.md file to get the badge: -
- [![gammapy](https://img.shields.io/badge/powered%20by-gammapy-orange.svg?style=flat)](https://www.gammapy.org/) -

-
-
- -
- - - - - - - - - - + title = "{Gammapy - A prototype for the CTA science tools}", + keywords = {Astrophysics - Instrumentation and Methods for Astrophysics}, + booktitle = {35th International Cosmic Ray Conference (ICRC2017)}, + year = 2017, + series = {International Cosmic Ray Conference}, + volume = {301}, + month = jan, + eid = {766}, + pages = {766}, + archivePrefix = {arXiv}, + eprint = {1709.01751}, + primaryClass = {astro-ph.IM}, + adsurl = {https://ui.adsabs.harvard.edu/abs/2017ICRC...35..766D}, + adsnote = {Provided by the SAO/NASA Astrophysics Data System} + } +

+ + + +
+
+

Acknowledging or Citing gammapy

+
+

+ In publications | In presentations | In projects +

+

+

In publications

+

+ If you use Gammapy for work or research presented in a publication (whether directly, or as a dependency to + another package), we ask you to add two citations to Gammapy: +

+ + +
+
+

In presentations

+

+ If you are giving a presentation or talk featuring work/research that makes use of Gammapy, we suggest + using this logo on your title slide: +

+ +


+
+

In projects

+

+ If you are using Gammapy as part of a code project (e.g., affiliated packages), a useful way to acknowledge + your use of Gammapy is with a badge in your README. We suggest this badge: +

+ +

+ Which is available at the URL + https://img.shields.io/badge/powered%20by-gammapy-orange.svg?style=flat. +

+

+ If your code is hosted on GitHub, you can place the following in your README.md file to get the badge: +
+ [![gammapy](https://img.shields.io/badge/powered%20by-gammapy-orange.svg?style=flat)](https://www.gammapy.org/) +

+
+
+
+ + + + \ No newline at end of file diff --git a/common-head.html b/common-head.html new file mode 100644 index 0000000..bd2e085 --- /dev/null +++ b/common-head.html @@ -0,0 +1,9 @@ + + + + + \ No newline at end of file diff --git a/contact.html b/contact.html index 0dd00f8..ebe9183 100644 --- a/contact.html +++ b/contact.html @@ -1,152 +1,70 @@ - - - - - - - - - - Gammapy - Contact - - - - - - - - - - - - -
-
-

Contact

-
-

This page lists the contact points and communication channels for Gammapy

- - -
-
- - - - - - - - - - + + + + + + + + Gammapy - Contact + +
+ + + + +
+
+

Contact

+
+

This page lists the contact points and communication channels for Gammapy

+ +
+
+ + + + + \ No newline at end of file diff --git a/contribute.html b/contribute.html index 7734844..63ae191 100644 --- a/contribute.html +++ b/contribute.html @@ -1,125 +1,41 @@ - - - - - - - - - Gammapy - Contribute - - - - - - - - - - - - -
-
-

Contribute

-
- -

Anyone is welcome to contribute to Gammapy !

- -

The Gammapy Project is made both by and for its users, so we welcome and encourage contributions of many kinds. Our goal is to keep this a positive, inclusive, successful, and growing community by abiding with the Gammapy Community Code of Conduct.

- -

Start by using Gammapy!! The "Getting Started" section of our documentation will give you the first steps. - Then if you notice a missing feature or issue, please report it (see contact page), - and if you are interested in contributing to the development, we can team you up with a mentor from the - Gammapy team to do it. -

- -

As developer, we can also contribute by presenting your activities into conferences, by making tutorial presenting recipies or by animating a Gammapy school or hands-on session. The list of contributions by type is given in the following list: -

-

-
-
- - - - - - - - - - + + + + + + + + Gammapy - Contribute + +
+ + + + +
+
+

Contribute

+
+

Anyone is welcome to contribute to Gammapy !

+

The Gammapy Project is made both by and for its users, so we welcome and encourage contributions of many kinds. Our goal is to keep this a positive, inclusive, successful, and growing community by abiding with the Gammapy Community Code of Conduct.

+

Start by using Gammapy!! The "Getting Started" section of our documentation will give you the first steps. + Then if you notice a missing feature or issue, please report it (see contact page), + and if you are interested in contributing to the development, we can team you up with a mentor from the + Gammapy team to do it. +

+

As developer, we can also contribute by presenting your activities into conferences, by making tutorial presenting recipies or by animating a Gammapy school or hands-on session. The list of contributions by type is given in the following list: +

+

+
+
+ + + + + \ No newline at end of file diff --git a/cta.html b/cta.html index d9dd415..2001c2c 100644 --- a/cta.html +++ b/cta.html @@ -1,176 +1,89 @@ - - - - - - - - - - - - Gammapy - CTA - - - - - - - - - - - - -
-
-

CTA

-
- -

- Introduction | Getting started | Resources -

- -

-

Introduction

-

- The Cherenkov Telescope Array (CTA) is the next generation - ground-based observatory for gamma-ray astronomy at very-high energies. - Gammapy was chosen on June 1st 2021 to be the official Science Analysis Tool library for the CTA Observatory (see CTAO news). -

-

- This page provides some information and links to useful resources concerning simulation and - analysis of CTA data with Gammapy. - Most of the pages we link here require a CTA user account to access the information. -

- -

-

Getting started

-

- To learn how to use Gammapy for CTA analysis, use the - Gammapy tutorials. - We suggest you first consult the "Getting started" page. Then continue with the "CTA with Gammapy" - tutorial, followed by the "3D map simulation" tutorial. -

-

- If you have any questions, please post on the Gammapy CTA mailing list or contact the Gammapy coordination committee (see Gammapy contact page) -

-

- Please note that Gammapy is a very young project and is under heavy development. - At the moment we are participating in the CTA first data challenge, fixing issues and adding new - functionality for CTA. -

- -

-

Resources

- - -
-
- - - - - - - - - - + + + + + + + + + Gammapy - CTA +
+ + + + +
+
+

CTA

+
+

+ Introduction | Getting started | Resources +

+

+

Introduction

+

+ The Cherenkov Telescope Array (CTA) is the next generation + ground-based observatory for gamma-ray astronomy at very-high energies. + Gammapy was chosen on June 1st 2021 to be the official Science Analysis Tool library for the CTA Observatory (see CTAO news). +

+

+ This page provides some information and links to useful resources concerning simulation and + analysis of CTA data with Gammapy. + Most of the pages we link here require a CTA user account to access the information. +

+

+

Getting started

+

+ To learn how to use Gammapy for CTA analysis, use the + Gammapy tutorials. + We suggest you first consult the "Getting started" page. Then continue with the "CTA with Gammapy" + tutorial, followed by the "3D map simulation" tutorial. +

+

+ If you have any questions, please post on the Gammapy CTA mailing list or contact the Gammapy coordination committee (see Gammapy contact page) +

+

+ Please note that Gammapy is a very young project and is under heavy development. + At the moment we are participating in the CTA first data challenge, fixing issues and adding new + functionality for CTA. +

+

+

Resources

+ +
+
+ + + + + \ No newline at end of file diff --git a/footer.html b/footer.html new file mode 100644 index 0000000..aff30c8 --- /dev/null +++ b/footer.html @@ -0,0 +1,4 @@ + \ No newline at end of file diff --git a/load-components.js b/load-components.js new file mode 100644 index 0000000..cdfcfe8 --- /dev/null +++ b/load-components.js @@ -0,0 +1,16 @@ +// load-components.js +function loadComponent(componentId, componentPath) { + fetch(componentPath) + .then(response => response.text()) + .then(data => { + document.getElementById(componentId).innerHTML = data; + }) + .catch(error => console.error('Error loading component:', error)); +} + +// Load navbar and footer components +window.onload = function () { + loadComponent('head-placeholder', 'common-head.html'); + loadComponent('navbar-placeholder', 'navbar.html'); + loadComponent('footer-placeholder', 'footer.html'); +}; diff --git a/load-scripts.js b/load-scripts.js new file mode 100644 index 0000000..d4a48d1 --- /dev/null +++ b/load-scripts.js @@ -0,0 +1,36 @@ +// load-scripts.js + +// Load Matomo +var _paq = window._paq = window._paq || []; +/* Matomo tracker methods like "setCustomDimension" should be called before "trackPageView" */ +_paq.push(['trackPageView']); +_paq.push(['enableLinkTracking']); +(function() { + var u = "https://apcstatview.in2p3.fr/"; + _paq.push(['setTrackerUrl', u + 'matomo.php']); + _paq.push(['setSiteId', '2']); + var d = document, g = d.createElement('script'), s = d.getElementsByTagName('script')[0]; + g.async = true; + g.src = u + 'matomo.js'; + s.parentNode.insertBefore(g, s); +})(); + +// Load Google Analytics +window.dataLayer = window.dataLayer || []; +function gtag() { + dataLayer.push(arguments); +} +gtag('js', new Date()); +gtag('config', 'UA-110956727-1'); + +// Load Popper.js +var popperScript = document.createElement('script'); +popperScript.src = "https://cdn.jsdelivr.net/npm/@popperjs/core@2.11.6/dist/umd/popper.min.js"; +document.head.appendChild(popperScript); + +// Load Bootstrap JS +var bootstrapScript = document.createElement('script'); +bootstrapScript.src = "https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js"; +bootstrapScript.integrity = "sha384-YvpcrYf0tY3lHB60NNkmXc5s9fDVZLESaAA55NDzOxhy9GkcIdslK1eN7N6jIeHz"; +bootstrapScript.crossOrigin = "anonymous"; +document.head.appendChild(bootstrapScript); diff --git a/navbar.html b/navbar.html new file mode 100644 index 0000000..9203ec2 --- /dev/null +++ b/navbar.html @@ -0,0 +1,45 @@ + \ No newline at end of file diff --git a/news.html b/news.html index f128acd..adb5821 100644 --- a/news.html +++ b/news.html @@ -1,531 +1,443 @@ - - - - - - - - - - - - Gammapy - News - - - - - - - - - - - - -
- -
- -
-

- Releases | News | Download statistics -

-
- -

Releases

-
-

- The Gammapy documentation and changelog for the last Gammapy releases is available here: -

- - - -

-

News

-
-

- Join the Gammapy mailing list ot or the Gammapy slack - (gammapy.slack.com) to get Gammapy-related news. + + + + + + + + + Gammapy - News + +

+ + + + +
+
+
+

+ Releases | News | Download statistics

-

- We have regular Gammapy user and developer calls - - see infos here.
- If you'd like to present or discuss something, contact Bruno - Khelifi and - Christoper van Eldik. -

- -

2024

-
    -
  • August 5th, 2024 - The OSCARS consortium finances the - Gammapy project - Contribution for the FAIRisation of Gammapy: FAIRGamma -
    • -
  • February 29th, 2024 - Gammapy 1.2 - (changelog)
    • +
    +

    Releases

    +
    +

    + The Gammapy documentation and changelog for the last Gammapy releases is available here: +

    + + +

    +

    News

    +
    +

    + Join the Gammapy mailing list ot or the Gammapy slack + (gammapy.slack.com) to get Gammapy-related news. +

    +

    + We have regular Gammapy user and developer calls - + see infos here.
    + If you'd like to present or discuss something, contact Bruno + Khelifi and + Christoper van Eldik. +

    +

    2024

    +
      +
    • August 5th, 2024 - The OSCARS consortium finances the + Gammapy project + Contribution for the FAIRisation of Gammapy: FAIRGamma +
      • +
    • February 29th, 2024 - Gammapy 1.2 + (changelog) +
      • +
    +

    2023

    + +

    2022

    +
      +
    • November 10th, 2022 - Gammapy 1.0 release - LTS + (changelog) +
      • +
    • June 27th-July 1st, 2022 - Gammapy co-working week (via Zoom) (infos)
      • +
    • June 16th, 2022 - Gammapy 0.20.1, the V1.0 release candidate + (changelog) +
      • +
    • May 12th, 2022 - Gammapy 0.20 release + (changelog) +
      • +
    • Feb. 5th, 2022 - Jury Prize of the Open Science Awards Ceremony during the Paris Open Science European Conference - OSEC Press Release
      • +
    • Jan 24-28, 2022 - Gammapy co-working week (via Zoom, as a coding sprint is not possible due to the pandemic) (infos)
      • +
    +

    2021

    +
      +
    • Nov 22nd, 2021 - Gammapy 0.19 release + (changelog) +
      • +
    • July, 2021 - Prize of the best poster for A. Donath during the 37th ICRC - ICRC announcement
      • +
    • + June 1st, 2021 - The CTA observatory choose Gammapy as core library for its Science Analysis Tool +
      • +
    • + May 3-7, 2021 - Gammapy co-working week (via Zoom, as a coding sprint is not possible due to the pandemic) + (infos) +
      • +
    +

    2020

    +
      +
    • + Nov 23-27, 2020 - Gammapy co-working week (via Zoom, as a coding sprint is not possible due to the pandemic) + (infos) +
      • +
    • + Nov 19, 2020 - Gammapy 0.18.2 release + (changelog) +
      • +
    • + Nov 6, 2020 - Gammapy 0.18.1 release + (changelog) +
      • +
    • + Nov 4, 2020 - Gammapy 0.18 release + (changelog) +
      • +
    • + Jul 6-10, 2020 - Gammapy co-working week (via Zoom, as a coding sprint is not possible due to the pandemic) + (infos) +
      • +
    • + April 1, 2020 - Gammapy 0.17 release + (changelog) +
      • +
    • + March 2-6, 2020 - Gammapy coding sprint at Consiglio Nazionale delle Ricerche, Milano - CANCELLED (SARS-COV-19) + (infos) +
      • +
    • + Feb 1, 2020 - Gammapy 0.16 release + (changelog) +
    - -

    2023

    +

    2019

      -
    • December 6th, 2023 - Gammapy 1.0.2 - (changelog)
      • -
    • - October 23, 2023 - The first Gammapy paper is published by A&A: - A&A, 678, A157 (2023). - It has been selected as highlighted paper by the publisher (link). -
      • -
    • October 16-20, 2023 - Gammapy Coding Sprint (INAF, Palermo) (infos)
      • -
    • July 7, 2023 - The first Gammapy paper is accepted by A&A - (link)
      • -
    • March 20-24, 2023 - Gammapy Coding Sprint (UCM, Madrid) (infos)
      • -
    • June 13th, 2023 - Gammapy 1.1 - (changelog)
      • -
    • March 14th, 2023 - Gammapy 1.0.1 - (changelog)
      • +
    • + Dec 3, 2019 - Gammapy 0.15 release + (changelog) +
      • +
    • + Nov 1-5, 2019 - Gammapy coding sprint at IAA-CSIC, Granada (infos) +
      • +
    • + Sep 30, 2019 - Gammapy 0.14 release + (changelog) +
      • +
    • + Jul 26, 2019 - Gammapy 0.13 release + (changelog) +
      • +
    • + July 15-19, 2019 - Gammapy coding sprint at ECAP, Erlangen (infos) +
      • +
    • + May 30, 2019 - Gammapy 0.12 release + (changelog) +
      • +
    • + Mar 29, 2019 - Gammapy 0.11 release + (changelog) +
      • +
    • + Feb 25 - Mar 1, 2019 - Gammapy coding sprint at APC, Paris (infos) +
      • +
    • + Jan 28, 2019 - Gammapy 0.10 release + (changelog) +
    - -

    2022

    -
      -
    • November 10th, 2022 - Gammapy 1.0 release - LTS - (changelog)
      • -
    • June 27th-July 1st, 2022 - Gammapy co-working week (via Zoom) (infos)
      • -
    • June 16th, 2022 - Gammapy 0.20.1, the V1.0 release candidate - (changelog)
      • -
    • May 12th, 2022 - Gammapy 0.20 release - (changelog)
      • -
    • Feb. 5th, 2022 - Jury Prize of the Open Science Awards Ceremony during the Paris Open Science European Conference - OSEC Press Release
      • -
    • Jan 24-28, 2022 - Gammapy co-working week (via Zoom, as a coding sprint is not possible due to the pandemic) (infos)
      • -
    - -

    2021

    -
      -
    • Nov 22nd, 2021 - Gammapy 0.19 release - (changelog)
      • -
    • July, 2021 - Prize of the best poster for A. Donath during the 37th ICRC - ICRC announcement
      • -
    • - June 1st, 2021 - The CTA observatory choose Gammapy as core library for its Science Analysis Tool -
      • -
    • - May 3-7, 2021 - Gammapy co-working week (via Zoom, as a coding sprint is not possible due to the pandemic) - (infos) -
      • -
    - -

    2020

    -
      -
    • - Nov 23-27, 2020 - Gammapy co-working week (via Zoom, as a coding sprint is not possible due to the pandemic) - (infos) -
      • -
    • - Nov 19, 2020 - Gammapy 0.18.2 release - (changelog) -
      • -
    • - Nov 6, 2020 - Gammapy 0.18.1 release - (changelog) -
      • -
    • - Nov 4, 2020 - Gammapy 0.18 release - (changelog) -
      • -
    • - Jul 6-10, 2020 - Gammapy co-working week (via Zoom, as a coding sprint is not possible due to the pandemic) - (infos) -
      • -
    • - April 1, 2020 - Gammapy 0.17 release - (changelog) -
      • -
    • - March 2-6, 2020 - Gammapy coding sprint at Consiglio Nazionale delle Ricerche, Milano - CANCELLED (SARS-COV-19) - (infos) -
      • -
    • - Feb 1, 2020 - Gammapy 0.16 release - (changelog) -
      • -
    - -

    2019

    -
      -
    • - Dec 3, 2019 - Gammapy 0.15 release - (changelog) -
      • -
    • - Nov 1-5, 2019 - Gammapy coding sprint at IAA-CSIC, Granada (infos) -
      • -
    • - Sep 30, 2019 - Gammapy 0.14 release - (changelog) -
      • -
    • - Jul 26, 2019 - Gammapy 0.13 release - (changelog) -
      • -
    • - July 15-19, 2019 - Gammapy coding sprint at ECAP, Erlangen (infos) -
      • -
    • - May 30, 2019 - Gammapy 0.12 release - (changelog) -
      • -
    • - Mar 29, 2019 - Gammapy 0.11 release - (changelog) -
      • -
    • - Feb 25 - Mar 1, 2019 - Gammapy coding sprint at APC, Paris (infos) -
      • -
    • - Jan 28, 2019 - Gammapy 0.10 release - (changelog) -
      • -
    - -

    2018

    -
      -
    • - Nov 29, 2018 - Gammapy 0.9 release - (changelog) -
      • -
    • - Oct 1-5, 2018 - Gammapy coding sprint at UCM Madrid (infos) -
      • -
    • - Sep 23, 2018 - Gammapy 0.8 release - (changelog) -
      • -
    • - July 9-13, 2018 - Gammapy coding sprint at MPIK Heidelberg (infos) -
      • -
    • - May 18, 2018 - Tutorial hands-on session at the CTA Consortium Meeting in Orsay - (Indico) -
      • -
    • - Feb 28, 2018 - Gammapy 0.7 release - (changelog) -
      • -
    • - February 5-9, 2018 - Gammapy coding sprint in Paris (infos) -
      • -
    - -

    2017

    -
      -
    • - Dec 8, 2017 - Gammapy webpage launched at gammapy.org.
      -
      • -
    • - Nov 21, 2017 - Add mailing list gammapy-cta-l for CTA users. - See contact page. -
      • -
    • - Nov 15, 2017 - Start coordination committee for Gammapy.
      -
      • -
    • - April 28, 2017 - Gammapy 0.6 release (changelog) -
      • -
    • - February 2017 - Gammapy workshop in Paris (link) -
      • -
    -

    2016

    -
      -
    • - November 22, 2016 - Gammapy 0.5 release (changelog) -
      • -
    • - July 2016 - Gammapy poster at Gamma 2016 (PDF) -
      • -
    • - June 2016 - First Gammapy coding sprint at MPIK, Heidelberg (infos) -
      • -
    • - June 2016 - Gammapy is used to build gamma-sky.net -
      • -
    • - May - August 2016 - Olga Vorokh GSoC 2016 on image analysis and source detection in Gammapy (blog) -
      • -
    • - May 2016 - First Gammapy presentation at a CTA meeting (PDF) -
      • -
    • - April 20, 2016 - Gammapy 0.4 release (changelog) -
      • -
    • - April 7, 2016 - Gammapy presentation at the IACT data meeting (webpage) -
      • -
    -

    2015

    -
      -
    • - November 16 - 20, 2015 - Python for gamma-ray astronomy workshop at MPIK, Heidelberg (webpage) -
      • -
    • - August 13, 2015 - Gammapy 0.3 release (changelog) -
      • -
    • - August 2015 - Gammapy poster and proceeding at ICRC 2015 (link) -
      • -
    • - May - August 2015 - Manuel Paz Arribas GSoC 2015 on observation handling and cube background - modeling in Gammapy (blog) -
      • -
    • - April 13, 2015 - Gammapy 0.2 release (changelog) -
      • -
    -

    2014

    -
      -
    • - August 25, 2014 - Gammapy 0.1 release (changelog) -
      • -
    • - Aug 19, 2013 - Rename tevpy code repository to gammapy - (commit: 7e955f) -
      • -
    • - May 15, 2013 - First commit to the tevpy code repository (commit: 11af4c) -
      • -
    - - -

    -

    Download statistics

    -
    -

    - Download statistics can be found using the PyPI stats website: -

    - - - -

    -

    - Downloads are made also with anaconda via 2 channels and the statistics can be found here: -

    -

    - -
-
- -
-
-

© Gammapy project

-
- - - - - - - - +

2018

+ +

2017

+ +

2016

+ +

2015

+ +

2014

+ +

+

Download statistics

+
+

+ Download statistics can be found using the PyPI stats website: +

+ +

+

+ Downloads are made also with anaconda via 2 channels and the statistics can be found here: +

+

+
+
+ + + + + \ No newline at end of file diff --git a/team.html b/team.html index eeeaef4..322d331 100644 --- a/team.html +++ b/team.html @@ -1,452 +1,369 @@ - - - - - - - - - - - Gammapy - Team - - - - - - - - - - - - - - -
-
- -

Project & Team

-
- -

- Introduction | Overview -

- -

-

Introduction

-

- This page describes the Gammapy project organisation and the main roles and responsibilities in the Gammapy - team. -

-

- This structure was put in place in January 2018 based on our experience developing Gammapy since 2013, - as well more generally with science tool software development in the H.E.S.S. - and CTA collaborations. We also took inspiration from the way - the Astropy and Sunpy - projects are organised, since they are in a similar situation as Gammapy: a distributed development team and - a variety of people and projects using and depending on them. -

-

- We expect this structure to evolve over the coming years, adapting to - the size and composition of the Gammapy development team, and the requirements and needs of scientists and - projects using Gammapy. If you would like to become part of the Gammapy team, please get in contact. - Help is always welcome! -

- -

-

Overview

-

- The following sections describe the major roles and responsibilities in the Gammapy team: -

- - -

-

Coordination Committee

-

- The Gammapy coordination committee (CC) is the board that is responsible to promote, coordinate and steer - Gammapy developments. It also serves as main contact point for the Gammapy project. -

-

- Gammapy is developed and used by people and projects from several institutes and countries, with different - needs, priorities and schedules. Members of the CC are representatives for the major stakeholders, i.e. - groups that have contributed significantly to Gammapy development, as well as projects like H.E.S.S. and CTA - that are using Gammapy. In addition, the Gammapy project managers and lead developers are part of the Gammapy - CC. -

-

- Responsibilities include: -

- -

- Current CC members (alphabetical order): -

- - -

-

Project managers

-

- The project manager and the deputy project manager are the non-technical executive lead for the Gammapy project. -

-

- The project managers are appointed by the Gammapy coordination committee, and work closely with the Gammapy - coordination committee, lead developers, contributors and users. -

-

- Responsibilities include: -

- -

- The current project manager is Bruno Khélifi, the deputy project manager is Christopher van Eldik. -

- -

-

Lead developers

-

- The lead developers are the technical executive leads for the Gammapy project. -

-

- The lead developers are appointed by the Gammapy coordination committee, and work closely with the Gammapy - coordination committee, project managers and contributors. -

-

- Responsibilities include: -

- -

- The current lead developers are Axel Donath and Régis Terrier. -

- -

-

Sub-package maintainers

-

Among the Gammapy core developer team, they are some experts that are devoted to the maintenance of some sub-packages.

- -

They are in charge of: -

-

- -

The list of sub-package maintainers is given below: - - - - - - - - - - - - - -
MaintainerSub-package(s)
Quentin Remy (MPIK)catalog, - datasets, - modeling
Atreyee Sinha (GAE-UCM)datasets, - irf, - makers
-

- - -

-

Contributors

-

- As of March 2021, there have been ~70 different contributors to Gammapy from ~10 countries and - ~200 people are subscribed to the Gammapy Slack. An overview of all contributors can be found on - GitHub. -

-

- There is no useful automatic way to measure how much someone contributed. The most common measure used - is commits to the code repository. However the number of commits is not the only a useful measure. - Some contributors spent several days to find and fix an important bug, or implement a big and complex - feature that only results in a single commit. If someone makes a good bug report or does code review - or mentoring or organisational work for Gammapy it does not show up in the commit statistic at all. - Please know that any contribution to the Gammapy project is valued! -

- -

- The list of contributions into conferences, hands-on sessions and schools, and for recipies can be found on the following list: -

-

- -

-

Supporting institutions

-

- People involved in Gammapy are coming from different institutions, laboratories and universities. We acknowledge - them for their daily support. Here are listed the main institutions (alphabetical order): + + + + + + + + + Gammapy - Team + +

+ + + + + +
+
+

Project & Team

+
+

+ Introduction | Overview +

+

+

Introduction

+

+ This page describes the Gammapy project organisation and the main roles and responsibilities in the Gammapy + team. +

+

+ This structure was put in place in January 2018 based on our experience developing Gammapy since 2013, + as well more generally with science tool software development in the H.E.S.S. + and CTA collaborations. We also took inspiration from the way + the Astropy and Sunpy + projects are organised, since they are in a similar situation as Gammapy: a distributed development team and + a variety of people and projects using and depending on them. +

+

+ We expect this structure to evolve over the coming years, adapting to + the size and composition of the Gammapy development team, and the requirements and needs of scientists and + projects using Gammapy. If you would like to become part of the Gammapy team, please get in contact. + Help is always welcome! +

+

+

Overview

+

+ The following sections describe the major roles and responsibilities in the Gammapy team: +

+

+

Coordination Committee

+

+ The Gammapy coordination committee (CC) is the board that is responsible to promote, coordinate and steer + Gammapy developments. It also serves as main contact point for the Gammapy project. +

+

+ Gammapy is developed and used by people and projects from several institutes and countries, with different + needs, priorities and schedules. Members of the CC are representatives for the major stakeholders, i.e. + groups that have contributed significantly to Gammapy development, as well as projects like H.E.S.S. and CTA + that are using Gammapy. In addition, the Gammapy project managers and lead developers are part of the Gammapy + CC. +

+

+ Responsibilities include: +

+
    +
  • + Ensure that scientists and projects that are using Gammapy have reliable, good and long-term support +
    • +
  • + Promote the use of Gammapy by new projects, especially as science tool for CTA +
    • +
  • + Support and grow the Gammapy team (help find manpower and funding) +
    • +
  • + Make decisions on the scope, content and development priorities for the Gammapy package.
    + In many cases this will be done via Proposal for + improvement of Gammapy (PIG) documents. +
    • +
  • + Support and coordinate the use of Gammapy for scientific or technical studies and papers +
    • +
  • + The CC is the official contact point for the Gammapy project. +
    • +
  • + Appoint the Gammapy project managers (non-technical lead) and lead developers (technical lead) +
    • +
  • + CC members should join the Gammapy CC mailing list and calls for important discussions
    + (day-to-day management is left to the project managers and lead developers). +
    • +
+

+ Current CC members (alphabetical order): +

+
    +
  • Axel Donath (CfA/Harvard, U.S.A.)
    • +
  • Bruno Khélifi (APC, France)
    • +
  • Catherine Boisson (LUTh, France)
    • +
  • Christopher van Eldik (Erlangen University, Germany)
    • +
  • David Berge, as deputy Emma de Ona Wilhelmi (DESY, Germany)
    • +
  • Fabio Acero (CEA/Irfu/DAp-AIM, France)
    • +
  • Fabio Pintore (IASF Palermo/INAF, Italy), as deputy Martina Cardillo (Roma, INAF)
    • +
  • Jim Hinton (MPIK, Germany)
    • +
  • Jose Luis Contreras (UCM, Spain)
    • + +
  • Matthias Fuessling (S.U.S.S. coordinator of CTAO)
    • +
  • Régis Terrier (APC, France)
    • +
  • Roberta Zanin (Project Scientist of CTAO)
    • +
  • Rubén López-Coto (IAA/CSIC, Spain)
    • +
  • Stefan Funk (Erlangen University, Germany)
    • +
+

+

Project managers

+

+ The project manager and the deputy project manager are the non-technical executive lead for the Gammapy project. +

+

+ The project managers are appointed by the Gammapy coordination committee, and work closely with the Gammapy + coordination committee, lead developers, contributors and users. +

+

+ Responsibilities include: +

+
    +
  • + Organise and drive all non-technical aspects of the project on a day-to-day basis. + Keep the overview of ongoing activities, schedules and action items and follow up + to make sure all important things get done. +
    • +
  • + Serve as Gammapy coordination committee secretary (schedule and moderate calls; give status reports; + write minutes) +
    • +
  • Organise Gammapy user calls and training events via gammapy-meetings +
    • +
  • + Keep an overview and help coordinate all activities that have some involvement of Gammapy, + such as e.g. papers, presentations or posters about or using Gammapy at gamma-ray astronomy meetings or + conferences, or tutorials at schools / workshops on gamma-ray astronomy data analysis. +
    • +
  • + Maintain Gammapy communication channels (mailing lists, slack, github, ...) + as well as the content at https://gammapy.org/ +
    • +
+

+ The current project manager is Bruno Khélifi, the deputy project manager is Christopher van Eldik. +

+

+

Lead developers

+

+ The lead developers are the technical executive leads for the Gammapy project. +

+

+ The lead developers are appointed by the Gammapy coordination committee, and work closely with the Gammapy + coordination committee, project managers and contributors. +

+

+ Responsibilities include: +

+
    +
  • + Organise and drive all technical aspects of the project on a day-to-day basis. + Keep the overview of ongoing activities, schedules and action items and follow up + to make sure all important things get done. +
    • +
  • + Serve on the Gammapy coordination committee, as the link between CC and the development team. +
    • +
  • + Ensure that Proposal for + improvement of Gammapy (PIG) documents are properly reviewed and + eventually decisions made by the CC. +
    • +
  • + Manage the Gammapy developer / maintainer / contributor team. Distribute tasks and assign + responsibilities to other Gammapy core developers. +
    • +
  • + Ensure that anyone interested in contributing to Gammapy development has good resources (documentation, + communication, mentoring) to get started. Specifically: maintain the Gammapy developer documentation + that describes all aspects of Gammapy development (code, testing, documentation, processes). +
    • +
  • + Ensure Gammapy infrastructure is well set up and maintained (issue tracker and pull requests on Github, + continuous integration tests, documentation builds, releases and distribution). +
    • +
  • Organise Gammapy developer calls and coding sprints via gammapy-meetings +
    • +
  • + Schedule Gammapy releases and define which fixes and features go in which release, taking the needs of + people and projects using Gammapy as well as available manpower for developments into account. + Either execute releases directly or assign a release manager. +
    • +
+

+ The current lead developers are Axel Donath and Régis Terrier. +

+

+

Sub-package maintainers

+

Among the Gammapy core developer team, they are some experts that are devoted to the maintenance of some sub-packages.

+

They are in charge of: +

    +
  • perform initial triage of issues and pull requests,
    • +
  • supporting developers on tasks associated to the sub-package(s),
    • +
  • evaluating new pull requests for quality, API consistency and Gammapy coding standards,
    • +
  • taking care of the global design of the sub-package(s) in the context of the global Gammapy architecture,
    • +
  • participating to the User Support for questions related to the sub-package(s).
    • +
+

+

The list of sub-package maintainers is given below: + + + + + + + + + + + + + +
MaintainerSub-package(s)
Quentin Remy (MPIK)catalog, + datasets, + modeling +
Atreyee Sinha (GAE-UCM)datasets, + irf, + makers +
+

+

+

Contributors

+

+ As of March 2021, there have been ~70 different contributors to Gammapy from ~10 countries and + ~200 people are subscribed to the Gammapy Slack. An overview of all contributors can be found on + GitHub. +

+

+ There is no useful automatic way to measure how much someone contributed. The most common measure used + is commits to the code repository. However the number of commits is not the only a useful measure. + Some contributors spent several days to find and fix an important bug, or implement a big and complex + feature that only results in a single commit. If someone makes a good bug report or does code review + or mentoring or organisational work for Gammapy it does not show up in the commit statistic at all. + Please know that any contribution to the Gammapy project is valued! +

+

+ The list of contributions into conferences, hands-on sessions and schools, and for recipies can be found on the following list: +

+

+

+

Supporting institutions

+

+ People involved in Gammapy are coming from different institutions, laboratories and universities. We acknowledge + them for their daily support. Here are listed the main institutions (alphabetical order): +

    +
  • AIM (Astrophysique, instrumentation, modélisation), DAp-CEA/CNRS, Saclay/France - + Web site +
  • APC (AstroParticules et Cosmologie), Université de Paris/CNRS, Paris/France - - Web site
    • + Web site +
  • DESY (Deutsches Elektronen-Synchrotron), Zeuthen/Germany - - Web site
    • -
  • ECAP (Erlangen Center for Astroparticle Physics), Friedrich-Alexander Univervität, Erlangen/Germany - - Web site
    • + Web site + +
  • ECAP (Erlangen Center for Astroparticle Physics), Friedrich-Alexander Univervität, Erlangen/Germany - + Web site +
  • IAA-CSIC (Instituto de Astrofísica de Andalucía), Consejo Superior de Investigaciones Científicas, Granada/Spain - - Web site
    • + Web site +
  • INAF (Istituto Nazionale di Astrofisica), Italy - - Web site
    • + Web site +
  • LUTh (Laboratoire Univers et Théorie), CNRS/Observatoire de Paris, Meudon/France - - Web site
    • + Web site +
  • MPIK (Max-Planck-Institut für Kernphysik), Max-Planck-Gesellschaft, Heidelberg/Germany - - Web site
    • + Web site +
  • Observatoire de Paris, Paris-Meudon-Nançay/France - - Web site
    • + Web site +
  • UCM (Universidad Complutense Madrid), Madrid/Spain - - Web site
    • + Web site +
  • CTA Observatory - Web site
-

-
-
- Institutions supporting the project -
- -

-

Grants

-

- Several grants have helped to support the development of Gammapy, including: -

    -
  • ESCAPE H2020 project (European Science Cluster of Astronomy & Particle Physics ESFRI research Infrastructure): - grant agreemant n. 824064, 2019/2022 in Germany and France (from EU)
    • -
  • PECORA ANR project: 2019/2022 (from France)
    • -
  • Action Fédératrice CTA: 2018, 2019, 2020, 2021 (from Observatoire de Paris)
    • -
  • Action Pluri-annauelle Initiatrice "Astrophysique des hautes énergies": 2022, - 2023 (from Observatoire de Paris)
    • -
  • ASTERICS H2020 project (Astronomy ESFRI & Research Infrastructure Cluster): - grant agreement n. 653477, 2015/2019 in France and Spain (from EU)
    • -
  • Spanish MINECO/AEI projects: FPA2015-69210-C6-3-R, FPA2017-82729-C6-3-R, AYA2016-8089-P (from Spain)
    • +

    +
    +
    + Institutions supporting the project +
    +

    +

    Grants

    +

    + Several grants have helped to support the development of Gammapy, including: +

      +
    • ESCAPE H2020 project (European Science Cluster of Astronomy & Particle Physics ESFRI research Infrastructure): + grant agreemant n. 824064, 2019/2022 in Germany and France (from EU) +
      • +
    • PECORA ANR project: 2019/2022 (from France)
      • +
    • Action Fédératrice CTA: 2018, 2019, 2020, 2021 (from Observatoire de Paris)
      • +
    • Action Pluri-annauelle Initiatrice "Astrophysique des hautes énergies": 2022, + 2023 (from Observatoire de Paris) +
      • +
    • ASTERICS H2020 project (Astronomy ESFRI & Research Infrastructure Cluster): + grant agreement n. 653477, 2015/2019 in France and Spain (from EU) +
      • +
    • Spanish MINECO/AEI projects: FPA2015-69210-C6-3-R, FPA2017-82729-C6-3-R, AYA2016-8089-P (from Spain)
    -

    - -
- -
- -
-
-

© Gammapy project

-
- - - - - - - - +

+
+
+ + + + + \ No newline at end of file