alice: new dataset LHC10h/000137135 #3691
Conversation
psaiz
force-pushed
the
alice
branch
4 times, most recently
from
5551809 to
5311a60
Compare
| "energy": "2.76TeV", | ||
| "type": "PbPb" | ||
| }, | ||
| "created": "2025-02-11T15:53:44.819508", |
There was a problem hiding this comment.
The value of created field should be just a year.
| @@ -0,0 +1,69 @@ | |||
| [ | |||
There was a problem hiding this comment.
The name of the file, alice-2010-pbpb.json, looks very generic. Will there be more records in the same file? Or will there be other files? In which case it would be good to name it more specifically.
There was a problem hiding this comment.
The current name is LHC10h_000139510_PbPb_7.0TeV_205656_record.json
I've been told that there will be a single run per record.
Let me know it there is something to change.
| "uri": "root://eospublic.cern.ch//eos/opendata/alice/upload/2010/LHC10h/000139510/file-indexes/LHC10h_000139510_PbPb_2.76TeV_205656_file_index.json" | ||
| } | ||
| ], | ||
| "license": { |
There was a problem hiding this comment.
For heavy-ion physics data, we should add also the keyword information:
"keywords": [
"heavy-ion physics"
],There was a problem hiding this comment.
what would be the algorithm behind this? anything that is not pp then it's heavy-ion?
how will be the treatment for Xe-Xe, O-O, or p-Xe or p-O?
| }, | ||
| "publisher": "CERN Open Data Portal", | ||
| "recid": "1114", | ||
| "title": "LHC10h_000137135_PbPb_2.76TeV_213750", |
There was a problem hiding this comment.
Note that this does not look consistent with the old existing titles such as "LHC2010h_PbPb_ESD_138275". Shall we harmonise them?
There was a problem hiding this comment.
I was pointed to such a name: {PERIOD}_{RUN}_{BEAMTYPE}_{ENERGY}_{COLLISIONS_NR}
This data is converted data to O2 ALICE framework, there are no longer ESD/AOD present, only AO2D.root files. Let me know if different name is required and with what content.
| "publisher": "CERN Open Data Portal", | ||
| "recid": "1114", | ||
| "title": "LHC10h_000137135_PbPb_2.76TeV_213750", | ||
| "title_additional": "Lead-Lead data sample at the collision energy of 2.76TeV from run number 137135 of the LHC10h data taking period", |
There was a problem hiding this comment.
For the former ALICE records, the description used to say "Pb-Pb data sample" instead of "lead". Another cosmetic observation for harmonising.
There was a problem hiding this comment.
Ok, let's get back to symbolic name. How should pp look in this phrase? Pp, PP, or pp ?
| "Collision" | ||
| ] | ||
| }, | ||
| "updated": "2025-02-11T15:53:44.819508", |
There was a problem hiding this comment.
The updated field should not be present in the record JSON.
| }, | ||
| "updated": "2025-02-11T15:53:44.819508", | ||
| "usage": { | ||
| "description": "You can access and analyse these data through the ALICE Virtual Machine. Please follow the instructions for getting started and setting up the Virtual Machine:", |
There was a problem hiding this comment.
Note that ALICE VM is not working well due to those microCERNVM format changes. (The container is still fine.) Will there be a new VM (that will also work for the past data)?
There was a problem hiding this comment.
I do not know, i just picked up this part of OpenData task. I do not know the requirements : what kind of VM is required? i'm not sure if microcernvm is available for everyone as AFAIR there was a need for contextualization that was done from within cern account. VirtualBox format is vendor centric (so not necessary good for the long run), KVM AFAIK is linux only ... If you can give me some specifications i can prepare a Alma9 VM with cvmfs installed that can run the ALICE software.
No description provided.