Re: Re(Jim): CCDCamera.GuiderCalibrate with AO7


Sep 19, 2006

 


----------------------------

#26091 Sep 19, 2006

Hi

Is there a possibility to program the guider calibration settings via

a script (to be done via ACP).



Background: Utilizing a rotator it is quite time consuming to perform

a "Calibrate Drive" for each new angle. Especially as the result is

quite predictable and can be replaced by a coordinate transformation

from Cartesian to Polar, add the angle and transform it back to

Cartesian operation.



Thus it would be very convenient to have some interfaces addressable

via scripts.



Does anyone have a hint?



/Andreas



----------------------------

#26098 Sep 19, 2006

John,

I thought that there are two different guiding algorithms with Maxim,

one for the AO7 guider and another one for the non AO7s. I'll try (as

soon as the clouds...) if the angle works also with the AO7, because

the manual does not explicitly emphasize that "CCDCamera.GuiderAngle

[= Double]" is utilized by the AO7.



It would be better than assumed as I could drop the coordination

transformation.



Andreas



--- In MaxImDL@yahoogroups.com, "John Winfield" winfij@...> wrote:

>

> You can easily get/set the guider angle via the automation interface:

>

> CCDCamera.GuiderAngle [= Double]

>

> So if you can somehow get the rotator angle you can compute the delta

> and update the guider angle via a script.

>

> John

>

>

> --- In MaxImDL@yahoogroups.com, "quaxah" quaxah@> wrote:

> >

> > Hi

> > Is there a possibility to program the guider calibration settings via

> > a script (to be done via ACP).

> >

> > Background: Utilizing a rotator it is quite time consuming to perform

> > a "Calibrate Drive" for each new angle. Especially as the result is

> > quite predictable and can be replaced by a coordinate transformation

> > from Cartesian to Polar, add the angle and transform it back to

> > Cartesian operation.

> >

> > Thus it would be very convenient to have some interfaces addressable

> > via scripts.

> >

> > Does anyone have a hint?

> >

> > /Andreas

> >

>



----------------------------

#26102 Sep 19, 2006

John/Andreas,



When ACP added rotator support a year or so ago (circa MaxIm 4.1x),

it was determined that the camera angle calculated when calibrating

the guider and/or updated when the camera angle field was changed

manually DOES NOT affect the AO7 bump calibration. Therefore, the

AO7 bump calibration DOES need to be done when using an AO7 and the

camera is rotated.



Having said all that, ACP understands this MaxIm behavior and

automatically does the bump calibration if using an AO7 and the

camera angle changes. No manual intervention is required.



To the best of my knowledge, this behavior in MaxIm hasn't changed

with 4.5x.



Jim McMillan

--- In MaxImDL@yahoogroups.com, "quaxah" quaxah@...> wrote:

>

> John,

> I thought that there are two different guiding algorithms with

Maxim,

> one for the AO7 guider and another one for the non AO7s. I'll try

(as

> soon as the clouds...) if the angle works also with the AO7,

because

> the manual does not explicitly emphasize

that "CCDCamera.GuiderAngle

> [= Double]" is utilized by the AO7.

>

> It would be better than assumed as I could drop the coordination

> transformation.

>

> Andreas

>

>

> --- In MaxImDL@yahoogroups.com, "John Winfield" winfij@> wrote:

> >

> > You can easily get/set the guider angle via the automation

interface:

> >

> > CCDCamera.GuiderAngle [= Double]

> >

> > So if you can somehow get the rotator angle you can compute the

delta

> > and update the guider angle via a script.

> >

> > John

> >

> >

> > --- In MaxImDL@yahoogroups.com, "quaxah" quaxah@> wrote:

> > >

> > > Hi

> > > Is there a possibility to program the guider calibration

settings via

> > > a script (to be done via ACP).

> > >

> > > Background: Utilizing a rotator it is quite time consuming to

perform

> > > a "Calibrate Drive" for each new angle. Especially as the

result is

> > > quite predictable and can be replaced by a coordinate

transformation

> > > from Cartesian to Polar, add the angle and transform it back to

> > > Cartesian operation.

> > >

> > > Thus it would be very convenient to have some interfaces

addressable

> > > via scripts.

> > >

> > > Does anyone have a hint?

> > >

> > > /Andreas

> > >

> >

>



----------------------------

#26118 Sep 20, 2006

John,



I tried it, it works if the AO7 is utilized as a guidercamera without

its tip/tilt possibilities (of course not really good way of

implementing an AO7). If the AO7 is started normally the

"CCDCamera.GuiderAngle" is not in the correction chain, is it?



Any further hints?



Andreas

--- In MaxImDL@yahoogroups.com, "quaxah" quaxah@...> wrote:

>

> John,

> I thought that there are two different guiding algorithms with Maxim,

> one for the AO7 guider and another one for the non AO7s. I'll try (as

> soon as the clouds...) if the angle works also with the AO7, because

> the manual does not explicitly emphasize that "CCDCamera.GuiderAngle

> [= Double]" is utilized by the AO7.

>

> It would be better than assumed as I could drop the coordination

> transformation.

>

> Andreas

>

>

> --- In MaxImDL@yahoogroups.com, "John Winfield" winfij@> wrote:

> >

> > You can easily get/set the guider angle via the automation interface:

> >

> > CCDCamera.GuiderAngle [= Double]

> >

> > So if you can somehow get the rotator angle you can compute the delta

> > and update the guider angle via a script.

> >

> > John

> >

> >

> > --- In MaxImDL@yahoogroups.com, "quaxah" quaxah@> wrote:

> > >

> > > Hi

> > > Is there a possibility to program the guider calibration

settings via

> > > a script (to be done via ACP).

> > >

> > > Background: Utilizing a rotator it is quite time consuming to

perform

> > > a "Calibrate Drive" for each new angle. Especially as the result is

> > > quite predictable and can be replaced by a coordinate transformation

> > > from Cartesian to Polar, add the angle and transform it back to

> > > Cartesian operation.

> > >

> > > Thus it would be very convenient to have some interfaces addressable

> > > via scripts.

> > >

> > > Does anyone have a hint?

> > >

> > > /Andreas

> > >

> >

>







----------------------------

#26119 Sep 20, 2006

Jim



I know that no manual intervention is required and the automatic

calibration works very well.



Today I tried John's suggestion but it doesn't work if the AO7 shall

be used.



The issue is that I'd like to save some time whilst scripting, because

the procedure is, that for every new target of the ACP plan a

calibration is done, than pinpoint solves the image, calculates the

delta and slews/rotates to centre the image. Thereafter another

calibration is performed and if the object crosses the meridian the

same sequence is to perform.

Yes, it can be done this way or one could perform one calibration and

do the other three with a little bit of mathematics in a script.

That would be much faster as one calibration does take some 50 seconds.

I would be happy if the AO7-Guider could get the same script

interfaces as currently available for the 'normal' guiders. As John

emphasized a CCDCamera.GuiderAngle, that works with an AO7 e.g.

CCDCamera.AO7GuiderAngle, would do.



Doug, could you imagine to include such an interface? If I understand

the principles of manual setting correctly, a

CCDCamera.AO7GuiderDeclination would be necessary too.



Regards,

Andreas





--- In MaxImDL@yahoogroups.com, "mcmillanjr4221" valueware@...> wrote:

>

> John/Andreas,

>

> When ACP added rotator support a year or so ago (circa MaxIm 4.1x),

> it was determined that the camera angle calculated when calibrating

> the guider and/or updated when the camera angle field was changed

> manually DOES NOT affect the AO7 bump calibration. Therefore, the

> AO7 bump calibration DOES need to be done when using an AO7 and the

> camera is rotated.

>

> Having said all that, ACP understands this MaxIm behavior and

> automatically does the bump calibration if using an AO7 and the

> camera angle changes. No manual intervention is required.

>

> To the best of my knowledge, this behavior in MaxIm hasn't changed

> with 4.5x.

>

> Jim McMillan

>

> --- In MaxImDL@yahoogroups.com, "quaxah" quaxah@> wrote:

> >

> > John,

> > I thought that there are two different guiding algorithms with

> Maxim,

> > one for the AO7 guider and another one for the non AO7s. I'll try

> (as

> > soon as the clouds...) if the angle works also with the AO7,

> because

> > the manual does not explicitly emphasize

> that "CCDCamera.GuiderAngle

> > [= Double]" is utilized by the AO7.

> >

> > It would be better than assumed as I could drop the coordination

> > transformation.

> >

> > Andreas

> >

> >

> > --- In MaxImDL@yahoogroups.com, "John Winfield" winfij@> wrote:

> > >

> > > You can easily get/set the guider angle via the automation

> interface:

> > >

> > > CCDCamera.GuiderAngle [= Double]

> > >

> > > So if you can somehow get the rotator angle you can compute the

> delta

> > > and update the guider angle via a script.

> > >

> > > John

> > >

> > >

> > > --- In MaxImDL@yahoogroups.com, "quaxah" quaxah@> wrote:

> > > >

> > > > Hi

> > > > Is there a possibility to program the guider calibration

> settings via

> > > > a script (to be done via ACP).

> > > >

> > > > Background: Utilizing a rotator it is quite time consuming to

> perform

> > > > a "Calibrate Drive" for each new angle. Especially as the

> result is

> > > > quite predictable and can be replaced by a coordinate

> transformation

> > > > from Cartesian to Polar, add the angle and transform it back to

> > > > Cartesian operation.

> > > >

> > > > Thus it would be very convenient to have some interfaces

> addressable

> > > > via scripts.

> > > >

> > > > Does anyone have a hint?

> > > >

> > > > /Andreas

> > > >

> > >

> >

>



----------------------------

#26120 Sep 20, 2006

Doug/Andreas,



Amplifying what you say, Andreas, my suggestion is for MaxIm to

determine the guider angle as part of the AO7 bump calibration (it

should be the same math that's already there as part of the guider

calibration routine). Then, when the camera angle is updated (via

ACP in this case), MaxIm could automatically do the math to update

the AO7 bump calibration in the same way as it does it for regular

guiding.



In other words, since the AO7 uses the regular scripting commands

already, don't introduce another variable specifically for the AO7,

just use the existing one (CCD.GuiderAngle), and extend its

functionality to adjust the AO7 bump calibration whenever it changes.



Jim McMillan

--- In MaxImDL@yahoogroups.com, "quaxah" quaxah@...> wrote:

>

> Jim

>

> I know that no manual intervention is required and the automatic

> calibration works very well.

>

> Today I tried John's suggestion but it doesn't work if the AO7

shall

> be used.

>

> The issue is that I'd like to save some time whilst scripting,

because

> the procedure is, that for every new target of the ACP plan a

> calibration is done, than pinpoint solves the image, calculates the

> delta and slews/rotates to centre the image. Thereafter another

> calibration is performed and if the object crosses the meridian the

> same sequence is to perform.

> Yes, it can be done this way or one could perform one calibration

and

> do the other three with a little bit of mathematics in a script.

> That would be much faster as one calibration does take some 50

seconds.

> I would be happy if the AO7-Guider could get the same script

> interfaces as currently available for the 'normal' guiders. As John

> emphasized a CCDCamera.GuiderAngle, that works with an AO7 e.g.

> CCDCamera.AO7GuiderAngle, would do.

>

> Doug, could you imagine to include such an interface? If I

understand

> the principles of manual setting correctly, a

> CCDCamera.AO7GuiderDeclination would be necessary too.

>

> Regards,

> Andreas

>

>

>

> --- In MaxImDL@yahoogroups.com, "mcmillanjr4221" valueware@>

wrote:

> >

> > John/Andreas,

> >

> > When ACP added rotator support a year or so ago (circa MaxIm

4.1x),

> > it was determined that the camera angle calculated when

calibrating

> > the guider and/or updated when the camera angle field was

changed

> > manually DOES NOT affect the AO7 bump calibration. Therefore,

the

> > AO7 bump calibration DOES need to be done when using an AO7 and

the

> > camera is rotated.

> >

> > Having said all that, ACP understands this MaxIm behavior and

> > automatically does the bump calibration if using an AO7 and the

> > camera angle changes. No manual intervention is required.

> >

> > To the best of my knowledge, this behavior in MaxIm hasn't

changed

> > with 4.5x.

> >

> > Jim McMillan

> >

> > --- In MaxImDL@yahoogroups.com, "quaxah" quaxah@> wrote:

> > >

> > > John,

> > > I thought that there are two different guiding algorithms with

> > Maxim,

> > > one for the AO7 guider and another one for the non AO7s. I'll

try

> > (as

> > > soon as the clouds...) if the angle works also with the AO7,

> > because

> > > the manual does not explicitly emphasize

> > that "CCDCamera.GuiderAngle

> > > [= Double]" is utilized by the AO7.

> > >

> > > It would be better than assumed as I could drop the

coordination

> > > transformation.

> > >

> > > Andreas

> > >

> > >

> > > --- In MaxImDL@yahoogroups.com, "John Winfield" winfij@>

wrote:

> > > >

> > > > You can easily get/set the guider angle via the automation

> > interface:

> > > >

> > > > CCDCamera.GuiderAngle [= Double]

> > > >

> > > > So if you can somehow get the rotator angle you can compute

the

> > delta

> > > > and update the guider angle via a script.

> > > >

> > > > John

> > > >

> > > >

> > > > --- In MaxImDL@yahoogroups.com, "quaxah" quaxah@> wrote:

> > > > >

> > > > > Hi

> > > > > Is there a possibility to program the guider calibration

> > settings via

> > > > > a script (to be done via ACP).

> > > > >

> > > > > Background: Utilizing a rotator it is quite time consuming

to

> > perform

> > > > > a "Calibrate Drive" for each new angle. Especially as the

> > result is

> > > > > quite predictable and can be replaced by a coordinate

> > transformation

> > > > > from Cartesian to Polar, add the angle and transform it

back to

> > > > > Cartesian operation.

> > > > >

> > > > > Thus it would be very convenient to have some interfaces

> > addressable

> > > > > via scripts.

> > > > >

> > > > > Does anyone have a hint?

> > > > >

> > > > > /Andreas

> > > > >

> > > >

> > >

> >

>







Contact Us
This Site's Privacy Policy
Google's privacy policies

S
e
n
i
o
r
T
u
b
e
.
o
r
g