EPICS Controls Argonne National Laboratory

Experimental Physics and
Industrial Control System

1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024  Index 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024 
<== Date ==> <== Thread ==>

Subject: scalcout and calc yielding different results
From: "Marco A. Barra Montevechi Filho via Tech-talk" <tech-talk at aps.anl.gov>
To: "tech-talk at aps.anl.gov" <tech-talk at aps.anl.gov>
Date: Tue, 12 Sep 2023 20:53:44 +0000
Hi all. I happened to bump into an interesting problem. Im using calc and scalcout records to translate a very small current measurement into a more convenient unit of measurement.

After having trouble with the software showing the wrong measurement unit, i came to the conclusion that  for some reason, although calc and scalcout are both double types, they seem to have different precision for comparisons.

I have the following example, made to get a very small amount of current in Amps and decide to either display it in pA, nA, uA, etc.:

record(ai, "CURRENT"){}

record(calc, "CALC") {

    field(INPA, "CURRENT CP")
    field(INPB, "1e-12")
    field(INPC, "1e-9")
    field(INPD, "1e-6")
    field(INPE, "1e-3")

    field(CALC, "F:=ABS(A);F<C?1:(F<D?2:(F<E?3:4))")
    field(PREC, "4")

    field(PINI, "YES")
    field(SCAN, "Passive")
}

record(scalcout, "CURRENTSCALEDUNIT"){

field(INPA, "CURRENT CP")
field(PREC, "15")
field(INPB, "1e-9")
field(BB, "pA")

field(INPC, "1e-6")
field(CC, "nA")

field(INPD, "1e-3")
field(DD, "uA")

field(INPE, "1")
field(EE, "mA")

field(CALC, "A:=ABS(A);A<B?BB:(A<C?CC:(A<D?DD:EE))")

field(OUT, "CURRENTSCALED.EGU")
field(OOPT, "Every Time")

field(PINI, "YES")
field(SCAN, "Passive")

}

record(calc, "CURRENTSCALED"){

field(INPA, "15")
field(CALC, "A")

field(PINI, "YES")
field(SCAN, "Passive")

}

However, if you caput CURRENT 9.94e-10 you will see CURRENTSCALEDUNIT.SVAL=nA and CALC.VAL=1, meaning that for the calc record, 9.94e-10<1e-09 is True but for the scalcout this is false.

Is this expected?

Thanks,

Marco

Aviso Legal: Esta mensagem e seus anexos podem conter informações confidenciais e/ou de uso restrito. Observe atentamente seu conteúdo e considere eventual consulta ao remetente antes de copiá-la, divulgá-la ou distribuí-la. Se você recebeu esta mensagem por engano, por favor avise o remetente e apague-a imediatamente.

Disclaimer: This email and its attachments may contain confidential and/or privileged information. Observe its content carefully and consider possible querying to the sender before copying, disclosing or distributing it. If you have received this email by mistake, please notify the sender and delete it immediately.


Replies:
Re: scalcout and calc yielding different results Mooney, Tim M. via Tech-talk

Navigate by Date:
Prev: Re: PyDevice device module compile error with linux-arm Josh Fiddler via Tech-talk
Next: Re: scalcout and calc yielding different results Mooney, Tim M. via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024 
Navigate by Thread:
Prev: Re: Question about text update widget is not updating text problem for phoebus neu lzf via Tech-talk
Next: Re: scalcout and calc yielding different results Mooney, Tim M. via Tech-talk
Index: 1994  1995  1996  1997  1998  1999  2000  2001  2002  2003  2004  2005  2006  2007  2008  2009  2010  2011  2012  2013  2014  2015  2016  2017  2018  2019  2020  2021  2022  <20232024 
ANJ, 12 Sep 2023 Valid HTML 4.01! · Home · News · About · Base · Modules · Extensions · Distributions · Download ·
· Search · EPICS V4 · IRMIS · Talk · Bugs · Documents · Links · Licensing ·