Photometric Colour Calibration

[Graham]

Any one else having problems with this tool. Until I updated today I did not have any problems, now it will not solve any images and gives only errors. I will try to roll back and see if that fixes it.

[acmalko]

Yes I do.
Since the 1.8.8 version.

Try UCAC3 catalog

[Juan Conejero]

Oh, well. I am accustomed to the fact that each new version of PixInsight we release is automatically guilty of every problem in the Universe, at least for a while. But, do you really think that the Vizier servers are not working properly as a result of the new version? Really? 

[Graham]

Thank you Juan, what a very disappointing response.

I was only asking a question and seeking direction because much smarter people than I have created this wonderful software.

If this is going to be the standard of response going forward I can invest my time and money in other software.

[acmalko]

You're right, probably too early to conclude. It was just a question about our respective experiences.
Let's check the Vizier's servers

[Juan Conejero]

Graham,

Sorry if my answer sounded harsh, that was not my purpose. When I read 'roll back and see if that fixes it' this morning I felt frustrated. Once more I've just released a new version, which is the best version of PixInsight ever, by far. I've invested thousands of hard work hours, literally, in the last two versions. This tends to make me more sensitive than usual.

Undoubtedly, it has been a very unprofessional comment on my part. I apologize for that.

[rakla]

Yes I had the same issue yesterday using 1.8.8 however had assumed the astrometry catalog server was having issues. I initially played around with the plate solve parameters (noise reduction and sensitivity), which usually works for me when dealing with more difficult (read bad quality) image data, but in the end I simply unselected the automatic catalog tick box and used the Tycho-2 catalog. That did the trick for for me.
/Ralf

[Graham]

Graham,

Sorry if my answer sounded harsh, that was not my purpose. When I read 'roll back and see if that fixes it' this morning I felt frustrated. Once more I've just released a new version, which is the best version of PixInsight ever, by far. I've invested thousands of hard work hours, literally, in the last two versions. This tends to make me more sensitive than usual.

Undoubtedly, it has been a very unprofessional comment on my part. I apologize for that.

Hello Juan,

No worries, mate. I understand and good of you to apologise. I also really appreciate the effort you put in to this very versatile program.

The issue is that I have been fiddling with a data set for a while now with never an issue with PCC until I changed versions. Unfortunately I'm a "monkey see, monkey do" when it comes to this clever stuff. I have taken the others' suggestions and played with the catalogues which works to a degree so I will try to get some better data and go again.

Any ideas as to what may lay behind the issue I am experiencing?

Cheers and clears!

[Armando]

Hi,

I'm experiencing the same issue and probably it's not related to PI update.
I made several attempts and I found that a crop excluding just the first or the last column of the frame (cropping from a size of 4290*2856 pixels to 4289*2856 pixels) makes calibration working as expected.
So it seems related to the size in pixels of the image.

I hope it helps

CS
Armando

[Armando]

Removing the first or last row by a crop also solves the issue.

[brent1123]

I had this issue but solved it by changing servers. Maybe the one in Paris is down for maintenance?

[andreasmax]

same problem here, server in france seems to be off.
swapping to alternative server did the job.
cheers from austria!
andreas