| 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 2025 | 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 2025 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: subArray record [SEC=UNOFFICIAL] |
| From: | Michael Davidsaver via Tech-talk <[email protected]> |
| To: | "STARRITT, Andrew" <[email protected]> |
| Cc: | "EPICS Tech Talk \([email protected]\)" <[email protected]> |
| Date: | Mon, 23 Dec 2019 17:41:34 -0800 |
On 12/23/19 5:13 PM, STARRITT, Andrew via Tech-talk wrote: > ... > My questions: Is this a bug or a feature? https://github.com/epics-base/epics-base/commit/3edc4b5c18741d1c17fd93d63498c2fe2bf594da#diff-3aae14301cf71a07ec8d5a307a827f46L172 While I haven't spent much time on subArrayRecord, the current code looks correct. no_elements should be set to the maximum element count here. Code which actually reads from this field should be calling rset::get_array_info() to find the actual length (from NORD). The previous code wouldn't work properly if the array size ever changed with clients connected. How many elements are are shown by: > camonitor -# 0 SR07BM01FPM01:FILL_PATTERN_ELEMENT_030_EXTRACT