Markus Wildi replied to the topic 'Dome Sync Gateway not producing timely GOTO commands' in the forum. 2 months ago

Hello Scott and all

I got hold of P.T. Wallace paper about dome slit synchronization
( www.tpointsw.uk/edome.pdf ) and implemented it as a Python
script and as a C library:

github.com/RTS2/rts2/blob/master/scripts/dome_target_az.py
github.com/RTS2/rts2/blob/master/lib/rts2/slitazimuth.c

Wallace's solution has the advantage being simpler and supporting
the cupola center versus HA/Dec axis intersection offset in x,y,z.

I tested it at Obs. Vermes (radius 1.26 meter) and the optical axis
pointed within 1...2 deg to the slit center with dec axis being set
to HA +/- pi/2 ("East", "West").

Before using it, read Wallace's paper and have a look at the
C library version. The script has an option: --test-wallace
which reproduces the values from the paper.

ciao, wildi

example values from the paper:
longitude: 0.00, latitude: 36.18, h: 2.50, dec:37.90
WALLACE : x_m: -35.0, y_m: 370.0, z_m: 1250.0, r: 0.0, p: 0.0, q: 505.0, rdome: 1900.0
WALLACE : lat: 36.182, h: 149.886 arcmin, dec: 37.901, dome az: 50.369/50.3694111 deg, el: 72.052/72.051742 deg
WALLACE_LB: dome az: 50.369/50.3694111 deg

WALLACE : x_m: -35.0 m, y_m: 370.0 m, z_m: 1250.0 m, r: 0.0, p: 0.0, q: 505.0, rdome: 1900.0 m
WALLACE : dome az: 305.595/305.595067 deg, el: 68.824/68.824495 deg
WALLACE_LB: dome az: 305.595/305.595067 deg

Read More...

Markus Wildi replied to the topic 'Dome Sync Gateway not producing timely GOTO commands' in the forum. 5 months ago

Hello Scott

it took me a while to get Obs. Vermes up and running. I checked the dome slit / mount synchronization and it worked reasonable.

regards, ciao, wildi

Read More...

Markus Wildi replied to the topic 'Dome Sync Gateway not producing timely GOTO commands' in the forum. 7 months ago

Hello Scott and Ferran

I have not seen RTS2 on OSX (and I would not try it, at least not for this purpose). There is an easier way: use Docker which provides an Ubuntu container on your OSX computer. But this is a several hours task.

My idea is, that Ferran produces a similar table with his code and depending on the results when know better where to dig deeper.
I read through my original notes and found that I was checking my code against Toshimi Taki's "reference implementation" saying it is identical (see www.geocities.jp/toshimi_taki/matrix/matrix.htm paragraph Applications and my similar plot: azug.minpet.unibas.ch/wikiobsvermes/images/9/97/DomeSync.jpg )

ciao, wildi

Read More...

Markus Wildi replied to the topic 'Dome Sync Gateway not producing timely GOTO commands' in the forum. 7 months ago

Hello Ferran and Scott

Jasem informed me about your issue. I quickly wrote a Python script which calls RTS2's slitazimuth.c,
my original implementation of Toshimi Taki's solution. It is available at

github.com/RTS2/rts2/blob/master/scripts/dome_target_az.py

In order to use it you must clone RTS2 and compile it (installation is not required)
and in do

cd ~/rts2/lib/rts2
gcc -c -Werror -fpic slitazimuth.c -I../../include/ && gcc -shared -o libslitazimuth.so slitazimuth.o -lnova

ciao, wildi


wildi@dc11:~/rts2/scripts$ ./dome_target_az.py
AZ coordinate systen: S=0, W=90 deg
xd: -0.0684 m, zd: -0.1934 m, rdec: 0.338 m, rdome: 1.265 m
telescope alt: 0.000, az: 0.000, dome az: 15.688 deg
telescope alt: 10.000, az: 0.000, dome az: 15.505 deg
telescope alt: 20.000, az: 0.000, dome az: 15.859 deg
telescope alt: 30.000, az: 0.000, dome az: 16.852 deg
telescope alt: 40.000, az: 0.000, dome az: 18.724 deg
telescope alt: 50.000, az: 0.000, dome az: 21.986 deg
telescope alt: 60.000, az: 0.000, dome az: 27.781 deg
telescope alt: 70.000, az: 0.000, dome az: 38.917 deg
telescope alt: 80.000, az: 0.000, dome az: 62.186 deg
telescope alt: 0.000, az: 90.000, dome az: 108.680 deg
telescope alt: 10.000, az: 90.000, dome az: 108.213 deg
telescope alt: 20.000, az: 90.000, dome az: 108.252 deg
telescope alt: 30.000, az: 90.000, dome az: 108.814 deg
telescope alt: 40.000, az: 90.000, dome az: 109.964 deg
telescope alt: 50.000, az: 90.000, dome az: 111.790 deg
telescope alt: 60.000, az: 90.000, dome az: 114.285 deg
telescope alt: 70.000, az: 90.000, dome az: 116.795 deg
telescope alt: 80.000, az: 90.000, dome az: 115.961 deg
telescope alt: 0.000, az: 180.000, dome az: 195.688 deg
telescope alt: 10.000, az: 180.000, dome az: 195.500 deg
telescope alt: 20.000, az: 180.000, dome az: 195.741 deg
telescope alt: 30.000, az: 180.000, dome az: 196.489 deg
telescope alt: 40.000, az: 180.000, dome az: 197.915 deg
telescope alt: 50.000, az: 180.000, dome az: 200.364 deg
telescope alt: 60.000, az: 180.000, dome az: 204.563 deg
telescope alt: 70.000, az: 180.000, dome az: 212.184 deg
telescope alt: 80.000, az: 180.000, dome az: 132.560 deg
telescope alt: 0.000, az: 270.000, dome az: 281.824 deg
telescope alt: 10.000, az: 270.000, dome az: 281.814 deg
telescope alt: 20.000, az: 270.000, dome az: 282.165 deg
telescope alt: 30.000, az: 270.000, dome az: 282.975 deg
telescope alt: 40.000, az: 270.000, dome az: 284.456 deg
telescope alt: 50.000, az: 270.000, dome az: 287.077 deg
telescope alt: 60.000, az: 270.000, dome az: 292.066 deg
telescope alt: 70.000, az: 270.000, dome az: 304.223 deg
telescope alt: 80.000, az: 270.000, dome az: 15.060 deg

Read More...

Login



3rd Party

Choose from the numerous 3rd party INDI drivers to suit your needs!

Got Problem?

Check out the FAQ, the forum, and the bug tracking system to resolve any issues you might have!
You can also subscribe to INDI newsletter and development mailing lists to get the latest updates on INDI!