[Feature Request] Include Trigger Link Check in testConnectivity.py
Closed this issue · 2 comments
Brief summary of issue
Right now the connectivity testing is only checking the GBT paths between the backend and frontend electronics. There is no check of the health of the trigger links.
Types of issue
- Bug report (report an issue with the code)
- Feature request (request for change which adds functionality)
Expected Behavior
I think a step should be added between Step 3, Programming FPGA, and Step 4, GBT Phase Scans, that checks trigger link status is good. An example of a good link status is shown here.
This can be implemented by exposing getmonTRIGGEROHmainLocal(...) to the python API. To do this, for the short term, an xhal interface to the remote callable version of the local function getmonTRIGGEROHmain(...) should be provided in the legacyPreBoost branch of xhal. This would then need to be added to the the HwAMC class in gempython.
Concerns for Only QC7
When working with detectors in some other test stand (e.g. coffin, QC8, sustained operation, etc...) we will only care about the GEM trigger link.
For QC7 we want to check that both the GEM trigger link (in the MTP12 connector panel) and the CSC trigger link (separate LC duplex connector on patch panel). The way to do this would be for OHN to have the GEM trigger link going to OHN and the CSC trigger link going to OHN+1 on the fiber patch panel. Then the code should check for a given OH that OHN and OHN+1 have the good status. Here the provided ohMask with respect to the trigger should be treated as a even bits corresponding to OHN and odd bits corresponding to the CSC trigger link of OHN.
This behavior should only be checked if a given flag is provided, e.g. --checkCSCTrigLink. Otherwise OHN should only correspond to OHN trigger link and the code should respect the given ohMask.
Current Behavior
No check of the trigger link status is presently performed.
Context (for feature requests)
Need a way to check the health of the trigger links before the superchamber is closed.
Your Environment
- Version used: d38b974
@BenjaminRS this is needed by mid-march.