#Astrometry .solved trial
#Astrometry .solved Pc
#Astrometry .solved download
#Astrometry .solved windows

solve_from_source_list ( sources, sources, image_width, image_height, solve_timeout = 120 ) reverse () image_width = 3073 image_height = 2048 wcs_header = ast.

sort ( 'FLUX' ) # Reverse to get descending order sources. read ( 'catalog.fits' ) # Sort sources in ascending order sources. api_key = 'XXXXXXXXXXXXXXXX' sources = Table. To be a longer time than the timeout set inĪstroquery.astrometry_, which is intended toĪct primarily as a timeout for network transactions.įrom astropy.table import Table from astroquery.astrometry_net import AstrometryNet ast = AstrometryNet () ast. The solve_timeout used below is the time, in seconds, to allow theĪ server to find a solution. Other columns, and that the image is 3073 by 2048 pixels. (columns X_IMAGE and Y_IMAGE) and flux (column FLUX) and perhaps In the example below, assume that catalog.fits is a table of pixel positions The only important requirement is that the list must be sorted by flux in The data can be inĪn, pandas data frame or something other structure. Sources in an image instead of uploading the entire image. The most efficient way to use is to pass it a list of

#Astrometry .solved download

Links to download the FITS files for the image. The log will contain the RA/Dec of the solution.įor publicly viewable images or source lists includes Is accessible if one knows the job id regardless of the permissions setįor the image. Oh and as always many thanks to Jasem and everyone else involved in this tremendous application.Be aware that some information you submit to is publiclyĪvailable even if the raw image isn’t. Otherwise it is posted for others having similar solving problems to try with no guarantees that it will work for you. If anyone can explain the logic of why this works so well I would be really interested. I thought that I would post my settings for anyone out there having similar problems using similar gear to try as some of them that seem important in getting things working for me were the last things that I thought would work. I am using NEQ6 mount (EQMod) with ASI294MCPro and ASI120MM as guider with OAG. Since using these settings I have not had a problem.

I was really surprised that I needed to use X10 downsampling and removal of the 'scale' and 'use position' options seemed counter intuitive that this would make things work. I also deleted the astrometry FIT files that were not needed for my FOV especially the really big ones as these seem to increase the chances of timeout and are not needed for the majority of user scenarios. Unticked use scale, ticked auto update, units aw and recalculate FOV before using the solver, downsample X 10 (I tried 8 times which took much longer and X4 timed out so this was important), I also unchecked use position (this appeared important using load and slew, less so for capture and slew). In the solver options I unticked no fits, ticked resort and no verify and unticked parity. So, in the solver options I ticked WCS, overlay and jpg upload.

#Astrometry .solved trial

After a lot of trial and error I have found the following settings worked really well and now solves quickly (within 20-30 secs using the offline solver on the odroid which also works well remotely under kStars for Windows. Most of my saved files are 60 -240 sec duration. Yesterday I had a clear night and managed to try all sorts of permutations to get previously saved FITs files to solve. Interestingly, trying to use the on-line astrometry solver timed out on upload which has never occurred before. ANSVR also ran though and failed (failure to get job ID). Recently I have tried a load and slew to test out the astrometry as the weather has precluded doing testing outside but nothing would work, the solver either failed straight away or ran through all of the astrometry fits and then timed out (even using 500sec time out settings) or failed. I generally find 1Xbinning works best in the field.

#Astrometry .solved windows

A few things that I have noticed that have been consistent are a failure to solve any image using the offline solver on the odroid or trying the ANSVR server on windows when using 4X binning with the ASI294. I have had some intermittent astrometry solving issues but generally these have been good for the last few weeks. In the field (away from my home network) this setup runs through a WiFi extender as a hot spot.

#Astrometry .solved Pc

Startup KStars, EKOS and INDI on the odroid then use KStars remotely through the home network on my PC inside. I use team viewer for headless operation on a windows laptop. I have KStars /EKOS/INDI running under Ubuntu 18.04 on an Odroid XU4. These have been driving me nuts but hopefully I now have them sorted so I thought that I would share some tips. I have recently had some persistent solver failure and time out issues with my Astrophotography set up.