If your field of view is larger then 4.5 degrees the G17 can be benefitial. But if not it is likely s cooincidance of an problemetic image. Check for hot pixels. I will have a look next week when i'm home.
Cheers han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
my field of view is 2.34º
I've tried 40 different objects and they all resolve in 0.4s or 0.7s. All except M20-M8. I do not know why.
The M20-m8 image has a lot of signal, just like the rest of the images
I have tried to solve the calibrated image with darks and bias and it does not solve it either
Take a look at it when you come back from your trip, there's no rush :)
thanks a lot Han!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Probably the star rich area of same magnitude combined with long exposure) is causing problems . Changing the number of stars to use (default 500) could help. Try temporary 100, 200 or 1000
Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I checked today your image. Yes this is a difficult one to solve. There is nothing wrong with the image except it contains many uniform Milky-way stars. I assume the solver has problem to select the default 500 brightest stars. It can be fixed by setting the maximum number of stars at 3000 instead of 500 and activating "Slow" . There are no other way to improved solving.
Questions:
1) Which filter was used if any?
2) Is the image manipulated (like stretching) in any way?
Cheers, Han
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello Han!!
I have a problem solving M20 and M8
ASTAP works perfectly and resolves all my photos except my M20 and M8 photo
My setup is a FSQ106ED (530mm) and an ATIK 16200 (KAF16200) and my Field Of View is 2,34º
I attach two photos that solve perfectly (M63 and NGC7635 and M8-M20 that does not solve it)
What is the problem? I have the latest version of the program and the H18 database
Thanks in advance
Last edit: Alvaro Ibañez Perez 2022-08-30
M63 solves it perfectly
and NGC7635 solves it perfectly
I'm currently travelling. I will answer your post next week.
Han
Thanks Han.
No rush :)
News!
several friends of mine with the G17 database have managed to solve the photo
I guess the problem is in the H18 database?
Alvaro.
Last edit: Alvaro Ibañez Perez 2022-08-31
If your field of view is larger then 4.5 degrees the G17 can be benefitial. But if not it is likely s cooincidance of an problemetic image. Check for hot pixels. I will have a look next week when i'm home.
Cheers han
my field of view is 2.34º
I've tried 40 different objects and they all resolve in 0.4s or 0.7s. All except M20-M8. I do not know why.
The M20-m8 image has a lot of signal, just like the rest of the images
I have tried to solve the calibrated image with darks and bias and it does not solve it either
Take a look at it when you come back from your trip, there's no rush :)
thanks a lot Han!
Probably the star rich area of same magnitude combined with long exposure) is causing problems . Changing the number of stars to use (default 500) could help. Try temporary 100, 200 or 1000
Han
I wil try
thank you Han!
I checked today your image. Yes this is a difficult one to solve. There is nothing wrong with the image except it contains many uniform Milky-way stars. I assume the solver has problem to select the default 500 brightest stars. It can be fixed by setting the maximum number of stars at 3000 instead of 500 and activating "Slow" . There are no other way to improved solving.
Questions:
1) Which filter was used if any?
2) Is the image manipulated (like stretching) in any way?
Cheers, Han
hello Han!
The images are direct from NINA.
Images have no processing.
The filter used is Luminance (Baader IR/UV Cut)
thanks, alvaro
Fixed!
with H18 and maximum number of stars at 1000 instead of 500 works perfect!!!
in 0.8s solved!
Thank you Han!!
Alvaro.