Karol and Manuel asked if we could add a control message mechanism
to InhibitMaster and friends to help cleanly start/stop/initialize/kill
the InhibitMaster. Requirement is a one-shot command issued from JCOP
that will put InhibitMaster through its paces. I have a prototype
working with the FakeSpillInhibit. Likely will add a "status" message
state as well.
(I realize that we have a state machine and commander interface and
etc. that this would be good to add into, but likely want something
quicker and dirtier for now)
Feature #20362
Add external controlling functionality to InhibitMaster
Added by [Wesley Ketchum](https://cdcvs.fnal.gov/redmine/users/899) [almost 4 years](https://cdcvs.fnal.gov/redmine/projects/artdaq/activity?from=2018-07-19) ago. Updated [almost 4 years](https://cdcvs.fnal.gov/redmine/projects/artdaq/activity?from=2018-07-25) ago.
Status:
Assigned
Priority:
Low
Assignee:
[Wesley Ketchum](https://cdcvs.fnal.gov/redmine/users/899)
Category:
-
Target version:
-
Start date:
07/19/2018
Due date:
% Done:
0%
Estimated time:
Experiment:
-
Co-Assignees:
Duration:
[Quote](https://cdcvs.fnal.gov/redmine/issues/20362/quoted)
Description
Karol and Manuel asked if we could add a control message mechanism to InhibitMaster and friends to help cleanly start/stop/initialize/kill the InhibitMaster. Requirement is a one-shot command issued from JCOP that will put InhibitMaster through its paces. I have a prototype working with the FakeSpillInhibit. Likely will add a "status" message state as well.
(I realize that we have a state machine and commander interface and etc. that this would be good to add into, but likely want something quicker and dirtier for now)
[Add](https://cdcvs.fnal.gov/redmine/projects/artdaq/issues/new?back_url=%2Fredmine%2Fissues%2F20362&issue%5Bparent_issue_id%5D=20362&issue%5Btracker_id%5D=2)
Subtasks
[Add](https://cdcvs.fnal.gov/redmine/issues/20362#)
Related issues
History
[#1](https://cdcvs.fnal.gov/redmine/issues/20362#note-1)
Updated by [Kurt Biery](https://cdcvs.fnal.gov/redmine/users/16) [almost 4 years](https://cdcvs.fnal.gov/redmine/projects/artdaq/activity?from=2018-07-25) ago
[Quote](https://cdcvs.fnal.gov/redmine/issues/20362/quoted?journal_id=62294) [Edit](https://cdcvs.fnal.gov/redmine/journals/62294/edit) [Delete](https://cdcvs.fnal.gov/redmine/journals/62294?journal%5Bnotes%5D=)
Something to be considered here is when the InhMaster should receive various RC commands, compared to other processes.
[#2](https://cdcvs.fnal.gov/redmine/issues/20362#note-2)
Updated by [Wesley Ketchum](https://cdcvs.fnal.gov/redmine/users/899) [almost 4 years](https://cdcvs.fnal.gov/redmine/projects/artdaq/activity?from=2018-07-25) ago
Status changed from New to Assigned
Assignee set to Wesley Ketchum
Feature #20362
Add external controlling functionality to InhibitMaster
Added by Wesley Ketchum almost 4 years ago. Updated almost 4 years ago.
0%
Description
Karol and Manuel asked if we could add a control message mechanism to InhibitMaster and friends to help cleanly start/stop/initialize/kill the InhibitMaster. Requirement is a one-shot command issued from JCOP that will put InhibitMaster through its paces. I have a prototype working with the FakeSpillInhibit. Likely will add a "status" message state as well.
(I realize that we have a state machine and commander interface and etc. that this would be good to add into, but likely want something quicker and dirtier for now)
Subtasks
Related issues
History
#1 Updated by Kurt Biery almost 4 years ago
Something to be considered here is when the InhMaster should receive various RC commands, compared to other processes.
#2 Updated by Wesley Ketchum almost 4 years ago