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

Create record for derived data for 2011 jet validation step #1192

Open
katilp opened this issue Oct 7, 2016 · 13 comments
Open

Create record for derived data for 2011 jet validation step #1192

katilp opened this issue Oct 7, 2016 · 13 comments

Comments

@katilp
Copy link
Member

katilp commented Oct 7, 2016

FIles from /afs/cern.ch/user/m/mhaapale/work/public/Jet-Tuples-Summer2016
need to uploaded to a record (similar to http://opendata.cern.ch/record/230)
@tamshai can provide the metadata details.
It will refer to the new sw records (in #1191)

@katilp
Copy link
Member Author

katilp commented Apr 23, 2018

@tiborsimko Could you kindly move these files to eospublic so that Freya can check the code:
/afs/cern.ch/user/m/mhaapale/work/public/Jet-Tuples-Summer2016

The parent dataset for data is: /Jet/Run2011A-12Oct2013-v1/AOD
For MC, as indicated in https://github.com/cms-opendata-validation/2011-jet-inclusivecrosssection-ntupleproduction/blob/master/tuple_info_mc

@katilp
Copy link
Member Author

katilp commented Apr 23, 2018

So for data, they could be under
https://eospublichttp01.cern.ch/eos/opendata/cms/Run2011A/Jet
What kind of naming we had for ther derived datasets? I see that for evt display file they are under IG
and in https://eospublichttp01.cern.ch/eos/opendata/cms/Run2011A/DoubleElectron
we have PATtuples, so their directory could be call jettuples
(output of http://opendata.cern.ch/record/5104)

@tiborsimko
Copy link
Member

@katilp I get permission denied:

$ ls -l /afs/cern.ch/user/m/mhaapale/work/public/Jet-Tuples-Summer2016/
ls: cannot access /afs/cern.ch/user/m/mhaapale/work/public/Jet-Tuples-Summer2016/: Permission denied

Could be due to CMS-only access, I guess.

Could you move the files to some fully public AFS space?

we have PATtuples, so their directory could be call jettuples

PAT was referring to Physics Analysis Toolkit. Could be used here too perhaps? (I haven't seen the what the files are...)

@katilp
Copy link
Member Author

katilp commented Apr 24, 2018

@tiborsimko OK, it is the same for me, and I'm following with the afs support, I've added you in cc, it should be possible to copy them still.
For the naming, PATtuples is no good here as it is a specific well-defined format while this are plain root tuples containing jets. But it is the same format as in use in the CMS jet group so I would go for jettuples.

@katilp
Copy link
Member Author

katilp commented May 9, 2018

@tiborsimko
Copy link
Member

@katilp Thanks, I have the files:

8302268834 Jet-Tuples-Summer2016/data/OpenDataTuple-Data-Jet-Run2011A-npv.root
8281446820 Jet-Tuples-Summer2016/data/OpenDataTuple-Data-Jet-Run2011A.root
2491180282 Jet-Tuples-Summer2016/MC/OpenDataTuple-MC-QCD_Pt-15to1000_TuneZ2_7TeV_pythia6.root

For Data, we discussed storing them under /eos/opendata/cms/Run2011A/Jet/jettuples.

For MC, since there are multiple parents, where do we store them? E.g. (1) we could create a new directory /eos/opendata/cms/MonteCarlo2011/Summer11LegDR/QCD_Pt-15to1000_TuneZ2_7TeV_pythia6 and store them under jettuples there? Or (2) we could simply store both Data and MC in the same place? Depending on how many bibliographic records shall we create for jet tuples perhaps...

@katilp
Copy link
Member Author

katilp commented May 18, 2018

@tiborsimko Thanks!
It would make sense to create a new directory for the MC as you suggest i.e. (1)
This is somewhat different from the Higgs to 4l root files record 5501 (root files from data and MC in the same record) as that record contains root files with histograms only, while these are root files with event-by-event information.

@tiborsimko
Copy link
Member

Done, everything is copied:

  • /eos/opendata/cms/Run2011A/Jet/jettuples/OpenDataTuple-Data-Jet-Run2011A-npv.root
  • /eos/opendata/cms/Run2011A/Jet/jettuples/OpenDataTuple-Data-Jet-Run2011A.root
  • /eos/opendata/cms/MonteCarlo2011/Summer11LegDR/QCD_Pt-15to1000_TuneZ2_7TeV_pythia6/jettuples/OpenDataTuple-MC-QCD_Pt-15to1000_TuneZ2_7TeV_pythia6.root

Please let me know if you'd like to change the names in some way. (currently "OpenDataTuple-...")

We can proceed with the record creation. CC @ArtemisLav

@ArtemisLav
Copy link
Member

@katilp could you please provide the metadata for this record?

@katilp
Copy link
Member Author

katilp commented May 23, 2018

@ArtemisLav
Copy link
Member

ArtemisLav commented May 24, 2018

@katilp The metadata for the data record only mentions one file with 25607902 events, but in EOS we have 2 (OpenDataTuple-Data-Jet-Run2011A.root & OpenDataTuple-Data-Jet-Run2011A-npv.root). Should both go on this record?

Also, we are missing authors for the metadata. Is it the collaboration or specific people?

You can check out the commit below for what I have so far.

ArtemisLav added a commit to ArtemisLav/opendata.cern.ch that referenced this issue May 24, 2018
* (closes cernopendata#1192)

Signed-off-by: Artemis Lavasa
@tiborsimko tiborsimko removed this from the COD3-Consolidation milestone Jul 12, 2019
@tiborsimko
Copy link
Member

@ArtemisLav Thanks, I noticed that you haven't done the PR yet, the commit is only in your personal repository. Can you please make a PR and I'll amend as appropriate.

Note to self:

  • 10.7483/OPENDATA.CMS.IIIF.M653
  • 10.7483/OPENDATA.CMS.WE44.2399

@ArtemisLav
Copy link
Member

@tiborsimko PR done. It is a pretty old commit, so it will most likely require a lot of editing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants