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 2023 2024 | 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 2023 2024 |
<== Date ==> | <== Thread ==> |
---|
Subject: | subArray record [SEC=UNOFFICIAL] |
From: | "STARRITT, Andrew via Tech-talk" <[email protected]> |
To: | "EPICS Tech Talk ([email protected])" <[email protected]> |
Date: | Tue, 24 Dec 2019 01:13:12 +0000 |
Happy Christmas Tech-Talkers, The following is an extract from one of my IOCs. record (waveform, "SR07BM01FPM01:FILL_PATTERN_ABS_WAVEFORM") { field (DESC, "FPM Abs Data") field (SCAN, "Passive") field (NELM, "360") field (FTVL, "DOUBLE") field (PREC, "5") } ... record (subArray, "SR07BM01FPM01:FILL_PATTERN_ELEMENT_030_EXTRACT") { field (DESC, "Extract element 30") field (SCAN, "Passive") field (INP, "SR07BM01FPM01:FILL_PATTERN_ABS_WAVEFORM CP") field (FTVL, "DOUBLE") field (MALM, "360") field (NELM, "1") field (INDX, "$(I)") } Using base-3-15-6, running cainfo SR07BM01FPM01:FILL_PATTERN_ELEMENT_030_EXTRACT
yields SR07BM01FPM01:FILL_PATTERN_ELEMENT_030_EXTRACT State: connected Host: CR01GW17-CTL:5064 Access: read, no write Native data type: DBF_DOUBLE Request type: DBR_DOUBLE Element count: 360 However, previously with an IOC using 3.14.8.4 this yielded a single valued PV. We only noticed this when examining the Archive Appliance statistics (which PVs are archiving the most data) The subArrayRecord.c cvt_dbaddr function has changed from if (!psa->udf && psa->nelm > psa->nord) paddr->no_elements = psa->nord; else paddr->no_elements = psa->nelm; to paddr->no_elements = prec->malm; My questions: Is this a bug or a feature? Cheers Andrew
|