Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PIG 5 - Gammapy 1.0 Roadmap #1841

Merged
merged 7 commits into from Feb 11, 2019
Merged

PIG 5 - Gammapy 1.0 Roadmap #1841

merged 7 commits into from Feb 11, 2019

Conversation

@adonath
Copy link
Member

@adonath adonath commented Oct 1, 2018

This PR contains the PIG document for the Gammapy roadmap with required development work until the Gammapy 1.0 release. It will be updated and improved in this PR.

@adonath adonath added the pig label Oct 1, 2018
@adonath adonath added this to the 1.0 milestone Oct 1, 2018
@adonath adonath self-assigned this Oct 1, 2018
@adonath adonath force-pushed the adonath:gammapy_roadmap_pig branch from 34c16b0 to 6f21201 Oct 1, 2018
@cdeil cdeil changed the title Gammapy Roadmap PIG PIG 5 - Gammapy 1.0 Roadmap Oct 2, 2018
@cdeil cdeil requested review from registerrier, robertazanin and bkhelifi Oct 2, 2018
The following use cases should be supported by Gammapy 1.0:

* Fit 1D spectrum and 3D cube simultaneously
* Further definitions defined by CTA (add link).

This comment has been minimized.

@cdeil

cdeil Oct 2, 2018
Member

@cboisson - Do you have a link to a CTA document containing a description of use cases for the CTA ST?
It's OK if it's a CTA-internal document, we can still link to it from here, most people are in CTA.

I don't think we should extend the use cases section in this PIG significantly, maybe add one or two bullets with use cases that aren't already possible, but trying to repeat the description of use cases here would be a huge time sink.


We plan to continue the **weekly developers calls** every Friday 10 am. In addition
we could start **monthly Gammapy user calls**, for regular user support and feedback.
(to be discussed).

This comment has been minimized.

@cdeil

cdeil Oct 2, 2018
Member

@robertazanin @bkhelifi - What do you think about this?

We suggest to have weekly Gammapy developer calls, which are for people actively coding on Gammapy and to discuss open issues and PRs in detail, i.e. these are meetings that are not of interest to Gammapy users or even the currently non-active Gammapy developers.

For users, maybe you could take charge of scheduling the meetings separately? E.g. it would be nice to hear about ongoing studies and papers using Gammapy, and hear about missing features and issues. Some developers would also join these meetings, but it's completely separate from the dev meetings.

docs/development/pigs/pig-005.rst Outdated Show resolved Hide resolved
@cdeil
Copy link
Member

@cdeil cdeil commented Oct 2, 2018

Suggest to add "Documentation" as one more project, after "Maintenance and quality". Goal would be to write a PIG outlining documentation structure we should have at the time of v1.0 release, and then to work towards that documentation, one notebook and page at a time.

@adonath adonath force-pushed the adonath:gammapy_roadmap_pig branch 2 times, most recently from 99400b1 to 2124a43 Oct 5, 2018
@adonath adonath force-pushed the adonath:gammapy_roadmap_pig branch from 2124a43 to 21bdc5f Nov 14, 2018
@adonath adonath closed this Nov 20, 2018
@adonath adonath deleted the adonath:gammapy_roadmap_pig branch Nov 20, 2018
@adonath adonath restored the adonath:gammapy_roadmap_pig branch Nov 20, 2018
@adonath adonath reopened this Nov 20, 2018
@adonath adonath force-pushed the adonath:gammapy_roadmap_pig branch from 21bdc5f to 736d272 Dec 14, 2018
@adonath
Copy link
Member Author

@adonath adonath commented Dec 20, 2018

@cdeil @cboisson @robertazanin @bkhelifi @registerrier @facero @contrera Do you have further comments on the Gammapy roadmap? If not I would like to go ahead and merge this PR soon, so that it starts to appear in the Gammapy documentation and we can link to it for talks and discussions.

@cdeil
Copy link
Member

@cdeil cdeil commented Dec 20, 2018

As mentioned here, I would suggest to put support for event classes on the roadmap, i.e. to mention it at least in the data project paragraph. And in modeling I would suggest to mention Bayesian priors and maybe also linked parameters if that is how you envision modeling to work.

The Gammapy paper in 2018 clearly didn't work out, so correct that sentence that it is for 2019. Also, we got the feedback that the most important thing to have is a plan / description of the design of Gammapy. So if we want to have that description in the paper, and to have a good design, we would have to defer the paper to later in 2019. Suggest to keep it short and vague for papers, OK to mention the Gammapy and HESS validation if you like as goals for 2019, but only very briefly.

The most important question is how to make this roadmap useful and to have an impact. I think it's important to have a shared vision what to build and to have it visible, so +1 to merge it. But maybe to actually lead to progress from existing and new contributors, some link concerning status and missing manpower for the different projects is needed? Updating the PIG all the time is not ideal. So either use https://github.com/gammapy/gammapy/projects or make a wiki page, and link to it from the PIG with some sentence encouraging people to contribute or lead projects listed on the roadmap has to exist. Maybe also a sentence how to get started concretely, IMO an email to the lead devs or mailing list is best. - so far we have not succeeded to describe the work to be done such that people just pick up tasks and start contributing, hopefully this roadmap will help focus the work of the exiting team, and help with onboarding in 2019.

@adonath adonath force-pushed the adonath:gammapy_roadmap_pig branch 2 times, most recently from c3cf6db to 5539c43 Jan 14, 2019
@adonath adonath force-pushed the adonath:gammapy_roadmap_pig branch 2 times, most recently from b21a497 to b0d9e3c Jan 28, 2019
@adonath adonath force-pushed the adonath:gammapy_roadmap_pig branch from b0d9e3c to 5c03495 Jan 28, 2019
@adonath adonath merged commit ad80fc6 into gammapy:master Feb 11, 2019
4 checks passed
4 checks passed
Codacy/PR Quality Review Up to standards. A positive pull request.
Details
Scrutinizer Analysis: No new issues – Tests: passed
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details
gammapy.gammapy Build #20190130.7 succeeded
Details
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

None yet

3 participants
You can’t perform that action at this time.