toggle quoted messageShow quoted text
Honestly the virtual cameras like this are useful; I use them all the time. Han even makes one himself and he uses it for testing ASTAP:https://sourceforge.net/projects/sky-simulator/
It can use DSS survey images or generate simulated images using the same G17/G18 star databases that ASTAP uses.
Yes, the images that come out of things like NASA's or ESO's sky survey sites can be wonky and not at all examples of an unstretched FIT image that's right off our own cameras, but it does work and has some utility, as Ray pointed out. The issue here tonight was just a case of image FoV not matching up with the database that was used; which I mentioned earlier in the thread. This is the same situation one would run into by not having the correct index files downloaded in ASPS/ansvr.
On Sep 27, 2020, at 1:07 AM, Bill Long <firstname.lastname@example.org> wrote:
Good work sir.
These are still not use cases that anyone would encounter. Testing a toaster to find out if it makes coffee or not isnt relevent. This is the same..
From: email@example.com <firstname.lastname@example.org> on behalf of Dale Ghent <email@example.com>
Sent: Saturday, September 26, 2020 10:03 PM
To: firstname.lastname@example.org <email@example.com>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
On Sep 26, 2020, at 8:37 PM, Ray Gralak <firstname.lastname@example.org> wrote:Ok, so I ran these myself and they solved in 0.2 and 0.3 seconds with the G18 database. It seems that however these images were generated, they were generated with a small enough FoV that they didn't include enough stars that were in the G17 database.
Right, but ASTAP is under active development. As was pointed out earlier in this thread, there have been fixesIs it correct that the latest version is a *beta* version? (v0.9.421) It is free now, but will it be free when it is released as v1.0?
even since I used it last. It's possible that if the problem is there (and we still don't know that, it could be SGP), that
it's already been fixed.
I just downloaded it, installed it and the G17 database. I then used APPM's NASA SkyView camera type to get an emulated image, which solved in PinPoint in a few seconds. Trying to solve the same image in ASTAP fails despite that it seemed to extra the correct RA/Dec and image scale from the FITS header.
Any idea of what I should check? Or is this a possible bug in the application?
00:59:50 Start finding stars
00:59:50 213 stars found of the requested 500. Background value is 3487. Detection level used 10027 above background. Star level is 10027 above background. Noise level is 316
00:59:50 550 stars found of the requested 500. Background value is 3487. Detection level used 4740 above background. Star level is 10027 above background. Noise level is 316
00:59:50 Selecting the 500 brightest stars only.
00:59:50 Finding stars done in 176 ms
00:59:50 510 stars selected and 416 quads selected in the image. 430 database stars required for the square search field of 0.5°. Search window at 200%
00:59:50 Using star database G18
00:59:50 Search 0, [0,0],
position: 15: 19 49.5
+70° 03 12 Up to magn 18.0 816 database quads to compare.
00:59:50 quad outlier removed due to abnormal size: 101.345565%
00:59:50 quad outlier removed due to abnormal size: 121.156045%
00:59:50 quad outlier removed due to abnormal size: 135.973701%
00:59:50 quad outlier removed due to abnormal size: 99.253178%
00:59:50 quad outlier removed due to abnormal size: 99.287188%
00:59:50 14 of 19 quads selected matching within 0.007 tolerance. Solution x:=1.621520*x+ 0.000907*y+ -1296.950386, y:=-0.000450*x+ 1.622169*y+ -972.841391
00:59:50 Solution found: 15: 19 49.5
+70° 03 11 Solved in 0.2 sec. Offset was 0.000 deg.
Used stars up to magnitude: 18.0
00:59:51 See viewer image for image stars used (red) and database star used (yellow)
<Screen Shot 2020-09-27 at 1.03.18 AM.png>