Why do I get a Track out of memory error while running open loop frequency response?

[JColich]

MatrixX Build 61mx1411: I get a "Track out of memory" error when I run the Open Loop Frequency Response from the MatrixX pull down tools. What can I do to prevent this? We are running on an HP B1000 with 768 MB of RAM under HP-UX 10.2.

[Garrett]

I am not certain that this is helpful, but if there is a later version of Mx for that version of HP-UX you may want to consider moving to it.

I found Mx 6.2.2 very robust.

Otherwise I would go through Tech support and see if they can duplicate the error with the model on which you are working and same OS version.

[JColich]

Thanks Garrett, I'll give it a try.

By chance, do you know what: Build {rstack=50000,istack=200000,sstack=50000,cstack=500000}
does?

Is this some sort of memory allocation?

Thanks.

Joe

[Garrett]

In the old days of Mx say Version 5 and prior the user actually selected the amount of memory that would be allocated. Depending on the size of the model etc. you would have to allocate memory. In version 6.0 and going forward there is no need for the user to manually allocate the memory.

Build {rstack=50000,istack=200000,sstack=50000,cstack=500 000}

If this is a command in a script file that you are running and the error is resulting from that then I would try commenting out everything after the letter d in the word build and then starting it back up.

i.e. only use Build

I don't believe that there is a way to manually allocate the initial SystemBuild Stack size.

I believe initially the stack size is set to 10010.

However, one way
you can manually set the initial SystemBuild stack size,is to create a large StateSpace as soon as you start up SystemBuild. This will prevent piece-meal reallocs while using SystemBuild.

You can created a new SuperBlock in SystemBuild and then drop down a StateSpace Block with 199 inputs and 199 Outputs and 1 State and entered ones(200,200)as the StateSpace Matrix without any problems. This would resize this internal stack to at least 40000.

You really should not have to do this but if that helps then you might think about doing this in your startup.ms file you could use SBA or load the file then you could delete the superblock and begin working.
"Bob" gave me this little tid bit.

Please let me know if any of this is of use.

Garrett