diff --git a/.gitignore b/.gitignore new file mode 100644 index 0000000..090a1f0 --- /dev/null +++ b/.gitignore @@ -0,0 +1,2 @@ +.idea +.DS_Store diff --git a/404.html b/404.html new file mode 100644 index 0000000..bc49821 --- /dev/null +++ b/404.html @@ -0,0 +1,53 @@ + + + + + + + + + + +
+ + + +
+ +
+ +
+

+ Error 404: Page not found. +

+
+

+ Looks like you followed a bad link. + Here's a link to the homepage. +

+

+ If there's a problem with the website, please let us know. +

+
+
+ +
+ + +
+ + + + + + + + + diff --git a/CNAME b/CNAME new file mode 100644 index 0000000..fb87eb5 --- /dev/null +++ b/CNAME @@ -0,0 +1 @@ +gammapy.org \ No newline at end of file diff --git a/CoC.html b/CoC.html new file mode 100644 index 0000000..1931a01 --- /dev/null +++ b/CoC.html @@ -0,0 +1,88 @@ + + + + + + + + + +
+ + + + +
+ +
+
+

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 has 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). +

+
+
+ + +
+ + + + + + + + + diff --git a/DataPrivacy.html b/DataPrivacy.html new file mode 100644 index 0000000..7a4bf96 --- /dev/null +++ b/DataPrivacy.html @@ -0,0 +1,131 @@ + + + + + + + + + +
+ + + +
+ +
+
+

Privacy Policy for Gammapy Websites

+

+ +

+ Effective Date: October 14th, 2024. +

+ +

+ Thank you for visiting our websites, gammapy.org and docs.gammapy.org. At Gammapy, we are committed to protecting your + privacy and ensuring that your personal data is handled in a safe and responsible manner. This Privacy Policy explains + how we collect, use, and protect any information obtained during your visit to our websites. +

+ +

+ We use an open-source analytics platform called Matomo to collect anonymized information about how users interact with our + websites. The data we collect includes: +

+

+ +

Important: all data collected is strictly anonymized, and we do not collect any personally identifiable + information (PII).

+ +

2. How We Collect Data

+ +

+ We have configured Matomo to prioritize your privacy: +

+ +

+ +

3. Why We Collect Data

+ +

+ We only use the collected data for the following purposes: +

+ + We do not use this data for any commercial or marketing purposes, and we do not share the data with third parties. + +

+ +

4. How We Protect Your Data

+ +

+ We take your privacy seriously and have taken the following steps to protect any data collected: +

+ +

+ +

5. Your Privacy Choices

+ +

+ Since we do not use cookies, there is no need to accept or manage cookie consent for analytics purposes. However, if you + wish to opt out of being tracked by our anonymized analytics, you can configure your browser to block all tracking or + analytics requests. +

+ +

6. Third-Party Links

+ +

+ Our websites may contain links to external sites, such as documentation resources or partner organizations. We are not + responsible for the privacy practices or content of these third-party sites. We encourage you to review their privacy + policies before sharing any personal information with them. +

+ +

7. Contact Us

+ +

+ If you have any questions or concerns about our privacy practices, please feel free to contact us at: + <> + Email: gammapy-coordination-l [at] in2p3 [dot] fr +

+ +
+
+ + +
+ + + + + + + + + + diff --git a/README.md b/README.md index a0c0eee..6258a9a 100644 --- a/README.md +++ b/README.md @@ -1,2 +1,5 @@ -# gammapy-webpage -Repository for the Gammapy webpage +# Gammapy webpage + +Repository for http://gammapy.org + +Github repo: https://github.com/gammapy/gammapy-webpage diff --git a/about.html b/about.html new file mode 100644 index 0000000..aef7fa6 --- /dev/null +++ b/about.html @@ -0,0 +1,143 @@ + + + + + + + + + + +
+ + + +
+ +
+ +
+

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 Observatory (CTAO), + 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 CTAO, 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 commonly + 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

+ + +

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

+ +

+

Awards and Prizes

+ + + +
+
+ + +
+ + + + + + + + + diff --git a/acknowledging.html b/acknowledging.html new file mode 100644 index 0000000..fffd6dc --- /dev/null +++ b/acknowledging.html @@ -0,0 +1,305 @@ + + + + + + + + + +
+ + +
+ + + + + + + + + + + + + + + + + + +
+
+ +

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/) +

+
+
+ +
+ + +
+ + + + + + + + + + diff --git a/contact.html b/contact.html new file mode 100644 index 0000000..e0fb38a --- /dev/null +++ b/contact.html @@ -0,0 +1,85 @@ + + + + + + + + + + +
+ + + + +
+ +
+
+

Contact

+
+

This page lists the contact points and communication channels for Gammapy

+ + +
+
+ + +
+ + + + + + + + diff --git a/contribute.html b/contribute.html new file mode 100644 index 0000000..e5e9d03 --- /dev/null +++ b/contribute.html @@ -0,0 +1,57 @@ + + + + + + + + + +
+ + +
+ +
+
+

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: +

+

+
+
+ + +
+ + + + + + + + + diff --git a/cta.html b/cta.html new file mode 100644 index 0000000..859c106 --- /dev/null +++ b/cta.html @@ -0,0 +1,102 @@ + + + + + + + + + + +
+ + + +
+ +
+
+

CTAO

+
+ +

+ Introduction | Getting started | Resources +

+ +

+

Introduction

+

+ The Cherenkov Telescope Array Observatory (CTAO) 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 CTAO (see CTAO news). +

+

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

+ +

+

Getting started

+

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

+

+ If you have any questions, please post on the Gammapy CTAO 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 first CTAO Science Data Challenge, fixing issues and adding new + functionalities for CTAO. +

+ +

+

Resources

+ + +
+
+ + +
+ + + + + + + + + + diff --git a/footer.html b/footer.html new file mode 100644 index 0000000..19c46a1 --- /dev/null +++ b/footer.html @@ -0,0 +1,15 @@ + diff --git a/gammapy_song.mp3 b/gammapy_song.mp3 new file mode 100644 index 0000000..39b1d9b Binary files /dev/null and b/gammapy_song.mp3 differ diff --git a/goto/index.html b/goto/index.html new file mode 100644 index 0000000..5254081 --- /dev/null +++ b/goto/index.html @@ -0,0 +1,28 @@ + + + + + + + + + + Page Redirection + + +

Gammapy redirect page

+

If you see this page, you have probably typed a non-existing redirect URL.

+

List of available redirect links:

+ + + diff --git a/goto/script.js b/goto/script.js new file mode 100644 index 0000000..604d211 --- /dev/null +++ b/goto/script.js @@ -0,0 +1,46 @@ +// List of redirects. Add or update, but never remove! +var redirects = [ + { + short: "gammapy-cta-1dc-docs", + url: "https://nbviewer.jupyter.org/github/gammapy/gammapy-extra/blob/master/notebooks/cta_1dc_introduction.ipynb" + }, + { + short: "tutorials", + url: "https://nbviewer.jupyter.org/github/gammapy/gammapy-extra/blob/master/index.ipynb" + } +]; + +function add_links() { + for (var i = 0; i < redirects.length; i++) { + var msg = redirects[i].short; + var a = $("").attr('href', redirects[i].url).text(msg); + $("#gotos").append($('
  • ').append(a)); + } +} + +function execute_redirect() { + var short = document.URL.split('#')[1]; + var url = 'not found'; + + for (var i = 0; i < redirects.length; i++) { + if (redirects[i].short === short) { + url = redirects[i].url; + } + } + + if (url === 'not found') { + console.log('document.URL: ' + document.URL); + console.log('short: ' + short); + console.log('URL redirect not found!!!') + } else { + console.log('Execubing redirect now ...'); + console.log('url: ' + url); + window.location.replace(url); + } +} + + +$( document ).ready(function() { + add_links(); + execute_redirect(); +}); diff --git a/header.html b/header.html new file mode 100644 index 0000000..8a1c48d --- /dev/null +++ b/header.html @@ -0,0 +1,29 @@ + + + + + + + + + + Gammapy + + + + + + + + + + + + \ No newline at end of file diff --git a/img/DC1_logo.png b/img/DC1_logo.png new file mode 100644 index 0000000..22ce325 Binary files /dev/null and b/img/DC1_logo.png differ diff --git a/img/LogoList.png b/img/LogoList.png new file mode 100644 index 0000000..47af1fb Binary files /dev/null and b/img/LogoList.png differ diff --git a/img/LogoList_V2019.png b/img/LogoList_V2019.png new file mode 100644 index 0000000..47af1fb Binary files /dev/null and b/img/LogoList_V2019.png differ diff --git a/img/LogoList_V2020.png b/img/LogoList_V2020.png new file mode 100644 index 0000000..ce4acfe Binary files /dev/null and b/img/LogoList_V2020.png differ diff --git a/img/LogoList_V2021.png b/img/LogoList_V2021.png new file mode 100644 index 0000000..7082c72 Binary files /dev/null and b/img/LogoList_V2021.png differ diff --git a/img/LogoList_V2021_V2.png b/img/LogoList_V2021_V2.png new file mode 100644 index 0000000..b02ff84 Binary files /dev/null and b/img/LogoList_V2021_V2.png differ diff --git a/img/LogoList_V2024.png b/img/LogoList_V2024.png new file mode 100644 index 0000000..9f6de9c Binary files /dev/null and b/img/LogoList_V2024.png differ diff --git a/img/LogoList_V2024_v2.png b/img/LogoList_V2024_v2.png new file mode 100644 index 0000000..06895bc Binary files /dev/null and b/img/LogoList_V2024_v2.png differ diff --git a/img/gammapy_LogoList.odp b/img/gammapy_LogoList.odp new file mode 100644 index 0000000..9c03315 Binary files /dev/null and b/img/gammapy_LogoList.odp differ diff --git a/img/gammapy_banner.png b/img/gammapy_banner.png new file mode 100644 index 0000000..2cc6628 Binary files /dev/null and b/img/gammapy_banner.png differ diff --git a/img/gp_favicon-16x16.png b/img/gp_favicon-16x16.png new file mode 100644 index 0000000..79f79fc Binary files /dev/null and b/img/gp_favicon-16x16.png differ diff --git a/img/gp_favicon-32x32.png b/img/gp_favicon-32x32.png new file mode 100644 index 0000000..cb20794 Binary files /dev/null and b/img/gp_favicon-32x32.png differ diff --git a/img/gp_favicon.ico b/img/gp_favicon.ico new file mode 100644 index 0000000..34c4811 Binary files /dev/null and b/img/gp_favicon.ico differ diff --git a/index.html b/index.html new file mode 100644 index 0000000..f4d5848 --- /dev/null +++ b/index.html @@ -0,0 +1,101 @@ + + + + + + + + + +
    + + +
    + +
    + +
    + Gammapy banner +

    + Gammapy is an open-source Python package for gamma-ray astronomy built on + Numpy, Scipy + and Astropy.
    + It is used as core library for the Science Analysis tools of the Cherenkov + Telescope Array Observatory (CTAO), recommended by the + H.E.S.S. collaboration to be used for Science publications, + and is already widely used in the analysis of existing gamma-ray instruments, + such as MAGIC, + VERITAS + and HAWC. +

    + +
    +
    +

    News:

    +
    + + + + + + + + + + + + + + + + + + + + + +
    Nov. 26th, 2024:Minor version release v1.3
    Aug. 5th, 2024:The OSCARS consortium finances Gammapy
    Feb. 29th, 2024:Minor version release v1.2
    Dec. 6th, 2023:Bug fix release v1.0.2
    Oct. 23rd, 2023:Publication of the first Gammapy paper in + A&A (accepted: 7th July 2023) + as highlighted paper (link) +
    +
    + +
    +
    +

    + Please remember to acknowledge and cite the use of Gammapy! +

    + +
    +
    + Documentation + Install + + +

    Current version: 1.3

    +

    v1.3 changelog and other releases

    +
    +
    + +
    + +
    + + + + + + + + + + diff --git a/navbar.html b/navbar.html new file mode 100644 index 0000000..052a6da --- /dev/null +++ b/navbar.html @@ -0,0 +1,46 @@ + + diff --git a/news.html b/news.html new file mode 100644 index 0000000..d568c44 --- /dev/null +++ b/news.html @@ -0,0 +1,464 @@ + + + + + + + + + + +
    + + + +
    + +
    + +
    + +
    +

    + Releases | News | Download statistics +

    +
    + +

    Releases

    +
    +

    + The Gammapy documentation and changelog for the last Gammapy releases are 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

    +
      +
    • November 26th, 2024 - Gammapy 1.3 + (changelog) +
      • +
    • 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 CTAO observatory chooses 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 CTAO 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 CTAO 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 CTAO 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: +

    +

    + +
    +
    + + +
    + + + + + + + + + + diff --git a/scripts/includeHTML.js b/scripts/includeHTML.js new file mode 100644 index 0000000..c093141 --- /dev/null +++ b/scripts/includeHTML.js @@ -0,0 +1,26 @@ +function includeHTML(callback) { + const elements = document.querySelectorAll('[data-include]'); + const promises = Array.from(elements).map(async (el) => { + const file = el.getAttribute('data-include'); + try { + const response = await fetch(file); + if (!response.ok) throw new Error(`Error fetching ${file}`); + const html = await response.text(); + el.innerHTML = html; + } catch (error) { + console.error(`Failed to load ${file}:`, error); + } + }); + + // Execute callback when all includes are complete + Promise.all(promises).then(callback).catch((error) => { + console.error("Error loading HTML fragments:", error); + }); +} + +document.addEventListener('DOMContentLoaded', () => { + includeHTML(() => { + console.log("All fragments loaded"); + initFooterScripts(); // This will now work + }); +}); diff --git a/scripts/matomo.js b/scripts/matomo.js new file mode 100644 index 0000000..a7d41fc --- /dev/null +++ b/scripts/matomo.js @@ -0,0 +1,25 @@ +function initializeMatomoTracker() { + var _paq = window._paq = window._paq || []; + + // Tracker methods 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); + })(); +} + +// Call the function to initialize Matomo tracking +initializeMatomoTracker(); diff --git a/scripts/myscripts.js b/scripts/myscripts.js new file mode 100644 index 0000000..8ccff11 --- /dev/null +++ b/scripts/myscripts.js @@ -0,0 +1,20 @@ + +function TodayDate() { + const dateObj = new Date(); + const month = String(dateObj.getMonth() + 1).padStart(2, '0'); + const day = String(dateObj.getDate()).padStart(2, '0'); + const year = dateObj.getFullYear(); + return `${day}/${month}/${year}`; +} + +function initFooterScripts() { + console.log("initFooterScripts called"); + const todayDateElement = document.getElementById("TodayDate"); + if (todayDateElement) { + todayDateElement.textContent = TodayDate(); + } else { + console.error("TodayDate element not found in footer"); + } +} + +window.initFooterScripts = initFooterScripts; // Make it globally accessible diff --git a/scripts/navbarCollapse.js b/scripts/navbarCollapse.js new file mode 100644 index 0000000..bb647e9 --- /dev/null +++ b/scripts/navbarCollapse.js @@ -0,0 +1,12 @@ +document.addEventListener('click', function (event) { + var navbar = document.querySelector('.navbar-collapse'); + var button = document.querySelector('.navbar-toggler'); + if ( + navbar.classList.contains('show') && + !navbar.contains(event.target) && + !button.contains(event.target) + ) { + var collapseInstance = bootstrap.Collapse.getInstance(navbar); + collapseInstance.hide(); + } +}); diff --git a/style.css b/style.css new file mode 100644 index 0000000..1942ca0 --- /dev/null +++ b/style.css @@ -0,0 +1,131 @@ +/* + Define custom colors: + https://stackoverflow.com/a/17595596/498873 +*/ +:root { + --gammapy-primary: rgb(224, 10, 52); + --gammapy-secondary: #1e254a; +} + +.navbar { + margin-bottom: 0; +} + +@media (max-width: 768px) { + .navbar-nav { + text-align: center; + width: 100%; /* Full width for mobile */ + } + + .navbar-collapse { + background-color: var(--gammapy-secondary); /* For a full-width menu on mobile */ + /* display: flex !important; /* Ensure visibility */ + flex-direction: column; /* Stack menu items */ + display: none; /* Hidden by default */ + transition: height 0.3s ease; /* Smooth transition */ + } + + .navbar-collapse.show { + display: block; /*flex !important; /* Shown when toggled */ + } + + .bg-dark { + color: white; /* Ensure text is bright on dark background */ + } +} + +.bg-dark { + background-color: #1e254a !important; + /* TODO: Make navbar text brighter! */ + color: white; +} + +body { + color: var(--gammapy-secondary); + font-family: 'Fira Sans', sans-serif; + padding-top: 56px; /* Adjust for fixed navbar height */ +} + +main { + padding-top: 7rem; + margin-bottom: 0; +} + +a { + color: var(--gammapy-primary); +} + +footer { + padding-top: 1.5rem; + padding-bottom: 1rem; +} + +.opener { + /*padding-top: 7rem;*/ + padding-bottom: 3rem; +} + +#gp-banner { + padding-bottom: 3rem; + width: 500px; + max-width: 100%; +} + +/* + https://css-tricks.com/quick-css-trick-how-to-center-an-object-exactly-in-the-center/ +*/ +.centered { + position: fixed; + top: 50%; + left: 50%; + /* bring your own prefixes */ + transform: translate(-50%, -50%); +} + + +.btn-outline-primary { + background-color: white; + border-color: var(--gammapy-primary); + color: var(--gammapy-primary); +} + +.btn-outline-primary:hover, +.btn-outline-primary:active, +.btn-outline-primary:focus { + background-color: var(--gammapy-primary); + border-color: var(--gammapy-primary); + color: white; +} + +.button-fancy { + background-color: #23b83c; + color: whitesmoke; + /* padding: 0.5em 1.1em; */ + padding: 0px; + text-align: center; + text-decoration: none; + font-size: 1em; + display: inline-block; + border-radius: 5px; + box-shadow: 3px 3px 8px 0 #000; /* h-offset v-offset blur spread color */ + cursor: pointer; +} + +.myfooter { + width:100%; +} + +.alignLeft { + width:33%; + float:left; +} +.alignCenter { + float:left; + width:33%; + text-align:center; +} +.alignRight { + float:right; + overflow:visible !important; +} + diff --git a/team.html b/team.html new file mode 100644 index 0000000..7f6ae15 --- /dev/null +++ b/team.html @@ -0,0 +1,359 @@ + + + + + + + + + +
    + + + +
    + +
    +
    + +

    Project & Team

    +
    + +

    + Introduction | Composition | Grants +

    + +

    +

    Introduction

    +

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

    +

    + This structure has been 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 CTAO 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! +

    + +


    +

    Composition

    +

    + 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 the 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 CTAO + 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 CTAO +
      • +
    • + 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 call 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 in the User Support for questions related to the sub-package(s).
      • +
    +

    + +

    The list of subpackage maintainers is given below: + + + + + + + + + + + + + +
    MaintainerSubpackage(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 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 recipes 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
      • +
    • DESY (Deutsches Elektronen-Synchrotron), Zeuthen/Germany - + 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
      • +
    • INAF (Istituto Nazionale di Astrofisica), Italy - + Web site
      • +
    • LUTh (Laboratoire Univers et Théorie), CNRS/Observatoire de Paris, Meudon/France - + Web site
      • +
    • MPIK (Max-Planck-Institut für Kernphysik), Max-Planck-Gesellschaft, Heidelberg/Germany - + Web site
      • +
    • Observatoire de Paris, Paris-Meudon-Nançay/France - + Web site
      • +
    • UCM (Universidad Complutense Madrid), Madrid/Spain - + Website
      • +
    • CTAO - Web site
      • +
    +

    +
    +
    + Institutions supporting the project +
    + +


    +

    Grants

    +

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

      +
    • OSCARS (Open Science Clusters ACtion for Research and Society): 2025–26,
      • +
    • ACME (Astrophysics Centre for Multi-messenger studies in Europe, HORIZON-INFRA-2023-SERV-01): 2025-27,
      • +
    • PUNCH4NFDI (German National Research Data Infrastructure for particle, astro-, astroparticle, hadron and nuclear physics),
      • +
    • ESCAPE H2020 project (European Science Cluster of Astronomy & Particle Physics ESFRI research Infrastructure): + grant agreement 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)
      • +
    +

    + +
    + +
    + + +
    + + + + + + + + + +