Dale Ghent

Requesting EQASCOM source

Hey Han, I was looking to play around with HFD analysis and I can't seem to get it working in Windows under either cmd.exe or PowerShell. Executing the following: astap.exe -f sample.fits -analyse 30 This does not produce any output and the %errorlevel% is set to 0. It is also set to 0 (True) when checking $? under Powershell. It appears to work on macOS, but the exit code is still set to 0. [daleg@iridium]~$ /Applications/ASTAP.app/Contents/MacOS/astap -f sample.fits -analyse 30 HFD_MEDIAN=4.4 STARS=575...

Using current svn head of freeimage.NET to extract the Canon maker notes from a cr2 raw file is unsuccessful for me. I am attempting to retrieve them using GetMetadata(): FreeImage.GetMetadata(FREE_IMAGE_MDMODEL.FIMD_EXIF_EXIF, img, "MakerNote", out MetadataTag tag); However GetMetadata returns false. I am able to retrieve the FocalLength and FNumber tags using the same method, but curiously I'm unable to retrieve typical tags such as ISOSpeed and other tags that are verified to be present in the...

Using current svn head of freeimage.NET to extract the Canon maker notes from a cr2 raw file is unsuccessful for me. I am attempting to retrieve them using GetMetadata(): FreeImage.GetMetadata(FREE_IMAGE_MDMODEL.FIMD_EXIF_EXIF, img, "MakerNote", out MetadataTag tag); However GetMetadata returns false. I am able to retrieve the FocalLength and FNumber tags using the same method, but curiously I'm unable to retrieve typical tags such as ISOSpeed and other tags that are verified to be present in the...

Han, thanks a lot for taking the time to put this in. Sorry for my delay in reply, but I was able to find time to test your beta release last night and it worked as expected. I took your advice and am working on a patch for NINA that adds the determined pixel scale to the solve results display in NINA. I have a question - assuming square pixels, is there any difference between using CDELT1 and CDELT2 even though their respective values may be ever so slightly different ?

In NINA 1.10, we feed ASTAP with FITS files, and populate that FITS file with relevant keywords for pixel size, such as XPIXSZ and YPIXSX. You could look for these keywords and take their values to know the pixel size. We source this info from cameras drivers or, in the case of DSLRs, we must rely on the user providing the correct pixel size as Canon and Nikon's camera SDKs do not provide this information.

Yes, we display that warning message in NINA and it has been useful in helping people realize that the effective focal length of their telescope is wrong or not what they thought it would be. Then the question turns to "well, what should the setting be, then?" and we advise them to run a solve on Astrometry.net, wihich will display the focal length it determines. They then enter that into NINA's focal length setting and all is well from that point onwards. My suggestion to display the calculated...

Hey Han, thank you for creating and giving such a great program to the community. I am wondering if you could display the calculated focal length of the optics that produced a solved image. I believe this is possible given the information that is derived from a solved image. This will help people configure the Focal Length property correctly in apps such as NINA, where it can used to calculate a more exact image scale. We've seen some issues where users with newtonians with coma correctors are specifying...