From: Walter Roberson on
Pierce wrote:
> 'pack' doesn't do anything to change the contingiuos memory. It just
> tries to place all the variable beside each other in memory.

Incorrect. "pack" saves all variables into a .mat file, then clears all
variables (thus getting back to the original state of having nothing in
use), and then re-loads the variables from the .mat file, a process that
will hopefully not result in memory fragmentation.

"pack" does NOT just move variables around in memory.
From: Pierce on
Walter Roberson <roberson(a)hushmail.com> wrote in message <%BV8o.12015$1v3.5581(a)newsfe20.iad>...
> Pierce wrote:
> > 'pack' doesn't do anything to change the contingiuos memory. It just
> > tries to place all the variable beside each other in memory.
>
> Incorrect. "pack" saves all variables into a .mat file, then clears all
> variables (thus getting back to the original state of having nothing in
> use), and then re-loads the variables from the .mat file, a process that
> will hopefully not result in memory fragmentation.
>
> "pack" does NOT just move variables around in memory.

okay it saves them, clears memory, and loads them (Which is just memory movement, though not in the sense of RAM).
Anyway, regardless of the details, it still doesn't restore the contiguous block of memory that is initailly seen by matlab. So i don't get why you are saying i'm incorrect.
'clear' and 'pack' were the 1st things i tried to solve the problem, but they just didn't work, hence the post.
From: Pierce on
Walter Roberson <roberson(a)hushmail.com> wrote in message <%BV8o.12015$1v3.5581(a)newsfe20.iad>...
> Pierce wrote:
> > 'pack' doesn't do anything to change the contingiuos memory. It just
> > tries to place all the variable beside each other in memory.
>
> Incorrect. "pack" saves all variables into a .mat file, then clears all
> variables (thus getting back to the original state of having nothing in
> use), and then re-loads the variables from the .mat file, a process that
> will hopefully not result in memory fragmentation.
>
> "pack" does NOT just move variables around in memory.

Well pack just saves, clears and loads, if that's not memory movement, then i don't know what is. (Okay what i should have said, is that all pack does, is try to fit the variables to the smallest contiguous blocks available thus freeing up larger blocks of memory)
Anyway regardless of the details of pack it still does not solve the problem of restoring the contiguous blocks of memory initialy seen by matlab.
clear and pack were the 1st things i tried to solve the problem