Hi guys,
I'm trying to jointly image a 32 pointing mosaic in L band. However, I get the following problem:
Reading the visibility data ...
Making MFS images
Visibilities accepted: 69360968
### Warning: Visibilities rejected: 2064250
Number of pointings: 32
### Informational: Interpolating beam models in frequency
Mean Frequency(GHz): 2.82
Doing the geometry calculations ...
Sidelobe suppression area is 8891x8891 arcsec
... this corresponds to uniform weighting
Calculating the weights ...
Applying weights and geometry corrections ...
Theoretical rms noise: 1.054E-04
... assuming pointings do not overlap
Forming the beam ...
### Fatal Error: Memory conservation algorithm failed, in Mapper
It executes correctly if I use imsize=2,2,beam, but anything larger than 2,2 produces the error (e.g. imsize=2.5,2.5,beam fails with the error above). Is there any way to fix this, or will I have to live with the limited imsize?
Cheers,
Craig.
Memory size issue with INVERT?
Moderator: Mark.Wieringa
-
- Site Admin
- Posts: 220
- Joined: Thu Feb 04, 2010 3:27 pm
- Location: Paul Wild Observatory Narrabri NSW
Re: Memory size issue with INVERT?
Hi Craig,
Why are you trying to image larger than the beam in a mosaic? That's what the mosaic is for.
Why are you trying to image larger than the beam in a mosaic? That's what the mosaic is for.
cheers
Jamie Stevens
ATCA Senior System Scientist
Jamie Stevens
ATCA Senior System Scientist
-
- ATCA Expert
- Posts: 297
- Joined: Mon Feb 08, 2010 1:37 pm
Re: Memory size issue with INVERT?
Hi Craig,
I agree with Jamie - first try modifying the inputs to see if you can reduce the size of the problem and still get what you want.
From the message it is not quite clear to me what limit we are exceeding - it could be a MAXBUF or MAXDIM (image size) issue or an integer overflow.
If you want me to investigate I'll need all your invert inputs and the data (or what to grab from the archive).
Cheers,
Mark
I agree with Jamie - first try modifying the inputs to see if you can reduce the size of the problem and still get what you want.
From the message it is not quite clear to me what limit we are exceeding - it could be a MAXBUF or MAXDIM (image size) issue or an integer overflow.
If you want me to investigate I'll need all your invert inputs and the data (or what to grab from the archive).
Cheers,
Mark
Re: Memory size issue with INVERT?
Hi guys,
Yep --- you're right about the mosaic of course. I was getting a few artifacts in my image so I was playing around with various parameters to see what difference it made. All sorted now though. We'll call this resolved!
Cheers,
Craig.
Yep --- you're right about the mosaic of course. I was getting a few artifacts in my image so I was playing around with various parameters to see what difference it made. All sorted now though. We'll call this resolved!
Cheers,
Craig.