I seem to be getting a "Memory Allocation Error" from DPlot when trying to run "Equal Intervals" in preparation for running an fft on one of the curves I'm plotting. It's not all the time, and it's happening sometimes with medium size data sets (4x48000) and not with larger sets (4x99000).
Is it something with my data?
This is a vague question on purpose. I am probably misapplying the commands, perhaps because my assumption about the x-axis values were not correct. But it seemed to work anyway on similar data from the same test series. The error complaint came with 2.1.3.0, but seemingly not with 2.1.2.8 or 2.1.2.9.
Version is 2.1.3.0 on WinXPPro sp2 and 1 gig memory.
Thanks.
Jon
Memory Allocation Error
Moderator: DPlotAdmin
-
DPlotAdmin
- Posts: 2312
- Joined: Tue Jun 24, 2003 9:34 pm
- Location: Vicksburg, Mississippi
- Contact:
Jon,
4x99000 isn't particularly large, so my best guess is something else is botched up. Like one or more of your curves don't have monotonically increasing X values (X(1)<X(2)<X(3)...), which might end up leading to attempting to allocate a negative number of points. DPlot should leave a curve that isn't sorted out of the list of curves so that you can't select it, but it is possible I've overlooked something.
Or, more likely... if instead of using the menu command you're using EditEqualInts in a macro or from another program then please let me know; checking the code I see that the above could easily happen in that case.
4x99000 isn't particularly large, so my best guess is something else is botched up. Like one or more of your curves don't have monotonically increasing X values (X(1)<X(2)<X(3)...), which might end up leading to attempting to allocate a negative number of points. DPlot should leave a curve that isn't sorted out of the list of curves so that you can't select it, but it is possible I've overlooked something.
Or, more likely... if instead of using the menu command you're using EditEqualInts in a macro or from another program then please let me know; checking the code I see that the above could easily happen in that case.
Visualize Your Data
support@dplot.com
support@dplot.com
No macro - this was all done through menu commands.
Data came through to DPlot via Excel through the plugin. X-axis, although not formatted in Excel as a time value, was all consecutively numbered, but I think I was losing precision because of the 3000/sec rate of the collection - I was manipulating two excel columns into one equivalent time value first as 00000.000, and then as 00.000000 digits of precision when I realized I had made a mistake. (Shouldn't have trouble with all of the double precision you have in there now!).
I'll watch what I'm doing and see if it happens any with some of the other data sets that I have to look at. I suppose the smart thing to do would be to take the decimal place out all together and make an integer out of the time data.
Data came through to DPlot via Excel through the plugin. X-axis, although not formatted in Excel as a time value, was all consecutively numbered, but I think I was losing precision because of the 3000/sec rate of the collection - I was manipulating two excel columns into one equivalent time value first as 00000.000, and then as 00.000000 digits of precision when I realized I had made a mistake. (Shouldn't have trouble with all of the double precision you have in there now!).
I'll watch what I'm doing and see if it happens any with some of the other data sets that I have to look at. I suppose the smart thing to do would be to take the decimal place out all together and make an integer out of the time data.