During the transition to ntp commands, AS and DPS integration it became clear that we need a test for the workflow.
Since a proxy is required (at least for now) I suggest the creation of ntp test for testing PRs.
ntp test should be a complete workflow test:
- process 1 file for each sample in the current campaign (miniAOD → ntuple → AS trees)
- run the complete DPS workflow (00 - 05)
- compare results to the previous iterations
This is a big PR, so I will break it down in several others. In the end this is something similar to what CMSSW does for validation. The question is if it will save us time in the long run to warrant the implementation.
We do have ntp run X --test to test things for a single file, so ntp test would run that for each sample.
During the transition to ntp commands, AS and DPS integration it became clear that we need a test for the workflow.
Since a proxy is required (at least for now) I suggest the creation of
ntp testfor testing PRs.ntp testshould be a complete workflow test:This is a big PR, so I will break it down in several others. In the end this is something similar to what CMSSW does for validation. The question is if it will save us time in the long run to warrant the implementation.
We do have
ntp run X --testto test things for a single file, sontp testwould run that for each sample.