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

Update example json config file #269

Merged
merged 1 commit into from
Sep 24, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/basics-usage/JsonConfigs.md
Original file line number Diff line number Diff line change
Expand Up @@ -43,7 +43,7 @@ that one wishes to execute.
"syst": "pp",
"muonSelection": "0",
"customDeltaBC": "300",
"isMC": "true",
"isMC": "1",
"processRun2": "false",
"processRun3": "true"
},
Expand All @@ -67,7 +67,7 @@ that one wishes to execute.

In the above example of json file, in the `pseudorapidity-density` section (line 37 to 44), you can see the different values of the configurables, `maxDCAZ` is now 3.2 for instance. You can also specify the type of data you are processing with the flags `processRun2` `processRun3` and `isMC`.

Another very useful thing is that inside this file you can provide a list of aod files to analyse, as you can see the line 10 `"aod-file": "@inputs-sim.txt"` means that the workflow will analyse the all the files contained in the txt file `inputs-sim.txt`, with one file name per line.
Another very useful thing is that inside this file you can provide a list of aod files to analyse, as you can see the line 10 `"aod-file-private": "@inputs-sim.txt"` means that the workflow will analyse the all the files contained in the txt file `inputs-sim.txt`, with one file name per line.

## How to give this json file to the workflow

Expand Down
Loading