Initial Orbit - Historique des versions

Admin : /* Copy/Paste */

2019-01-11T14:30:31Z

Copy/Paste

← Version précédente		Version du 11 janvier 2019 à 14:30
Ligne 45 :		Ligne 45 :
	== Copy/Paste ==		== Copy/Paste ==

	Thanks to [[http://genius.cnes.fr GENIUS]] and [[http://genopus.cnes.fr GENOPUS]] functionnalities, it is possible to do a Copy/Paste/Import/Export on orbit data. To do it, you have just to click with the right button above the "Orbit:" label (in blue (or red if values are uncorrect).		Thanks to [http://genius.cnes.fr GENIUS] and [http://genopus.cnes.fr GENOPUS] functionnalities, it is possible to do a '''Copy/Paste/Import/Export''' on orbit data. To do it, you have just to click with the right button above the "Orbit" label (in blue (or red if values are uncorrect!).

	[[Fichier:OrbitCopyPaste.png]]		[[Fichier:OrbitCopyPaste.png]]

	~~Thus~~, you can copy your orbit data on any other tool that uses the [[http://genopus.cnes.fr]] widget [[http://genopus.cnes.fr/index.php/GPOrbit GPOrbit]]. You may also paste (or export) the data in a file. With ~~tyhe~~ previous example, you will get:		Then, you can copy your orbit data on any other tool that uses the [http://genopus.cnes.fr GENOPUS] widget [http://genopus.cnes.fr/index.php/GPOrbit GPOrbit]. You may also paste (or export) the data in a file. With the previous example, you will get:

	<syntaxhighlight lang="XML">		<syntaxhighlight lang="XML">

Admin : /* Copy/Paste */

2019-01-11T14:29:08Z

Copy/Paste

← Version précédente		Version du 11 janvier 2019 à 14:29
Ligne 45 :		Ligne 45 :
	== Copy/Paste ==		== Copy/Paste ==

	Thanks to [[http://genius.cnes.fr GENIUS]] and [[http://genopus.cnes.fr]] functionnalities, it is possible to do a Copy/Paste/Import/Export on orbit data. To do it, you have just to click with the right button above the "Orbit:" label (in blue (or red if values are uncorrect).		Thanks to [[http://genius.cnes.fr GENIUS]] and [[http://genopus.cnes.fr GENOPUS]] functionnalities, it is possible to do a Copy/Paste/Import/Export on orbit data. To do it, you have just to click with the right button above the "Orbit:" label (in blue (or red if values are uncorrect).

	[[Fichier:OrbitCopyPaste.png]]		[[Fichier:OrbitCopyPaste.png]]

Admin : /* Copy/Paste */

2019-01-11T14:28:54Z

Copy/Paste

← Version précédente		Version du 11 janvier 2019 à 14:28
Ligne 45 :		Ligne 45 :
	== Copy/Paste ==		== Copy/Paste ==

	Thanks to [[http://genius.cnes.fr]] and [[http://genopus.cnes.fr]] functionnalities, it is possible to do a Copy/Paste/Import/Export on orbit data. To do it, you have just to click with the right button above the "Orbit:" label (in blue (or red if values are uncorrect).		Thanks to [[http://genius.cnes.fr GENIUS]] and [[http://genopus.cnes.fr]] functionnalities, it is possible to do a Copy/Paste/Import/Export on orbit data. To do it, you have just to click with the right button above the "Orbit:" label (in blue (or red if values are uncorrect).

	[[Fichier:OrbitCopyPaste.png]]		[[Fichier:OrbitCopyPaste.png]]

Admin : /* Constants */

2019-01-11T14:26:54Z

Constants

← Version précédente		Version du 11 janvier 2019 à 14:26
Ligne 42 :		Ligne 42 :

	[[Fichier:Constants.png]]		[[Fichier:Constants.png]]

			== Copy/Paste ==

			Thanks to [[http://genius.cnes.fr]] and [[http://genopus.cnes.fr]] functionnalities, it is possible to do a Copy/Paste/Import/Export on orbit data. To do it, you have just to click with the right button above the "Orbit:" label (in blue (or red if values are uncorrect).

			[[Fichier:OrbitCopyPaste.png]]

			Thus, you can copy your orbit data on any other tool that uses the [[http://genopus.cnes.fr]] widget [[http://genopus.cnes.fr/index.php/GPOrbit GPOrbit]]. You may also paste (or export) the data in a file. With tyhe previous example, you will get:

			<syntaxhighlight lang="XML">
			<?xml version="1.0" encoding="UTF-8"?>
			<fr.cnes.genopus.orbits.GPOrbit>
			<Orbit name="Orbit">
			<AbsoluteDate name="Date">
			<String name="date">01/01/2000 00h00m00s</String>
			<String name="scale">UTC</String>
			</AbsoluteDate>
			<Frame name="Frame">
			<String name="name">GCRF</String>
			</Frame>
			<String name="typeOfParameters">Apsis Altitude</String>
			<ApsisAltitudeParameters name="Apsis_Altitude_Parameters">
			<Real name="hp" unit="km">3.0E2</Real>
			<Real name="ha" unit="km">3.0E2</Real>
			<Real name="i" unit="deg">5.16E1</Real>
			<Real name="raan" unit="deg">0.0E0</Real>
			<Real name="pa" unit="deg">0.0E0</Real>
			<String name="typeOfAnomaly">true</String>
			<Real name="anomaly" unit="deg">0.0E0</Real>
			<Real name="mu" unit="km^3/s^2">3.986004415E5</Real>
			<Real name="req" unit="km">6.3781363E3</Real>
			</ApsisAltitudeParameters>
			</Orbit>
			</fr.cnes.genopus.orbits.GPOrbit>
			</syntaxhighlight>

Admin le 10 juillet 2017 à 07:33

2017-07-10T07:33:37Z

← Version précédente		Version du 10 juillet 2017 à 07:33
Ligne 39 :		Ligne 39 :

	Some constants are necessary depending on the kind of parameters. Nominally, only Cartesian parameters do not need it but it has been decided to show “µ” value anytime. On the contrary, equatorial radius and/or flatness will be displayed only when needed (as for reentry parameters).		Some constants are necessary depending on the kind of parameters. Nominally, only Cartesian parameters do not need it but it has been decided to show “µ” value anytime. On the contrary, equatorial radius and/or flatness will be displayed only when needed (as for reentry parameters).
	These constants are modifiable via the <font color=#FF8C00>GUI</font> but a list of predefined values (present in [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] library) is accessible via a select button that will display a pop-up window as below …		These constants are modifiable via the <font color=#FF8C00 title="Graphical User Interface">GUI</font> but a list of predefined values (present in [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] library) is accessible via a select button that will display a pop-up window as below …

	[[Fichier:Constants.png]]		[[Fichier:Constants.png]]

Admin le 6 juillet 2017 à 14:02

2017-07-06T14:02:18Z

← Version précédente		Version du 6 juillet 2017 à 14:02
Ligne 36 :		Ligne 36 :
	Moreover, it is always possible to disconnect this conversion possibility: indeed, it is a basic case when the user started to enter orbital parameters before choosing the right frame!		Moreover, it is always possible to disconnect this conversion possibility: indeed, it is a basic case when the user started to enter orbital parameters before choosing the right frame!

	== ~~CONSTANTS~~ ==		== Constants ==

	Some constants are necessary depending on the kind of parameters. Nominally, only Cartesian parameters do not need it but it has been decided to show “µ” value anytime. On the contrary, equatorial radius and/or flatness will be displayed only when needed (as for reentry parameters).		Some constants are necessary depending on the kind of parameters. Nominally, only Cartesian parameters do not need it but it has been decided to show “µ” value anytime. On the contrary, equatorial radius and/or flatness will be displayed only when needed (as for reentry parameters).

Admin le 6 juillet 2017 à 14:01

2017-07-06T14:01:37Z

← Version précédente		Version du 6 juillet 2017 à 14:01
Ligne 39 :		Ligne 39 :

	Some constants are necessary depending on the kind of parameters. Nominally, only Cartesian parameters do not need it but it has been decided to show “µ” value anytime. On the contrary, equatorial radius and/or flatness will be displayed only when needed (as for reentry parameters).		Some constants are necessary depending on the kind of parameters. Nominally, only Cartesian parameters do not need it but it has been decided to show “µ” value anytime. On the contrary, equatorial radius and/or flatness will be displayed only when needed (as for reentry parameters).
	These constants are modifiable via the GUI but a list of predefined values (present in PATRIUS library) is accessible via a select button that will display a pop-up window as below …		These constants are modifiable via the <font color=#FF8C00>GUI</font> but a list of predefined values (present in [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] library) is accessible via a select button that will display a pop-up window as below …

	[[Fichier:Constants.png]]		[[Fichier:Constants.png]]

Admin le 6 juillet 2017 à 14:00

2017-07-06T14:00:35Z

← Version précédente		Version du 6 juillet 2017 à 14:00
Ligne 35 :		Ligne 35 :
	On the other side, if the user modifies an entry (as the eccentricity when Keplerian parameters), the “pivot” will be automatically modified (as we will be on a new orbit). On the same idea, if the user modifies the “µ” value (or equatorial radius or flatness), the orbit will also be modified. Nevertheless, a conversion will be done as it could be useful to see the influence of such constants.		On the other side, if the user modifies an entry (as the eccentricity when Keplerian parameters), the “pivot” will be automatically modified (as we will be on a new orbit). On the same idea, if the user modifies the “µ” value (or equatorial radius or flatness), the orbit will also be modified. Nevertheless, a conversion will be done as it could be useful to see the influence of such constants.
	Moreover, it is always possible to disconnect this conversion possibility: indeed, it is a basic case when the user started to enter orbital parameters before choosing the right frame!		Moreover, it is always possible to disconnect this conversion possibility: indeed, it is a basic case when the user started to enter orbital parameters before choosing the right frame!

			== CONSTANTS ==

			Some constants are necessary depending on the kind of parameters. Nominally, only Cartesian parameters do not need it but it has been decided to show “µ” value anytime. On the contrary, equatorial radius and/or flatness will be displayed only when needed (as for reentry parameters).
			These constants are modifiable via the GUI but a list of predefined values (present in PATRIUS library) is accessible via a select button that will display a pop-up window as below …

			[[Fichier:Constants.png]]

Admin le 6 juillet 2017 à 13:58

2017-07-06T13:58:36Z

← Version précédente		Version du 6 juillet 2017 à 13:58
Ligne 24 :		Ligne 24 :

	The widget used to entry initial orbit parameters proposes a lot of different frames an type of parameters but also allows executing conversions. It is very interesting for example if you want to see quickly at which altitude is your perigee when you initially get Cartesian parameters!		The widget used to entry initial orbit parameters proposes a lot of different frames an type of parameters but also allows executing conversions. It is very interesting for example if you want to see quickly at which altitude is your perigee when you initially get Cartesian parameters!

			[[Fichier:Pivot.png]]

	Unfortunately, a feedback of many years of such use shows that you will definitively get numerical uncertainties and when you will have to return to the first entry, you will not recover exactly the same values.		Unfortunately, a feedback of many years of such use shows that you will definitively get numerical uncertainties and when you will have to return to the first entry, you will not recover exactly the same values.

Admin le 6 juillet 2017 à 13:57

2017-07-06T13:57:46Z

← Version précédente		Version du 6 juillet 2017 à 13:57
Ligne 16 :		Ligne 16 :

	[[Fichier:DateScale.png]]		[[Fichier:DateScale.png]]

	… and also have the possibility to use a date offset utility (very useful when you want to add duration to a previous date) by clicking on the [[Fichier:DateOffsetButton.png]] button:		… and also have the possibility to use a date offset utility (very useful when you want to add duration to a previous date) by clicking on the [[Fichier:DateOffsetButton.png]] button:

	[[Fichier:DateOffset.png]]		[[Fichier:DateOffset.png]]

			== Conversions and “pivot” notion ==

			The widget used to entry initial orbit parameters proposes a lot of different frames an type of parameters but also allows executing conversions. It is very interesting for example if you want to see quickly at which altitude is your perigee when you initially get Cartesian parameters!

			Unfortunately, a feedback of many years of such use shows that you will definitively get numerical uncertainties and when you will have to return to the first entry, you will not recover exactly the same values.
			The “pivot” is a very important notion that allows answering to this problematic. The basic idea is to store the initial entry as a reference (the “pivot”). So every time the user will ask for a conversion, it will be checked if the format is equal (or not) to the reference. If it is the case, no conversion will be done, the reference will be retrieved. The “pivot” is then defined by:
			* The frame
			* The kind of parameters
			* The kind of anomaly (if relevant)
			At every moment, the user may change the “pivot” definition by clicking on the dedicated button.
			On the other side, if the user modifies an entry (as the eccentricity when Keplerian parameters), the “pivot” will be automatically modified (as we will be on a new orbit). On the same idea, if the user modifies the “µ” value (or equatorial radius or flatness), the orbit will also be modified. Nevertheless, a conversion will be done as it could be useful to see the influence of such constants.
			Moreover, it is always possible to disconnect this conversion possibility: indeed, it is a basic case when the user started to enter orbital parameters before choosing the right frame!

Initial Orbit - Historique des versions

Admin : /* Copy/Paste */

Admin : /* Copy/Paste */

Admin : /* Copy/Paste */

Admin : /* Constants */

Admin le 10 juillet 2017 à 07:33

Admin le 6 juillet 2017 à 14:02

Admin le 6 juillet 2017 à 14:01

Admin le 6 juillet 2017 à 14:00

Admin le 6 juillet 2017 à 13:58

Admin le 6 juillet 2017 à 13:57

Admin : /* Copy/Paste */

Admin : /* Copy/Paste */

Admin : /* Copy/Paste */

Admin : /* Constants */