Out of Memory

[astropixel]

Hi. I'm getting an Out of Memory message while using BatchPreprocessing - this occurs while reading and computing bias frames, after 50 frames. Tried v1.7 same thing. So I guess its my system.

Linux - xubuntu 64bit - 8G RAM quad core i5 - no error messages when PI starts - /home directory has ~128G remaining.

I have moved the swap file from /tmp to my /home directory (Global Preferences) and added this line to /etc/fstab

##RAMDISK##
none /tmp tmpfs defaults 0 0

Frames are 16bit tiff files converted from Fuji RAF files in SilkyPix.

Reading 1 image(s):
/home/geoland/Pictures/ScorpioPro-1/20130811_0106.tif
Reading TIFF: 16-bit integers, 3 channel(s), 4896x3264 pixels, chunky: done

I get this message as well

** Incremental image integration disabled due to lack of file format support: TIFF

Many thanks for your help

Rowland

[pfile]

well, you need to use fits format to get the incremental reading, which will save on memory footprint.

no idea why you can't allocate enough memory on that platform - are you using 64 bit PI as well?

but aside from that, are you sure the conversion to tiff was done in a linear fashion with no debayering?

rob

[astropixel]

Thanks pfile. You are correct on all points. I was not aware of these intricacies when using other than RAW Canon files. Files are debayered 16bit tif, being the only conversion option available in SilkyPix for Fuji RAF files. Platform is 64bit PI. I have not found a way in PI to deal with the non-standard mosaic of the Fuji XPro1, which has a very weak IR cut filter and no anti-aliasing filter - the Fuji colour matrix avoids moire and produces very sharp images as a result. Its great for tripod extreme wide field.

[pfile]

i guess maybe you are stuck then? is there a way to do superpixel debayering in silkypix at least?

are you sure that DCRAW does not support the Xpro1 RAF files? google seems to reveal some discussion of support for Xpro1...

rob

[astropixel]

Thanks Rob. I really need to have a closer look at the options. Good point though, super pixel is an option and that will fix the massive file size as well, if I understand the process properly.

I could have used a batch grayscale converter today. That is, one that converts already debayered images. The batch debayer script uses a grayscale conversion,, but I don't need to debayer. Would have been very handy. Perhaps grab that bit of code out of the batch debayer script and setup a batch process.