Author Topic: BATCH PROCESSING SCRIPT ERROR: INVALID PIXEL BATCH?  (Read 145 times)

Offline ballyhoo

  • Newcomer
  • Posts: 21
    • View Profile
Does anyone know why one would get this error?

ALSO, Ido I have the correct settings, for integrating 48 image and 20 dark files?

Offline ballyhoo

  • Newcomer
  • Posts: 21
    • View Profile
Re: BATCH PROCESSING SCRIPT ERROR: INVALID PIXEL BATCH?
« Reply #1 on: 2019 April 12 13:57:20 »
I think I know what the problem is: I tried to integrate the image from the debayered folder. But looking further, each file in that folder is only 8k in size.   Does anyone know the relevance  of those files?

Offline bulrichl

  • PixInsight Old Hand
  • ****
  • Posts: 319
    • View Profile
Re: BATCH PROCESSING SCRIPT ERROR: INVALID PIXEL BATCH?
« Reply #2 on: 2019 April 13 02:30:17 »
> Does anyone know why one would get this error?

The XISF files that cause the error

Code: [Select]
*** Invalid block position: attachment:8192:140332416 (line_4 offset=208)
*** Error: The XISF file contains no readable images.

are corrupted for some reason. These files only contain the metadata (i.e. the XISF header) and no image data. I cannot imagine that these files are generated by PixInsight directly. Did you modify them somehow?


Irrespective of the corrupted files I wonder why you wanted to integrate calibrated, debayered light frames. This is note useful as the images are not yet registered. The workflow for preprocessing the light frames should be:

    ImageCalibration -> (optional: CosmeticCorrection) -> Debayer -> StarAlignment -> ImageIntegration


> ALSO, Ido I have the correct settings, for integrating 48 image and 20 dark files?

No, the settings are not correct.

For the integration of preprocessed light frames use these settings: Call ImageIntegration and reset the process. Under Pixel Rejection (1) set 'Percentile clipping' for 3 to 6 images, or 'Winsorized Sigma Clipping' for 8 to 10 images or Linear Fit Clipping for at least 15 images. Under Pixel Rejection (2) the default parameter are meant as a starting point. These values shall be adjusted by the user so that artifacts caused by aeroplanes, satellites, meteors etc. are fully rejected at the least percentage of rejected pixels.

For the integration of calibration frames use the settings given here for the particular sort of calibration frames: https://www.pixinsight.com/tutorials/master-frames/
The preferred settings are the same for bias, dark and flat-dark frames (see chapter "Bias and Dark Integration"), but different for the integration of calibrated flat frames (see chapter "Master Flat Generation (II)").

Bernd

Offline ballyhoo

  • Newcomer
  • Posts: 21
    • View Profile
Re: BATCH PROCESSING SCRIPT ERROR: INVALID PIXEL BATCH?
« Reply #3 on: 2019 April 14 10:39:02 »
So to integrate calibrated lights I can use the same settings in the link you showed that is used for barks and  biases?
Also do biases need to be captured in the same image train as do flats? I was told that in order to use my flats they must be captured in the exact same image train configuration, meaning that the camera and everything needs to be oriented the same rotationally etc.  So that if I take out the camera from the focser, and then put it back in, there would be a change in rotation and I cannot then do flats. Is that the same w bias frames?

Offline pfile

  • PTeam Member
  • PixInsight Jedi Grand Master
  • ********
  • Posts: 4078
    • View Profile
Re: BATCH PROCESSING SCRIPT ERROR: INVALID PIXEL BATCH?
« Reply #4 on: 2019 April 14 12:49:26 »
think about what bias and darks are and you will have your answer. how can an image taken where no light is allowed to reach the sensor be dependent on the optical train?

rob

Offline ballyhoo

  • Newcomer
  • Posts: 21
    • View Profile
Re: BATCH PROCESSING SCRIPT ERROR: INVALID PIXEL BATCH?
« Reply #5 on: 2019 April 14 15:06:01 »
Thanks I forgot about that.

Offline ballyhoo

  • Newcomer
  • Posts: 21
    • View Profile
Re: BATCH PROCESSING SCRIPT ERROR: INVALID PIXEL BATCH?
« Reply #6 on: 2019 April 14 15:09:16 »
> Does anyone know why one would get this error?

The XISF files that cause the error

Code: [Select]
*** Invalid block position: attachment:8192:140332416 (line_4 offset=208)
*** Error: The XISF file contains no readable images.

are corrupted for some reason. These files only contain the metadata (i.e. the XISF header) and no image data. I cannot imagine that these files are generated by PixInsight directly. Did you modify them somehow?


Irrespective of the corrupted files I wonder why you wanted to integrate calibrated, debayered light frames. This is note useful as the images are not yet registered. The workflow for preprocessing the light frames should be:

    ImageCalibration -> (optional: CosmeticCorrection) -> Debayer -> StarAlignment -> ImageIntegration


> ALSO, Ido I have the correct settings, for integrating 48 image and 20 dark files?

No, the settings are not correct.

For the integration of preprocessed light frames use these settings: Call ImageIntegration and reset the process. Under Pixel Rejection (1) set 'Percentile clipping' for 3 to 6 images, or 'Winsorized Sigma Clipping' for 8 to 10 images or Linear Fit Clipping for at least 15 images. Under Pixel Rejection (2) the default parameter are meant as a starting point. These values shall be adjusted by the user so that artifacts caused by aeroplanes, satellites, meteors etc. are fully rejected at the least percentage of rejected pixels.

For the integration of calibration frames use the settings given here for the particular sort of calibration frames: https://www.pixinsight.com/tutorials/master-frames/
The preferred settings are the same for bias, dark and flat-dark frames (see chapter "Bias and Dark Integration"), but different for the integration of calibrated flat frames (see chapter "Master Flat Generation (II)").

Bernd


I  ended up using BPP and I believe selecting RGGB debayers the images accordingly. I am sorry it escapes me who recommended that setting on these boards but that seemed to work out.