Hi Euan,
I had the same problem as you a few months ago when I played with a digitizer with huge memory. What I did is just removing the macro MAX_ARRAY_SIZE and its associated codes from aSubRecord.c so that there won't be any limit on the array size. I have not seen any problem with this change since.
It is Big Data Epoch in EPICS community.
Cheers,
Yong
________________________________________
From: [email protected] [[email protected]] on behalf of [email protected] [[email protected]]
Sent: Sunday, February 17, 2013 1:13 AM
To: [email protected]
Subject: aSub MAX_ARRAY_SIZE increase
Hi tech-talk,
I have an EPICS application that runs on Linux/Darwin where I need to increase the value of MAX_ARRAY_SIZE in aSubRecord.c from ten million to 200 million or possibly even 1000 million. Apart from creating a version of EPICS that is only locally compatible (and needing lots of memory to run) are there any likely problems with this change?
cheers,
Euan.
--
Euan Troup CSIRO Astronomy & Space Science +61 2 9372 4660
[email protected]<mailto:[email protected]>
- Replies:
- RE: aSub MAX_ARRAY_SIZE increase Dalesio, Leo
- References:
- aSub MAX_ARRAY_SIZE increase Euan.Troup
- Navigate by Date:
- Prev:
aSub MAX_ARRAY_SIZE increase Euan.Troup
- Next:
Re: AsynInt32 device support and mbbo records Hu, Yong
- 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
- Navigate by Thread:
- Prev:
aSub MAX_ARRAY_SIZE increase Euan.Troup
- Next:
RE: aSub MAX_ARRAY_SIZE increase Dalesio, Leo
- 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
| 
·
Home
·
News
·
About
·
Base
·
Modules
·
Extensions
·
Distributions
·
Download
·