Very minimal changes actually needed, as the majority of "offline" trigger reconstruction for MC happens during the RDO to RDO_TRIG substep.
Continue to veto Run 1 MC (currently unsupported workflow)
Support R2 navigation thinning (similar to R3 MC)
Support R2->R3 navigation conversion. NOTE: We intent to initially do this via AOD->DAOD, but nice to be able to support it during AOD production too in the future for the next R2 reprocessing to AOD in 2025 (cc @wprzygod)
Support R3 AOD/ESD level navigation thinning on any R2->R3 conversion output.
Tim Martin authored
