isorb - #243
Conversation
|
|
||
| The principle of operation is to 'dose' gas into a porous material, and measure the rate at which that gas gets adsorbed onto that material. When used on a beamline, we also want to perform neutron measurements between doses. | ||
|
|
||
| The iSorb has no native communication interface (despite the manufacturer having been asked for this). Our support is implemented in an unusual way: |
There was a problem hiding this comment.
Pretty concerned we are describing ourselves as supporting this device, despite having explicitly told the group that having procured something we couldn't talk to we wouldn't prioritise doing so.
There was a problem hiding this comment.
Is there something you'd like me to reword?
There was a problem hiding this comment.
Does the nature of this work need reflecting here? I.e. are we offering a different level of support? Do we have different expectations around reliability? If the answer is no to both, then no changes needed.
There was a problem hiding this comment.
Perhaps the word "support" here is doing too much - I wrote it in the purely technical sense as in device support or EPICS support module. Whereas I think you're interpreting it as a slightly different version of "support". I'll edit and clarify this...
Clarified the implementation of EPICS support for the iSorb gas adsorption system, detailing the use of GUI automation and log-scraping.
2 participants
ISISComputingGroup/IBEX#8935