Skip to content

Protection in the navigation conversion against loops in the navigation & configuration

This is small fix in the Run2 to Run 3 trigger navigation. It turns out that we have loops in the graph Here is (a bit speculative) explanation:

  • we set parent child relation between the TEs according to the linkage in Run2 navigation (no loop is possible there)
  • but then we cure this structure using config information So it is possible that chain A has TEs listed in signatures: T1 and then T2, but chain B has T2 and then T1. This may lead to loops. Tagging @wprzygod @tamartin

Merge request reports