Experimental Physics and
Industrial Control System

"Thompson, David H." <[email protected]> · Tue, 20 Jan 2009 14:05:03 -0500

I have been using comments like this for some time:

# @req $(S)_$(SS):Gate$(N)_$(DI):SubRevDlySet
# @arReq $(S)_$(SS):Gate$(N)_$(DI):SubRevDlySet 3600 Monitor
record(longout, "$(S)_$(SS):Gate$(N)_$(DI):SubRevDlySet") {
  field(DESC, "Sub-Revolution Delay").....

These are super easy to pull out of the expanded db file with sed. VDCT
preserves comments with the records. With a supporting make target in
the RULES file it becomes reasonably transparent.    Not elegant but
functional.

I don't maintain most of the IOCs where this PV lives so I have to do as
much as I can to help the IOC engineers if I want the timing PVs
restored.

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Andrew Johnson
Sent: Tuesday, January 13, 2009 11:20 AM
To: [email protected]
Cc: Alarcon, Arturo
Subject: Re: Vdct and autosave's info field

On Tuesday 13 January 2009 09:01:03 Tim Mooney wrote:
>
> Autosave (v 4.3 and later) does already permit info nodes to specify
the
> fields that are to be autosaved.  However, I have not found a way to
> make vdct leave these fields in a database.

This doesn't solve the issue with vdct remembering info data (the
ability to 
do so will have to be coded into vdct; if someone needs this and is
willing 
to pay for it, I'm sure CosyLab will be happy to oblige), but you can at

least put the info data into a separate file.db that just contains
entries 
like these:

record(type,name) {
  info(key,value)
  ...
}
...

It wouldn't be hard to write a tool to pull just these items out of an 
existing .db file into a separate file; ask me if it would help and I'll
see 
what I can do.

- Andrew
-- 
The best FOSS code is written to be read by other humans -- Harold Welte

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System