yaq-project / yaq-fyi Goto Github PK

I'm opening this issue to ask for community discussion.

The Krishna group has asked for the addition of a new safety daemon. They are aware that mortal safety issues CANNOT be place PURELY in the hands of software. The point of the daemon is to hopefully prevent their mechanical safety features from kicking in because it's a big hassle to recover from that.

The desired behavior is to have a system of "checks" (other daemon state) and "consequences" (other daemon action). If any check reads as false all consequences will be immediately activated.

Checks

• all MFCs [1] have position between 75% and 125% of destination (with ~90 seconds of allowance for hysteresis)
• MFC supplying inert carrier gas has flow rate greater than 100 mL per minute

Consequences

• all reactive gas MFCs set to zero flow
• solenoid valves [2] set to direct gas to vent, away from catalyst
• tube furnace turned off

I'm tempted to make a general purpose daemon to achieve this behavior, name yaqd-watchdog. It would have a complex config format with some sort of way of specifying different kinds of checks and consequences.

My question to the community: would other people use this? What similar functionality have you been wishing for?

[1] https://www.brooksinstrument.com/en/products/mass-flow-controllers
[2] https://www.vici.com/vval/vval_2pos.php

https://gitlab.com/yaq/yaq-fyi/-/blob/main/helpers.py#L59

link to youtube channel from main page, blog posts

We should actively encourage people to cite yaq, and give clear guidlines as to how to do so.