IRIS: Support for IRIS CryoValve

[kjwoodsISIS]

As scientist working on IRIS, I need to monitor and control the IRIS CryoValve (i.e. open it or close it).

Acceptance Criteria

1. I can view and change the PVs which define the state of the ISIS CryoValve.
2. I can view and change the state of the ISIS CryoValve via the IBEX GUI.

Notes

1. The IRIS CryoValve is a device that is unique to IRIS.
2. We can base the IOC and OPI on the existing VI for the IRIS CryoValve. The commands for the CryoValve are very simple - they are documented in the attached readme.txt file.
3. When we have created the IOC and OPI, ask if we can test it on IRIS.

[AdrianPotter]

From @davidkeymer: IRIS Cryovalve - Readme.txt

[AdrianPotter]

ISISComputingGroup/ibex_gui#285
https://github.com/ISISComputingGroup/EPICS/pull/30
ISISComputingGroup/EPICS-ioc#50
https://github.com/ISISComputingGroup/EPICS-IrisCryoValve

[AdrianPotter]

I still have 2 cryo valves on my desk. Come get them from me when you want to do the testing.

[IsabellaRey]

Minor rework needed:

• IOC name should be max 8 chars long, and IOC top directory should have same name as IOC
• Following clarification with Freddie and update of developer Wiki: in the support module, the Makefile in the same directory as the protocol should include the protocol as "DATA += ". This will separate the source protocol from the build protocol, which lives in a data/ directory at the top of the support module. The st.cmd should then set its stream protocol path to "$(IRISCRYOVALVE)/data"

No functionality reviewed yet

[IsabellaRey]

Following review:

• Have protocol Makefile add protocol as "DATA += " and st.cmd should set protcol path pointing at the data/ directory (see updated manual)
• MASTER_RELEASE file: just move CRYVALVE macro up so file is in alphabetical order
• OPI: add $(NAME) macro at least in the OPI Name property
• Add emulator

[AdrianPotter]

All done