Dan Guest (34ae248a) at 28 Mar 18:06
Updated documentation to use Derivation_tf rather than Reco_tf.
Hi @dguest, updated documentation for making new test files.
Hi @dguest, updated documentation for making new test files.
Review checklist:
This is a good compromise for now. I wouldn't copy the whole configuration for each variation though: you can make a base file, where "track_systematics": []
and similar for jet systematics, and then make each variation more like
{
"file": "retag_minimal_base.json",
"track_systematics": ["something"]
}
this will only be around 4 lines per file rather than 60
I would do this in the Athena
place below, and make it inherit from .run_athena
, that way you can also run the test with the rich
augmenter.
You need to add it to the .gitlab-ci.yaml
file, that's the one that actually steers the pipelines, the thing you edited is just the script it calls.
good question, I just looked, see here
https://atlas-ami.cern.ch/?subapp=tagsShow&userdata=p5981
I don't think there's any big difference from the default you'd get from that release, but there are a few extra settings. I probably wouldn't remake the test file for this but we should have the correct instructions.
I would be very surprised if it were clever enough but anything is possible.
That might explain why the metadata doesn't look the same between the file you created and the one where you truncated. But we also know something else isn't the same...
ok! So the derivation that you are creating here isn't the same as the one that has the p-tag you specified. You still need the --AMIConfig
(or similar) argument to make sure any specific flags are picked up. Sorry, I should have explained this before.
sorry! yes
I think we should create another variable for ONLINE_FTAG1_MC20
here.
@vhomsak this needs you to manually rebase it for some reason.
Hi @dguest, adding new 800030 sample just so I can pipeline test with exactly my configuration.
you got here first...
was this added by accident?
Dan Guest (c8a1d92d) at 28 Mar 15:21