Beta 3.1.0.307 - Dome Sync Problems

PhotoGav · October 17, 2019, 8:11am

First of all I would like to thank Ken & Jared for the recent flurry of development and the stream of beta versions. I have had rubbish weather for a while and I think 8 new versions of SGPro have been released between the last imaging session I had and last night’s session!

First impressions of 3.1.0.307 (and now I see that there is already a newer release!) were excellent. I really like the new auto focusing routine, which seems smart and works well. Almost perfect - more of that below…

Now on to the main issue seen last night:

I ran a sequence that started with M29 and a few Blue subs - collected perfectly. I then wanted to test out the new auto focus routine on a Globular Cluster, so the next target in the sequence was M15. The sequence duly clicked on to this target at about 00:06 and slewed to the target. The problem that ensued was all to do with Dome Sync (I am using a Pulsar Dome and Mesu 200 mount with all syncing done through SGPro) - it kept on switching between two sync points, one was perfect and the other was off. I couldn’t work out what was causing the discrepancy, but it would slew to the target and the Dome Sync would be good, it would then do its slew to start the Centre routine and the Dome would move to an out of sync point. The camera would take an image for plate solving, but this would be of the inside of the roof and the solve would obviously fail. Meanwhile the Dome would move back to the good sync point. What is going on???!!! The target was well away from the Meridian, so that is not an issue here. The only thing that has changed is the version of SGPro. Previous versions have worked flawlessly with Dome Sync, when away from the Meridian.

Here is the log file:

I hope that you are able to have a look at this issue and see what is happening to cause this problem.

Eventually I manually intervened and got the system to lock on to the target, the Globular Cluster M15. Time for a look at the new improved auto focus routine and to see how it now copes with Globular Clusters. Unfortunately it did not go well as this image shows:

It was late, the Moon was high and bright, the Dome was playing up, auto focus was playing up, so I gave up and went to bed!!

I look forward to seeing what you all come up with here.

Many thanks,

Gav.

jmacon · October 17, 2019, 11:19am

What has happened here is your focus curve is of poor quality, as indicated by the quadratic curve displayed in RED, as opposed to one displayed in GREEN for ok. This is determined by the Quality measure of the fit, which is the quadratic R^2 value. My guess is it is somewhere in the vicinity of .8. Hopefully Ken and Jarod will add the R^2 value to the summary display under the graph. No summary display is even showing on this graph. That is a bug. Sometimes the summary line shows on the final graph display, and sometimes not. It is a new feature added in recent releases. A great enhancement since we need to communicate with the user what is going on.
My recommended summary display would contain the following:
(19928 HFR 3.1 L 13.9C 81%)
If this were implemented, you would see that the Quality for this run was 81%. For this particular target and your equipment, that may be a fairly typical result.

So specifically what has happened is a rerun of some sort has been triggered because your Quality is less that the .90 that the current routine requires for a successful run. Currently this is not a user settable parameter. It needs to be for exactly this reason. Some targets and/or equipment will need a lower value for the Quality cutoff. For your specific example, the Quadratic fit will give a very acceptable value of something between the two low points. If you could set the cutoff to say .75, this run would have been successful and focus would go to about 19960. The graph shows it with the value of the lowest point, but that is because it was flagged as unacceptable quality, so it always picks the lowest point, and not the value the quadratic fit would provide.

About the rerun: exactly what kind of rerun we don’t know. The message says “Moving focuser to next position”. I am not sure why it would be moving the focuser. I would expect it to do a rerun from the same starting position to try for a better curve with Quality >= .90.

The scheme I am in favor of for the user settable Quality factor would allow the user to set two Quality factors. Example: Q1 = .90, Q2 = .75.
When focus first runs it would expect Q to be >= Q1. If it fails this, it would do a rerun from the same position and that rerun would only need Q2 to qualify for acceptance. This would try for good quality runs on decent targets, and allow the more difficult targets to succeed.

An additional change to the focus routine would be very useful here. Currently and in the past, the intermediate sequences of images that the focus routines takes that result in moving the focuser to a new position and starting over have not been receiving a graph of the results. They should. This is important for both the developers and the users understanding what logic the focus routine has used in making its decision for the next phase of the focus. This intermediate graph should include the full summary line.

Ken · October 17, 2019, 2:13pm

This is in 3.1.0.313

PhotoGav · October 17, 2019, 2:36pm

Thank you for the input so far folks.

This auto focus run continued moving the focuser in ever further, so this image was taken ‘mid-run’. I aborted the run manually as it was just going massively out of focus and not getting anywhere.

The major issue going on here is not in the logic of the routine, but in the results generated by the star field. The kit used here works very efficiently when auto focusing on any target other than a Globular Cluster. The problem comes when the Glob is out of focus and the cluster stars merge to make much larger out of focus blobs which completely skew the field HFR value with high values that suddenly appear. It then gets to a point where the Glob is so out of focus that it is ignored, as in the image above. That creates very false HFR values that make the fit impossible. I think!

The only solution to this I have found in the past is to just move the scope a bit, focus on a non Glob patch of sky and then return to the main target. This is a manual process and a PITA, especially at 3am!!!

I look forward to hearing thoughts about the Dome Sync issue too, please.

jmacon · October 18, 2019, 8:04pm

@PhotoGav, do you still have the Auto Focus Packs from when you tried to image M15? I would like to take a close look at them to see what is going wrong. Maybe I can help Ken and Jarod come up with a solution to getting good focus on these targets. I have tried to duplicate these issues with globs with my rig, but to no avail. I always get great focus results on them. I tried using a small focus region but it would only let me go down to 40%. My FOV is .56 degree but that is still not small enough.

PhotoGav · October 18, 2019, 8:29pm

Good stuff, thank you for your help with this. Hopefully these are what you are after?

What kit are you using that doesn’t have problems with globs?!

jmacon · October 18, 2019, 10:36pm

These logs are not what I need. You must be saving the “Auto Focus Packages”
The bottom right check box with a path to save them to.
Capture

Each focus run will have a directory named like this:
AFPack_1
Inside is a FIT file for each focus image that was taken, plus a JPG of the result dialog that displays the focus chart. I need all of those. Then from Ken I can get a special program that will run the star finding routine against each fit file so we can see what the star detection routine has done.

My kit:
Orion Optic UK AG12" Newtonian, + ZWO ASI 1600MM, resulting in .70 arcsec/pixel resolution
Televue NP127is 127mm refractor + ZMO ASI 183MM resulting in .75 arcsec/pixel resolution
Here is a link to an R image I took of M14 with the AG12, a glob the same size as M15. I have not done M15 yet, may do it tonight. I need a new early target.
https://1drv.ms/u/s!ApZRrk2grXleluIuuxhpgT64TjGeDw?e=1zSQpo

If you don’t have these Auto Focus Packages, maybe you could turn that feature on and do another glob so I would have some focus fit files to work with. Thanks.

PhotoGav · October 19, 2019, 8:19am

Ah, OK, no I didn’t have that turned on. I have just set it up and will try focusing on M15 tonight - the forecast looks like I should have the opportunity to do so. Update to follow.

Interesting to see your kit list. My EdgeHD 8” & QSI 683 is operating at 0.55”/pixel. I really hope that you are able to create a solution to the Glob focus issue as I know I am not alone with this.

PhotoGav · October 19, 2019, 10:05pm

Hi,

I ran, well tried to run, auto focus on M15 again this evening. It did the same and kept on going ever further out of focus to the left and I manually aborted the run. Here is what it generated for the AF package:

I hope that helps the development process.

Thanks,

Gav.

jmacon · October 19, 2019, 10:09pm

Please send the Log file too.

PhotoGav · October 19, 2019, 10:13pm

And here is the main SGP log file:

I also suffered the wandering Dome Sync issue again. It has a habit of syncing perfectly on the initial slew, then moving about 25° away from sync when it does the first slew in the centre routine. Why?!

I also suffered from autofocus issues with the Green filter on M74… ??

It all seems to be testing me at the moment!

Ken · October 19, 2019, 10:31pm

I thought AFPacks had a jpg of the graph in them? Is that broken in 3.1?

Anyhow, have not had time to look in detail… but take a look at my last post here:

PhotoGav · October 19, 2019, 11:16pm

Ken, it appears that the jpeg is only saved for successful runs. I have some successful packages that have the jpeg and some unsuccessful ones that don’t.

I will have a read through of the other post you link to above.

flywaldo · October 20, 2019, 7:11pm

I am having the same dome sync issues as you describe. It ruined two nights of imaging last week as they happened while I was sleeping. I was able to see it happen two nights ago when I was attempting to start a session manually. I was able to go around it by disabling dome sync while I did the centering routine, and then re-syncing it. But that is not a solution.

This is a serious issue that I hope is addressed soon.

Eric

PhotoGav · October 20, 2019, 7:27pm

Eric, that is very interesting to hear that you are having the Dome Sync issues too. Has your system worked properly in the past and then gone a bit strange with recent beta updates? I’ve used the un-sync, centre, re-sync procedure to get round it too, but that’s no use for ‘an automated imaging solution’!

Hopefully the boys will be on it and find a silly bug that is causing it very soon.

jmacon · October 20, 2019, 10:04pm

All of my successful packs have a jpg in them. This has always been the case going back years. So no, that is not broken.

What I think is important for the new Quadratic focus routine going forward is that unsuccessful packs, the intermediate ones that did not succeed and caused a rerun of some sort, should have one too. Particularly including the R^2 Quality factor. These are what users will need to refer to to figure out what quality cutoff value is going to work best for them.

Example: they are running with the current 90% default cutoff value and they are getting a lot of reruns. They have not seen what these runs look like because there is no jpg of these runs, so they don’t know if they need to set a lower quality threshold to minimize the number of reruns. There are basically two scenarios:

all those runs were really bad and warranted a rerun, so quality cutoff should stay at 90%.
a large percentage of them were acceptable that had quality as high as 85%. The ones below 85% warranted a rerun. In this case the quality cutoff should be lowered to 85%.

This is also important for the quadratic focus development team to be able to most easily be able to diagnose what the routine is doing so we can make it work for everyone under the widest possible conditions. So an entry in the Log which includes all the same data a successful run gets is really important, including all the parameters for defining the quadratic curve that the routine came up with.

flywaldo · October 23, 2019, 3:27pm

I have confirmed that the dome slew errors are connected to both ‘slew now’ and ‘center now’ commands.

I am in the dome now. All equipment connected and dome slaved. I command a slew to a target, the scope slews properly, the dome slews approximately 25 degrees off of that point initially. Then re-slews around 30 seconds later to the correct position and tracks normally.

When I command the ‘center now’ command the same behavior occurs. Target azimuth at 335, dome slews to 311, then 30 seconds later corrects to the right AZ. But by this time the plate solve image has been taken and it of course fails because it’s looking at the inside of the dome.

I have attached the logs of that series of events. There are lines in there that show the initial slew command to the correct location, but then a command from the Observatory function to adjust to the wrong location.

[10/23/19 11:23:45.061][DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[10/23/19 11:23:46.772][DEBUG] [Main Thread] Slewing to target…
[10/23/19 11:23:46.778][DEBUG] [Telescope Thread] Slew telescope message received…
[10/23/19 11:23:46.778][DEBUG] [Telescope Thread] Telescope: Slewing to J2000 RA: 2.4482 (02h26m53.52s) Dec: 62.035 (62°02’06.00")
[10/23/19 11:23:46.778][DEBUG] [Telescope Thread] Telescope: Slew received J2000 coordinates, mount requires JNOW, converting…
[10/23/19 11:23:46.779][DEBUG] [Telescope Thread] Telescope: Slewing to JNOW RA: 2.47380325982841 Dec: 62.1219692379047
[10/23/19 11:23:46.779][DEBUG] [Telescope Thread] Telescope: Calling Observatory Slave Slew
[10/23/19 11:23:46.784][DEBUG] [Slew Monitor] Waiting for slew to complete…
[10/23/19 11:23:46.798][DEBUG] [Telescope Thread] Observatory: Calculating new position using:
[10/23/19 11:23:46.798][DEBUG] [Telescope Thread] Azimuth: 323.730438634818
[10/23/19 11:23:46.798][DEBUG] [Telescope Thread] Altitude: 43.8983399166111
[10/23/19 11:23:46.798][DEBUG] [Telescope Thread] Hour Angle: 146.957599942115
[10/23/19 11:23:46.798][DEBUG] [Telescope Thread] Pier Side: East
[10/23/19 11:23:46.798][DEBUG] [Telescope Thread] Observatory: Adjustment needed, slewing to Azimuth: 311.531636095379
[10/23/19 11:23:46.855][DEBUG] [CP Update Thread] Error in control panel UI updater: Object reference not set to an instance of an object.
[10/23/19 11:23:56.898][DEBUG] [Telescope Thread] Scope reports it is done with synchronous slew, verifying…
[10/23/19 11:23:56.898][DEBUG] [Telescope Thread] Telescope: Observatory is reporting slewing
[10/23/19 11:23:57.900][DEBUG] [Telescope Thread] Telescope: Slewing has completed
[10/23/19 11:23:57.900][DEBUG] [Telescope Thread] Telescope: Settling for 5 seconds
[10/23/19 11:24:02.900][DEBUG] [Telescope Thread] Telescope: Settling has completed
[10/23/19 11:24:02.900][DEBUG] [Telescope Thread] Slew complete…
[10/23/19 11:24:31.673][DEBUG] [Main Thread] PopulateDataModel: Transferring view to the data model…
[10/23/19 11:24:31.686][DEBUG] [MF Update Thread] Performing serialize…
[10/23/19 11:24:31.697][DEBUG] [MF Update Thread] Serialization took 11 msec.
[10/23/19 11:24:32.162][DEBUG] [Dome Thread] Observatory: Calculating new position using:
[10/23/19 11:24:32.162][DEBUG] [Dome Thread] Azimuth: 344.878333061788
[10/23/19 11:24:32.162][DEBUG] [Dome Thread] Altitude: 13.5625731048911
[10/23/19 11:24:32.162][DEBUG] [Dome Thread] Hour Angle: 147.155213356018
[10/23/19 11:24:32.162][DEBUG] [Dome Thread] Pier Side: East
[10/23/19 11:24:32.162][DEBUG] [Dome Thread] Observatory: Adjustment needed, slewing to Azimuth: 334.862688356941
[10/23/19 11:24:45.194][DEBUG] [PHD2 Listener Thread] PHD2 - No messages received from PHD2 for 1 minute, checking socket with status…
[10/23/19 11:24:45.194][DEBUG] [PHD2 Listener Thread] Checking PHD2 state…
[10/23/19 11:24:45.194][DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Pre-Wait : Stopped
[10/23/19 11:24:45.194][DEBUG] [PHD2 Listener Thread] Sending to PHD2:
{“method”: “get_app_state”, “id”: 1001}

[10/23/19 11:24:45.194][DEBUG] [PHD2 Listener Thread] PHD2 GetPhdStatus - Post-Wait: Stopped
[10/23/19 11:24:48.317][DEBUG] [Telescope Thread] Center telescope message received…
[10/23/19 11:24:48.317][DEBUG] [Telescope Thread] Solving with Plate Solver PlateSolve2…
[10/23/19 11:24:48.375][DEBUG] [Telescope Thread] Performing auto center step 1…
[10/23/19 11:24:48.375][DEBUG] [Telescope Thread] Skipping step 1…
[10/23/19 11:24:48.375][DEBUG] [Telescope Thread] Auto center reference frame solved successfully…
[10/23/19 11:24:48.375][DEBUG] [Telescope Thread] Performing auto center step 3 (scope)…
[10/23/19 11:24:48.375][DEBUG] [Telescope Thread] Auto center slewing scope to match reference…
[10/23/19 11:24:48.375][DEBUG] [Telescope Thread] Telescope: Slewing to J2000 RA: 2.4482 (02h26m53.52s) Dec: 62.035 (62°02’06.00")
[10/23/19 11:24:48.375][DEBUG] [Telescope Thread] Telescope: Slew received J2000 coordinates, mount requires JNOW, converting…
[10/23/19 11:24:48.376][DEBUG] [Telescope Thread] Telescope: Slewing to JNOW RA: 2.47380325982841 Dec: 62.1219692379047
[10/23/19 11:24:48.376][DEBUG] [Telescope Thread] Telescope: Calling Observatory Slave Slew
[10/23/19 11:24:48.398][DEBUG] [Telescope Thread] Observatory: Calculating new position using:
[10/23/19 11:24:48.398][DEBUG] [Telescope Thread] Azimuth: 323.730438634818
[10/23/19 11:24:48.398][DEBUG] [Telescope Thread] Altitude: 43.8983399166111
[10/23/19 11:24:48.398][DEBUG] [Telescope Thread] Hour Angle: 147.215375224899
[10/23/19 11:24:48.398][DEBUG] [Telescope Thread] Pier Side: East
[10/23/19 11:24:48.398][DEBUG] [Telescope Thread] Observatory: Adjustment needed, slewing to Azimuth: 311.522290051472
[10/23/19 11:24:58.508][DEBUG] [Telescope Thread] Scope reports it is done with synchronous slew, verifying…
[10/23/19 11:24:58.508][DEBUG] [Telescope Thread] Telescope: Observatory is reporting slewing
[10/23/19 11:24:59.509][DEBUG] [Telescope Thread] Telescope: Slewing has completed
[10/23/19 11:24:59.509][DEBUG] [Telescope Thread] Telescope: Settling for 5 seconds
[10/23/19 11:25:04.510][DEBUG] [Telescope Thread] Telescope: Settling has completed
[10/23/19 11:25:04.510][DEBUG] [Telescope Thread] Auto center slew complete…
[10/23/19 11:25:04.510][DEBUG] [Telescope Thread] Performing auto center step 4…
[10/23/19 11:25:04.510][DEBUG] [Telescope Thread] Created full file name: C:\Users\Eric\AppData\Local\SequenceGenerator\Temp\plate_solve_image-3.fit
[10/23/19 11:25:04.512][DEBUG] [Camera Thread] SGM_CAMERA_PLATE_SOLVER_CAPTURE message received…
[10/23/19 11:25:04.512][DEBUG] [Camera Thread] Alnitak Flat Box - Getting shutter status
[10/23/19 11:25:04.563][DEBUG] [Camera Thread] Alnitak Flat Box - Updating Device Variables - Model: 99 Motor Status: 0 Light Status: 0
[10/23/19 11:25:04.563][DEBUG] [Camera Thread] Collecting FITs headers for plate solve frame…
[10/23/19 11:25:04.563][DEBUG] [Camera Thread] Collecting FITs headers for plate solve frame…
[10/23/19 11:25:04.702][DEBUG] [Camera Thread] SetAscomHighSpeed…
[10/23/19 11:25:04.702][DEBUG] [Camera Thread] Cannot set readout speed, not supported by camera…
[10/23/19 11:25:11.394][DEBUG] [Camera Thread] Created full file name: C:\Users\Eric\AppData\Local\SequenceGenerator\Temp\plate_solve_image-3.fit
[10/23/19 11:25:11.394][DEBUG] [Camera Thread] SaveFileAscom: Start…
[10/23/19 11:25:11.394][DEBUG] [Camera Thread] SaveFileAscom: Checking image data…
[10/23/19 11:25:11.394][DEBUG] [Camera Thread] SaveFileAscom: Create normal preview bitmap…
[10/23/19 11:25:11.395][DEBUG] [Camera Thread] SaveFileAscom: Locking preview bits…
[10/23/19 11:25:11.396][DEBUG] [Camera Thread] SaveFileAscom: Validating file name…
[10/23/19 11:25:11.396][DEBUG] [Camera Thread] SaveFileAscom: Starting byte traversal…
[10/23/19 11:25:11.421][DEBUG] [Camera Thread] SaveFileAscom: Unlocking preview bits…
[10/23/19 11:25:11.421][DEBUG] [Camera Thread] SaveFileAscom: Saving preview bitmap to disk…
[10/23/19 11:25:11.421][DEBUG] [Camera Thread] SaveFileBmp16: Locking bitmap for disk write…
[10/23/19 11:25:11.421][DEBUG] [Camera Thread] SaveFileBmp16: Opening file stream…
[10/23/19 11:25:11.421][DEBUG] [Camera Thread] SaveFileBmp16: Writing FITS headers…
[10/23/19 11:25:11.421][DEBUG] [Camera Thread] SaveFileBmp16: Traversing and persisting bitmap data…
[10/23/19 11:25:11.468][DEBUG] [Camera Thread] SaveFileBmp16: FITS block fill…
[10/23/19 11:25:11.468][DEBUG] [Camera Thread] SaveFileBmp16: Unlocking bitmap…
[10/23/19 11:25:11.468][DEBUG] [Camera Thread] SaveFileBmp16: Closing file stream
[10/23/19 11:25:11.473][DEBUG] [Camera Thread] Internal Interface: Set Preview…
[10/23/19 11:25:11.473][DEBUG] [Camera Thread] Display image preview using asynch task…
[10/23/19 11:25:11.668][DEBUG] [Unknown] Image analysis (async) START
[10/23/19 11:25:11.866][DEBUG] [Camera Thread] SaveFileAscom: Done
[10/23/19 11:25:11.866][DEBUG] [Camera Thread] =========== Save file took 473 ms
[10/23/19 11:25:11.866][DEBUG] [Camera Thread] SGM_CAMERA_PLATE_SOLVER_CAPTURE complete…
[10/23/19 11:25:11.924][DEBUG] [Telescope Thread] Auto center verification frame complete. Plate solving image C:\Users\Eric\AppData\Local\SequenceGenerator\Temp\plate_solve_image-3.fit
[10/23/19 11:25:11.925][DEBUG] [Unknown] Image analysis (async) END
[10/23/19 11:25:12.096][DEBUG] [Telescope Thread] ************* SOLVE HINTS ****************
[10/23/19 11:25:12.096][DEBUG] [Telescope Thread] SOLVER: PlateSolve2
[10/23/19 11:25:12.096][DEBUG] [Telescope Thread] BLIND: False
[10/23/19 11:25:12.096][DEBUG] [Telescope Thread] METHOD: Max Regions
[10/23/19 11:25:12.096][DEBUG] [Telescope Thread] RA: 2.44768159077164
[10/23/19 11:25:12.096][DEBUG] [Telescope Thread] DEC: 62.0373165506095
[10/23/19 11:25:12.096][DEBUG] [Telescope Thread] SCALE: 1.46226
[10/23/19 11:25:12.096][DEBUG] [Telescope Thread] ******************************************
[10/23/19 11:25:12.319][DEBUG] [Telescope Thread] FitsFileHeaderData: Angle - 0
[10/23/19 11:25:12.319][DEBUG] [Telescope Thread] FitsFileHeaderData: Scale - 0
[10/23/19 11:25:12.319][DEBUG] [Telescope Thread] FitsFileHeaderData: RA - 2.44769157599553
[10/23/19 11:25:12.319][DEBUG] [Telescope Thread] FitsFileHeaderData: DEC - 62.037316734145
[10/23/19 11:25:12.324][DEBUG] [Telescope Thread] PlateSolve2 Param: RA (RAD) - 0.640801541991263
[10/23/19 11:25:12.324][DEBUG] [Telescope Thread] PlateSolve2 Param: DEC (RAD) - 1.08275543291011
[10/23/19 11:25:12.324][DEBUG] [Telescope Thread] PlateSolve2 Param: Width - 2328
[10/23/19 11:25:12.324][DEBUG] [Telescope Thread] PlateSolve2 Param: Height - 1761
[10/23/19 11:25:12.324][DEBUG] [Telescope Thread] PlateSolve2 Command Line:
[10/23/19 11:25:12.324][DEBUG] [Telescope Thread] C:\Users\Eric\AppData\Local\SequenceGenerator\PlateSolve2.exe 0.64080154199126,1.08275543291011,0.01650374264974,0.01248414553530,3000,C:\Users\Eric\AppData\Local\SequenceGenerator\Temp\psXSolve_2.fit
[10/23/19 11:25:19.750][DEBUG] [Unknown] PlateSolve2: INI file was modified! Changed
[10/23/19 11:25:19.793][DEBUG] [Telescope Thread] PlateSolve2: read APM file…
[10/23/19 11:25:20.294][DEBUG] [Telescope Thread] PlateSolve2: Exit state → ValidNoSolve
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] *********** SUCCESSFUL SOLVE *************
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] SOLVER: False
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] SUCCESS: False
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] CONF: 0
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] BLIND: False
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] RA: 0
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] DEC: 0
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] SCALE: 0
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] FLIPPED: False
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] ANGLE (EON): -500
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] MSG: Solve failed! Unanticipated problem during plate matching.
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] ******************************************
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] Auto center validation frame failed to solve. Solve failed! Unanticipated problem during plate matching.
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] Auto center validation frame solve failed, invoking blind failover…
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] Astrometry.NET: Sequence endpoint data: Astrometry.NET (Remote)
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] Astrometry.NET: Sequence endpoint data: Astrometry.NET (Remote)
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] ************* SOLVE HINTS ****************
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] SOLVER: Astrometry.NET
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] BLIND: True
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] METHOD: Max Regions
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] RA: 2.44768159077164
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] DEC: 62.0373165506095
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] SCALE: 1.46226
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] ******************************************
[10/23/19 11:25:20.368][DEBUG] [Telescope Thread] Astrometry.NET: Sequence endpoint data: Astrometry.NET (Remote)
[10/23/19 11:25:20.481][DEBUG] [Telescope Thread] Astrometry.NET convertedAstrometry.fits path: C:\Users\Eric\AppData\Local\SequenceGenerator\Temp\convertedAstometry.fits
[10/23/19 11:25:20.481][DEBUG] [Telescope Thread] Astrometry.NET - File is too large, resizing
[10/23/19 11:25:20.501][DEBUG] [Telescope Thread] Astrometry.NET - Saving file
[10/23/19 11:25:20.501][DEBUG] [Telescope Thread] SaveFileBmp16: Locking bitmap for disk write…
[10/23/19 11:25:20.501][DEBUG] [Telescope Thread] SaveFileBmp16: Opening file stream…
[10/23/19 11:25:20.502][DEBUG] [Telescope Thread] SaveFileBmp16: Writing FITS headers…
[10/23/19 11:25:20.502][DEBUG] [Telescope Thread] SaveFileBmp16: Traversing and persisting bitmap data…
[10/23/19 11:25:20.513][DEBUG] [Telescope Thread] SaveFileBmp16: FITS block fill…
[10/23/19 11:25:20.513][DEBUG] [Telescope Thread] SaveFileBmp16: Unlocking bitmap…
[10/23/19 11:25:20.513][DEBUG] [Telescope Thread] SaveFileBmp16: Closing file stream
[10/23/19 11:25:20.518][DEBUG] [Telescope Thread] Astrometry.NET using endpoint: http://nova.astrometry.net/api/
[10/23/19 11:25:20.518][DEBUG] [Telescope Thread] Astrometry.NET - Calling Async Solve
[10/23/19 11:25:20.638][DEBUG] [Unknown] Astrometry.NET uploading file: C:\Users\Eric\AppData\Local\SequenceGenerator\Temp\convertedAstometry.fits
[10/23/19 11:25:21.539][DEBUG] [Main Thread] Centering: User abort…
[10/23/19 11:25:23.803][DEBUG] [Auto Center Closing Thread] Aborting auto center, waiting for centering routine to terminate…
[10/23/19 11:25:23.804][DEBUG] [Unknown] Astrometry.NET request: /api/submissions/3002977
[10/23/19 11:25:23.804][DEBUG] [Unknown] Astrometry.NET returned: {“processing_started”: “None”, “job_calibrations”: , “jobs”: , “processing_finished”: “None”, “user”: 794, “user_images”: }
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] *********** SUCCESSFUL SOLVE *************
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] SOLVER: True
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] SUCCESS: False
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] CONF: 0
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] BLIND: True
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] RA: 0
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] DEC: 0
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] SCALE: 0
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] FLIPPED: False
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] ANGLE (EON): -500
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] MSG: User Aborted
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] ******************************************
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] Auto center validation frame solve failed. User Aborted
[10/23/19 11:25:24.521][DEBUG] [Telescope Thread] Auto center aborted, closing centering dialog…
[10/23/19 11:25:24.847][DEBUG] [Unknown] Astrometry.NET request: /api/submissions/3002977
[10/23/19 11:25:24.847][DEBUG] [Unknown] Astrometry.NET returned: {“processing_started”: “None”, “job_calibrations”: , “jobs”: , “processing_finished”: “None”, “user”: 794, “user_images”: }
[10/23/19 11:25:24.886][DEBUG] [Unknown] Astrometry.NET solve done in 2 seconds.
[10/23/19 11:25:32.201][DEBUG] [Dome Thread] Observatory: Calculating new position using:
[10/23/19 11:25:32.201][DEBUG] [Dome Thread] Azimuth: 344.986889988268
[10/23/19 11:25:32.201][DEBUG] [Dome Thread] Altitude: 13.511004519788
[10/23/19 11:25:32.201][DEBUG] [Dome Thread] Hour Angle: 147.405652366903
[10/23/19 11:25:32.201][DEBUG] [Dome Thread] Pier Side: East
[10/23/19 11:25:32.201][DEBUG] [Dome Thread] Observatory: Adjustment needed, slewing to Azimuth: 334.949688801006