![]() Only reads 8 and 16 bit FITS images.Ĭonverts to RAW, TIF, TGA, BMP, and JPEG formats AstroImageJ: processing, modeling and plotting astronomical image data in one package based upon the ImageJ.Including blind solving of the astrometry of each image using the GAIA database. Users can determine the astrometric properties of images, stack and display them, This program, available as an executable on Windows, Macs and most varieties of Linux, supports 8, 16, and 32 bit integer ASTAP: viewer, image stacker, plate solver.Interactive software tool for visualizing and performing aperture photometry In Python is a Python module aimed at producing publication-quality plots ofĪstronomical imaging data in FITS format. an extensive listing of commercial and freeware image processing software compiled Of astronomical data sets, so these packages are not necessarily capable ofĭevelopers of new image display programs should be aware of the It should be noted thatĭata format that is used for many different types Often of celestial objects in the night sky. Simple class of FITS data files that containing 2-dimensional images, The following software packages display or manipulate the relatively Jasem may be able to shed more light on the simulator issues but that's out of my league.FITS Image Software Packages for image viewing, analysis, and format conversion If this does not work even using load and slew post similar screenshots of your settings and another log using a loaded image rather than the simulator and we may be able to gradually work out what is wrong. Enable astrometry in INDI as per the screenshot and ensure that astrometry is selected in Auxillary in your equipment profile as per screenshot. (Dont forget to unpark and set tracking to sidereal or astrometry will not work). I always click these at the start of a session after I have unparked and started tracking. The little icons circled re-calculate the FOV based on your profile and reset the co-ordinates to your current mount position. The first attachment just draws attention to the "use scale " and RAposition " that you may need to uncheck if the image that you are loading is from a different rig therefore a different scale to the one set in your current profile. I have attached a load of screenshots of my settings which may or may not be relevant to your set up. This is using the offline solver on the RPi not ANSVER in Windows which does not display much of any use to troubleshooting. If you go to the logs section in EKOS and check verbose and alignment as per the screenshots you should be able to watch the process in realtime (in the text area in underneath the alignment panel in EKOS) which I find is more helpful. If not you will need to do a blind solve which means uncheck the "use scale" and "use RA position" boxes in the alignment options in EKOS. If you load a saved image into astrometry and slew to target make sure that the image was taken with your current rig. As I never use the simulators I cannot help you there. Just looking at your log file there is a lot of data from the "capturing image to "extracting sources" that does not happen when I solve. Choose an image file that would normally be visible at the time you are testing.Īs everyone's system is different what works for one may not work for another. Try checking with Load and Slew (but be ready with the manual stop slew just in case it tries to go somehere below the horizon). I deleted the ANSVR then reinstalled it (keeping the FITS files of course) and it started working consistently again and has worked ever since. I did have a problem with ANSVR a while back, it constantly failed after it had worked for some time. ![]() Both offline on my Odroid or ANSVR on Windows. In the field I use 10 secs exposures and 4X downsample and it works well. If its a standard 10 sec exposure I only downsample by 4 but if a saved long exposure 60-300 sec) I downsample by 8 as the star field is much richer. So I tend to set the telescope up inside the house but like in the field and use a saved image to Load and Slew to check astrometry is working. I find the simulators do not work very well with astrometry (for me) so I don't bother with them. I usually reckon between 300-1000 is about right so I downsample to approximately arrive at that figure although it's very rule of thumb (over 1500 sources takes much longer to solve). I am not an expert on this but from your log the number of sources that you are solving on is very small (1-25).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |