This involved a bit of tweaking everywhere, including to make sure I
actually have the kinematic selection build in and not making a view
container for them.

Chris Malena Delitzsch authored 2 years ago and Tadej Novak committed 2 years ago

Removing PFlow-Muon OR in R22

Jon Burr authored 2 years ago and Walter Lampl committed 2 years ago

Allow setting container selections directly in the MET maker

Nils Krumnack authored 2 years ago and Nils Erik Krumnack committed 2 years ago

If I want to do everything via blocks, this is one I need.

This is still very basic, but so is the sequence version.

That will be needed for most actual jobs, so it is good to have.

This now makes most algorithms work on PHYSLITE, and the ones that do
not work can be turned off.

This adds some tweaks to improve the performance of the sequence, some
extra variables commonly used, and allow running trigger selection
without filtering.

Teng Jian Khoo authored 2 years ago and Edward Moyse committed 2 years ago

Update jet analysis algs with NNJVT

Mostly based on what I did for the leptons and the existing jet
sequences.

Those were already there, just needed to be updated.

These are based closely on the ones for the electrons, with the code
from the current photon sequences.

This is mostly a transcribing of the electron sequence in the style of
the muon configuration block.

This removes all the implicit views created by the various sequences,
and instead creates explicit views as inputs for MET and OR.  And it
adds actual consistent thinning for all containers for the output.
And it adds pt/eta cuts for all the objects, which are probably way
off from what they should be...

I also had to add some extra configuration options/decorations to some
of the sequences to make it all consistent.

This is mostly a collection of all the algorithms tests from the
various CP algorithm packages loosely stitched together.  It probably
will need some more cleanup at some point, but it at least provides a
baseline to test the configuration blocks against as I develop them.

This is hopefully very straightforward, but also very incomplete: The
idea is that to validate the config blocks, I produce the same n-tuple
once with the config blocks and once with the sequences and then
compare it.  That validates that (at least for the chosen settings and
variables) both configurations are the same.  As a bonus, once
completed this also runs a fairly complete CP algorithms job in CI.

So far this is very incomplete, it only runs muons and only checks the
four-momentum, but having this in the release should allow adding more
objects and variables as I add more configuration blocks.

Currently that does nothing, but since meta-information might be used
it is probably better to configure than not to configure the sequence.

For now this just replaces the algorithm with a service, and
communicates the systematics list via the service interface instead of
via the event store.

The plan is to add more functionality in future merge requests that
will move a lot of the systematics handling functionality from the
configuration layer into the service.

Originally I had tried sweeping/cherry-picking this from 21.2, but
with all the three-way merges and commits that involve other
packages/directories that was rather painful, so this is now just a
direct copy from the current state in 21.2.