Re: SynApps sscan record: timestamp issue for BUSY DATA and EXSC fields; causing problem archiving with Phoebus Archive engine

[Mark Rivers via Tech-talk <tech-talk at aps.anl.gov>]

What do you see if you use "-tc" in camonitor?


________________________________
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Kuldeep Joshi via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, September 14, 2021 5:20 AM
To: tech-talk at aps.anl.gov
Subject: SynApps sscan record: timestamp issue for BUSY DATA and EXSC fields; causing problem archiving with Phoebus Archive engine

Hello
I am getting the following output from camonitor for BUSY DATA and EXSC field of sscan record. I see in camonitor the timestamp for the sscan BUSY field is same for busy state and not busy.

iocA:scan1.EXSC               2021-09-14 14:10:10.180717 1
iocA:scan1.DATA               2021-09-14 14:24:49.126318 0
iocA:scan1.BUSY               2021-09-14 14:24:49.126318 1
iocA:scan1.EXSC               2021-09-14 14:24:49.126318 0
iocA:scan1.DATA               2021-09-14 14:24:49.126318 1
iocA:scan1.BUSY               2021-09-14 14:24:49.126318 0
iocA:scan1.EXSC               2021-09-14 14:24:49.126318 1
iocA:scan1.DATA               2021-09-14 14:30:58.778731 0
iocA:scan1.BUSY               2021-09-14 14:30:58.778731 1
iocA:scan1.EXSC               2021-09-14 14:30:58.778731 0
iocA:scan1.DATA               2021-09-14 14:30:58.778731 1
iocA:scan1.BUSY               2021-09-14 14:30:58.778731 0

I was thinking of archiving the BUSY field to indicate the start and end of scan. Here the archive engine of phoebus stores only the initial event Busy =1. This also causes the BUSY to be seen a spike in the databrowser.

The postgresql table listing for BUSY is given below
         56 | 2021-09-14 14:24:49.126318 | 126317989 |           5 |         8 |       1 |           |             |          |
         56 | 2021-09-14 14:30:01.659215 | 659214550 |           4 |        10 |         |           | Archive_Off |          |
         56 | 2021-09-14 14:30:01.759215 | 759215000 |           5 |         8 |       0 |           |             |          |
         56 | 2021-09-14 14:30:58.778731 | 778731080 |           5 |         8 |       1 |           |             |          |

If I have to extract the timeperiod during which the scan was active, I may have to use additional records to monitor the BUSY field and archive it.
Anyway in which I can achieve it elegantly

Regards,
Kuldeep