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

Initial roadmap for high-level cyberinfrastructure components of analysis system #11

Closed
BenGalewsky opened this issue Sep 16, 2019 · 10 comments
Assignees
Labels
AS Analysis Systems
Milestone

Comments

@BenGalewsky
Copy link
Collaborator

BenGalewsky commented Sep 16, 2019

Assumptions

High-level cyberinfrastructure components include:

  • INSPIRE
  • HEPData
  • CERN Analysis Preservation framework
  • CERN Open Data
  • REANA
  • INDICO
  • Zenodo
  • RECAST
  • GitHub and GitLab at CERN

These projects are pre-existing and funded through a variety of mechanisms (sometimes including IRIS-HEP). IRIS-HEP's role is largely about

  • integration with analysis system tools (eg. pyhf and HEPData)
  • enhancing interoperability between those components (eg. RECAST, CAP, REANA, HEPData)

Acceptance criteria

  • figure or other documentation describing interaction of components needed to achieve specific analysis user stories (eg. on-boarding, reinterpretation, publishing, preservation).
  • pointeres to specific engagements with these cyberinfrastructure components (eg. via GitHub issues)
@BenGalewsky BenGalewsky added the AS Analysis Systems label Sep 16, 2019
@BenGalewsky BenGalewsky added this to the Y2Q2 milestone Sep 16, 2019
@cranmer cranmer assigned cranmer and unassigned cranmer Sep 18, 2019
@matthewfeickert
Copy link
Member

matthewfeickert commented Feb 5, 2020

@cranmer @gordonwatts Can you give some feedback on what the goals of this Milestone are? It wasn't really clear to anyone in the AS meeting on 2020-02-05, so as they are due soon it would be good to understand how to move forward.

Edit: Comments from @gordonwatts and @msneubauer later in the meeting.

What infrastructure are you going to host all the different parts of the AS software pipeline on?

c.f. River at Chicago

@mweinberg2718 can you add some comments here as well about what you've done with Coffea and River?

@gordonwatts
Copy link
Member

I would guess we need text that is about 1/2 a page for this - since it is mostly Hardware. There were some conclusions from the NYU blueprint meeting (@msneubauer), that might be relevant. It might be useful to use the ecosystem coherency to help here too.

@cranmer
Copy link
Collaborator

cranmer commented Feb 13, 2020

Had nice discussion with @lukasheinrich and @Sinclert about this. This should focus mainly on HEPData, INSPIRE, CAP, RECAST, etc. pyhf and fitting service are also related.

@cranmer
Copy link
Collaborator

cranmer commented Feb 17, 2020

See issue with HEPData: HEPData/hepdata#164

@cranmer
Copy link
Collaborator

cranmer commented Feb 17, 2020

See issue: HEPData/hepdata#163

@cranmer
Copy link
Collaborator

cranmer commented Feb 17, 2020

see issue: indico/indico#4293

@cranmer
Copy link
Collaborator

cranmer commented Feb 17, 2020

See HEPData Advisory Board agenda: https://conference.ippp.dur.ac.uk/event/875/

@cranmer
Copy link
Collaborator

cranmer commented Feb 17, 2020

For reference, many ideas of this road map first discussed at AAHEP7 in 2014
https://indico.cern.ch/event/262430/sessions/48420/#20140402

@cranmer
Copy link
Collaborator

cranmer commented Feb 17, 2020

@cranmer
Copy link
Collaborator

cranmer commented Feb 17, 2020

Initial roadmap tied to reinterpretation user story:
https://github.com/iris-hep/as-user-facing/blob/master/reinterpretation.md

@cranmer cranmer closed this as completed Feb 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
AS Analysis Systems
Projects
None yet
Development

No branches or pull requests

4 participants