Update the minimum number of events per lumi from 45 to 10.
Is your feature related to a problem?
Some requests are not able to reach the minimum number of events per lumi (45), when this happens, PdmV manually skips the validation steps after checking some constraints and then injects them. This scenario is starting to become common and it brings delays to the MC production. Update the minimum boundary to 10, this value is also a valid lower boundary for the production system and avoids having this common issue related to the minimum number of events. For more details about this discussion, please see: CMSBPHMC-45
Describe the solution you'd like
Update the minimum number of events in the ValidationControl entity here and the request model here to 10.
Current behavior
The minimum number of events per lumi required to consider a request validation successful is 45.
Expected behavior
The minimum number of events per lumi required to consider a request validation successful is 10.
Update the minimum number of events per lumi from 45 to 10.
Is your feature related to a problem?
Some requests are not able to reach the minimum number of events per lumi (45), when this happens, PdmV manually skips the validation steps after checking some constraints and then injects them. This scenario is starting to become common and it brings delays to the MC production. Update the minimum boundary to 10, this value is also a valid lower boundary for the production system and avoids having this common issue related to the minimum number of events. For more details about this discussion, please see: CMSBPHMC-45
Describe the solution you'd like
Update the minimum number of events in the ValidationControl entity here and the request model here to 10.
Current behavior
The minimum number of events per lumi required to consider a request validation successful is 45.
Expected behavior
The minimum number of events per lumi required to consider a request validation successful is 10.