fredvanner
Well-known member
This is really what I was getting at in post #33.if you have this image in a better format, that would be the one to be working with here
This is really what I was getting at in post #33.if you have this image in a better format, that would be the one to be working with here
After 100GB of GAIA database, what's another 1GB...I figured NO ONE would want to download a 1 GB file
True!After 100GB of GAIA database, what's another 1GB...
Well, it wouldn't surprise me at all for the TIFF to not solve. In fact, 24-bit TIFF files are not standard at all for saving astronomical images. Take your XISF file and save it as a 16-bit per channel TIFF, which will provide a MUCH better test as it will retain pretty much all the pixel level data. And that should be small enough, maybe 150 MB. (We're downloading files all the time that are hundreds of MB around here.)I attempted to solve as the original XISF from calibration and no luck.
I am shooting with the 2600MC-P, each file is 50 MB. The XISF file was too big for my drop box (~ 1 GB) and I figured NO ONE would want to download a 1 GB file so... I placed it as a TIF which is pretty standard. You can solve a JPEG at lower resolutions in other programs so...not the issue at hand.
But yeah, when I did WBPP it couldn't solve the astrometry with the original XISF file.
It does not explain why I still can't solve in any format. Frustrating.
But we are happily solving the TIFF, so why can't @stardad1994 ?it wouldn't surprise me at all for the TIFF to not solve
It's worth a try.I were to send you the entire process console info on the XISF image failure does that provide info to help sniff the issue
As I noted, it doesn't explain that weirdness. But it's a terrible image to use for testing. There's no way that good PSFs are going to be calculated on tiny stars and 8 bits of dynamic range. For all I know things are already on the hairy edge, and it's nothing more than the difference between the hardware floating point processors, or some other oddity.But we are happily solving the TIFF, so why can't @stardad1994 ?
I am more optimistic. The stars often look tiny on a wide field image like this, so it is best to ask the software. FWHMEccentricity gives:There's no way that good PSFs are going to be calculated on tiny stars and 8 bits of dynamic range. For all I know things are already on the hairy edge,
I do not trust the quality of a fitted PSF derived from 8-bit data! Anyway, my point remains the same. Trying to debug this with a file that doesn't even accurately represent the actual data isn't a good idea, and just adds an unnecessary variable to the diagnosis process.I am more optimistic. The stars often look tiny on a wide field image like this, so it is best to ask the software. FWHMEccentricity gives:
View attachment 18091
This is a very healthy FWHM and eccentricity over a large star support.
SPCC is quite choosy about what stars it selects for processing, but it is happy to analyse 552 stars in this image. Lower precision in the PSF estimation will give bigger scatter in the luminosity ratio plots - the question is whether the resulting distrubution is good enough to estimate the linear fits. At the end of the day SPCC only calculates three parameters for colour balance and three for BN. This is the SPCC result:
View attachment 18092
This looks OK to me.
It is not ideal, but it is all we have unless the OP uploads a full precision file.Trying to debug this with a file that doesn't even accurately represent the actual data isn't a good idea
I suggest you try switching off the automatic limiting magnitude, and set a value of 16. You could also try reducing the star detection sensitivity, say to about 0.4.run --execute-mode=auto "C:/Program Files/PixInsight/src/scripts/AdP/ImageSolver.js"
Processing script file: C:/Program Files/PixInsight/src/scripts/AdP/ImageSolver.js
Loading control points...
Simplified surfaces: tolerance = 0.96 as | l:2091 | b:1809
Simplified surfaces: tolerance = 0.33 px | X:2074 | Y:1862
Loaded 4805 control points (metadata version 1.1).
Gaia: Global context
3.900 us
Searching for optimal magnitude limit...
Gaia: Global context
29.604 ms
Gaia: Global context
32.485 ms
Gaia: Global context
41.031 ms
Gaia: Global context
61.927 ms
Gaia: Global context
112.989 ms
Gaia: Global context
240.981 ms
Gaia: Global context
182.528 ms
Gaia: Global context
107.506 ms
Gaia: Global context
240.033 ms
Gaia: Global context
170.616 ms
Gaia: Global context
104.605 ms
Gaia: Global context
235.641 ms
Gaia: Global context
164.309 ms
Gaia: Global context
98.728 ms
Gaia: Global context
224.164 ms
Gaia: Global context
133.172 ms
* Using an automatically calculated limit magnitude of 16.57.
Seed parameters for plate solving:
Center coordinates: RA = 11 19 02.374, Dec = +13 05 38.57
Resolution: 2.600 as/px
Starting StarAlignment iteration
Gaia: Global context
Executing Gaia DR3 search command...
9075 sources found.
135.630 ms
Catalog Gaia DR3 (XPSD): 5310 objects inside the image.
* Using the triangle similarity star matching algorithm.
StarAlignment: Processing view: masterLight_BIN_1_6248x4176_EXPOSURE_240_00s_FILTER_NoFilter_RGB_integration_ABEcomp_w_clone
C:/Users/fred/AppData/Local/Temp/stars.csv:
Scanning star data: done
7256 stars.
masterLight_BIN_1_6248x4176_EXPOSURE_240_00s_FILTER_NoFilter_RGB_integration_ABEcomp_w_clone:
Structure map: done
Detecting stars: done
14151 stars found.
* Reference image: Limiting to 2000 brightest stars.
* Target image: Limiting to 2000 brightest stars.
* Distortion correction: Iteration 1 of 50
Matching stars: done
9 putative star pair matches.
Performing RANSAC: done
* Previous attempt failed - this is try #2
useScaleDifferences=true
* Reference image: Limiting to 2000 brightest stars.
* Target image: Limiting to 2000 brightest stars.
* Distortion correction: Iteration 1 of 50
Matching stars: done
237 putative star pair matches.
Performing RANSAC: done
229 star pair matches in 102 RANSAC iterations. Residual: 997.0022 px
Computing global distortion correction: done
Performing RANSAC: done
Global distortion correction applied with 369 stars.
* Distortion correction: Iteration 2 of 50
Matching stars: done
365 putative star pair matches.
Performing RANSAC: done
361 star pair matches in 86 RANSAC iterations. Residual: 0.1044 px
Computing global distortion correction: done
Performing RANSAC: done
Global distortion correction applied with 664 stars.
* Distortion correction: Iteration 3 of 50
Matching stars: done
527 putative star pair matches.
Performing RANSAC: done
525 star pair matches in 4 RANSAC iterations. Residual: 0.1537 px
Computing global distortion correction: done
Performing RANSAC: done
Global distortion correction applied with 921 stars.
* Distortion correction: Iteration 4 of 50
Matching stars: done
692 putative star pair matches.
Performing RANSAC: done
690 star pair matches in 14 RANSAC iterations. Residual: 0.7646 px
Computing global distortion correction: done
Performing RANSAC: done
Global distortion correction applied with 1067 stars.
* Distortion correction: Iteration 5 of 50
Matching stars: done
857 putative star pair matches.
Performing RANSAC: done
853 star pair matches in 102 RANSAC iterations. Residual: 0.8698 px
Computing global distortion correction: done
Performing RANSAC: done
Global distortion correction applied with 1212 stars.
* Distortion correction: Iteration 6 of 50
Matching stars: done
996 putative star pair matches.
Performing RANSAC: done
994 star pair matches in 4 RANSAC iterations. Residual: 0.2322 px
Computing global distortion correction: done
Performing RANSAC: done
Global distortion correction applied with 1323 stars.
* Distortion correction: Iteration 7 of 50
Matching stars: done
1039 putative star pair matches.
Performing RANSAC: done
1037 star pair matches in 5 RANSAC iterations. Residual: 0.0441 px
Computing global distortion correction: done
Performing RANSAC: done
Global distortion correction applied with 1339 stars.
* Distortion correction: Iteration 8 of 50
Matching stars: done
1056 putative star pair matches.
Performing RANSAC: done
1053 star pair matches in 1 RANSAC iterations. Residual: 0.0000 px
Computing global distortion correction: done
Performing RANSAC: done
Global distortion correction applied with 1340 stars.
* Distortion correction: Iteration 9 of 50
Matching stars: done
1047 putative star pair matches.
Performing RANSAC: done
1045 star pair matches in 57 RANSAC iterations. Residual: 0.0000 px
Computing global distortion correction: done
Performing RANSAC: done
Global distortion correction applied with 1340 stars.
* Distortion correction: Iteration 10 of 50
Matching stars: done
1047 putative star pair matches.
Performing RANSAC: done
1045 star pair matches in 13 RANSAC iterations. Residual: 0.0000 px
Computing global distortion correction: done
Performing RANSAC: done
Global distortion correction applied with 1340 stars.
* Distortion correction: Iteration 11 of 50
Matching stars: done
1047 putative star pair matches.
Performing RANSAC: done
1045 star pair matches in 32 RANSAC iterations. Residual: 0.0000 px
* Distortion correction: Convergence reached after 11 iterations.
* Summary of model properties:
Inliers : 0.998
Overlapping : 1.000
Regularity : 0.983
Quality : 0.995
Root mean square error:
delta_RMS : 0.000 px
RMS error deviation:
sigma_RMS : 0.000 px
Peak errors:
delta_x_max : 0.000 px
delta_y_max : 0.000 px
residual : 0.0000 px
* Projective transformation matrix:
+0.834727 +0.488737 -1006.256912
-0.486484 +0.833457 +1006.390212
+0.000000 +0.000000 +1.000000
translation : 1423.16 px
translation_x : -1006.26 px
translation_y : +1006.39 px
rotation : -30.33 deg
scale : 1.033
scale_x : 1.035
scale_y : 1.035
02:32.93
Simplified surfaces: tolerance = 0.15 as | l:1045 | b:1045
Simplified surfaces: tolerance = 0.05 px | X:1045 | Y:1045
Something still strikes me as wrong. The tool only uses the focal length if it has to in order to calculate a pixel scale. But according to the long process log you posted above, the pixel scale was correctly set to 2.6" and that's the value that was used... without a solution being found. The focal length shouldn't have mattered.Well, I have just solved the image. Attached is the SPCC result.
Anyone care to guess the issue???
Oh yes, infinitely stupid here. At least I think this is the reason.
The focal length is not as I kept stating in my solver: 360 mm. I had the 0.8X focal reducer on the scope so the focal length is 288 mm. I kept using the wrong focal length in my attempts to solve.
Once I placed the correct focal length in...well, you know...it solved.
So, I am sorry I wasted everyone's energy/ time. Please know I have learned quite a bit from all of the suggestions.
I appreciate this community. Thank you ALL very much!
And..I really like PI. But so much to learn.
Marc