Current version : Différence entre versions

De Wiki
Aller à : navigation, rechercher
Ligne 3 : Ligne 3 :
 
<u>Known bugs of this version</u> (to be corrected in the new V11.5 version):
 
<u>Known bugs of this version</u> (to be corrected in the new V11.5 version):
  
* There are some problems with the fact that, since V11.3, <font color=#556B2F>'''PSIMU'''</font> is able to memorize in its context file, both "'''Pivot'''" and "'''Display'''" data for initial orbital conditions. Indeed :
+
* There are some problems with the fact that, since V11.3, <font color=#556B2F>'''PSIMU'''</font> is able to store in its context file, both "'''Pivot'''" and "'''Display'''" data for initial orbital conditions. Indeed :
** if "'''Pivot'''" and "'''Display'''" frames are not the same ones, <font color=#556B2F>'''PSIMU'''</font> will consider orbital parameters coming from the "'''Pivot'''" data and frame characteristics from the "'''Display'''" ones <u>which is of course totally wrong</u>.
+
** if "'''Pivot'''" and "'''Display'''" frames are not the same, <font color=#556B2F>'''PSIMU'''</font> will consider orbital parameters coming from the "'''Pivot'''" data and frame characteristics from the "'''Display'''" ones <u>which is of course totally wrong</u>.
** if the user will modify the context file not via the <font color=#556B2F>'''PSIMU'''</font> <font color=#FF8C00 title="Graphical User Interface">GUI</font>, it will have to modify both "'''Pivot'''" and "'''Display'''" data in order to have consistency between both data.
+
** if the user modifies the context file not through the <font color=#556B2F>'''PSIMU'''</font> <font color=#FF8C00 title="Graphical User Interface">GUI</font>, it has to modify both "'''Pivot'''" and "'''Display'''" data in order to keep consistency between both data.
* When modifying constants (for example µ) of initial orbital conditions (even only the units), a conversion is done as it has not to be done.
+
* When modifying constants (for example µ) of initial orbital conditions (even only the units), a conversion is done which is useless.
 
* When reading the initial orbit, <font color=#556B2F>'''PSIMU'''</font> has not already read [[Earth_Features|Earth Features characteristics]]. So, in some cases, it may exit in an error mode (for example when using H0-n frames) saying that no <font color=#FF8C00 title="Earth Orientation Parameters>EOP</font> are available even if we do not need them as it will use the [[http://patrius.cnes.fr PATRIUS]] by default configuration.
 
* When reading the initial orbit, <font color=#556B2F>'''PSIMU'''</font> has not already read [[Earth_Features|Earth Features characteristics]]. So, in some cases, it may exit in an error mode (for example when using H0-n frames) saying that no <font color=#FF8C00 title="Earth Orientation Parameters>EOP</font> are available even if we do not need them as it will use the [[http://patrius.cnes.fr PATRIUS]] by default configuration.
 
* When using the <font color=#FF8C00>Java</font> <font color=#FF8C00 title="Application Programming Interface ">API</font>, due to a [http://patrius.cnes.fr PATRIUS] anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the <font color=#4169E1>Vehicle</font> constructor with all parameters and the <font color=#4169E1>VehiculeSurfaceModel</font> including the panels as above (and not a list of <font color=#4169E1>Facet</font>); also, do not use the setters methods.
 
* When using the <font color=#FF8C00>Java</font> <font color=#FF8C00 title="Application Programming Interface ">API</font>, due to a [http://patrius.cnes.fr PATRIUS] anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the <font color=#4169E1>Vehicle</font> constructor with all parameters and the <font color=#4169E1>VehiculeSurfaceModel</font> including the panels as above (and not a list of <font color=#4169E1>Facet</font>); also, do not use the setters methods.
 
* See also possible anomalies raised due to [[http://genopus.cnes.fr GENOPUS]] or [[http://genius.cnes.fr GENIUS]] widgets used by <font color=#556B2F>'''PSIMU'''</font>. In particular, due to a [[http://genius.cnes.fr GENIUS]] anomaly, when using the [[Output#Custom_plots|Custom plots]] tab, we can normally display data together from the ephemeris table data but also from the events table. With this version, it is no more possible. To do it up to now, we must display data of the second table using the secondary axis possibility (but the range might be different between both axis).
 
* See also possible anomalies raised due to [[http://genopus.cnes.fr GENOPUS]] or [[http://genius.cnes.fr GENIUS]] widgets used by <font color=#556B2F>'''PSIMU'''</font>. In particular, due to a [[http://genius.cnes.fr GENIUS]] anomaly, when using the [[Output#Custom_plots|Custom plots]] tab, we can normally display data together from the ephemeris table data but also from the events table. With this version, it is no more possible. To do it up to now, we must display data of the second table using the secondary axis possibility (but the range might be different between both axis).

Version du 18 janvier 2021 à 14:38

New version, correcting two V11.4 anomalies (see here).

Known bugs of this version (to be corrected in the new V11.5 version):

  • There are some problems with the fact that, since V11.3, PSIMU is able to store in its context file, both "Pivot" and "Display" data for initial orbital conditions. Indeed :
    • if "Pivot" and "Display" frames are not the same, PSIMU will consider orbital parameters coming from the "Pivot" data and frame characteristics from the "Display" ones which is of course totally wrong.
    • if the user modifies the context file not through the PSIMU GUI, it has to modify both "Pivot" and "Display" data in order to keep consistency between both data.
  • When modifying constants (for example µ) of initial orbital conditions (even only the units), a conversion is done which is useless.
  • When reading the initial orbit, PSIMU has not already read Earth Features characteristics. So, in some cases, it may exit in an error mode (for example when using H0-n frames) saying that no EOP are available even if we do not need them as it will use the [PATRIUS] by default configuration.
  • When using the Java API, due to a PATRIUS anomaly, if the user needs to define solar panels characteristics, it is mandatory to use the Vehicle constructor with all parameters and the VehiculeSurfaceModel including the panels as above (and not a list of Facet); also, do not use the setters methods.
  • See also possible anomalies raised due to [GENOPUS] or [GENIUS] widgets used by PSIMU. In particular, due to a [GENIUS] anomaly, when using the Custom plots tab, we can normally display data together from the ephemeris table data but also from the events table. With this version, it is no more possible. To do it up to now, we must display data of the second table using the secondary axis possibility (but the range might be different between both axis).