Skip to content

Conversation

@sawenzel
Copy link
Collaborator

@sawenzel sawenzel commented Jun 4, 2025

AOD: Possibility to inject additional meta data

Commit provides possibility to inject additional (non-hard-coded)
meta data into AOD. This could be used by MC to add information about
timeframe length used or other specific configurations etc.

The commit relates to https://its.cern.ch/jira/browse/O2-6027

By default this does not change any production behaviour. Existing
meta data is not touched.

This works by generating a simple key-value json (foo.json) like

{
    "ALIEN_JDL_MC_ORBITS_PER_TF": "4",
    "ALIEN_JDL_ANCHOR_SIM_OPTIONS": "-gen pythia8"
}

and then exporting an environment variable pointing to this json.

export AOD_ADDITIONAL_METADATA_FILE=${PWD}/foo.json

@sawenzel sawenzel requested a review from a team as a code owner June 4, 2025 13:13
@github-actions
Copy link
Contributor

github-actions bot commented Jun 4, 2025

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

@sawenzel sawenzel force-pushed the swenzel/aod-additional-metadata branch from be76adc to 0c0ea9a Compare June 4, 2025 13:16
@alibuild
Copy link
Collaborator

alibuild commented Jun 4, 2025

Error while checking build/O2/fullCI_slc9 for 0c0ea9a at 2025-06-04 19:42:

## sw/BUILD/O2-latest/log
/sw/SOURCES/O2/14362-slc9_x86-64/0/Detectors/AOD/src/AODProducerWorkflowSpec.cxx:106:10: fatal error: nlohmann/json.hpp: No such file or directory
ninja: build stopped: subcommand failed.

Full log here.

Commit provides possibility to inject additional (non-hard-coded)
meta data into AOD. This could be used by MC to add information about
timeframe length used or other specific configurations etc.

The commit relates to https://its.cern.ch/jira/browse/O2-6027

By default this does not change any production behaviour. Existing
meta data is not touched.

This works by generating a simple key-value json (foo.json) like
```
{
  "ALIEN_JDL_MC_ORBITS_PER_TF": "4",
  "ALIEN_JDL_ANCHOR_SIM_OPTIONS": "-gen pythia8"
}
```

and then exporting an environment variable pointing to this json.

```
export AOD_ADDITIONAL_METADATA_FILE=${PWD}/foo.json
```
@sawenzel sawenzel force-pushed the swenzel/aod-additional-metadata branch from 0c0ea9a to b71868c Compare June 5, 2025 09:30
@sawenzel sawenzel merged commit 893836d into AliceO2Group:dev Jun 6, 2025
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants