[Hallb-engineering] Data logging of Hall B vacuum signals

[Nathan Baltzell]

Hi Dave,

All but one of the PVs on the attached screenshot are already being archived, with the deadbands below.

-Nathan

B_TORUS:VAC:CG8100: host=opsmya9, active=1, request=1, type=6, size=1, deadband='2e-6' {TORUS_VACUUM}
B_TORUS:VAC:CG8100TB: host=opsmya9, active=1, request=1, type=6, size=1, deadband='5%' {TORUS_VACUUM}
B_TORUS:VAC:CG8101: host=opsmya9, active=1, request=1, type=6, size=1, deadband='2e-6' {TORUS_VACUUM}
B_TORUS:VAC:CG8102: host=opsmya9, active=1, request=1, type=6, size=1, deadband='2e-6' {TORUS_VACUUM}
B_TORUS:VAC:CG8103: host=opsmya9, active=1, request=1, type=6, size=1, deadband='2e-6' {TORUS_VACUUM}
B_TORUS:VAC:CG8103_AVG10HR: host=opsmya9, active=1, request=1, type=6, size=1, deadband='2%' {TORUS_VACUUM}
B_TORUS:VAC:CG8103_AVG1HR: host=opsmya9, active=1, request=1, type=6, size=1, deadband='2%' {TORUS_VACUUM}
B_TORUS:VAC:CG8103_RATE: host=opsmya9, active=1, request=1, type=6, size=1, deadband='2%' {TORUS_VACUUM}
B_TORUS:VAC:PV8100: host=opsmya9, active=1, request=1, type=3, size=1 {TORUS_VACUUM}
B_TORUS:VAC:PV8101: host=opsmya9, active=1, request=1, type=3, size=1 {TORUS_VACUUM}
B_TORUS:VAC:PV8105RB: host=opsmya9, active=1, request=1, type=3, size=1 {TORUS_VACUUM}
B_TORUS:VAC:TB8100: host=opsmya9, active=1, request=1, type=6, size=1, deadband='1%' {TORUS_VACUUM}
B_TORUS:VAC:TB8101: host=opsmya9, active=1, request=1, type=6, size=1, deadband='1%' {TORUS_VACUUM}
B_TORUS:VAC:TC8100: host=opsmya9, active=1, request=1, type=6, size=1, deadband='5%' {TORUS_VACUUM}
B_TORUS:VAC:TC8101: host=opsmya9, active=1, request=1, type=6, size=1, deadband='5%' {TORUS_VACUUM}
B_TORUS:VAC:TC8102: host=opsmya9, active=1, request=1, type=6, size=1, deadband='5%' {TORUS_VACUUM}
B_TORUS:VAC:TC8103: host=opsmya9, active=1, request=1, type=6, size=1, deadband='5%' {TORUS_VACUUM}
B_TORUS:VAC:TC8103_AVG10HR: host=opsmya9, active=1, request=1, type=6, size=1, deadband='2%' {TORUS_VACUUM}
B_TORUS:VAC:TC8103_AVG1HR: host=opsmya9, active=1, request=1, type=6, size=1, deadband='2%' {TORUS_VACUUM}
B_TORUS:VAC:TC8103_RATE: host=opsmya9, active=1, request=1, type=6, size=1, deadband='5' {TORUS_VACUUM}
B_TORUS:VAC:TC8104RP: host=opsmya9, active=1, request=1, type=6, size=1, deadband='5%' {TORUS_VACUUM}
B_TORUS:VAC:TC8105: host=opsmya9, active=1, request=1, type=6, size=1, deadband='5%' {TORUS_VACUUM}
B_TORUS:VAC:UPS_OnBatt: host=opsmya9, active=1, request=1, type=3, size=1 {TORUS_VACUUM}
B_TORUS:VAC:XFER_SW: host=opsmya9, active=1, request=1, type=3, size=1 {TORUS_VACUUM}
B_TORUS:VAC:XFER_SW_CTRL not archived
[cid:4077CE22-5A32-41E0-85C7-144379BA801F]

On Aug 24, 2023, at 8:39 AM, David Kashy <kashy at jlab.org<mailto:kashy at jlab.org>> wrote:

Hi Nathan,
I'm not sure if you are still involved in this but I'm requesting that ALL Hall B Torus vacuum epics signals are data logged. These are allon the Torus Vacuum  Controls - PLC GUI

My suggestion is that if a signal changes more than 10% in value the new value is logged. This should be plenty granular to see important changes and log events and yet not take too much data, because these are quite stablel signals. They typically jitter on the 2nd or 3rd significant digit.

Thanks
Dave

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/hallb-engineering/attachments/20230824/4ab98788/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2023-08-24 at 1.50.43 PM.png
Type: image/png
Size: 99589 bytes
Desc: Screen Shot 2023-08-24 at 1.50.43 PM.png
URL: <https://mailman.jlab.org/pipermail/hallb-engineering/attachments/20230824/4ab98788/attachment-0001.png>