recast-hep / recast-flask-frontend Goto Github PK

mode:

ScanRequest
    - PointRequest1
        - PointCoordinate: {name: X, value: 1.03}
        - PointCoordinate: {name: Y, value: 1.05}
    - PointRequest2
        - PointCoordinate: {name: X, value: 2.03}
        - PointCoordinate: {name: Y, value: 2.05}
    - PointRequest3
        - PointCoordinate: {name: X, value: 3.03}
        - PointCoordinate: {name: Y, value: 3.05}

currently we have DOI, arxivID, inspireID, etc....

I think we have an evolving picture of what the input is. And there might be more complicated schemes to determined the xsec (filter efficiencies / branching ratios etc..) so I think it's best to just have a generic ZIP file as the lowest common denominator. if a pattern emerges we can evolve later.

cc @cranmer

from an email with Javier Montul working on INSPIRE next

It is a a mixture between this part of Invenio https://github.com/inveniosoftware/invenio/blob/master/invenio/ext/arxiv/__init__.py that allows to query arXiv and get Json back and then all the user facing part happens on JavaScript here:

• https://github.com/inspirehep/inspire-next/blob/master/inspire/modules/deposit/static/js/deposit/literature_submission_form.js#L562
• https://github.com/inspirehep/inspire-next/blob/master/inspire/modules/deposit/static/js/deposit/data_sources/arxiv.js

There is quite a lot of code ;) you can ask me some questions if you want.

@lukasheinrich can point to his eve + flask example

show values related to the PointResponse (and if there are BasicResponses, show all of them, too)

maybe already done. State about "complete, in process, completed, etc."

this view should show all the basic requests (with links to download the archive)

one off user provided LHE file (not reproducible)

aretha based model, parameter, process
https://github.com/aretha-hep

User stories should also tie into tests

Note some overlap with https://github.com/recast-hep/recast-frontend/issues

Perimeter,
NSF,
DASPOS, DIANA,
CERN, CAP, DPHEP
GitHub (ask @arfon )
Other potential partners: rackspace,carina, AWS, travis, etc.

Might want to include universities,

we need some way to store the recast requests archives on the server, so that they can be retrieved later. so for this we need some fixed filestructure.

In heroku this can be tricky, but this can work:

https://devcenter.heroku.com/articles/s3