Affiliation
American Association of Variable Star Observers (AAVSO)
Tue, 01/07/2020 - 18:45
What is the largest .FIT file you processed with AIJ without it running out of memory? I tried using AIJ to calibrate a batch of files 39 megs each and it conked out even though I set the allocated memory to over 6000 megs. I need to know since I can keep my file size small either by binning or smaller ROI.
Are there any disadvantages to binning 3x3 on a 39MB chip?
Ray
I would have to defocus my scope to get FWHM on the required 3-5 pixels. Right now, I'm at 2x2 binning and I reduced my resolution (region of interest) on my CMOS. That got my .FIT image size to 4.5MB each.
I don't know if it will solve your particular issue, but I always select 'Use Virtual Stack' in the Sequence Options dialog when I am importing an image sequence.
Roy
Roy,
I don't think the problem is the image size. I think it is the memory needed for the sequence of images that are all being loaded into memory at once IF you load them without checking the box to use a virtual stack. .
I think you will be ok if when you import the image sequence if you check that box. Earlier today I loaded a stack of 225 16 MB images and processed them without problem. I have loaded over 300 24 MB images in the past withoug a problem but only when the use virtual stack option is checked. With a virtual stack you essentailly have only one image )or perhas two or three) loaded in memory plus what amounts to an ordered list of pointers.
Brad Walter, WBY
Brad,
I didn't have the problem. It was CrossoverManiac who had the issue.
I mentioned Use Virtual Stack as a possible solution.
Roy
Roy,
Well I have only been using the forum for a decade or so. Perhaps in another decade I will learn how to read it properly or, simply, how to read properly.
Brad, WBY
No problem Brad. I'm sometimes embarrassed by finding that I haven't read an email properly.
Roy