UPDATE FROM MABULA
I have had a very rough 2 months unfortunately health wise. I was struck 3x in a row with bacterial infections. The second infection occurred  after a routine hospital checkup and I became very sick. I had to rest and take a lot of antibiotics. Once I was recovering and restarting work 1 month ago, I again became sick. The infection was not yet gone, so even more antibiotics and rest was needed. Needless to say, it took a lot of my energy and I needed a lot of rest.
Finally, the infection is really gone and my energy is coming back step-by-step now and I have started work again. I am terribly sorry to have kept you waiting for support. I will address all outstanding questions and e-mails step-by step and will be on the forum daily from today.
APP 2.0.0-beta47 will come soon as well, a lot of work was already completed before I became very ill, so the release is also nearly ready for you. Beta47 will be much faster actually. Many workflows will be more than 2x faster, mosaics can even be 10x faster than before because registration really received a major boost... all compared to beta46. Â Before I release it, I will make sure that everything is working properly and then I will release it.
I'm having a bit of trouble analyzing an image with Astrometry.net because of improper DEC and RA coordinates after a crop.
When you (batch) crop an image in the Tools tab, it doesn't look like the DEC and RA coordinates in the header are updated to reflect the new center of the cropped image.
Shouldn't the reference point (CRVAL1 and CRVAL2) for the new center (and potentially other WCS-related keywords) be recalculated to ensure the mapping remains correct?
Cheers
Gil
Hi Gilles @museceleste,
Thank you very much for your post.
APP 2.0.0-beta33 had the improvement that at least from now on, relevant and distinct FITS tags will remain present in the FITS files that APP produces. So if you do not crop the files, the DEC and RA coordinates and other pointing information from the reference are stored in the integration files.
Unfortunately, APP does not plate solve yet, so we can not update the coordinates/pointing information yet. I will try to implement this soon going forward.Â
For now, you will need to plate solve the image in the software that requires it. Can't Astrometry.net solve this easily by the way?Â
Mabula
Hello Mabula,
That’s good news, thank you. It represents a fair amount of work but should benefit and bolster the entire product! Curious to know how you are planning it: some packages involve downloading a star database (e.g. Kstar), others will link to Simbad online, etc.
I found the problem by regression. The first time I uploaded to Astrometry, it asked me if I wanted to plate solve the image. Surprised, I then realized that, following a batch crop in APP, the DEC and RA coordinates were gone. But Astrometry will plate solve from the stars all right.
G.
Hi Gilles @museceleste,
You are most welcome, I need to investigate a bit on how to implement it, but it should not be a problem and it is high on my todo list.
Glad all is fine now đŸ˜‰
Mabula
