Just remember, this is only one of several kinds of issues. PCC is complex! This refers to the photometry side of things- plate solution issues- that is a different problem.
Glad you enjoyed the information. I am considering creating a Patreon page. I do not make money on UA-cam videos directly...but hopefully it points people to my tutorials. PI is now releasing their own- which puts me in a tough spot. Would someone like yourself who obivously benefited from my material consider being a Patreon?
Fantastic tutorial- solves an issue that randomly occurs and yes- I would always think what is 'wrong' with my image when I get this error. I have read many forums about this, but your explanation is by far the most comprehensive and educational. Thank you.
You would not believe it: I was experiencing exactly this issue two days ago, and with the very M101 with APASS 10 (I did not install APASS 9, as I supposed that 10 was more than 9!). Thanks for solving the mistery with your usual mastery (oops, wod pun!). After watching your video, I revised my M101 processing with PhotometricCalibration this time!
To be clear...the density of stars in the covered regions IS more in APASS 10 compared to 9... but the problem is that the coverage is less complete in some areas. I am glad you found the information useful!
Fantastic videos Adam, the fact th a t your not charging money for some of your videos is saying a lot. All the other Pixinsight tutorials do not show half as much and you have to pay for the time they talk an bs. Thank you very much!
BRILLIANT! Thanks so much Adam. I'd been struggling with PCC for ages on an image that could be plate solved perfectly easily. I hadn't appreciated that the photometry was a different database, and still less that you have to use the OLDER version! (somewhat misleading). Anyway, all working now. Thanks SUBSCRIBED
A very helpful video. It can be easy to lose the thread (path) to your star catalogs when you are frequently filling hard drives and moving to the next one. PCC has to have exactly what it needs and know where to find it. But some of us have a particular problem with astrometry because of our capture software. I use the ASIAIR Pro for capture because it frees me from having a laptop tethered to the driveway scope. But the manufacturer saw fit to (cluelessly) put a binned (4x4) plate solving solution into the image FITS headers. PixInsight doesn't understand this solution. It assumes the plate solve is 1x1 and "corrects" the scope focal length to make it so. This results in a failed PCC every time! One way to get around it is to not use the actual image data and also check the box "ignore image metadata". Juan suggested that. The other way is to use the script "Image Solver", which corrects the FITS headers (I am told). It's very difficult for a non IT guy to explain the problem to people who don't speak English. I just said, "please don't use binned plate solving solutions in the FITS headers! I am also told this is atypical of capture software.
Well said! It isn't just for "non IT" guys though- this crazy minutiae and problem solving is exactly what *everyone* deals with. I am no better position than you when it comes to solving one of these kinds of problems- I have just made it something of my job to work on them though. You now have a taste of what it is like to solve a typical issue- and this one doesn't require any math! :)
Thank you very much for this tutorial, Adam. I had already experimented the results you mentioned here, and I ended color balancing with other options like Linear Fit between the R, G and B channels, or doing Background Neutralization with Color Calibration. Knowing this, I’ll check first if the catalogue is enough for the object I’m processing. Very valuable and useful technique! Regards, Alfredo
Can we use the artificial star map to paste in pictures like we are creating a mosaic? It would suppress the need to make large overlaps and save lots of integration time, especially when using a large focal length.
Your process doesn't show coordinates? I am not certain I understand. If you are no taking images with software that talks to a telescope your images will not have any coordinates initially. You can always choose an object (or type in coordinates). You might need to provide some screen captures. If you are a member of my site... you are welcome to connect with me (or write on my forum) for help. If you are NOT a member of my site... there are benefits of being one. :)
@@AdamBlock Thank you so much for the reply. My camera is ASI2600MC Pro stacked in SiriL, so I'm pretty sure it has all the information it needs. I was recommended to you by a member of my local Astronomy club SAAA(San Antonio Astronomical Association) so I'll gladly join your website and am considering purchasing your class on PixInsight!
@@greggbell I replied to your e-mail. You need to plate solve images with Image Solver first. Things have changed in PixInsight since perhaps the last time you used it.
@@greggbell OK. I would recommend FastTrack Training. (If you do not want to fully invest in Fundamentals). In a few days you can be pretty much up-to-speed with what you initially need to know.
Thanks for this video. It indeed clarifies why PCC is sometimes not working.
Just remember, this is only one of several kinds of issues. PCC is complex! This refers to the photometry side of things- plate solution issues- that is a different problem.
This was great! I have in fact had this error message. I especially appreciated seeing the catalogs printed and annotated. Really fascinating.
Glad you enjoyed the information. I am considering creating a Patreon page. I do not make money on UA-cam videos directly...but hopefully it points people to my tutorials. PI is now releasing their own- which puts me in a tough spot. Would someone like yourself who obivously benefited from my material consider being a Patreon?
Fantastic tutorial- solves an issue that randomly occurs and yes- I would always think what is 'wrong' with my image when I get this error. I have read many forums about this, but your explanation is by far the most comprehensive and educational. Thank you.
Thanks Adam, this really helped me. I am going to watch this over and over again until I get a really good understanding of this.
You would not believe it: I was experiencing exactly this issue two days ago, and with the very M101 with APASS 10 (I did not install APASS 9, as I supposed that 10 was more than 9!).
Thanks for solving the mistery with your usual mastery (oops, wod pun!).
After watching your video, I revised my M101 processing with PhotometricCalibration this time!
To be clear...the density of stars in the covered regions IS more in APASS 10 compared to 9... but the problem is that the coverage is less complete in some areas. I am glad you found the information useful!
Fantastic videos Adam, the fact th a t your not charging money for some of your videos is saying a lot. All the other Pixinsight tutorials do not show half as much and you have to pay for the time they talk an bs. Thank you very much!
Of course...I am showing you just the low hanging fruit here. You know where to find the good stuff... :)
@@AdamBlock Well put, I am already signing up for the lessons my friend.
BRILLIANT! Thanks so much Adam. I'd been struggling with PCC for ages on an image that could be plate solved perfectly easily. I hadn't appreciated that the photometry was a different database, and still less that you have to use the OLDER version! (somewhat misleading). Anyway, all working now. Thanks SUBSCRIBED
Thanks for watching!
A very helpful video. It can be easy to lose the thread (path) to your star catalogs when you are frequently filling hard drives and moving to the next one. PCC has to have exactly what it needs and know where to find it.
But some of us have a particular problem with astrometry because of our capture software.
I use the ASIAIR Pro for capture because it frees me from having a laptop tethered to the driveway scope. But the manufacturer saw fit to (cluelessly) put a binned (4x4) plate solving solution into the image FITS headers. PixInsight doesn't understand this solution. It assumes the plate solve is 1x1 and "corrects" the scope focal length to make it so. This results in a failed PCC every time! One way to get around it is to not use the actual image data and also check the box "ignore image metadata". Juan suggested that. The other way is to use the script "Image Solver", which corrects the FITS headers (I am told).
It's very difficult for a non IT guy to explain the problem to people who don't speak English. I just said, "please don't use binned plate solving solutions in the FITS headers! I am also told this is atypical of capture software.
Well said! It isn't just for "non IT" guys though- this crazy minutiae and problem solving is exactly what *everyone* deals with. I am no better position than you when it comes to solving one of these kinds of problems- I have just made it something of my job to work on them though. You now have a taste of what it is like to solve a typical issue- and this one doesn't require any math! :)
Thank you very much for this tutorial, Adam.
I had already experimented the results you mentioned here, and I ended color balancing with other options like Linear Fit between the R, G and B channels, or doing Background Neutralization with Color Calibration.
Knowing this, I’ll check first if the catalogue is enough for the object I’m processing. Very valuable and useful technique!
Regards,
Alfredo
Brilliant instructional video. I don’t even have PI but found this really informative and interesting to watch.
Excellent!
I ran into this problem right after I changed which catalog to use, so I knew it was a catalog issue and not something wrong with my image.
Thank you for this Adam! I appreciate these types of tutorials!
Thank you Dale!
Very helpful. It was this very target that I was struggling with.
I am glad you found it helpful. Thanks!
Thank you Adam, teaching done right!
This was a fantastic informative walk thru.. Thank you.
fantastic information!
Thanks, have been wondering how to annotate images 🙂
Interesting, I wonder if ASTAP has the same issue? Anyone know? I've never really had an issue with it but now that I've seen this makes me wonder.
Can we use the artificial star map to paste in pictures like we are creating a mosaic? It would suppress the need to make large overlaps and save lots of integration time, especially when using a large focal length.
My Photometriccolorcalibration doesn't show coordinates and same for SpectroPhotometriccolorcalibration...I cant choose a object in the catalogue
Your process doesn't show coordinates? I am not certain I understand. If you are no taking images with software that talks to a telescope your images will not have any coordinates initially. You can always choose an object (or type in coordinates). You might need to provide some screen captures. If you are a member of my site... you are welcome to connect with me (or write on my forum) for help. If you are NOT a member of my site... there are benefits of being one. :)
@@AdamBlock Thank you so much for the reply.
My camera is ASI2600MC Pro stacked in SiriL, so I'm pretty sure it has all the information it needs. I was recommended to you by a member of my local Astronomy club SAAA(San Antonio Astronomical Association) so I'll gladly join your website and am considering purchasing your class on PixInsight!
@@greggbell I replied to your e-mail. You need to plate solve images with Image Solver first. Things have changed in PixInsight since perhaps the last time you used it.
@@AdamBlock Thank you! I'm a brand new user on my second day of the trail so it's all very new to me.
@@greggbell OK. I would recommend FastTrack Training. (If you do not want to fully invest in Fundamentals). In a few days you can be pretty much up-to-speed with what you initially need to know.