Error message when using Batch Pre-Processing

[Mariner10]

Hi everybody,
I'm very new to PixInsight but thanks to a whole bunch of tutorials the learning curve has commenced.
I generally use the Batch Pre-Processing script to commence processing of my images and every time I have I keep getting an error message (I've copied and pasted it below from the Process Console).
The problem doesn't appear to have a negative effect on the final outcome but there again as I always get the error message I don't really know.
So I would appreciate any help with it please. The error message is at the bottom of the script but I've included all the details in the event they are helpful.
Regards.

Steve (Mariner10)

51 FITS keyword(s) extracted.
Noise reduction: done
Structure map: done
Detecting stars: done
711 stars found.
Matching stars: done
672 putative star pair matches.
Performing RANSAC: done
671 star pair matches in 271 RANSAC iterations.
Summary of model properties:
Inliers     : 0.999
Overlapping : 1.000
Regularity  : 0.984
Quality     : 0.981
Root mean square error:
delta_RMS   :  0.116 px
RMS error deviation:
sigma_RMS   :  0.051 px
Peak errors:
delta_x_max :  0.457 px
delta_y_max :  0.373 px
Transformation matrix:
     +0.9999     +0.0000     -0.1417
     -0.0000     +1.0000     -0.2190
     +0.0000     -0.0000     +1.0000
scale       : 1.000
scale-X     : 1.000
scale-Y     : 1.000
rotation    :     -0.00 deg
dx          :     -0.14 px
dy          :     -0.22 px
Generating registered image
Homographic Projection / Lanczos-3 interpolation, c=0.30: done
Registration successful.
Writing output file: C:/Users/Steves/Pictures/Backyard EOS/QHY20160102/Springs 11.03.16/LMC/Batch Preprocessed/registered/LMC-5-120s-0-C0-2_c_d_r.xisf
Writing image: w=3328 h=2030 n=3 RGB Float32
72 FITS keyword(s) embedded.
Writing output file: C:/Users/Steves/Pictures/Backyard EOS/QHY20160102/Springs 11.03.16/LMC/Batch Preprocessed/registered/LMC-5-120s-0-C0-2_c_d_r.drz

Registering target image 10 of 10
Loading target file:
C:/Users/Steves/Pictures/Backyard EOS/QHY20160102/Springs 11.03.16/LMC/Batch Preprocessed/calibrated/light/debayered/LMC-5-120s-0-C0_c_d.xisf
Loading image: w=3328 h=2030 n=3 RGB Float32
*** Error: Parsing 32-bit floating point expression: conversion error:
1.?#QNAN (line=59,column=160)

[pfile]

when something like that happens it usually means the disk filled up during the calibration phase... can you check if you have enough free space?

rob

[Mariner10]

Hi Rob,
I have plenty of disc space, I've only used approximately 25% of my hard drive.
Cheers.

Steve

[Juan Conejero]

Hi Steve,

As you say this shouldn't have any impact on the final result. However, I am interested in knowing more about this issue. Could you please upload one of the images where this is happening, so I can investigate?

[Mariner10]

Hi Juan,
I've attached an image for you (hopefully) as requested, I had to save it in .jpg.
This error message comes up with every image I try to process.
For example yesterday I was processing the LMC and today Eta Carina Nebula, both came up with the same error message.
For some background information I image with a QHY8L one shot colour camera.
The images are saves in the .fit format.
My normal way of processing is to start with the batch pre-processing script which is where I get the error message.
I generally get the message the same number of times as lights plus one that I'm processing.
For example if I have 10 lights the error message will appear 11 times.

As we're talking about one issue can I ask you for your advice about another I'm having please
Whenever I start processing I get to the point in the tutorials where I want to use the "CIE L*Component" function but unlike on the tutorial when the function has completed and the duplicate image appears mine is always completely black.
Even if I apply and auto-stretch the image stays completely black.
Could you give me some direction as to where I may be going wrong please.

Thanks.

Steve.

[pfile]

juan needs the .fit files, you need to upload them to dropbox or google drive or whatever and post a link here. it's probably best to upload a bias, dark, flat and light frame that causes the problem.

rob

[Mariner10]

Thanks Rob,
I was wondering how it would go with a JPG, now I know and know how to do it in future if needed.
I'll try and get to it tomorrow.
Cheers.

Steve.

[Mariner10]

I'm new to Google Drive so lets hope this works.
Juan try this link: https://drive.google.com/file/d/0B1ukVdgQG9QoX3BZSGZTUkVNSmc/view?usp=sharing.
Cheers.

Steve

[Mariner10]

Sorry, try this link (it should be able to be edited): https://drive.google.com/file/d/0B1ukVdgQG9QoX3BZSGZTUkVNSmc/view?usp=sharing