GPOrbit - Historique des versions

Admin : /* How to call it */

2019-10-31T12:31:12Z

How to call it

← Version précédente		Version du 31 octobre 2019 à 12:31
Ligne 24 :		Ligne 24 :
	gpOrbit = new GPOrbit("Orbit", orbit);		gpOrbit = new GPOrbit("Orbit", orbit);
	</syntaxhighlight>		</syntaxhighlight>

			== Display ==

	With the first example, we will be able to display this:		With the first example, we will be able to display this:

Admin : /* How to call it */

2018-10-09T15:42:57Z

How to call it

← Version précédente		Version du 9 octobre 2018 à 15:42
Ligne 37 :		Ligne 37 :
	Note that since the '''<font color=#FF0000>V2.0</font>''' version, it exists the possibility to enter data from a <font color=#FF8C00 title="Two Lines Elements">TLE</font> by cicking on the dedicated button. These data will be automatically converted in osculating parameters.		Note that since the '''<font color=#FF0000>V2.0</font>''' version, it exists the possibility to enter data from a <font color=#FF8C00 title="Two Lines Elements">TLE</font> by cicking on the dedicated button. These data will be automatically converted in osculating parameters.

	[[File:GPOrbitTle1.png]]		[[File:GPOrbitTle1.png]] [[File:GPOrbitTle2.png]]

	[[File:GPOrbitTle2.png]]

	We have also the possibility to customize the list of frames and/or types of parameters. In the example below, we will be able only to propose <font color=#FF8C00 title="Geocentric Celestial Reference Frame">GCRF</font>, <font color=#FF8C00 title="Celestial Intermediate Reference Frame">CIRF</font> and <font color=#FF8C00 title="Frame using the mean equinox at epoch J2000.0, i.e. 2000-01-01T12:00:00 in Terrestrial Time (not UTC!)">EME2000</font> for frames when only Keplerian, Cartesian, ApsisRadius and Reentry will be available for type of parameters:		We have also the possibility to customize the list of frames and/or types of parameters. In the example below, we will be able only to propose <font color=#FF8C00 title="Geocentric Celestial Reference Frame">GCRF</font>, <font color=#FF8C00 title="Celestial Intermediate Reference Frame">CIRF</font> and <font color=#FF8C00 title="Frame using the mean equinox at epoch J2000.0, i.e. 2000-01-01T12:00:00 in Terrestrial Time (not UTC!)">EME2000</font> for frames when only Keplerian, Cartesian, ApsisRadius and Reentry will be available for type of parameters:

Admin : /* How to call it */

2018-10-09T15:41:57Z

How to call it

← Version précédente		Version du 9 octobre 2018 à 15:41
Ligne 35 :		Ligne 35 :
	[[File:GPOrbit2.png]]		[[File:GPOrbit2.png]]

	Note that since the '''<font color=#FF0000>V2.0</font>''' version, it exists the possibility to enter data from a TLE by cicking on the dedicated button.		Note that since the '''<font color=#FF0000>V2.0</font>''' version, it exists the possibility to enter data from a <font color=#FF8C00 title="Two Lines Elements">TLE</font> by cicking on the dedicated button. These data will be automatically converted in osculating parameters.

			[[File:GPOrbitTle1.png]]

			[[File:GPOrbitTle2.png]]

	We have also the possibility to customize the list of frames and/or types of parameters. In the example below, we will be able only to propose <font color=#FF8C00 title="Geocentric Celestial Reference Frame">GCRF</font>, <font color=#FF8C00 title="Celestial Intermediate Reference Frame">CIRF</font> and <font color=#FF8C00 title="Frame using the mean equinox at epoch J2000.0, i.e. 2000-01-01T12:00:00 in Terrestrial Time (not UTC!)">EME2000</font> for frames when only Keplerian, Cartesian, ApsisRadius and Reentry will be available for type of parameters:		We have also the possibility to customize the list of frames and/or types of parameters. In the example below, we will be able only to propose <font color=#FF8C00 title="Geocentric Celestial Reference Frame">GCRF</font>, <font color=#FF8C00 title="Celestial Intermediate Reference Frame">CIRF</font> and <font color=#FF8C00 title="Frame using the mean equinox at epoch J2000.0, i.e. 2000-01-01T12:00:00 in Terrestrial Time (not UTC!)">EME2000</font> for frames when only Keplerian, Cartesian, ApsisRadius and Reentry will be available for type of parameters:

Admin : /* How to call it */

2018-10-09T15:39:08Z

How to call it

← Version précédente		Version du 9 octobre 2018 à 15:39
Ligne 34 :		Ligne 34 :

	[[File:GPOrbit2.png]]		[[File:GPOrbit2.png]]

			Note that since the '''<font color=#FF0000>V2.0</font>''' version, it exists the possibility to enter data from a TLE by cicking on the dedicated button.

	We have also the possibility to customize the list of frames and/or types of parameters. In the example below, we will be able only to propose <font color=#FF8C00 title="Geocentric Celestial Reference Frame">GCRF</font>, <font color=#FF8C00 title="Celestial Intermediate Reference Frame">CIRF</font> and <font color=#FF8C00 title="Frame using the mean equinox at epoch J2000.0, i.e. 2000-01-01T12:00:00 in Terrestrial Time (not UTC!)">EME2000</font> for frames when only Keplerian, Cartesian, ApsisRadius and Reentry will be available for type of parameters:		We have also the possibility to customize the list of frames and/or types of parameters. In the example below, we will be able only to propose <font color=#FF8C00 title="Geocentric Celestial Reference Frame">GCRF</font>, <font color=#FF8C00 title="Celestial Intermediate Reference Frame">CIRF</font> and <font color=#FF8C00 title="Frame using the mean equinox at epoch J2000.0, i.e. 2000-01-01T12:00:00 in Terrestrial Time (not UTC!)">EME2000</font> for frames when only Keplerian, Cartesian, ApsisRadius and Reentry will be available for type of parameters:

Admin le 7 septembre 2017 à 10:31

2017-09-07T10:31:22Z

← Version précédente		Version du 7 septembre 2017 à 10:31
Ligne 1 :		Ligne 1 :
	== How to call it ==		== How to call it ==

	For using the ~~<font color=#4169E1>~~GPOrbit~~</font>~~ class, the developer has only to create such an object with these two possibilities:		For using the [{{PathCurrentJavaDoc}}/fr/cnes/genopus/orbits/GPOrbit.html GPOrbit] class, the developer has only to create such an object with these two possibilities:

	* With no orbit initialization:		* With no orbit initialization:

Admin le 28 juillet 2017 à 14:36

2017-07-28T14:36:23Z

← Version précédente		Version du 28 juillet 2017 à 14:36
Ligne 58 :		Ligne 58 :
	This widget is in fact a relatively complex one as it 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 <font color=#FF8C00>Cartesian</font> parameters!		This widget is in fact a relatively complex one as it 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 <font color=#FF8C00>Cartesian</font> parameters!

	[[File:GPOrbitPivot1.png]] [[File:GPOrbitPivot2.png]]		[[File:GPOrbitPivot1.png]] => [[File:GPOrbitPivot2.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.
Ligne 76 :		Ligne 76 :
	=== Constants ===		=== Constants ===

	Some constants are necessary depending on the kind of parameters. Nominally, only <font color=#FF8C00>Cartesian</font> 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 title="Graphic User Interface">GUI</font> 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 …		Some constants are necessary depending on the kind of parameters. Nominally, only <font color=#FF8C00>Cartesian</font> 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 title="Graphic 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 …

	[[File:GPOrbitConstants.png]]		[[File:GPOrbitConstants.png]]
Ligne 82 :		Ligne 82 :
	== How to use it ==		== How to use it ==

	To get a [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] <font color=#4169E1>Orbit</font> object, we will just have to call for the getPatriusObject() method as below:		To get a [[https://logiciels.cnes.fr/en/node/62?type=desc PATRIUS]] <font color=#4169E1>Orbit</font> object, we will just have to call for the <font color=#4169E1>getPatriusObject()</font> method as below:

	<syntaxhighlight lang="java">		<syntaxhighlight lang="java">

Admin le 28 juillet 2017 à 14:31

2017-07-28T14:31:57Z

← Version précédente		Version du 28 juillet 2017 à 14:31
Ligne 24 :		Ligne 24 :
	gpOrbit = new GPOrbit("Orbit", orbit);		gpOrbit = new GPOrbit("Orbit", orbit);
	</syntaxhighlight>		</syntaxhighlight>

			With the first example, we will be able to display this:

			[[File:GPOrbit1.png]]

			We can see that the widget is automatically set in an error mode as the semi major axis is null.

			On the contrary, if it is not the case (as for the second previous example):

			[[File:GPOrbit2.png]]

	We have also the possibility to customize the list of frames and/or types of parameters. In the example below, we will be able only to propose <font color=#FF8C00 title="Geocentric Celestial Reference Frame">GCRF</font>, <font color=#FF8C00 title="Celestial Intermediate Reference Frame">CIRF</font> and <font color=#FF8C00 title="Frame using the mean equinox at epoch J2000.0, i.e. 2000-01-01T12:00:00 in Terrestrial Time (not UTC!)">EME2000</font> for frames when only Keplerian, Cartesian, ApsisRadius and Reentry will be available for type of parameters:		We have also the possibility to customize the list of frames and/or types of parameters. In the example below, we will be able only to propose <font color=#FF8C00 title="Geocentric Celestial Reference Frame">GCRF</font>, <font color=#FF8C00 title="Celestial Intermediate Reference Frame">CIRF</font> and <font color=#FF8C00 title="Frame using the mean equinox at epoch J2000.0, i.e. 2000-01-01T12:00:00 in Terrestrial Time (not UTC!)">EME2000</font> for frames when only Keplerian, Cartesian, ApsisRadius and Reentry will be available for type of parameters:
Ligne 44 :		Ligne 54 :
	</syntaxhighlight>		</syntaxhighlight>

	~~With the first example, we will be able to display this:~~		=== The "pivot" notion ===

	~~[[File:GPOrbit1.png]]~~

	~~We can see that the widget is automatically set in an error mode as the semi major axis is null.~~

	~~On the contrary, if it is not the case (as for the second previous example):~~

	~~[[File:GPOrbit2.png]]~~

	This widget is in fact a relatively complex one as it 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 <font color=#FF8C00>Cartesian</font> parameters!		This widget is in fact a relatively complex one as it 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 <font color=#FF8C00>Cartesian</font> parameters!

Ligne 88 :		Ligne 90 :
	== How it is stored ==		== How it is stored ==

	Here is the XML format for such an orbit:		Here is the <font color=#FF8C00 title="Extensible Markup Language">XML</font> format for such an orbit:

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

Admin le 28 juillet 2017 à 14:28

2017-07-28T14:28:56Z

@@ Ligne 11 : / Ligne 11 : @@
 * Or, if we want to initialize the widget with a predefined orbit:
-<syntaxhighlight lang="java">final Frame CIRF = FramesFactory.getCIRF();
+<syntaxhighlight lang="java">
 final TimeScale TUC = TimeScalesFactory.getUTC();
 final AbsoluteDate date0 = new AbsoluteDate(2010, 1, 1, 12, 0, 0., TUC);
@@ Ligne 65 : / Ligne 66 : @@
 * The kind of anomaly (if relevant)
-At every moment, the user may change the “pivot” definition by clicking on the dedicated button.
+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.
+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!
@@ Ligne 73 : / Ligne 74 : @@
 === Constants ===
-Some constants are necessary depending on the kind of parameters. Nominally, only <font color=#FF8C00>Cartesian</font> 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 …
+Some constants are necessary depending on the kind of parameters. Nominally, only <font color=#FF8C00>Cartesian</font> 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 title="Graphic User Interface">GUI</font> 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 …
 [[File:GPOrbitConstants.png]]

Admin le 28 juillet 2017 à 14:22

2017-07-28T14:22:10Z

← Version précédente		Version du 28 juillet 2017 à 14:22
Ligne 42 :		Ligne 42 :
	gpOrbit.setAvailableParamsTypes(tabParamsSimplified);		gpOrbit.setAvailableParamsTypes(tabParamsSimplified);
	</syntaxhighlight>		</syntaxhighlight>

			With the first example, we will be able to display this:

			[[File:GPOrbit1.png]]

			We can see that the widget is automatically set in an error mode as the semi major axis is null.

			On the contrary, if it is not the case (as for the second previous example):

			[[File:GPOrbit2.png]]

			This widget is in fact a relatively complex one as it 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 <font color=#FF8C00>Cartesian</font> parameters!

			[[File:GPOrbitPivot1.png]] [[File:GPOrbitPivot2.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.

			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!

			=== Constants ===

			Some constants are necessary depending on the kind of parameters. Nominally, only <font color=#FF8C00>Cartesian</font> 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 …

			[[File:GPOrbitConstants.png]]

Admin : Page créée avec « == How to call it == For using the GPOrbit class, the developer has only to create such an object with these two possibilities: * With no orbi... »

2017-07-28T13:10:19Z

Page créée avec « == How to call it == For using the GPOrbit class, the developer has only to create such an object with these two possibilities: * With no orbi... »

Nouvelle page

== How to call it ==

For using the GPOrbit class, the developer has only to create such an object with these two possibilities:

* With no orbit initialization:

<syntaxhighlight lang="java">
gpOrbit = new GPOrbit("Orbit");
</syntaxhighlight>

* Or, if we want to initialize the widget with a predefined orbit:

<syntaxhighlight lang="java">final Frame CIRF = FramesFactory.getCIRF();
final TimeScale TUC = TimeScalesFactory.getUTC();
final AbsoluteDate date0 = new AbsoluteDate(2010, 1, 1, 12, 0, 0., TUC);
final double ae = Constants.WGS84_EARTH_EQUATORIAL_RADIUS;
final double mu = Constants.WGS84_EARTH_MU;

ApsisOrbit orbit =
new ApsisOrbit(ae+200.e+3, ae+300.e+3, FastMath.toRadians(51.6), 0., 0., 0.,
PositionAngle.MEAN, CIRF, date0, mu);

gpOrbit = new GPOrbit("Orbit", orbit);
</syntaxhighlight>

We have also the possibility to customize the list of frames and/or types of parameters. In the example below, we will be able only to propose GCRF, CIRF and EME2000 for frames when only Keplerian, Cartesian, ApsisRadius and Reentry will be available for type of parameters:

<syntaxhighlight lang="java">
GPRefFrame[] tabFrames = gpOrbit.getAvailableFrames();
GPRefFrame[] tabFramesSimplified = new GPRefFrame[3];
tabFramesSimplified[0] = tabFrames[0];
tabFramesSimplified[1] = tabFrames[1];
tabFramesSimplified[2] = tabFrames[6];
gpOrbit.setAvailableFrames(tabFramesSimplified);

GPParamsType[] tabParams = gpOrbit.getAvailableParamsTypes();
GPParamsType[] tabParamsSimplified = new GPParamsType[4];
tabParamsSimplified[0] = tabParams[0];
tabParamsSimplified[1] = tabParams[1];
tabParamsSimplified[2] = tabParams[5];
tabParamsSimplified[3] = tabParams[7];
gpOrbit.setAvailableParamsTypes(tabParamsSimplified);
</syntaxhighlight>

GPOrbit - Historique des versions

Admin : /* How to call it */

Admin : /* How to call it */

Admin : /* How to call it */

Admin : /* How to call it */

Admin le 7 septembre 2017 à 10:31

Admin le 28 juillet 2017 à 14:36

Admin le 28 juillet 2017 à 14:31

Admin le 28 juillet 2017 à 14:28

Admin le 28 juillet 2017 à 14:22

Admin : Page créée avec « == How to call it == For using the GPOrbit class, the developer has only to create such an object with these two possibilities: * With no orbi... »

Admin : /* How to call it */

Admin : /* How to call it */

Admin : /* How to call it */

Admin : /* How to call it */

Admin : Page créée avec « == How to call it == For using the GPOrbit class, the developer has only to create such an object with these two possibilities: * With no orbi... »