Date   

locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Worsel
 

That's very weird...

See attached ASTAP screenshot

Bryan


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Ray Gralak
 

The images solve in pinpoint, ccdstack, maximdl, and astap can open them too.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Worsel via groups.io
Sent: Saturday, September 26, 2020 7:08 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

Ray

I could not solve these in local astrometry.net, remote astrometry.net, ASTAP. Further investigation shows that I
cannot even open these in

ImagesPlus
NASA FITS Libeartor
ASIFitsView

Bryan


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Ray Gralak
 

Dale,

The issue I care about is the accuracy of its plate solves.

The issue you and others seem to most care about, is that it is free!

I would rather have slower, yet more accurate plate solves, so tracking rate modelling will be as accurate as possible. Until I can
run through a set of images to test accuracy I won't know.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Dale Ghent
Sent: Saturday, September 26, 2020 6:54 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE



On Sep 26, 2020, at 9:24 PM, Ray Gralak <groups3@gralak.com> wrote:

Hi Dale,

I'm not saying this is the case here but surely you must know that open source does not necessarily mean it has
to be free, or
remain free?
The ASTAP code is licensed under a very tested and common open source license, and the code as it is will remain
free under the terms of that license. The only way that code could be made non-free is if all contributors to that code
all voted favorably to change the license to a non-open one. If that happened the code as it was up to that point
remains open, as it existed under the open license. Subsequent revisions will continue under the non-open license.
This still allows someone to fork the codebase prior to the re-licensing and continue developing the software on their
own, perhaps under a different organization or project, under the original open license. That's just how it works, and
why I say that the code cannot just disappear.

Believe me, Ray, it's not so common and certainly isn't as dire as a lot of people seem to make it out to be. Open
source licenses would be pretty weak things if they permitted this stuff and we would not see open source
frameworks, libraries, apps and entire operating environments flourish and end up in things from our home router to
our car infotainment to medical devices if this were a real fear. Another thing that seems to get people confused is
having an open source program but charging for support, which is a common model in the open source community
that is used to support development.

I was more concerned that this is just a beta and doesn't seem to be able to solve the images I gave to it.

The purpose for this test is to determine the accuracy of the solutioms.
Right, so I don't know what you got from the NASA server exactly so I passed you the list of things that make
ASTAP work well. It's designed to be a solver for imagers and so it's really geared towards consuming data that
would come from such an environment. Stretched, processed, and whatever else the NASA sky survey server
(slowly) regurgitates might not fit the bill in that regard.

/dale


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Worsel
 

Ray

I could not solve these in local astrometry.net, remote astrometry.net, ASTAP.  Further investigation shows that I cannot even open these in

ImagesPlus
NASA FITS Libeartor
ASIFitsView

Bryan


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Dale Ghent
 

On Sep 26, 2020, at 9:24 PM, Ray Gralak <groups3@gralak.com> wrote:

Hi Dale,

I'm not saying this is the case here but surely you must know that open source does not necessarily mean it has to be free, or
remain free?
The ASTAP code is licensed under a very tested and common open source license, and the code as it is will remain free under the terms of that license. The only way that code could be made non-free is if all contributors to that code all voted favorably to change the license to a non-open one. If that happened the code as it was up to that point remains open, as it existed under the open license. Subsequent revisions will continue under the non-open license. This still allows someone to fork the codebase prior to the re-licensing and continue developing the software on their own, perhaps under a different organization or project, under the original open license. That's just how it works, and why I say that the code cannot just disappear.

Believe me, Ray, it's not so common and certainly isn't as dire as a lot of people seem to make it out to be. Open source licenses would be pretty weak things if they permitted this stuff and we would not see open source frameworks, libraries, apps and entire operating environments flourish and end up in things from our home router to our car infotainment to medical devices if this were a real fear. Another thing that seems to get people confused is having an open source program but charging for support, which is a common model in the open source community that is used to support development.

I was more concerned that this is just a beta and doesn't seem to be able to solve the images I gave to it.

The purpose for this test is to determine the accuracy of the solutioms.
Right, so I don't know what you got from the NASA server exactly so I passed you the list of things that make ASTAP work well. It's designed to be a solver for imagers and so it's really geared towards consuming data that would come from such an environment. Stretched, processed, and whatever else the NASA sky survey server (slowly) regurgitates might not fit the bill in that regard.

/dale


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Ray Gralak
 

Also, for some reason it displays images flipped vertically by default.

Here is a link to a folder with two images. What I tried is: load the FITS file in the UI and clicked the Solve button.

https://www.dropbox.com/sh/qlp1qgtaptccyu4/AADaSEl7EE0z1VO298pFGs2Ea?dl=0


-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, September 26, 2020 6:28 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

Post the FITS image file please.
________________________________

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@gralak.com>
Sent: Saturday, September 26, 2020 6:24 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

Hi Dale,

I'm not saying this is the case here but surely you must know that open source does not necessarily mean it has to
be free, or
remain free?

I was more concerned that this is just a beta and doesn't seem to be able to solve the images I gave to it.

The purpose for this test is to determine the accuracy of the solutioms.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%
7C1%7C0%7C637367666987247003&amp;sdata=F5Ig87yZjOBii2bvXlbxkHburljTKUJBpSqYm2Ye4O4%3D&amp;re
served=0 <https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%
7C1%7C0%7C637367666987247003&amp;sdata=F5Ig87yZjOBii2bvXlbxkHburljTKUJBpSqYm2Ye4O4%3D&amp;re
served=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
ata=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367666987247003&amp;sdata=XqAPTrD21MCZ3xsV4%2BAJPJbosp8E2O3zuD0X7vsin0E%3D&amp;rese
rved=0
<https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367666987247003&amp;sdata=XqAPTrD21MCZ3xsV4%2BAJPJbosp8E2O3zuD0X7vsin0E%3D&amp;res
erved=0>


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Dale Ghent
Sent: Saturday, September 26, 2020 6:14 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE



On Sep 26, 2020, at 8:37 PM, Ray Gralak <groups3@gralak.com> wrote:

Right, but ASTAP is under active development. As was pointed out earlier in this thread, there have been fixes
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.
Is 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?

What can I say, Han doesn't really care about versioning. I wouldn't quibble over that since we as developers
know
that versioning can be rather arbitrary. At any rate, the source for ASTAP and all of Han's other projects are
licensed under the GNU GPLv3 license, which is one of the most commonly-used open source licenses out there.
No one, not even himself, can suddenly disappear that code as part of any attempt to make it closed-source.
Doing
so would violate one of the core points that comprise the GNU GPL and other open source licenses like it.

I've noticed that the "but what if he/she/they charges for it later" response is common, especially in the astro
scene,
when it comes to open source projects. This primarily indicates to me a lack of familiarity of what open source
licensing means and entails and maybe even an unfamiliarity with the open source community as a whole. If there
is
some confusion, please feel welcome to contact me directly and I can help explain any points of curiosity or
confusion.

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 extract 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?
Might want to check out the "Quick checklist for solving" section in the ASTAP docs:
https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hnsky.org%2Fastap.htm%23conditions&
amp;data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1
%7C0%7C637367666987247003&amp;sdata=dDEaCWlKpGxYVLp527D1JjrflGs8FRHFkuE7wuePbAA%3D&amp;r
eserved=0
<https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hnsky.org%2Fastap.htm%23conditions
&amp;data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C
1%7C0%7C637367666987247003&amp;sdata=dDEaCWlKpGxYVLp527D1JjrflGs8FRHFkuE7wuePbAA%3D&amp;
reserved=0>

/dale









locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Bill Long
 

No disagreement from me. I do have SkyX, but it runs like a slug on my MiniPC I use for imaging, while PS2 and ASTAP run like lightning on it. Voyager (and NINA by the way) also run very smoothly on the MiniPC. I cringe when I have to open up SkyX to do my model building. The solves run so slow because the software is just a behemoth, and all I need it to do is run Image Link. 



From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Dale Ghent <daleg@...>
Sent: Saturday, September 26, 2020 6:35 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
 

So here's the the main issue I have that has been preventing me from wanting to upgrade from Standard to Pro: I have to buy other software to make APPM work, and APPM is really one of the primary reasons for going to APCC Pro.

ANSVR, Astrometry.Net, ASTAP, ASPS, PlateSolve2... these are all free(*) solvers with various qualities and capabilities. But to use them with APPM, I have to put some other non-free (and now, subscription-based) software in front of them, such as TSX, SGPro or PinPoint. I have -zero- other uses for such software; if I bought (or subscribed) to them, I would be doing so only to be able to use APPM. This really feels like it could be a better arrangement.

I think what people, and certainly myself, would like is for APPM to not have this dependency and for it to be able to plate solve on its own using any (or all!) of the aforementioned solving suites. Let APPM run an ASCOM camera, and devise an internal Interface that would let you make a driver for each of whatever solvers you'd like to support. At that point, the user now has the power to choose which solver they wish to use, wether it be ASTAP or PS2 or whatever else - and do so without the middleware.

The internal interface for plate solvers is what we had to do in NINA because we realized that different folks have their preferences for solvers, sometimes nearing total religious adherence. So if someone popped up asking if they could use some new and previously-unheard of XYZ Solver with the app, all we need to know is how to make XYZ Solver solve an image that we pass to it and how to parse its results through whatever means it makes those results available. Everyone is happy and there's yet another solver listed in the drop-down menu of solvers to choose from.

> On Sep 26, 2020, at 1:04 PM, Ray Gralak <groups3@...> wrote:
>
>> Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
>> concerned about it.
>
> I don't even understand what that means?
>
> APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
> or intermediary app.
>
> For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
> even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
> reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
> where there are too many stars in the selected database, typically around the milkyway.
>
> If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.
>
> -Ray Gralak
> Author of PEMPro
> Author of APCC (Astro-Physics Command Center): https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7Ce44fc52051134aa30b7208d862859dfa%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367673298046020&amp;sdata=JyZ0r6Co5EzRgzRdupHQx9LRrxmoB%2F9is0JvIuNUXxw%3D&amp;reserved=0
> Author of Astro-Physics V2 ASCOM Driver: https://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7Ce44fc52051134aa30b7208d862859dfa%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367673298046020&amp;sdata=tnbpfItdqeNMIidCjnnx6MbFCAwGH32IgHREgMZ1VIY%3D&amp;reserved=0
>
>
>> -----Original Message-----
>> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
>> Sent: Saturday, September 26, 2020 9:48 AM
>> To: Ray Gralak; main@ap-gto.groups.io
>> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>>
>> Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
>> concerned about it.
>>
>> ________________________________
>>
>> From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
>> Sent: Saturday, September 26, 2020 9:26 AM
>> To: main@ap-gto.groups.io <main@ap-gto.groups.io>
>> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>>
>>> It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
>>
>> I hope that's not true because it might make ASTAP a poor choice for plate solving.
>>
>> -Ray Gralak
>> Author of PEMPro
>> Author of APCC (Astro-Physics Command Center):
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
>> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
>> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
>> amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
>> physics.com%2Fapcc-
>> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
>> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
>> amp;reserved=0>
>> Author of Astro-Physics V2 ASCOM Driver:
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
>> ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
>> %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
>> p;reserved=0
>> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
>> data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
>> 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
>> mp;reserved=0>
>>
>>
>>> -----Original Message-----
>>> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
>>> Sent: Saturday, September 26, 2020 8:50 AM
>>> To: main@ap-gto.groups.io
>>> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>>>
>>> I agree.
>>>
>>> I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it.  It could be as simple as
>> the
>>> fact that APPM is doing a large number of plate solves in a short period of time.  As I mentioned, I've not had time
>>> to do any investigation at all yet.
>>>
>>> -----Original Message-----
>>> From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
>>> Sent: Friday, September 25, 2020 6:52 PM
>>> To: main@ap-gto.groups.io
>>> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>>>
>>>> I switched to ASTAP for my plate solves with SGP and am seeing what is
>>>> probably the same issue described in the first post of this thread.
>>>
>>> APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
>>> way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
>>> seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.
>>>
>>> -Ray Gralak
>>> Author of PEMPro
>>> Author of APCC (Astro-Physics Command Center):
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
>> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
>> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
>> amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
>> physics.com%2Fapcc-
>> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
>> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
>> amp;reserved=0>
>>> Author of Astro-Physics V2 ASCOM Driver:
>> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
>> ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
>> %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
>> p;reserved=0
>> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
>> data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
>> 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
>> mp;reserved=0>
>>>
>>>> -----Original Message-----
>>>> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
>>>> Of W Hilmo
>>>> Sent: Friday, September 25, 2020 9:29 AM
>>>> To: main@ap-gto.groups.io
>>>> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>>>>
>>>> I switched to ASTAP for my plate solves with SGP and am seeing what is
>>>> probably the same issue described in the first post of this thread.
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>







locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Dale Ghent
 

So here's the the main issue I have that has been preventing me from wanting to upgrade from Standard to Pro: I have to buy other software to make APPM work, and APPM is really one of the primary reasons for going to APCC Pro.

ANSVR, Astrometry.Net, ASTAP, ASPS, PlateSolve2... these are all free(*) solvers with various qualities and capabilities. But to use them with APPM, I have to put some other non-free (and now, subscription-based) software in front of them, such as TSX, SGPro or PinPoint. I have -zero- other uses for such software; if I bought (or subscribed) to them, I would be doing so only to be able to use APPM. This really feels like it could be a better arrangement.

I think what people, and certainly myself, would like is for APPM to not have this dependency and for it to be able to plate solve on its own using any (or all!) of the aforementioned solving suites. Let APPM run an ASCOM camera, and devise an internal Interface that would let you make a driver for each of whatever solvers you'd like to support. At that point, the user now has the power to choose which solver they wish to use, wether it be ASTAP or PS2 or whatever else - and do so without the middleware.

The internal interface for plate solvers is what we had to do in NINA because we realized that different folks have their preferences for solvers, sometimes nearing total religious adherence. So if someone popped up asking if they could use some new and previously-unheard of XYZ Solver with the app, all we need to know is how to make XYZ Solver solve an image that we pass to it and how to parse its results through whatever means it makes those results available. Everyone is happy and there's yet another solver listed in the drop-down menu of solvers to choose from.

On Sep 26, 2020, at 1:04 PM, Ray Gralak <groups3@gralak.com> wrote:

Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
concerned about it.
I don't even understand what that means?

APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
or intermediary app.

For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
where there are too many stars in the selected database, typically around the milkyway.

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, September 26, 2020 9:48 AM
To: Ray Gralak; main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
concerned about it.

________________________________

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@gralak.com>
Sent: Saturday, September 26, 2020 9:26 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
I hope that's not true because it might make ASTAP a poor choice for plate solving.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
p;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
mp;reserved=0>


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
Sent: Saturday, September 26, 2020 8:50 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I agree.

I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it. It could be as simple as
the
fact that APPM is doing a large number of plate solves in a short period of time. As I mentioned, I've not had time
to do any investigation at all yet.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, September 25, 2020 6:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.
APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
p;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
mp;reserved=0>

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Friday, September 25, 2020 9:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.






















locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Bill Long
 

Also PlateSolve2 is free. I would even accept that for APPM. Anything to prevent folks from needing to run the expensive PinPoint program or a full imaging suite just to plate solve.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
Sent: Saturday, September 26, 2020 6:24 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
 
Hi Dale,

I'm not saying this is the case here but surely you must know that open source does not necessarily mean it has to be free, or
remain free?

I was more concerned that this is just a beta and doesn't seem to be able to solve the images I gave to it.

The purpose for this test is to determine the accuracy of the solutioms.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367666987247003&amp;sdata=F5Ig87yZjOBii2bvXlbxkHburljTKUJBpSqYm2Ye4O4%3D&amp;reserved=0
Author of Astro-Physics V2 ASCOM Driver: https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367666987247003&amp;sdata=XqAPTrD21MCZ3xsV4%2BAJPJbosp8E2O3zuD0X7vsin0E%3D&amp;reserved=0


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Dale Ghent
> Sent: Saturday, September 26, 2020 6:14 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
>
>
> > On Sep 26, 2020, at 8:37 PM, Ray Gralak <groups3@...> wrote:
> >
> >> Right, but ASTAP is under active development.  As was pointed out earlier in this thread, there have been fixes
> >> 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.
> >
> > Is 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?
>
> What can I say, Han doesn't really care about versioning. I wouldn't quibble over that since we as developers know
> that versioning can be rather arbitrary. At any rate, the source for ASTAP and all of Han's other projects are
> licensed under the GNU GPLv3 license, which is one of the most commonly-used open source licenses out there.
> No one, not even himself, can suddenly disappear that code as part of any attempt to make it closed-source. Doing
> so would violate one of the core points that comprise the GNU GPL and other open source licenses like it.
>
> I've noticed that the "but what if he/she/they charges for it later" response is common, especially in the astro scene,
> when it comes to open source projects. This primarily indicates to me a lack of familiarity of what open source
> licensing means and entails and maybe even an unfamiliarity with the open source community as a whole. If there is
> some confusion, please feel welcome to contact me directly and I can help explain any points of curiosity or
> confusion.
>
> > 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 extract 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?
>
> Might want to check out the "Quick checklist for solving" section in the ASTAP docs:
> https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hnsky.org%2Fastap.htm%23conditions&amp;data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367666987247003&amp;sdata=dDEaCWlKpGxYVLp527D1JjrflGs8FRHFkuE7wuePbAA%3D&amp;reserved=0
>
> /dale
>
>








locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Bill Long
 

Post the FITS image file please.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
Sent: Saturday, September 26, 2020 6:24 PM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
 
Hi Dale,

I'm not saying this is the case here but surely you must know that open source does not necessarily mean it has to be free, or
remain free?

I was more concerned that this is just a beta and doesn't seem to be able to solve the images I gave to it.

The purpose for this test is to determine the accuracy of the solutioms.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367666987247003&amp;sdata=F5Ig87yZjOBii2bvXlbxkHburljTKUJBpSqYm2Ye4O4%3D&amp;reserved=0
Author of Astro-Physics V2 ASCOM Driver: https://nam05.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367666987247003&amp;sdata=XqAPTrD21MCZ3xsV4%2BAJPJbosp8E2O3zuD0X7vsin0E%3D&amp;reserved=0


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Dale Ghent
> Sent: Saturday, September 26, 2020 6:14 PM
> To: main@ap-gto.groups.io
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
>
>
> > On Sep 26, 2020, at 8:37 PM, Ray Gralak <groups3@...> wrote:
> >
> >> Right, but ASTAP is under active development.  As was pointed out earlier in this thread, there have been fixes
> >> 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.
> >
> > Is 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?
>
> What can I say, Han doesn't really care about versioning. I wouldn't quibble over that since we as developers know
> that versioning can be rather arbitrary. At any rate, the source for ASTAP and all of Han's other projects are
> licensed under the GNU GPLv3 license, which is one of the most commonly-used open source licenses out there.
> No one, not even himself, can suddenly disappear that code as part of any attempt to make it closed-source. Doing
> so would violate one of the core points that comprise the GNU GPL and other open source licenses like it.
>
> I've noticed that the "but what if he/she/they charges for it later" response is common, especially in the astro scene,
> when it comes to open source projects. This primarily indicates to me a lack of familiarity of what open source
> licensing means and entails and maybe even an unfamiliarity with the open source community as a whole. If there is
> some confusion, please feel welcome to contact me directly and I can help explain any points of curiosity or
> confusion.
>
> > 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 extract 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?
>
> Might want to check out the "Quick checklist for solving" section in the ASTAP docs:
> https://nam05.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.hnsky.org%2Fastap.htm%23conditions&amp;data=02%7C01%7C%7Cff52e3ea96ef4b2f57bb08d8628425e2%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367666987247003&amp;sdata=dDEaCWlKpGxYVLp527D1JjrflGs8FRHFkuE7wuePbAA%3D&amp;reserved=0
>
> /dale
>
>








locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Ray Gralak
 

Hi Dale,

I'm not saying this is the case here but surely you must know that open source does not necessarily mean it has to be free, or
remain free?

I was more concerned that this is just a beta and doesn't seem to be able to solve the images I gave to it.

The purpose for this test is to determine the accuracy of the solutioms.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Dale Ghent
Sent: Saturday, September 26, 2020 6:14 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE



On Sep 26, 2020, at 8:37 PM, Ray Gralak <groups3@gralak.com> wrote:

Right, but ASTAP is under active development. As was pointed out earlier in this thread, there have been fixes
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.
Is 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?

What can I say, Han doesn't really care about versioning. I wouldn't quibble over that since we as developers know
that versioning can be rather arbitrary. At any rate, the source for ASTAP and all of Han's other projects are
licensed under the GNU GPLv3 license, which is one of the most commonly-used open source licenses out there.
No one, not even himself, can suddenly disappear that code as part of any attempt to make it closed-source. Doing
so would violate one of the core points that comprise the GNU GPL and other open source licenses like it.

I've noticed that the "but what if he/she/they charges for it later" response is common, especially in the astro scene,
when it comes to open source projects. This primarily indicates to me a lack of familiarity of what open source
licensing means and entails and maybe even an unfamiliarity with the open source community as a whole. If there is
some confusion, please feel welcome to contact me directly and I can help explain any points of curiosity or
confusion.

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 extract 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?
Might want to check out the "Quick checklist for solving" section in the ASTAP docs:
http://www.hnsky.org/astap.htm#conditions

/dale


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Dale Ghent
 

On Sep 26, 2020, at 8:37 PM, Ray Gralak <groups3@gralak.com> wrote:

Right, but ASTAP is under active development. As was pointed out earlier in this thread, there have been fixes
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.
Is 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?
What can I say, Han doesn't really care about versioning. I wouldn't quibble over that since we as developers know that versioning can be rather arbitrary. At any rate, the source for ASTAP and all of Han's other projects are licensed under the GNU GPLv3 license, which is one of the most commonly-used open source licenses out there. No one, not even himself, can suddenly disappear that code as part of any attempt to make it closed-source. Doing so would violate one of the core points that comprise the GNU GPL and other open source licenses like it.

I've noticed that the "but what if he/she/they charges for it later" response is common, especially in the astro scene, when it comes to open source projects. This primarily indicates to me a lack of familiarity of what open source licensing means and entails and maybe even an unfamiliarity with the open source community as a whole. If there is some confusion, please feel welcome to contact me directly and I can help explain any points of curiosity or confusion.

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 extract 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?
Might want to check out the "Quick checklist for solving" section in the ASTAP docs:
http://www.hnsky.org/astap.htm#conditions

/dale


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Ray Gralak
 
Edited

Right, but ASTAP is under active development. As was pointed out earlier in this thread, there have been fixes
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.
Is 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?

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 extract 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?

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
Sent: Saturday, September 26, 2020 4:56 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

Right, but ASTAP is under active development. As was pointed out earlier in this thread, there have been fixes
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 would also echo the other comments here that it would be great if APPM could use it directly. It would be nice to
have the option of running APPM with an ASCOM camera driver and direct calls to ASTAP. It would be possible
then to do an APPM run without a separate imaging package.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Saturday, September 26, 2020 9:27 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
I hope that's not true because it might make ASTAP a poor choice for plate solving.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Saturday, September 26, 2020 8:50 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I agree.

I suspect that it's an ASTAP problem, but something that APPM is doing
is exposing it. It could be as simple as the fact that APPM is doing
a large number of plate solves in a short period of time. As I mentioned, I've not had time to do any investigation
at all yet.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray
Gralak
Sent: Friday, September 25, 2020 6:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what
is probably the same issue described in the first post of this thread.
APPM doesn’t know which plate solver is in use when SGPro is used for
plate solving. APPM operates the same way for all SGPro plate solvers
because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn’t seem to show the same
problem, it seems likely that the problem is with how SGPro handles ASTAP.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver:
https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Friday, September 25, 2020 9:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with
AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what
is probably the same issue described in the first post of this thread.





















locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

W Hilmo
 

Right, but ASTAP is under active development. As was pointed out earlier in this thread, there have been fixes 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 would also echo the other comments here that it would be great if APPM could use it directly. It would be nice to have the option of running APPM with an ASCOM camera driver and direct calls to ASTAP. It would be possible then to do an APPM run without a separate imaging package.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Saturday, September 26, 2020 9:27 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
I hope that's not true because it might make ASTAP a poor choice for plate solving.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Saturday, September 26, 2020 8:50 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I agree.

I suspect that it's an ASTAP problem, but something that APPM is doing
is exposing it. It could be as simple as the fact that APPM is doing
a large number of plate solves in a short period of time. As I mentioned, I've not had time to do any investigation at all yet.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray
Gralak
Sent: Friday, September 25, 2020 6:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what
is probably the same issue described in the first post of this thread.
APPM doesn’t know which plate solver is in use when SGPro is used for
plate solving. APPM operates the same way for all SGPro plate solvers
because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn’t seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver:
https://www.siriusimaging.com/apdriver

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Friday, September 25, 2020 9:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with
AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what
is probably the same issue described in the first post of this thread.











900 Clutch Plug Help

rrumfield
 

After sometime off from using my 900GTO mount, I realized I needed to replace the clutch plugs on the right ascension unit.  I ordered the removal tool and new plugs.  The first plug removal was a learning experience and didn’t get totally removed, the other three were no problem.  I started to disassemble the R.A unit to get the first plug out.  I didn’t realize it was filled with plastic rollers.  At present I have been able to re-assemble it with two rows of rollers and a center axis that just doesn’t seem to now fit into the RA head properly.  Does anyone have the procedure to re-assemble the unit?  Should I send all back to Astro-Physics at this point?

Help,
Bob


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Ray Gralak
 

I never said APPM natively solves. I was saying it doesn't need to solve frequently enough for me to be concerned
about ASTAP.
Okay, sorry Bill. I completely misunderstood what you meant!

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, September 26, 2020 10:32 AM
To: Ray Gralak; main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I never said APPM natively solves. I was saying it doesn't need to solve frequently enough for me to be concerned
about ASTAP.

________________________________

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@gralak.com>
Sent: Saturday, September 26, 2020 10:04 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
concerned about it.
I don't even understand what that means?

APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values
from the solver,
or intermediary app.

For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate
solves. Maybe
even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have
been extremely
reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas
of the sky
where there are too many stars in the selected database, typically around the milkyway.

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7Cfd6b7446b6dc43767ff008d8623e4d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367367004625483&amp;sdata=EKSA7MUuJDqcoDekyEMjE8INqIh5GVSoZwH0hSPz9lE%3D
&amp;reserved=0 <https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7Cfd6b7446b6dc43767ff008d8623e4d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367367004625483&amp;sdata=EKSA7MUuJDqcoDekyEMjE8INqIh5GVSoZwH0hSPz9lE%3D
&amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
ata=02%7C01%7C%7Cfd6b7446b6dc43767ff008d8623e4d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367367004625483&amp;sdata=o5MMFwdXea6TScC7O0BQ3kwCw7E8tL17gFCDPSaO3oc%3D&amp;res
erved=0
<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7Cfd6b7446b6dc43767ff008d8623e4d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367367004625483&amp;sdata=o5MMFwdXea6TScC7O0BQ3kwCw7E8tL17gFCDPSaO3oc%3D&amp;re
served=0>


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, September 26, 2020 9:48 AM
To: Ray Gralak; main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
concerned about it.

________________________________

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@gralak.com>
Sent: Saturday, September 26, 2020 9:26 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
I hope that's not true because it might make ASTAP a poor choice for plate solving.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc->
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
d>
ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
p;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
mp;reserved=0>


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
Sent: Saturday, September 26, 2020 8:50 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I agree.

I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it. It could be as simple as
the
fact that APPM is doing a large number of plate solves in a short period of time. As I mentioned, I've not had
time
to do any investigation at all yet.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, September 25, 2020 6:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.
APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the
same
way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc->
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
d>
ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
p;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
mp;reserved=0>

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Friday, September 25, 2020 9:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.
























locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

 

Dale that's a good point, and relevant to other plate solvers as well

There are many choices of star databases out there to solve from. picking the right one that matches your fov is important

On Sat, Sep 26, 2020 at 11:12 AM Dale Ghent <daleg@...> wrote:

If one is using ASTAP with long focal length telescopes, there is this *very* important tidbit in the ASTAP documentation:

        • For telescope with a small field of view <20 arcmin you could download the installer G18 up to magnitude 18 or a zipped G18 star database for manual install. at the program directory c:\program files\astap.  Remove the G17 files or force use of the G18 in ASTAP. tab alignment.

Excuse the broken English but what it basically means is that you need the larger G18 database instead of the smaller G17 star database if you're operating at a tight FoV, on the order of 20 arc minutes or less. Despite being only 1 magnitudes of difference, the G18 database is almost twice the size of the default G17 database and weighs in around 1GB in size. This means more stars for ASTAP to make quads against given a small FoV. Obviously telescopes with wider FoVs will contain more brighter stars in their images which is why the G17 database is adequate enough for most.

/dale

> On Sep 26, 2020, at 2:02 PM, Brian Valente <bvalente@...> wrote:
>
> >>> If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.
>
> we're at 0.63"/pix and APPM+pinpoint has worked great
>
> When we do a sky model with around 270 points, we might get <5 failed plate solves
>
>
>
> On Sat, Sep 26, 2020 at 10:04 AM Ray Gralak <groups3@...> wrote:
> > Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> > concerned about it.
>
> I don't even understand what that means?
>
> APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
> or intermediary app.
>
> For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
> even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
> reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
> where there are too many stars in the selected database, typically around the milkyway.
>
> If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.
>
> -Ray Gralak
> Author of PEMPro
> Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
> Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver
>
>
> > -----Original Message-----
> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
> > Sent: Saturday, September 26, 2020 9:48 AM
> > To: Ray Gralak; main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> > concerned about it.
> >
> > ________________________________
> >
> > From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
> > Sent: Saturday, September 26, 2020 9:26 AM
> > To: main@ap-gto.groups.io <main@ap-gto.groups.io>
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > >  It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
> >
> > I hope that's not true because it might make ASTAP a poor choice for plate solving.
> >
> > -Ray Gralak
> > Author of PEMPro
> > Author of APCC (Astro-Physics Command Center):
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> > pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> > %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> > amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> > physics.com%2Fapcc-
> > pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> > %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> > amp;reserved=0>
> > Author of Astro-Physics V2 ASCOM Driver:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> > ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> > %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> > p;reserved=0
> > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> > data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> > 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> > mp;reserved=0>
> >
> >
> > > -----Original Message-----
> > > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
> > > Sent: Saturday, September 26, 2020 8:50 AM
> > > To: main@ap-gto.groups.io
> > > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> > >
> > > I agree.
> > >
> > > I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it.  It could be as simple as
> > the
> > > fact that APPM is doing a large number of plate solves in a short period of time.  As I mentioned, I've not had time
> > > to do any investigation at all yet.
> > >
> > > -----Original Message-----
> > > From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
> > > Sent: Friday, September 25, 2020 6:52 PM
> > > To: main@ap-gto.groups.io
> > > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> > >
> > > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > > probably the same issue described in the first post of this thread.
> > >
> > > APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
> > > way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
> > > seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.
> > >
> > > -Ray Gralak
> > > Author of PEMPro
> > > Author of APCC (Astro-Physics Command Center):
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> > pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> > %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> > amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> > physics.com%2Fapcc-
> > pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> > %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> > amp;reserved=0>
> > > Author of Astro-Physics V2 ASCOM Driver:
> > https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> > ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> > %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> > p;reserved=0
> > <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> > data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> > 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> > mp;reserved=0>
> > >
> > > > -----Original Message-----
> > > > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
> > > > Of W Hilmo
> > > > Sent: Friday, September 25, 2020 9:29 AM
> > > > To: main@ap-gto.groups.io
> > > > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> > > >
> > > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > > probably the same issue described in the first post of this thread.
> > > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
> --
> Brian
>
>
>
> Brian Valente
> portfolio brianvalentephotography.com
>








--
Brian 



Brian Valente


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Dale Ghent
 

If one is using ASTAP with long focal length telescopes, there is this *very* important tidbit in the ASTAP documentation:

• For telescope with a small field of view <20 arcmin you could download the installer G18 up to magnitude 18 or a zipped G18 star database for manual install. at the program directory c:\program files\astap. Remove the G17 files or force use of the G18 in ASTAP. tab alignment.

Excuse the broken English but what it basically means is that you need the larger G18 database instead of the smaller G17 star database if you're operating at a tight FoV, on the order of 20 arc minutes or less. Despite being only 1 magnitudes of difference, the G18 database is almost twice the size of the default G17 database and weighs in around 1GB in size. This means more stars for ASTAP to make quads against given a small FoV. Obviously telescopes with wider FoVs will contain more brighter stars in their images which is why the G17 database is adequate enough for most.

/dale

On Sep 26, 2020, at 2:02 PM, Brian Valente <bvalente@gmail.com> wrote:

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.
we're at 0.63"/pix and APPM+pinpoint has worked great

When we do a sky model with around 270 points, we might get <5 failed plate solves



On Sat, Sep 26, 2020 at 10:04 AM Ray Gralak <groups3@gralak.com> wrote:
Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
concerned about it.
I don't even understand what that means?

APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
or intermediary app.

For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
where there are too many stars in the selected database, typically around the milkyway.

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
Sent: Saturday, September 26, 2020 9:48 AM
To: Ray Gralak; main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
concerned about it.

________________________________

From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@gralak.com>
Sent: Saturday, September 26, 2020 9:26 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
I hope that's not true because it might make ASTAP a poor choice for plate solving.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
p;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
mp;reserved=0>


-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
Sent: Saturday, September 26, 2020 8:50 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I agree.

I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it. It could be as simple as
the
fact that APPM is doing a large number of plate solves in a short period of time. As I mentioned, I've not had time
to do any investigation at all yet.

-----Original Message-----
From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
Sent: Friday, September 25, 2020 6:52 PM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.
APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center):
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
physics.com%2Fapcc-
pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
%7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
amp;reserved=0>
Author of Astro-Physics V2 ASCOM Driver:
https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;d
ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
p;reserved=0
<https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&;
data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
mp;reserved=0>

-----Original Message-----
From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
Of W Hilmo
Sent: Friday, September 25, 2020 9:29 AM
To: main@ap-gto.groups.io
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE

I switched to ASTAP for my plate solves with SGP and am seeing what is
probably the same issue described in the first post of this thread.
























--
Brian



Brian Valente
portfolio brianvalentephotography.com


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

 

>>> If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

we're at 0.63"/pix and APPM+pinpoint has worked great

When we do a sky model with around 270 points, we might get <5 failed plate solves



On Sat, Sep 26, 2020 at 10:04 AM Ray Gralak <groups3@...> wrote:
> Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> concerned about it.

I don't even understand what that means?

APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
or intermediary app.

For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
where there are too many stars in the selected database, typically around the milkyway.

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://www.astro-physics.com/apcc-pro
Author of Astro-Physics V2 ASCOM Driver: https://www.siriusimaging.com/apdriver


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
> Sent: Saturday, September 26, 2020 9:48 AM
> To: Ray Gralak; main@ap-gto.groups.io
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> concerned about it.
>
> ________________________________
>
> From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
> Sent: Saturday, September 26, 2020 9:26 AM
> To: main@ap-gto.groups.io <main@ap-gto.groups.io>
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> >  It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
>
> I hope that's not true because it might make ASTAP a poor choice for plate solving.
>
> -Ray Gralak
> Author of PEMPro
> Author of APCC (Astro-Physics Command Center):
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0>
> Author of Astro-Physics V2 ASCOM Driver:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> p;reserved=0
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> mp;reserved=0>
>
>
> > -----Original Message-----
> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
> > Sent: Saturday, September 26, 2020 8:50 AM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > I agree.
> >
> > I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it.  It could be as simple as
> the
> > fact that APPM is doing a large number of plate solves in a short period of time.  As I mentioned, I've not had time
> > to do any investigation at all yet.
> >
> > -----Original Message-----
> > From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
> > Sent: Friday, September 25, 2020 6:52 PM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > probably the same issue described in the first post of this thread.
> >
> > APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
> > way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
> > seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.
> >
> > -Ray Gralak
> > Author of PEMPro
> > Author of APCC (Astro-Physics Command Center):
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0>
> > Author of Astro-Physics V2 ASCOM Driver:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> p;reserved=0
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> mp;reserved=0>
> >
> > > -----Original Message-----
> > > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
> > > Of W Hilmo
> > > Sent: Friday, September 25, 2020 9:29 AM
> > > To: main@ap-gto.groups.io
> > > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> > >
> > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > probably the same issue described in the first post of this thread.
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>








--
Brian 



Brian Valente


locked Re: #APCC APCC/APPM blocking issue with AP1100GTOAE #APCC

Bill Long
 

I never said APPM natively solves. I was saying it doesn't need to solve frequently enough for me to be concerned about ASTAP.


From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
Sent: Saturday, September 26, 2020 10:04 AM
To: main@ap-gto.groups.io <main@ap-gto.groups.io>
Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
 
> Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> concerned about it.

I don't even understand what that means?

APPM does not natively plate solve. It uses an external plate solver. It simply reads the RA/Dec and other values from the solver,
or intermediary app.

For plate-solving I typically use PinPoint and all-sky backup to Astrometry.Net. I've done many thousands of plate solves. Maybe
even hundreds of thousands. Unless there is a tree, clouds, or something else obscuring the sky, plate solves have been extremely
reliable at the image scale I typically use (around 1.6 arc-sec/pixel). That said, PinPoint can have problems in areas of the sky
where there are too many stars in the selected database, typically around the milkyway.

If the image area is smaller, for example because of a longer focal length, it may be more of a challenge.

-Ray Gralak
Author of PEMPro
Author of APCC (Astro-Physics Command Center): https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-pro&amp;data=02%7C01%7C%7Cfd6b7446b6dc43767ff008d8623e4d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367367004625483&amp;sdata=EKSA7MUuJDqcoDekyEMjE8INqIh5GVSoZwH0hSPz9lE%3D&amp;reserved=0
Author of Astro-Physics V2 ASCOM Driver: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;data=02%7C01%7C%7Cfd6b7446b6dc43767ff008d8623e4d81%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C637367367004625483&amp;sdata=o5MMFwdXea6TScC7O0BQ3kwCw7E8tL17gFCDPSaO3oc%3D&amp;reserved=0


> -----Original Message-----
> From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of Bill Long
> Sent: Saturday, September 26, 2020 9:48 AM
> To: Ray Gralak; main@ap-gto.groups.io
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> Voyager uses ASTAP natively and it works like a champ. APPM doesn't solve repetitively enough for me to be
> concerned about it.
>
> ________________________________
>
> From: main@ap-gto.groups.io <main@ap-gto.groups.io> on behalf of Ray Gralak <groups3@...>
> Sent: Saturday, September 26, 2020 9:26 AM
> To: main@ap-gto.groups.io <main@ap-gto.groups.io>
> Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
>
> >  It could be as simple as the fact that APPM is doing a large number of plate solves in a short period of time.
>
> I hope that's not true because it might make ASTAP a poor choice for plate solving.
>
> -Ray Gralak
> Author of PEMPro
> Author of APCC (Astro-Physics Command Center):
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0>
> Author of Astro-Physics V2 ASCOM Driver:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> p;reserved=0
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> mp;reserved=0>
>
>
> > -----Original Message-----
> > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf Of W Hilmo
> > Sent: Saturday, September 26, 2020 8:50 AM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > I agree.
> >
> > I suspect that it's an ASTAP problem, but something that APPM is doing is exposing it.  It could be as simple as
> the
> > fact that APPM is doing a large number of plate solves in a short period of time.  As I mentioned, I've not had time
> > to do any investigation at all yet.
> >
> > -----Original Message-----
> > From: main@ap-gto.groups.io <main@ap-gto.groups.io> On Behalf Of Ray Gralak
> > Sent: Friday, September 25, 2020 6:52 PM
> > To: main@ap-gto.groups.io
> > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> >
> > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > probably the same issue described in the first post of this thread.
> >
> > APPM doesn't know which plate solver is in use when SGPro is used for plate solving. APPM operates the same
> > way for all SGPro plate solvers because APPM uses the SGPro API for plate solving. Since PlateSolve2 doesn't
> > seem to show the same problem, it seems likely that the problem is with how SGPro handles ASTAP.
> >
> > -Ray Gralak
> > Author of PEMPro
> > Author of APCC (Astro-Physics Command Center):
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0 <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.astro-
> physics.com%2Fapcc-
> pro&amp;data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa
> %7C1%7C0%7C637367343966191971&amp;sdata=L5NWYJiNctTmuNFXvB37zZINb6CJ57eCgg7MyuWklfw%3D&
> amp;reserved=0>
> > Author of Astro-Physics V2 ASCOM Driver:
> https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;d
> ata=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0
> %7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&am
> p;reserved=0
> <https://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.siriusimaging.com%2Fapdriver&amp;
> data=02%7C01%7C%7C5d031ac0f6f64c67c2a908d86238f03c%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C
> 0%7C637367343966191971&amp;sdata=L0AH7Z1UH%2FJv8TKH4hHT4xKWMZHMWDSKLJQbgVhwQsg%3D&a
> mp;reserved=0>
> >
> > > -----Original Message-----
> > > From: main@ap-gto.groups.io [mailto:main@ap-gto.groups.io] On Behalf
> > > Of W Hilmo
> > > Sent: Friday, September 25, 2020 9:29 AM
> > > To: main@ap-gto.groups.io
> > > Subject: Re: [ap-gto] #APCC APCC/APPM blocking issue with AP1100GTOAE
> > >
> > > I switched to ASTAP for my plate solves with SGP and am seeing what is
> > > probably the same issue described in the first post of this thread.
> > >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
>
>
>
>
>
>
>
>
>






6241 - 6260 of 79689