[AFIT-112]: FT0's reco update, 3 new event bits

[afurs]

https://its.cern.ch/jira/browse/AFIT-112

1. Added new three event bits for reco: IsActiveA, IsActiveC, IsFlangeEvent
2. Tech bits moved to dedicated recpoint field(+1 byte), mostly for recoQC

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[afurs]

+async-label async-2023-pbpb-apass4, async-2023-pp-apass4, async-2024-pp-apass1, async-2022-pp-apass7, async-2024-pp-cpass0, async-2024-PbPb-apass1, async-2024-ppRef-apass1, async-2024-PbPb-apass2, async-2023-PbPb-apass5

[alibuild]

Error while checking build/O2/fullCI_slc9 for 706c483 at 2025-03-28 18:57:

## sw/BUILD/O2-latest/log
CMake Error at cmake/O2RootMacroExclusionList.cmake:87 (message):

Full log here.

[afurs]

tests on macros failed? This PR does not contain any ROOT macros

[shahor02]

@afurs could you rebase your branch to dev?

[afurs]

Hello @shahor02 , done.

[shahor02]

Looks fine but I would prefer this to be validated by FT0. Since you want it to be used for the next Pb passes: did you test it?

[afurs]

Looks fine but I would prefer this to be validated by FT0. Since you want it to be used for the next Pb passes: did you test it?

Do you mean approve from FT0 experts? Codeowners(@jotwinow @andreasmolander ) or somebody else? I also attached(first comment and branch name as ID) JIRA ticket related to this PR, ticket was approved by FIT team at the "FIT Software Meeting" on 2024/02/27 An only difference is that I decided also to keep tech bits within rec point entity for next reco QC patch (will be prepared just right after this PR is merged)
I did some tests, but right now I'm repeating them for double check.

[afurs]

hotfix is needed

[afurs]

Actually we need to reconsider o2::fit::Triggers usage in recpoints, it is kind of overhead since these

AliceO2/DataFormats/Detectors/FIT/common/include/DataFormatsFIT/Triggers.h

Lines 135 to 140 in 1102011

	uint8_t nChanA = DEFAULT_ZERO; // number of fired channels A side
	uint8_t nChanC = DEFAULT_ZERO; // number of fired channels A side
	int32_t amplA = DEFAULT_AMP; // sum amplitude A side
	int32_t amplC = DEFAULT_AMP; // sum amplitude C side
	int16_t timeA = DEFAULT_TIME; // average time A side (shouldn't be used if nChanA == 0)
	int16_t timeC = DEFAULT_TIME; // average time C side (shouldn't be used if nChanC == 0)

fields are not informative in view of reconstruction. And they are reconstructed from ChannelData entities at CTF reading stage, w/o any calibration correction. Only trigger field is required for recpoints. But I will keep old logic just in case.

[afurs]

@shahor02 I tested again, only found minor incorrectness in the fields I mentioned above in comment. Hotfix applied. I think once some one from FT0 approve this we can go with merging (after successful CICD of course :) ), ok?

[alibuild]

Error while checking build/O2/fullCI_slc9 for fd24c67 at 2025-04-01 11:38:

## sw/BUILD/O2Physics-latest/log
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:
Error in cling::AutoLoadingVisitor::InsertIntoAutoLoadingState:


## sw/BUILD/O2-sim-challenge-test-latest/log
./sim-challenge.logDetected critical problem in logfile digi.log
./sim-challenge.logdigi.log:[5390:internal-dpl-ccdb-backend]: [11:38:18][ERROR] Exception while running: Fatal error. Rethrowing.
./sim-challenge.logdigi.log-[5390:internal-dpl-ccdb-backend]: [11:38:18][FATAL] Unhandled o2::framework::runtime_error reached the top of main of o2-sim-digitizer-workflow, device shutting down. Reason: Fatal error
./sim-challenge.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/37}
./sim-challenge.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/38}
./sim-challenge.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/40}
./sim-challenge.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/42}
./sim-challenge.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/43}
./sim-challenge.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/45}
./sim-challenge.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/46}
./sim-challenge.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/47}
./sim-challenge.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/48}
./sim-challenge.log[ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/49}
./sim-challenge.log[5391:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/37}
./sim-challenge.log[5391:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/38}
./sim-challenge.log[5391:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/40}
./sim-challenge.log[5391:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/42}
./sim-challenge.log[5391:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/43}
./sim-challenge.log[5391:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/45}
./sim-challenge.log[5391:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/46}
./sim-challenge.log[5391:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/47}
./sim-challenge.log[5391:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/48}
./sim-challenge.log[5391:TRDDigitizer]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/49}
./sim-challenge.log[5385:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/37}
./sim-challenge.log[5385:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/38}
./sim-challenge.log[5385:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/40}
./sim-challenge.log[5385:SimReader]: [ERROR] Found duplicate input binding with different spec.:collisioncontext {SIM/COLLISIONCONTEXT/42}
[0 more errors; see full log]

Full log here.

[afurs]

@shahor02 rebase again? Unrelated issues came in CICD

[shahor02]

@afurs it was a ccdb timeout after the main part of the FST was passed, ignore this.

[afurs]

@shahor02 only build/O2/fullCI_slc9 pipeline failed. Shall we skip it or restart only this one(if we have such functionality in AliecO2 CICD) ?

[shahor02]

@afurs that's ok, shall I merge it?

[afurs]

@shahor02 yes, please