Experimental Physics and
Industrial Control System

[email protected] (Rozelle Wright) · Wed, 27 Mar 96 08:43:34 MST

> From [email protected] Wed Mar 27 07:47:15 1996
> Return-Path: <[email protected]>
> Sender: [email protected]
> Date: Wed, 27 Mar 1996 08:45:52 -0600
> X-Mailer: Mozilla 2.01 (X11; I; SunOS 5.4 sun4m)
> Mime-Version: 1.0
> To: [email protected]
> Subject: Re: Problem changing to use ASCII database
> Content-Type> : > multipart/mixed> ; > boundary="------------4DE8112158A7"> 
> Content-Length: 2168
> X-Lines: 68
> 
> This is a multi-part message in MIME format.
> 
> --------------4DE8112158A7
> Content-Type: text/plain; charset=us-ascii
> Content-Transfer-Encoding: 7bit
> 
> Here is the problem:
> 
> sf2db passes along PP or NPP IF it is defined. If neither PP or NPP
> is defined then the .db file will not have it defined.
> 
> If the .db file does not have have PP or NPP defined,
> NPP is the default.
> This default is made by the Static Database Access Library,
> which can not be changed without causing problems for non-capfast
> users.
> 
> If DCT reads in a short form report that does not have PP .or NPP
> defined the default is PP.
> 
> Thus if CAPFAST Users do not define PP on pv links there will
> be a different result using dct to convert the short form report
> vs using sf2db.
> 
> In hindsite the default for capfast users should also have been
> NPP. Since capfast users relied on dct to convert short form reports,
> the default become PP.


> 
> What to do??
> 
> Marty Kraimer
> 
I'm not sure about other sites, but here at Los Alamos, all of our capfast symbols
have pproc(<for every link where it matters>) set to NPP, so the change won't affect
us at all.  I think most places using capfast got their symbols from us, so
it should not be a real problem for capfast users.  It is a problem for people
who made their databases directly from dct.
Rozelle

Experimental Physics and Industrial Control System

Experimental Physics and
Industrial Control System