Skip to content
This repository was archived by the owner on Mar 12, 2019. It is now read-only.

Conversation

@kakwok
Copy link
Collaborator

@kakwok kakwok commented Jun 19, 2018

Global runkey is useful for taking calibration events during interfill, instead of local health check runs.
The idea is to have two and only two runkeys: collision and cosmic for HCAL in LV0, which corresponds to two runkey names in the Grand Mastersnipept.

Since RUN_KEY comes with configure command in global, we will stop supporting maskedapps in the runkey like in local runs (maskedFMs already replaced by FEDmasking). In principle, we could still implement apps masking by disabling the apps in supervisor since we don't have excessive inter-FM connections for global configurations. But the use case for maskedapps is rare and will be quite confusing.

Therefore, in global, LV1 will have no selected runkey/mastersnippets during initAction and will only receive them from LV0 and pass them to LV2s during configueAction

//functionManager.getHCALparameterSet().put(new FunctionManagerParameter<StringT>("STATE",new StringT("Error")));
//if (TestMode.equals("off")) { functionManager.firePriorityEvent(HCALInputs.SETERROR); functionManager.ErrorState = true; return; }
}
}
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same check is done by checking: if (LocalRunKeyMap.get(LocalRunkeySelected)!=null){

@kakwok
Copy link
Collaborator Author

kakwok commented Jun 19, 2018

Tested at P5: http://cmsonline.cern.ch/cms-elog/1048320
We probably need to set a default runkey either in the code or preferably in LV0 configuration, to prevent shifter passing an empty runkey by default.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants