Calibration and align batch operations

[Harry page]

Hi

Indeed this does debayer the image correctly, But the image is loaded up the same orientation what ever way the box is checked 

Makes my comment in my video " check setting with the debayer mod " slightly redundant

It would make more sense for the images to be treated the same inside the script and outside ( by default anyway )

Harry

[Juan Conejero]

Hi Harry,

The latest version seems to have lost the ability to save any image  files when you save a "new instance"

Does this happen consistently? I have just checked the script and it saves/restores all file items normally.

[Harry page]

Hi

Spent all day trying to get it to work inc rebooting machine and now it works 

Will keep my eye on  it and see if it happens again

Harry

[Juan Conejero]

It would make more sense for the images to be treated the same inside the script and outside ( by default anyway )

Since this script is intended to make things simpler, and since most users don't (want to) know what this orientation stuff is all about, I avoided that behavior on purpose. By default, the script loads all FITS files with the 'normal' orientation used by all amateur image acquisition applications (which is the opposite to the professional orientation used by default in PixInsight). This 'forced setting' prevents a common source of errors (wrongly oriented images, wrong CFA patterns) and makes the whole preprocessing task more consistent.

[Juan Conejero]

There is a bug at line 250 of BatchPreprocessing-helper.js. The line read:
Code: [Select]

      if ( ext != ".fit" && ext != ".$" )

but the calling code in BatchPreprocessing-engine.js around line 385 reads
Code: [Select]

   if ( ext == ".fit" || ext == ".fits" || ext == ".fts" )

The test  at line 250 of BatchPreprocessing-helper.js must accept files with extensions 'fits' and 'fts' also.

Thank you for catching this. I'll include a fix in the next release. However I don't think the original problem is due to ".fts" extension, is it?

[Harry page]

It would make more sense for the images to be treated the same inside the script and outside ( by default anyway )

Since this script is intended to make things simpler, and since most users don't (want to) know what this orientation stuff is all about, I avoided that behavior on purpose. By default, the script loads all FITS files with the 'normal' orientation used by all amateur image acquisition applications (which is the opposite to the professional orientation used by default in PixInsight). This 'forced setting' prevents a common source of errors (wrongly oriented images, wrong CFA patterns) and makes the whole preprocessing task more consistent.

Hi Therefore my Files should be debayered the same in the script and by the debayer module and they are not  I have to uncheck the box to achieve this , opposite to what it should be 

Harry

[Juan Conejero]

Every time when I run the script, I get the following error: ImageWindow.windowById(): invalid view identifier

This shouldn't happen. The bug must be in either the ImageIntegration or the Debayer process. To understand and fix this problem I need to know:

- The full file names of the files you're working with.
- The filter name(s).

Thanks, and sorry for the inconvenience.

[atheelen]

There is a bug at line 250 of BatchPreprocessing-helper.js. The line read:
Code: [Select]

      if ( ext != ".fit" && ext != ".$" )

but the calling code in BatchPreprocessing-engine.js around line 385 reads
Code: [Select]

   if ( ext == ".fit" || ext == ".fits" || ext == ".fts" )


The test  at line 250 of BatchPreprocessing-helper.js must accept files with extensions 'fits' and 'fts' also.

The workaround is naturally to rename your files in '.fit'.
Hope this helps

-- bitli

bitli, thanks for this. I tried what you suggested  but unfortunately this did not fix the problem 

Hi Andrew,

This problem is strange. The FITS header looks correct, and all tests we have made with Maxim DL images have worked fine so far.

We need a sample of your data to understand and fix the problem. It would be great if you could upload a calibration set. Just 3 or 4 light and flat frames for each filter plus 3 bias and 3 darks would suffice. Do you have an Endor file server account?

Juan, yes I have received access to Endor file server. Where on the server do you want me to upload the files to?

[Juan Conejero]

Where on the server do you want me to upload the files to?

Create a folder on "Forum Shared Files" and upload your files there.

[atheelen]

Where on the server do you want me to upload the files to?

Create a folder on "Forum Shared Files" and upload your files there.

hi Juan, I have uploaded a zip file called “atheelen_NGC5128.zip” containing the sample pictures requested into the folder titled “Calibration_Align_Batch_Operations”.

[Harry page]

Hi

So anybody else see what I do 

Harry

It would make more sense for the images to be treated the same inside the script and outside ( by default anyway )

Since this script is intended to make things simpler, and since most users don't (want to) know what this orientation stuff is all about, I avoided that behavior on purpose. By default, the script loads all FITS files with the 'normal' orientation used by all amateur image acquisition applications (which is the opposite to the professional orientation used by default in PixInsight). This 'forced setting' prevents a common source of errors (wrongly oriented images, wrong CFA patterns) and makes the whole preprocessing task more consistent.

Hi Therefore my Files should be debayered the same in the script and by the debayer module and they are not  I have to uncheck the box to achieve this , opposite to what it should be 

Harry

[astropixel]

I'm used to be being ignored

[Harry page]

Sorry did you say something 

Harry

I'm used to be being ignored

[erikgu]

Hi !

I dont know if the Preprosessing script is a correct place to put Canon Banding Reduction as an inital and optional prosessing step but could it be ?

I have done this by use of an ImageContainer with the lights and a Process container with CBR, Rotate 90, CBR and the rotate back to initial orientation so its not a big deal, but it could have been nice if it was included in the script as a step before calibration. Default settings could be used in CBR.

Erik G

[georg.viehoever]

Erik,

currently CBR is not suitable for processing RAW frames, so you need to apply it to the calibrated+debayered (and possibly already stacked) frames.  See the following links for some discussions:

http://pixinsight.com/forum/index.php?topic=3522.msg24377#msg24377
http://pixinsight.com/forum/index.php?topic=4214.msg29600#msg29600

Georg