Experimental Physics and
Industrial Control System

an input link disables the associated calculation
   because the value field will have been fetched by the record
   before the calculation was to be performed. 

Bruce,

The transform record has two modes of operation.  The mode is
selected by the field COPT, which can take one of two values:

0) ("Conditional") do calculations only for fields that have
   not been written to since the last time the record processed.
   This is the default, because it's the behavior for which the
   record was originally written, and for backward compatibility
   with databases written before the COPT field was added.  In
   this mode, an input link disables the associated calculation
   because the value field will have been fetched by the record
   before the calculation was to be performed. 

1)  ("Always") do all calculations regardless of whether fields
   have been written to.  This is relatively new, and it's the
   behavior you want.

In either mode it's ok for an output link to point to the same
PV as the associated input link.

The idea of conditional, by the way, is to separate value fields
into independent variables (written to) and dependent variables
(not written to; recalculated from independent variables), to
implement bidirectional coordinate transformations.  More
details are in the documentation:

https://subversion.xor.aps.anl.gov/synApps/calc/trunk/documentation/transformRecord.html

Tim

----- Original Message -----
  

From: "Bruce Hill" <[email protected]>
To: [email protected]
Cc: [email protected]
Sent: Tuesday, September 27, 2011 5:05:16 PM
Subject: Transform Record no_inlink test
In using the transform record V5.7 from calc 2.8, I found that the
record has
a test in transformRecord.c line 398 that disables output calculations
for each variable that
has an input link.

If I disable that test for no_inlink, my transform record behaves as I
expect.

Does anyone know why that test is there?

It seems to preclude using the transform record input links which
select the same PV as the output links.
I can get around it by adding dfanout records to write the values
directly to the
transform record input fields, A-P, but it seems like an ugly
workaround.

Regards,
- Bruce



record( ao, "$(CAM):Gain" )
{
field( DESC, "Set camera gain" )
field( DRVH, "100" )
field( DRVL, "0" )
field( HOPR, "100" )
field( LOPR, "0" )
field( PINI, "YES" )
field( FLNK, "$(CAM):Gain:Calc PP" )
}

record( ao, "$(CAM):GainA" )
{
field( DESC, "Gain for side A" )
field( FLNK, "$(CAM):Gain:Calc PP" )
field( DOL, "0x042" )
field( DRVL, "0x042" )
field( DRVH, "0x1E8" )
}

record( ao, "$(CAM):GainB" )
{
field( DESC, "Gain for side B" )
field( FLNK, "$(CAM):Gain:Calc PP" )
field( DOL, "0x042" )
field( DRVL, "0x042" )
field( DRVH, "0x1E8" )
}

record( ao, "$(CAM):Gain:Offset" )
{
field( DESC, "Offset between gain halves" )
field( PINI, "YES" )
field( FLNK, "$(CAM):Gain:Calc PP" )
}

record( transform, "$(CAM):Gain:Calc" )
{
field( DESC, "Calc camera gain" )
field( INPA, "$(CAM):GainA" )
field( INPB, "$(CAM):GainB" )
field( INPH, "0x1E8" )
field( INPL, "0x042" )
field( INPO, "$(CAM):Gain:Offset" )
field( INPG, "$(CAM):Gain" )
field( CLCA, "(G/100)*(H-L)+L-(O/2)" )
field( CLCB, "(G/100)*(H-L)+L+(O/2)" )
field( CLCG, "(((A+B)/2)-L)*100/(H-L)" )
field( CLCO, "B-A" )
field( PINI, "YES" )
field( OUTA, "$(CAM):GainA PP" )
field( OUTB, "$(CAM):GainB PP" )
field( OUTG, "$(CAM):Gain PP" )
field( OUTO, "$(CAM):Gain:Offset PP" )
}
    

-- 
Bruce Hill
Member Technical Staff
SLAC National Accelerator Lab
2575 Sand Hill Road M/S 10
Menlo Park, CA  94025