"Fatal Error: Bad value for size, in MemAllop"

Is MIRIAD being a pain? Let us know your experience.

Moderator: Mark.Wieringa

"Fatal Error: Bad value for size, in MemAllop"

Postby Anita » Fri Nov 18, 2016 12:32 pm

When trying to run selfcal I get the following error:

"Fatal Error: Bad value for size, in MemAllop"

Looking at https://www.cfa.harvard.edu/sma/miriad/ ... subs/mem.f it seems that the error is caused by miriad not having enough memory to perform the task.

Is there a quick work around for this?
Anita
 
Posts: 9
Joined: Thu Aug 25, 2016 2:39 pm

Re: "Fatal Error: Bad value for size, in MemAllop"

Postby Mark.Wieringa » Fri Nov 18, 2016 3:05 pm

Hi Anita,

it's hard to say without further info, but I suspect the MemAllop is called when reading an image model.
Are you using an especially large size model?
The maximum size memory allocation in one block that Miriad can currently handle is 8 GB.

If your input model is a cube, you could try breaking it up into smaller channel ranges.

Let me know what your situation is (dimensions of model) and I can see if there is a way around this problem.

Cheers,

Mark
Mark.Wieringa
ATCA Expert
 
Posts: 284
Joined: Mon Feb 08, 2010 1:37 pm

Re: "Fatal Error: Bad value for size, in MemAllop"

Postby Anita » Tue Nov 22, 2016 9:36 am

It probably was the size of the cube, but I've ended up not doing selfcal as my signal to noise isn't good enough. Thanks for the reply though!
Anita
 
Posts: 9
Joined: Thu Aug 25, 2016 2:39 pm


Return to MIRIAD

Who is online

Users browsing this forum: No registered users and 0 guests

cron