en:documentation:computation_method_and_precision
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
| en:documentation:computation_method_and_precision [2014/02/21 17:11] – created pch | en:documentation:computation_method_and_precision [2018/12/06 11:34] (current) – [Planets equatorial positions] pch | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== | + | ====== |
| - | This page is to give some information about the computation method used by Cartes du Ciel - Skychart and the precision you can expect | + | This page give some information about the computation method used by //Cartes du Ciel - Skychart// and the precision you can expect |
| - | You must be careful this description is about the standard configuration setting of the program, using the default catalog data. You have many option available to alter this results, principally in the [[chart_coordinates|Chart, | + | You must be careful this description is valid with the standard configuration setting of the program, using the default catalog data. You have many option available to alter the results, principally in the [[chart_coordinates|Chart, |
| ===== Stellar equatorial positions ===== | ===== Stellar equatorial positions ===== | ||
| - | The basic precision depend on the star catalog used, for the precision of the position but also for the proper motion. The default catalog is the Extended Hipparcos Compilation ([[http:// | + | The basic precision depend on the star catalog used, for the precision of the position but also for the proper motion. The default catalog is the Extended Hipparcos Compilation ([[http:// |
| After it get the catalog data the program compute the position corrected for the star proper motion at the current chart date using the pmRA and pmDEC values, and full space motion if the parallax and radial velocity are available (u_projection.pas, | After it get the catalog data the program compute the position corrected for the star proper motion at the current chart date using the pmRA and pmDEC values, and full space motion if the parallax and radial velocity are available (u_projection.pas, | ||
| Line 15: | Line 15: | ||
| To find the apparent position we compute the nutation using the value given by the JPL ephemeris, then the annual aberration and the light deflection by the Sun (u_projection.pas, | To find the apparent position we compute the nutation using the value given by the JPL ephemeris, then the annual aberration and the light deflection by the Sun (u_projection.pas, | ||
| - | For the current epoch the precision is expected to be better than 0.1 arcsec. | + | For the current epoch the precision is expected to be better than 0.1 arcsec. \\ |
| + | The precision of the proper motion calculation over a long time period depend of the availability of the parallax and the radial velocity, but also of the standard error on the values. An error of about 1 arcsecond by millennium is to be expect.\\ | ||
| + | The precession computation is valid for a +/- 200' | ||
| ===== DSO equatorial positions ===== | ===== DSO equatorial positions ===== | ||
| Line 26: | Line 28: | ||
| The position of the planets are computed using the JPL ephemeris or if no file are found for the current date, the library [[http:// | The position of the planets are computed using the JPL ephemeris or if no file are found for the current date, the library [[http:// | ||
| - | By default an extract of DE405 valid between 2000 and 2050 is supplied with the program. So the first thing to do if you want long term high precision planet position is to install a [[ftp:// | + | By default an extract of DE430 valid between 2000 and 2050 is supplied with the program. So the first thing to do if you want long term high precision planet position is to install a [[ftp:// |
| DE431 is recommended if you can afford the 2.5GB download. With this file you can compute precise planet position and nutation between -13000 and +17000. | DE431 is recommended if you can afford the 2.5GB download. With this file you can compute precise planet position and nutation between -13000 and +17000. | ||
| Line 35: | Line 37: | ||
| Then the apparent position is computed by applying the nutation and annual aberration (not for the Moon). This is the topocentric apparent position. | Then the apparent position is computed by applying the nutation and annual aberration (not for the Moon). This is the topocentric apparent position. | ||
| - | For the current epoch the precision is expected to be better than 0.1 arcsec. | + | For the current epoch the precision is expected to be better than 0.1 arcsec.\\ |
| + | For a date far in the past or the future the major source of error is the uncertainty in the difference between the universal time and the terrestrial time [[http:// | ||
| + | The precision of the computation itself depend on the individual ephemeris, but it is always far better than every expectation for a terrestrial observer. Refer to the JPL documentation.\\ | ||
| + | The error on precession is the same as discussed for the stars. | ||
| ===== Comets and asteroids equatorial positions ===== | ===== Comets and asteroids equatorial positions ===== | ||
| Line 48: | Line 53: | ||
| Then precession, parallax and apparent position is computed the same as for the planets. | Then precession, parallax and apparent position is computed the same as for the planets. | ||
| - | When using current element data the precision is expected to be about 0.1 arcsec. | + | The orbit computation use the classic two body solution, no perturbation from other body is taken into account. |
| + | You can reliably compute the asteroids and comets position only for a few month around the date of the elements. So it make no sens to compute this position for a date far in the past or future. | ||
| ===== Alt/Az positions ===== | ===== Alt/Az positions ===== | ||
| Line 61: | Line 67: | ||
| The refraction is computed using two different method, one for the display on the map, the other to display a more precise value in the detailed information window.\\ | The refraction is computed using two different method, one for the display on the map, the other to display a more precise value in the detailed information window.\\ | ||
| The first method need to be fully reversible without too much computation. It is currently based on Bennett formula.\\ | The first method need to be fully reversible without too much computation. It is currently based on Bennett formula.\\ | ||
| - | The second is based on the method in slalib | + | The second is based on the method in [[http:// |
| - | If all the observatory parameters are given with the maximum precision the azimuth and the geometric altitude must be better than 0.5 arcsec. The precision on the refracted altitude depend on the difference between the model and the real atmosphere. | + | If all the observatory parameters are given with the maximum precision, the precision of the azimuth and the geometric altitude must be better than 0.5 arcsec. The precision on the refracted altitude depend on the difference between the model and the real atmosphere.\\ |
| + | But remember that 0.1 arcsec represent 3 meters on the soil and a star on the celestial equator move by this distance in 0.007 second. You need to set your observatory location and measure the time with this precision if you want it make some sens. | ||
en/documentation/computation_method_and_precision.1392999094.txt.gz · Last modified: 2015/11/06 20:34 (external edit)
