Re: channelwatcher vs BURT

[Ralph Lange <Ralph.Lange@bessy.de>]

Hello Heinrich,

You are correct:

BURT is about saving and restoring snapshots. You have pre-configured 
lists of channels, and the operator decides at a certain moment to take 
a snapshot of the listed channels' values. This snapshot is saved as (a 
set of) file(s), and can be restored to the channels at a later time.

AutoSaveRestore is about having channels keep their values during a 
reboot. You have similar pre-configured lists of channels, but the 
values are continuously saved to file, and the IOC loads the most recent 
values back during startup.

ChannelWatcher only replaces the "save" part of that system: the 
original AutoSaveRestore writes the data directly from the IOC to a 
file, while the ChannelWatcher is a daemon on a remote system, that 
collects the data through channel access to write it locally to file.

There are GUI interfaces to BURT: Thomas Birke wrote one (TCL/TK) that 
we use at BESSY (Thomas.Birke@bessy.de), Steve Singleton recently wrote 
a new GUI with similar features (python), which is in use at Diamond. 
(He was giving a talk at the last EPICS meeting, you will find his 
slides on the meeting page.)

Hope this helps,
Ralph


Heinrich du Toit wrote:
> Hi
>
> Am I correct in saying that channel watcher and BURT does not do exactly
> the same thing?
>
> channel watcher will make sure PVs keep values between IOC reboots
> (crashes/powertrips)
>
> while BURT can be used if we have multiple/different setups for PVs
> inside IOCs.
>
> So actually both is needed?
>
> Is there some kind of GUI interface to manage BURT?
> So that operators can easily switch between different configs?
>
> -Heinrich
>
>