Telescope Control (client-server)

2007-10-09T23:08:26Z

Johannes: /* Useful Stellarium features */

'''Warning: when you abuse stellariums telescope control feature for pointing your telescope to the sun without a proper solar filter, then this is your own fault. Stellarium cannot check if you have your solar filter properly installed or not. So when you ruin your telescope, your eyes, your childrens eyes or whatever, then this is not our fault, but yours.'''

==Introduction==
In this page I describe the telescope control feature that is present in stellarium since version 0.8.1.

===Overview===

Although stellarium is currently (since 0.8.1) able to control any telescope using a suiting external telescope server, up to now there exist only the following telescope server programs:

TelescopeServerDummy: can be used for testing and as a starting point for developing new telescope servers, no telescope is required

TelescopeServerDummy.exe: same for MS Windows

TelescopeServerLx200: used for controlling Meade LX200 or AutoStar telescopes, G11 or compatible

TelescopeServerLx200.exe: same for MS Windows

TelescopeServerNexStar: used for controlling Celestron NexStar telescopes, contributed by Michael Heinz

TelescopeServerNexStar.exe: same for MS Windows

'''ASCOM Support'''

StellariumServer.exe (http://www.geocities.com/scottpinkham/astro): is a program for MS Windows allowing stellarium to control a variety of telescope using the ASCOM drivers (http://ascom-standards.org).

===Architecture===

Actual communication with the telescope is not done by stellarium itself, but by an external program which is called telescope server. Stellarium and the telescope server communicate with each other over TCP/IP. For the TCP communication there is an LGPL library which should make the development of telescope servers easy. This architecture has the following advantages:

1) The stellarium source code does not get bloated by incorporation of dozens of telescope control mechanisms and protocols. Instead the stellarium sourcecode stays maintainable.

2) TCP is available on any platform, so for stellarium there are little or no portability problems.

3) Any developer can easily provide an own telescope server for his own telescope, eigther by using the stellarium telescope library (recommended) or without it. No knowledge about the stellarium programs source code is required.

4) There are no license problems: An external telescope server can, but does not need to be GPL. When building your own telescope server you can link with any library you want: ASCOM, Indy, any proprietary library, whatever.

===Building===

The telescope server programs described above are available from anonymous svn:

svn co https://stellarium.svn.sourceforge.net/svnroot/stellarium/trunk/telescope_server

There is a README file. Just change into the src directory and type 'make' (no autoconf/automake). In order to cross-compile for MS Windows export the environment variable CROSS_GPP and type 'make exe'. I have never tried native MS Windows compilation, but I suppose that any compiler will do. Same for other operating systems. If you have problems, write to the forum. Or write an email to me.

Michael Heinz has provided an XCode project file for Mac, which is included in svn.

===Alternatively: downloading precompiled MS Windows binaries===

I have noticed that MS Windows users often prefer downloading precompiled binaries instead of building by themselves. Therefore I provide Windows binaries:

[http://members.chello.at/johannes.gajdosik/TelescopeServerLx200.exe.gz TelescopeServerLx200.exe.gz]
[http://members.chello.at/johannes.gajdosik/TelescopeServerNexStar.exe.gz TelescopeServerNexStar.exe.gz]
[http://members.chello.at/johannes.gajdosik/TelescopeServerDummy.exe.gz TelescopeServerDummy.exe.gz]

Some people have problems with their browsers: the browser silently unpacks the gziped file. If you suffer from such a problem, just rename the downloaded file to TelescopeServerLx200.exe (or similar).

==Usage==

Start stellarium, the telescope server(s) and your telescope(s). The order of starting does not matter. You can also stop and restart stellarium, the telescope server(s) or your telescope(s) at any time.

As soon as the telescope server has sent the telescopes position to stellarium, you will see a crosshair marker indicating the telescopes position, labeled with your telescopes name (config.ini). Note that the crosshair marker might be outside your current field of view. Zoom out and search for the marker, or alternatively use stellariums search feature. When you see the marker, you know that stellarium has successfully connected to the telescope server.

===Run the server===

Navigate to the directory containing the file, and start the telescope server with a command line like

TelescopeServerDummy 10000 or
TelescopeServerDummy.exe 10000 or
TelescopeServerLx200 10000 /dev/ttyS0 or
TelescopeServerLx200.exe 10000 COM1:

depending on your telescope and serial port. In this example I assume you use TCP port 10000, but you can use any free port you want. The telescope servers are capable of serving a huge number of Stellarium programs, so you can share the control of your telescope with other stellarium programs.

In your config.ini write

[astro]
flag_telescopes = true
flag_telescope_name = true
...
[telescopes]
1 = My_first_telescope:TCP:localhost:10000:500000
2 = My_second_telescope:TCP:localhost:10001:500000

Here I have assumed that you have started two different telescope servers on your machine for controlling two different telescopes. When you have just 1 GOTO telescope like me, leave out the last line. If you run the telescope server on a different machine, you must replace 'localhost' with the name of this machine. The value 500000 indicates, that Stellarium will not show the telescopes current position - which is unknown anyway - but instead an interpolated position of 500000 microseconds (=0.5 seconds) ago. If you have a slow telescope controller - like the Meade AutoStar 494 that comes with ETX 70 - you should increase this value to 1200000 or higher, in order to get smooth movement of the telescope marker. 'My_first_telescope' is the name that will be shown in stellarium next to the telescope marker. '1' is the keyboard shortcut: <Ctlr><1> will make the telescope point to the currently selected object (GOTO). Currently up to 10 telescopes can be controlled using keys 0,1,...,9.

===Gathering debug information===

For debugging in most cases I will need the log of the telescope server. You can produce the logfile eigther by redirecting stdout into a file, or by supplying the logfiles name as an additional command line parameter upon startup of the telescope server:

TelescopeServerLx200 10000 /dev/ttyS0 name-of-logfile.txt
TelescopeServerLx200.exe 10000 COM1: name-of-logfile.txt

Other information useful for me is stellariums stdout and config.ini. The windows version stellarium.exe already redirects stdout into a file named stdout.txt.

===Useful Stellarium features===

in your config.ini write

[astro]
flag_light_travel_time = true
...
[gui]
flag_show_flip_buttons = true

Accounting for light travel time is a must when you observe planetary satellites.
You will also want to flip the stellarium image horizontally and/or vertically in order to match what you see in your eyepiece. You can do this with the flip buttons and/or the following keyboard shortcuts:

<Ctrl><Shift><h>: toggle horizontal image flip
<Ctrl><Shift><v>: toggle vertical image flip

Since version 0.9.1: For displaying concentric circles around the telescope marker indicating the FOV of your oculars write for example:

[telescopes]
1_ocular_0 = 0.5
1_ocular_1 = 0.1
...

This will define 2 oculars with FOV=0.5 and 0.1 degrees for telescope 1. You can specify up to 10 oculars for each telescope.

When you have problems or when you are satisfied, write to the forum.

Yours,
--[[User:Johannes|Johannes]] 14:48, 18 June 2006 (PDT)

==Telescope Compatibility List==
*[[Telescope Compatibility]]

Telescope Control (client-server)

2007-10-09T22:59:51Z

Johannes: /* Useful Stellarium features */

'''Warning: when you abuse stellariums telescope control feature for pointing your telescope to the sun without a proper solar filter, then this is your own fault. Stellarium cannot check if you have your solar filter properly installed or not. So when you ruin your telescope, your eyes, your childrens eyes or whatever, then this is not our fault, but yours.'''

==Introduction==
In this page I describe the telescope control feature that is present in stellarium since version 0.8.1.

===Overview===

Although stellarium is currently (since 0.8.1) able to control any telescope using a suiting external telescope server, up to now there exist only the following telescope server programs:

TelescopeServerDummy: can be used for testing and as a starting point for developing new telescope servers, no telescope is required

TelescopeServerDummy.exe: same for MS Windows

TelescopeServerLx200: used for controlling Meade LX200 or AutoStar telescopes, G11 or compatible

TelescopeServerLx200.exe: same for MS Windows

TelescopeServerNexStar: used for controlling Celestron NexStar telescopes, contributed by Michael Heinz

TelescopeServerNexStar.exe: same for MS Windows

'''ASCOM Support'''

StellariumServer.exe (http://www.geocities.com/scottpinkham/astro): is a program for MS Windows allowing stellarium to control a variety of telescope using the ASCOM drivers (http://ascom-standards.org).

===Architecture===

Actual communication with the telescope is not done by stellarium itself, but by an external program which is called telescope server. Stellarium and the telescope server communicate with each other over TCP/IP. For the TCP communication there is an LGPL library which should make the development of telescope servers easy. This architecture has the following advantages:

1) The stellarium source code does not get bloated by incorporation of dozens of telescope control mechanisms and protocols. Instead the stellarium sourcecode stays maintainable.

2) TCP is available on any platform, so for stellarium there are little or no portability problems.

3) Any developer can easily provide an own telescope server for his own telescope, eigther by using the stellarium telescope library (recommended) or without it. No knowledge about the stellarium programs source code is required.

4) There are no license problems: An external telescope server can, but does not need to be GPL. When building your own telescope server you can link with any library you want: ASCOM, Indy, any proprietary library, whatever.

===Building===

The telescope server programs described above are available from anonymous svn:

svn co https://stellarium.svn.sourceforge.net/svnroot/stellarium/trunk/telescope_server

There is a README file. Just change into the src directory and type 'make' (no autoconf/automake). In order to cross-compile for MS Windows export the environment variable CROSS_GPP and type 'make exe'. I have never tried native MS Windows compilation, but I suppose that any compiler will do. Same for other operating systems. If you have problems, write to the forum. Or write an email to me.

Michael Heinz has provided an XCode project file for Mac, which is included in svn.

===Alternatively: downloading precompiled MS Windows binaries===

I have noticed that MS Windows users often prefer downloading precompiled binaries instead of building by themselves. Therefore I provide Windows binaries:

[http://members.chello.at/johannes.gajdosik/TelescopeServerLx200.exe.gz TelescopeServerLx200.exe.gz]
[http://members.chello.at/johannes.gajdosik/TelescopeServerNexStar.exe.gz TelescopeServerNexStar.exe.gz]
[http://members.chello.at/johannes.gajdosik/TelescopeServerDummy.exe.gz TelescopeServerDummy.exe.gz]

Some people have problems with their browsers: the browser silently unpacks the gziped file. If you suffer from such a problem, just rename the downloaded file to TelescopeServerLx200.exe (or similar).

==Usage==

Start stellarium, the telescope server(s) and your telescope(s). The order of starting does not matter. You can also stop and restart stellarium, the telescope server(s) or your telescope(s) at any time.

As soon as the telescope server has sent the telescopes position to stellarium, you will see a crosshair marker indicating the telescopes position, labeled with your telescopes name (config.ini). Note that the crosshair marker might be outside your current field of view. Zoom out and search for the marker, or alternatively use stellariums search feature. When you see the marker, you know that stellarium has successfully connected to the telescope server.

===Run the server===

Navigate to the directory containing the file, and start the telescope server with a command line like

TelescopeServerDummy 10000 or
TelescopeServerDummy.exe 10000 or
TelescopeServerLx200 10000 /dev/ttyS0 or
TelescopeServerLx200.exe 10000 COM1:

depending on your telescope and serial port. In this example I assume you use TCP port 10000, but you can use any free port you want. The telescope servers are capable of serving a huge number of Stellarium programs, so you can share the control of your telescope with other stellarium programs.

In your config.ini write

[astro]
flag_telescopes = true
flag_telescope_name = true
...
[telescopes]
1 = My_first_telescope:TCP:localhost:10000:500000
2 = My_second_telescope:TCP:localhost:10001:500000

Here I have assumed that you have started two different telescope servers on your machine for controlling two different telescopes. When you have just 1 GOTO telescope like me, leave out the last line. If you run the telescope server on a different machine, you must replace 'localhost' with the name of this machine. The value 500000 indicates, that Stellarium will not show the telescopes current position - which is unknown anyway - but instead an interpolated position of 500000 microseconds (=0.5 seconds) ago. If you have a slow telescope controller - like the Meade AutoStar 494 that comes with ETX 70 - you should increase this value to 1200000 or higher, in order to get smooth movement of the telescope marker. 'My_first_telescope' is the name that will be shown in stellarium next to the telescope marker. '1' is the keyboard shortcut: <Ctlr><1> will make the telescope point to the currently selected object (GOTO). Currently up to 10 telescopes can be controlled using keys 0,1,...,9.

===Gathering debug information===

For debugging in most cases I will need the log of the telescope server. You can produce the logfile eigther by redirecting stdout into a file, or by supplying the logfiles name as an additional command line parameter upon startup of the telescope server:

TelescopeServerLx200 10000 /dev/ttyS0 name-of-logfile.txt
TelescopeServerLx200.exe 10000 COM1: name-of-logfile.txt

Other information useful for me is stellariums stdout and config.ini. The windows version stellarium.exe already redirects stdout into a file named stdout.txt.

===Useful Stellarium features===

in your config.ini write

[astro]
flag_light_travel_time = true
...
[gui]
flag_show_flip_buttons = true

Accounting for light travel time is a must when you observe planetary satellites.
You will also want to flip the stellarium image horizontally and/or vertically in order to match what you see in your eyepiece. You can do this with the flip buttons and/or the following keyboard shortcuts:

<Ctrl><Shift><h>: toggle horizontal image flip
<Ctrl><Shift><v>: toggle vertical image flip

Since version 0.9.2: For displaying concentric circles around the telescope marker indicating the FOV of your oculars write for example:

[telescopes]
1_ocular_0 = 0.5
1_ocular_1 = 0.1
...

This will define 2 oculars with FOV=0.5 and 0.1 degrees for telescope 1. You can specify up to 10 oculars for each telescope.

When you have problems or when you are satisfied, write to the forum.

Yours,
--[[User:Johannes|Johannes]] 14:48, 18 June 2006 (PDT)

==Telescope Compatibility List==
*[[Telescope Compatibility]]

Star Catalogues

2007-06-07T21:35:23Z

Johannes:

Star Catalogues

2007-06-07T21:33:28Z

Johannes:

Telescope Control (client-server)

2007-06-07T21:13:53Z

Johannes: /* Alternatively: downloading precompiled MS Windows binaries */

'''Warning: when you abuse stellariums telescope control feature for pointing your telescope to the sun without a proper solar filter, then this is your own fault. Stellarium cannot check if you have your solar filter properly installed or not. So when you ruin your telescope, your eyes, your childrens eyes or whatever, then this is not our fault, but yours.'''

==Introduction==
In this page I describe the telescope control feature that is present in stellarium since version 0.8.1.

===Overview===

Although stellarium is currently (since 0.8.1) able to control any telescope using a suiting external telescope server, up to now there exist only the following telescope server programs:

TelescopeServerDummy: can be used for testing and as a starting point for developing new telescope servers, no telescope is required

TelescopeServerDummy.exe: same for MS Windows

TelescopeServerLx200: used for controlling Meade LX200 or AutoStar telescopes, G11 or compatible

TelescopeServerLx200.exe: same for MS Windows

TelescopeServerNexStar: used for controlling Celestron NexStar telescopes, contributed by Michael Heinz

TelescopeServerNexStar.exe: same for MS Windows

'''ASCOM Support'''

StellariumServer.exe (http://www.geocities.com/scottpinkham/astro): is a program for MS Windows allowing stellarium to control a variety of telescope using the ASCOM drivers (http://ascom-standards.org).

===Architecture===

Actual communication with the telescope is not done by stellarium itself, but by an external program which is called telescope server. Stellarium and the telescope server communicate with each other over TCP/IP. For the TCP communication there is an LGPL library which should make the development of telescope servers easy. This architecture has the following advantages:

1) The stellarium source code does not get bloated by incorporation of dozens of telescope control mechanisms and protocols. Instead the stellarium sourcecode stays maintainable.

2) TCP is available on any platform, so for stellarium there are little or no portability problems.

3) Any developer can easily provide an own telescope server for his own telescope, eigther by using the stellarium telescope library (recommended) or without it. No knowledge about the stellarium programs source code is required.

4) There are no license problems: An external telescope server can, but does not need to be GPL. When building your own telescope server you can link with any library you want: ASCOM, Indy, any proprietary library, whatever.

===Building===

The telescope server programs described above are available from anonymous svn:

svn co https://svn.sourceforge.net/svnroot/stellarium/trunk/telescope_server

There is a README file. Just change into the src directory and type 'make' (no autoconf/automake). In order to cross-compile for MS Windows export the environment variable CROSS_GPP and type 'make exe'. I have never tried native MS Windows compilation, but I suppose that any compiler will do. Same for other operating systems. If you have problems, write to the forum. Or write an email to me.

Michael Heinz has provided an XCode project file for Mac, which is included in svn.

===Alternatively: downloading precompiled MS Windows binaries===

I have noticed that MS Windows users often prefer downloading precompiled binaries instead of building by themselves. Therefore I provide Windows binaries:

[http://members.chello.at/johannes.gajdosik/TelescopeServerLx200.exe.gz TelescopeServerLx200.exe.gz]
[http://members.chello.at/johannes.gajdosik/TelescopeServerNexStar.exe.gz TelescopeServerNexStar.exe.gz]
[http://members.chello.at/johannes.gajdosik/TelescopeServerDummy.exe.gz TelescopeServerDummy.exe.gz]

Some people have problems with their browsers: the browser silently unpacks the gziped file. If you suffer from such a problem, just rename the downloaded file to TelescopeServerLx200.exe (or similar).

==Usage==

Start stellarium, the telescope server(s) and your telescope(s). The order of starting does not matter. You can also stop and restart stellarium, the telescope server(s) or your telescope(s) at any time.

As soon as the telescope server has sent the telescopes position to stellarium, you will see a crosshair marker indicating the telescopes position, labeled with your telescopes name (config.ini). Note that the crosshair marker might be outside your current field of view. Zoom out and search for the marker, or alternatively use stellariums search feature. When you see the marker, you know that stellarium has successfully connected to the telescope server.

===Run the server===

Navigate to the directory containing the file, and start the telescope server with a command line like

TelescopeServerDummy 10000 or
TelescopeServerDummy.exe 10000 or
TelescopeServerLx200 10000 /dev/ttyS0 or
TelescopeServerLx200.exe 10000 COM1:

depending on your telescope and serial port. In this example I assume you use TCP port 10000, but you can use any free port you want. The telescope servers are capable of serving a huge number of Stellarium programs, so you can share the control of your telescope with other stellarium programs.

In your config.ini write

[astro]
flag_telescopes = true
flag_telescope_name = true
...
[telescopes]
1 = My_first_telescope:TCP:localhost:10000:500000
2 = My_second_telescope:TCP:localhost:10001:500000

Here I have assumed that you have started two different telescope servers on your machine for controlling two different telescopes. When you have just 1 GOTO telescope like me, leave out the last line. If you run the telescope server on a different machine, you must replace 'localhost' with the name of this machine. The value 500000 indicates, that Stellarium will not show the telescopes current position - which is unknown anyway - but instead an interpolated position of 500000 microseconds (=0.5 seconds) ago. If you have a slow telescope controller - like the Meade AutoStar 494 that comes with ETX 70 - you should increase this value to 1200000 or higher, in order to get smooth movement of the telescope marker. 'My_first_telescope' is the name that will be shown in stellarium next to the telescope marker. '1' is the keyboard shortcut: <Ctlr><1> will make the telescope point to the currently selected object (GOTO). Currently up to 10 telescopes can be controlled using keys 0,1,...,9.

===Gathering debug information===

For debugging in most cases I will need the log of the telescope server. You can produce the logfile eigther by redirecting stdout into a file, or by supplying the logfiles name as an additional command line parameter upon startup of the telescope server:

TelescopeServerLx200 10000 /dev/ttyS0 name-of-logfile.txt
TelescopeServerLx200.exe 10000 COM1: name-of-logfile.txt

Other information useful for me is stellariums stdout and config.ini. The windows version stellarium.exe already redirects stdout into a file named stdout.txt.

===Useful Stellarium features===

in your config.ini write

[astro]
flag_light_travel_time = true
...
[gui]
flag_show_flip_buttons = true

Accounting for light travel time is a must when you observe planetary satellites.
You will also want to flip the stellarium image horizontally and/or vertically in order to match what you see in your eyepiece. You can do this with the flip buttons and/or the following keyboard shortcuts:

<Ctrl><Shift><h>: toggle horizontal image flip
<Ctrl><Shift><v>: toggle vertical image flip

When you have problems or when you are satisfied, write to the forum.

Yours,
--[[User:Johannes|Johannes]] 14:48, 18 June 2006 (PDT)

==Telescope Compatibility List==
*[[Telescope Compatibility]]

Help with Fortran90

2007-05-14T20:47:19Z

Johannes: /* Summary */

This page is dedicated to conversation and mutual help on creating Neptunian satellite ephemeris using
Le Guyader's and Jerome Berthier's ftp://ftp.imcce.fr/pub/ephem/satel/neptuno/

== First approach: f77 ==
In Config.mk replace FC = xlf with FC = f77 and type 'make'. You will see lots of errors like

isat_d.f: In subroutine `isatd':
isat_d.f:1353:
210 format(8x,' Dernier pas:',d23.16)'
^
Invalid form for FORMAT statement at (^)

In my opinion the reason is that the code is not FORTRAN77 conform. I tried to overcome this problem by fixing the source code, there is an awful lot of wrong format statements. For finding the input files I changed in fs2fd.f:

infile = trim(dir_s)//trim(fil_s)
outfile = trim(dir_d)//trim(fil_d)

into

infile = './data/Nsat-fs.dat'
outfile = './data/Nsat-fd.dat'

Same in ins_d.f:

theofile = './data/Nsat-fd.dat'

Additionally in ins_d.f I had to move the passage

LOGICAL FIRST
DATA FIRST/.TRUE./

after the COMMON block:

COMMON/STCOMX/KM,BARY,PVSUN
LOGICAL FIRST
DATA FIRST/.TRUE./

FORTRAN77 seem not to support variable size arrays, so in isat_d.f I had to replace

dimension tp(np),up(np),cp(3,np),aia(4)

in line 183 with

dimension tp(100000),up(100000),cp(3,100000),aia(4)

The same for lines 2455 and 2456. In line 2408 I removed the definition of w(3,np,0:nd).
After that the source compiled into an executable called 'ilgs_d', which is ought to be the double precision version. The quad precision version would be called 'ilgs_q'. Anyway, the executable failed with the following output:

________________________________________

Fichier ./data/Nsat-fd.dat
________________________________________

open: No such file or directory
apparent state: unit 12 named /DATA/DE403/de403.unx
last format: list io
lately reading direct unformatted external IO
Aborted

== Second approach: f2c ==
Using f2c gives the same results as using f77. I hoped to get more insight from reading the C-code, but I did not. I had big success for the other IMCCE fortran programs with f2c, it helped me a lot in understanding and getting functional executables. But not this time.

== Summary ==
The file ./data/Nsat-fd.dat exists, maybe the error refers to the file /DATA/DE403/de403.unx, which is indeed missing on my system. And I do not know from where to get it. At ftp://ssd.jpl.nasa.gov/pub/eph/planets/bsp/DE403.BSP I found the file for Sparc architecture, for i386 it seems not to be available any more, but it could be created from DE403.BSP.

But before doing further investigation I would like to ask a FORTRAN programmer about this software. My understanding is as follows, please correct me when I am wrong:

1) The software is a numerical integrator for a physical model of the Nepunian system. For as a period as long as the planet positions are provided, the Neptunian satellites position can be computed by numerical integration. Especially dates outside the interval 1800-2050 are no problem, when the DE403 planet positions are replaced by VSOP87 or similar.

2) Therefore it is possible to produce a large table of each satellites position and velocity for a long period, lets say 1500-2500. In fact this is the main goal. When I have this table, I will try frequency analysis techniques in order to create poisson series or similar, that can be included into stellarium.

My problem is that I can speak neigther french nor FORTRAN, so I really do not know what is going on in this software, and I would really appreciate your help. You can contact be by:

- email: johannes (dot) gajdosik (at) gmx (dot) at

- posting into the forum

- writing something in this wiki page

I am sorry for having written: "If you do not mind I would prefer to be contacted by email, please write the words
"stellarium" and "fortran" into the subject line."
This was really a bad idea, because it caused multiple work on the same subject for the community.
So lets stay with this wiki.

Yours,

[[User:Johannes|Johannes]] 14:38, 1 May 2007 (PDT)

Hi! I'm a french programmer, but unfortunately not a fortran programmer, and I'd like to help if I can . I've started to read fortran tutorial and I plan to test lf95 trial as fortran compiler since it's the one used in the linux Config.mk provided in neptuno package but I don't have much free time these days. I'll let know if I succeed in any way, let me know if you have questions.
Blakbear.

Hello Blackbear,
thank you very much for offering help! I first did not see your writing into the wiki, because the "watch" function seems not to work for me. If you get any insight into the code,
or if you can give any answers to 1) or 2) please send me an email, this will be the easiest way of communication.
Johannes

Hi, Johannes. I could build "ilgs3_d" by g77 and execute without error. But I could not investigate that result is correct or is not correct. Shall I report my procedure?(in this page? or e-mail?) I write a part of output(little formatted), instead answer your questions.
( 1) Date: 0.2378496500000000E+07
Nombre maximum d"enregistrements = 22829
Intervalle cherché = 1
Temps initial d"intégration = 0.2378496500000000E+07
Intervalle d"intégration = 0.0000000000000000E+00
Pas d"intégration = 0.0000000000000000E+00
Temps final d"intégration = 0.2378496500000000E+07
___________________________________________________
Résultats
----------
Triton
( 1) Date: 0.2378496500000000E+07
v0(1,1,0) =-0.2019388268736855E-04
v0(2,1,0) = 0.1722904160856275E-02
v0(3,1,0) = 0.1629414715885055E-02
v0(1,1,1) = 0.2533936570868142E-02
v0(2,1,1) =-0.4058902541155617E-04
v0(3,1,1) = 0.7430677191550270E-04
By the way, when create de403.unx, why did not you convert from unxpXXXX.403 or ascpXXXX.403?--[[User:Sigma|Sigma]] 06:10, 9 May 2007 (PDT)

Same here, I've succeeded in compiling ilgs3_d with lf95 but I can't get a result yet, so Sigma seems more advanced. So far I can't validate my email so I can't use it for the time being, but feel free to ask if you need french to english translation.
Blakbear.

:I uploaded diff files: [http://www.h5.dion.ne.jp/~sigma/stellarium/neptune/ins3_d.f.diff for ins3_d.f],[http://www.h5.dion.ne.jp/~sigma/stellarium/neptune/ins8_d.f.diff for ins8_d.f],[http://www.h5.dion.ne.jp/~sigma/stellarium/neptune/isat8_d.f.diff for isat8_d.f]. Sorry, I could not upload de403.unx, because it was big size for my space(about 9MB gziped). And ilgs8_d did not execute. Probably, there may be a hint for 8 satellites code in LISETMOI and README. Please check them. I'm weak in English, additionaly can not read French. orz--[[User:Sigma|Sigma]] 20:41, 10 May 2007 (PDT)

Hi! I've succeeded in compiling and running both ilgs3_d and ilgs8_d, getting some results and some problems when testing with later dates but at least it works for initial date it seems.<br />
All the modifications I've done for ilgs8_d to work have already been pointed out by Johannes : bad formatting with ' where there shouldn't be and bad location, missing the . to access current dir. I've used unxp1950.403 found on jpl ftp ftp://ssd.jpl.nasa.gov/pub/eph/export/unix/ renamed in de403.unx.<br />
I'm going to make an archive with all the files I've used and make it available tonight, so anyone will be able to test it.

--[[User:Blakbear|Blakbear]] 13:56, 11 May 2007 (PDT)

== Results ==
Thank you all so much for your help! In addition to the information in the wiki I got also emails describing how to create de403.unx. Indeed you had more success then I running the program. Now remains only the problem of creating ephemeris data over a reasonably long timespan, lets say 1500-2500. The file Nsat-fd.dat provides initial values not for this whole period, but I doubt that this is needed. Instead isat_d and ilgs_d should contain a numerical model and an integrator suitable for creating data for an arbitrary period, provided there are the planet positions. This leads to the question:

Can anybody of you understand the contents of isat_d.f and ilgs_d.f? where is the integrator, where is the numerical model, and from where are the planet positions needed for planetary perturbation? This is the part, where French language skills might be helpful. For I cannot understand the comments, function and variable names, for me these are just meaningless accumulations of letters.

Thanks again,
--[[User:Johannes|Johannes]] 09:44, 14 May 2007 (PDT)

Help with Fortran90

2007-05-14T16:44:22Z

Johannes:

This page is dedicated to conversation and mutual help on creating Neptunian satellite ephemeris using
Le Guyader's and Jerome Berthier's ftp://ftp.imcce.fr/pub/ephem/satel/neptuno/

== First approach: f77 ==
In Config.mk replace FC = xlf with FC = f77 and type 'make'. You will see lots of errors like

isat_d.f: In subroutine `isatd':
isat_d.f:1353:
210 format(8x,' Dernier pas:',d23.16)'
^
Invalid form for FORMAT statement at (^)

In my opinion the reason is that the code is not FORTRAN77 conform. I tried to overcome this problem by fixing the source code, there is an awful lot of wrong format statements. For finding the input files I changed in fs2fd.f:

infile = trim(dir_s)//trim(fil_s)
outfile = trim(dir_d)//trim(fil_d)

into

infile = './data/Nsat-fs.dat'
outfile = './data/Nsat-fd.dat'

Same in ins_d.f:

theofile = './data/Nsat-fd.dat'

Additionally in ins_d.f I had to move the passage

LOGICAL FIRST
DATA FIRST/.TRUE./

after the COMMON block:

COMMON/STCOMX/KM,BARY,PVSUN
LOGICAL FIRST
DATA FIRST/.TRUE./

FORTRAN77 seem not to support variable size arrays, so in isat_d.f I had to replace

dimension tp(np),up(np),cp(3,np),aia(4)

in line 183 with

dimension tp(100000),up(100000),cp(3,100000),aia(4)

The same for lines 2455 and 2456. In line 2408 I removed the definition of w(3,np,0:nd).
After that the source compiled into an executable called 'ilgs_d', which is ought to be the double precision version. The quad precision version would be called 'ilgs_q'. Anyway, the executable failed with the following output:

________________________________________

Fichier ./data/Nsat-fd.dat
________________________________________

open: No such file or directory
apparent state: unit 12 named /DATA/DE403/de403.unx
last format: list io
lately reading direct unformatted external IO
Aborted

== Second approach: f2c ==
Using f2c gives the same results as using f77. I hoped to get more insight from reading the C-code, but I did not. I had big success for the other IMCCE fortran programs with f2c, it helped me a lot in understanding and getting functional executables. But not this time.

== Summary ==
The file ./data/Nsat-fd.dat exists, maybe the error refers to the file /DATA/DE403/de403.unx, which is indeed missing on my system. And I do not know from where to get it. At ftp://ssd.jpl.nasa.gov/pub/eph/planets/bsp/DE403.BSP I found the file for Sparc architecture, for i386 it seems not to be available any more, but it could be created from DE403.BSP.

But before doing further investigation I would like to ask a FORTRAN programmer about this software. My understanding is as follows, please correct me when I am wrong:

1) The software is a numerical integrator for a physical model of the Nepunian system. For as a period as long as the planet positions are provided, the Neptunian satellites position can be computed by numerical integration. Especially dates outside the interval 1800-2050 are no problem, when the DE403 planet positions are replaced by VSOP87 or similar.

2) Therefore it is possible to produce a large table of each satellites position and velocity for a long period, lets say 1500-2500. In fact this is the main goal. When I have this table, I will try frequency analysis techniques in order to create poisson series or similar, that can be included into stellarium.

My problem is that I can speak neigther french nor FORTRAN, so I really do not know what is going on in this software, and I would really appreciate your help. You can contact be by:

- email: johannes (dot) gajdosik (at) gmx (dot) at

- posting into the forum

- writing something in this wiki page

If you do not mind I would prefer to be contacted by email, please write the words
"stellarium" and "fortran" into the subject line.

Yours,

[[User:Johannes|Johannes]] 14:38, 1 May 2007 (PDT)

Hi! I'm a french programmer, but unfortunately not a fortran programmer, and I'd like to help if I can . I've started to read fortran tutorial and I plan to test lf95 trial as fortran compiler since it's the one used in the linux Config.mk provided in neptuno package but I don't have much free time these days. I'll let know if I succeed in any way, let me know if you have questions.
Blakbear.

Hello Blackbear,
thank you very much for offering help! I first did not see your writing into the wiki, because the "watch" function seems not to work for me. If you get any insight into the code,
or if you can give any answers to 1) or 2) please send me an email, this will be the easiest way of communication.
Johannes

Hi, Johannes. I could build "ilgs3_d" by g77 and execute without error. But I could not investigate that result is correct or is not correct. Shall I report my procedure?(in this page? or e-mail?) I write a part of output(little formatted), instead answer your questions.
( 1) Date: 0.2378496500000000E+07
Nombre maximum d"enregistrements = 22829
Intervalle cherché = 1
Temps initial d"intégration = 0.2378496500000000E+07
Intervalle d"intégration = 0.0000000000000000E+00
Pas d"intégration = 0.0000000000000000E+00
Temps final d"intégration = 0.2378496500000000E+07
___________________________________________________
Résultats
----------
Triton
( 1) Date: 0.2378496500000000E+07
v0(1,1,0) =-0.2019388268736855E-04
v0(2,1,0) = 0.1722904160856275E-02
v0(3,1,0) = 0.1629414715885055E-02
v0(1,1,1) = 0.2533936570868142E-02
v0(2,1,1) =-0.4058902541155617E-04
v0(3,1,1) = 0.7430677191550270E-04
By the way, when create de403.unx, why did not you convert from unxpXXXX.403 or ascpXXXX.403?--[[User:Sigma|Sigma]] 06:10, 9 May 2007 (PDT)

Same here, I've succeeded in compiling ilgs3_d with lf95 but I can't get a result yet, so Sigma seems more advanced. So far I can't validate my email so I can't use it for the time being, but feel free to ask if you need french to english translation.
Blakbear.

:I uploaded diff files: [http://www.h5.dion.ne.jp/~sigma/stellarium/neptune/ins3_d.f.diff for ins3_d.f],[http://www.h5.dion.ne.jp/~sigma/stellarium/neptune/ins8_d.f.diff for ins8_d.f],[http://www.h5.dion.ne.jp/~sigma/stellarium/neptune/isat8_d.f.diff for isat8_d.f]. Sorry, I could not upload de403.unx, because it was big size for my space(about 9MB gziped). And ilgs8_d did not execute. Probably, there may be a hint for 8 satellites code in LISETMOI and README. Please check them. I'm weak in English, additionaly can not read French. orz--[[User:Sigma|Sigma]] 20:41, 10 May 2007 (PDT)

Hi! I've succeeded in compiling and running both ilgs3_d and ilgs8_d, getting some results and some problems when testing with later dates but at least it works for initial date it seems.<br />
All the modifications I've done for ilgs8_d to work have already been pointed out by Johannes : bad formatting with ' where there shouldn't be and bad location, missing the . to access current dir. I've used unxp1950.403 found on jpl ftp ftp://ssd.jpl.nasa.gov/pub/eph/export/unix/ renamed in de403.unx.<br />
I'm going to make an archive with all the files I've used and make it available tonight, so anyone will be able to test it.

--[[User:Blakbear|Blakbear]] 13:56, 11 May 2007 (PDT)

== Results ==
Thank you all so much for your help! In addition to the information in the wiki I got also emails describing how to create de403.unx. Indeed you had more success then I running the program. Now remains only the problem of creating ephemeris data over a reasonably long timespan, lets say 1500-2500. The file Nsat-fd.dat provides initial values not for this whole period, but I doubt that this is needed. Instead isat_d and ilgs_d should contain a numerical model and an integrator suitable for creating data for an arbitrary period, provided there are the planet positions. This leads to the question:

Can anybody of you understand the contents of isat_d.f and ilgs_d.f? where is the integrator, where is the numerical model, and from where are the planet positions needed for planetary perturbation? This is the part, where French language skills might be helpful. For I cannot understand the comments, function and variable names, for me these are just meaningless accumulations of letters.

Thanks again,
--[[User:Johannes|Johannes]] 09:44, 14 May 2007 (PDT)

Help with Fortran90

2007-05-08T22:31:11Z

Johannes: /* Summary */

Help with Fortran90

2007-05-08T22:22:59Z

Johannes: /* Second approach: f2c */

Main Page

2007-05-01T21:55:51Z

Johannes:

__NOTOC__
==Welcome==
Welcome to the Stellarium wiki, a knowledge website about Stellarium, the free planetarium for your computer. The wiki allows Stellarium users to collectively build the knowledge base about Stellarium, so if you have something to add, register and edit the page.

<div style="float:left; width:29%; margin-right:25px;">
<div style="margin-bottom:25px; background-color:#3d4045; padding:7px; border:solid 1px #847f93;">
<h2 style="color:#f4d385;">Getting started</h2>
* [[Stellarium:About|What is Stellarium?]]
* [[Complete feature list]]
* [[Download|Where to download Stellarium]]
* [[Installation guide]]
* [[Quickstart guide]]
* [[Keyboard actions]]
* [[FAQ|Frequently Asked Questions]]
===User's Guide===
* [http://prdownloads.sourceforge.net/stellarium/stellarium_user_guide-0.8.1-1.pdf?download Download User's Guide PDF]
* [http://www.porpoisehead.net/mysw/stellarium_user_guide_html-0.8.1-1/ Online version]
* [[:Category:User's_Guide|wiki page about the guide]]
* [[User guide contributions|Making user guide contributions]]
</div>

<div style="margin-bottom:25px; background-color:#3d4045; padding:7px; border:solid 1px #847f93;">

<h2 style="color:#f4d385">Extras</h2>
===extra files for Stellarium===
* [[Landscapes]]
* [[Nebula images]]
* [[Scripts]]
* [[Sky cultures]]: See how people across the world look at the heavens above.
===education===
* [[Education|Education Resources]]
</div>
</div>

<div style="float:left; width:29%; margin-right:25px;">
<div style="margin-bottom:25px; background-color:#3d4045; padding:7px; border:solid 1px #847f93;">
<h2 style="color:#f4d385">Help us</h2>
===ongoing efforts===
* [[Translation using gettext|Translate Stellarium in your language]]
* [[Homepage translation|Translate the homepage in your language]]
* [[Help:Contents|Tips for editing the wiki]]
===specific things you can do===
* here will be a list of specific tasks
* [[Help:Fortran90|Compiling FORTRAN90 Neptunian satellite ephemeris]]
</div>
</div>

<div style="float:left; width:29%; margin-right:0px;">
<div style="margin-bottom:25px; background-color:#3d4045; padding:7px; border:solid 1px #847f93;">
<h2 style="color:#f4d385">Advanced topics</h2>
===Projection===
* [[Setting up your own dome using Stellarium's spheric mirror distortion feature|Dome projection with a spheric mirror]]
===Telescope Control===
* [[Telescope Control|Control your telescope]]
* [[Telescope Compatibility|Telescope control compatibility]]
</div>

<div style="margin-bottom:25px; background-color:#3d4045; padding:7px; border:solid 1px #847f93;">
<h2 style="color:#f4d385">Developers</h2>
===compiling===
* [[Svn checkout|Checking out a Subversion development version]] (the old CVS page is [[Cvs checkout|here]] for historical purposes).
* [[Compilation on Linux]]
* [[Windows Build Instructions]]
* [[Building universal Stellarium 0.8.1 on an Intel Mac]]
===coding===
* [[Coding Standard]]
* [[Stellarium Code Architecture]]
</div>
</div>

{| cellpadding=0 cellspacing=1
|- valign="top"
|style="border: none;padding-left:1em;padding-right:0.5em; background-color:#2b2a30;"|

==The Stellarium wiki in other languages==
''<small>[[Template:MetaHomePages|Edit this list:]]</small>'' <small>{{MetaHomePages}}</small>
|}

Main Page

2007-05-01T21:55:16Z

2006-06-21T19:57:18Z

Johannes:

Telescope Control (client-server)

2006-06-18T22:10:46Z

Johannes:

Telescope Control (client-server)

2006-06-18T22:00:42Z

Johannes:

In this page I describe the telescope control feature that is present in stellarium since version 0.8.1.

Overview:

Although stellarium is currently (since 0.8.1) able to control any telescope using a suiting external telescope server, up to now there exist only the following telescope server programs:

TelescopeServerDummy: can be used for testing and as a starting point for developing new telescope servers, no telescope is required

TelescopeServerDummy.exe: same for MS Windows

TelescopeServerLx200: used for controlling Meade LX200 telescopes

TelescopeServerLx200.exe: same for MS Windows

----

Architecture:

Actual communication with the telescope is not done by stellarium itself, but by an external program which is called telescope server. Stellarium and the telescope server communicate with each other over TCP/IP. For the TCP communication there is an LGPL library which should make the development of telescope servers easy. This architecture has the following advantages:

1) The stellarium source code does not get bloated by incorporation of dozens of telescope control mechanisms and protocols. Instead the stellarium sourcecode stays maintainable.

2) TCP is available on any platform, so for stellarium there are little or no portability problems.

3) Any developer can easily provide an own telescope server for his own telescope, eigther by using the stellarium telescope library (recommended) or without it. No knowledge about the stellarium programs source code is required.

4) There are no license problems: An external telescope server can, but does not need to be GPL. When building your own telescope server you can link with any library you want: ASCOM, Indy, any proprietary library, whatever.

----

Building:

The telescope server programs described above are available from anonymous cvs:

cvs -d:pserver:anonymous@stellarium.cvs.sourceforge.net:/cvsroot/stellarium login
cvs -z3 -d:pserver:anonymous@stellarium.cvs.sourceforge.net:/cvsroot/stellarium co -P telescope_server

There is a README file. Just change into the src directory and type 'make' (no autoconf/automake). In order to cross-compile for MS Windows export the environment variable CROSS_GPP and type 'make exe'. I have never tried native MS Windows compilation, but I suppose that any compiler will do. Same for other operating systems. If you have problems, write to the forum. Or write an email to me, I can also provide binaries.

----

Usage:

Start the telescope server with a command line like

TelescopeServerDummy 10000 or
TelescopeServerDummy.exe 10000 or
TelescopeServerLx200 10000 /dev/ttyS0 or
TelescopeServerLx200.exe 10000 COM1:

depending on your telescope and serial port. In this example I assume you use TCP port 10000, but you can use any free port you want. The telescope servers are capable of serving a huge number of stellarium programs, so you can share the control of your telescope with other stellarium programs.

In your config.ini write

[astro]
flag_telescopes = true
flag_telescope_name = true
...
[telescopes]
1 = My_first_telescope:TCP:localhost:10000:500000
2 = My_second_telescope:TCP:localhost:10001:500000

Here I have assumed that you have started two differnt telescope servers on your machine for controlling two different telescopes. When you have just 1 GOTO telescope like me, leave away the last line. If you run the telescope server on a different machine, you must replace 'localhost' with the name of this machine. The value 500000 indicates, that stellarium will not show the telescopes current position - which is unknown anyway - but instead an interpolated position of 500000 microseconds (=0.5 seconds) ago. 'My_first_telescope' is the name that will be shown in stellarium next to the telescope marker. '1' is the keyboard shortcut: <Ctlr><1> will make the telescope point to the currently selected object (GOTO). Currently up to 10 telescopes can be controlled using keys 0,1,...,9.

----

You will want to flip the stellarium image horizontally and/or vertically in order to match what you see in your eyepiece. Currently there are the following keyboard shortcuts:

<Ctrl><Shift><h>: toggle horizontal image flip
<Ctrl><Shift><v>: toggle vertical image flip

I also plan to commit menu buttons for the flipping, which also show the current flipping state.

When you have problems or when you are satisfied, write to the forum.

Yours,
--[[User:Johannes|Johannes]] 14:48, 18 June 2006 (PDT)