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: Using subArray |
From: | Michael Abbott <[email protected]> |
To: | Carl Lionberger <[email protected]> |
Cc: | Michael Abbott <[email protected]>, [email protected] |
Date: | Mon, 28 Nov 2005 21:01:16 +0000 (GMT) |
The thought was that the subarray record would be purely a soft record, and any hardware device support would be for waveform records that the subarray would read from. The MALM code makes sense in this context because the API for the dbaccess (as Noburu alluded to) always starts at element 0 of the source record. Therefore it is impossible to index an element larger than the buffer space you have.
You might consider writing a device support suite which supports a waveform record of the length you want and a couple of ao or longout records which control the index and length of the reference into the hardware..