09-24-2010 12:29 PM
@for(imstuck) wrote:
Blah, I don't have 2010 installed yet.
Don't get too upset, I'm still stuck back at 8.6.1
09-24-2010 12:30 PM
Here's the 2009 version
09-24-2010 12:49 PM
If you want to delete the headers, just use Delete Array. Wire in the length (1 for one row), and the starting row number (0). This will remove the first row from the array. No need to transpose. You may be getting an error because you have not wired your array subset function fully. You specify an index number and length, and another index number but no length. This returns all the items starting at that index. Then you do it again in your next array subset function. You are displaying 5 very huge arrays. No wonder you are running out of memory. You don't have to display all of those arrays. Just delete the headers and display the rest once.
09-27-2010 01:47 AM
If you want to compare the versions you can skip the All rows and write to a local variable of the end result and pause through a Breakpoint. Your indicators below the sequence (which you dont need at all, btw) makes 3 copies of that big data chunk so it will stress your memory. 🙂
This is a simple change that should make it easier.
/Y
09-27-2010 03:36 AM
@dt1804 wrote:
Why would one way (non-transposing) make me run out of memory, while the other would not?
I think the memory is used up by the charts. (You set the chart history to 7200).
Your data is 8x100k, so if you don't transpose, you are trying to display 100k traces, which would need a monitor the size of a skyscraper (You set it to "Stack plots!). If you transpose, you are displaying 8 traces.
So the memory footprint of the charts for the two scenarios is:
09-27-2010 09:08 AM
That indeed is the memory issue as soon as I get rid of the charts or transpose the array all is well.
09-28-2010 01:44 AM
That's why altenbach is a knight and the rest of us squires at best. 🙂