MOIS 245100

Document Sample
MOIS 245100 Powered By Docstoc
					                                                                                 14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                            JOINT AR

                                                                                                                    Context  Criticalit Configurati Entity in
Reference              Title                                   Description                          Phase          reference     y         on Item       charge                        Comments
    10044 TTFEE APPLICATION CAN NOT     During the connectivity tests between main TTFEE (at Atv- Test - Test     CONNECTIV C - Critical 233000 -      DLR        21/04/06: Kept open until test with redundant IGS -
          START WITH R-AFEE IN DLR      CC) and R-AFEE (in Redu ESA gateway) at DLR, the                          ITY TESTS              LANS                     12/04/06: tests OK with prime IGS -14/02/06:
                                        main TTFEE application (at ATV-CC) does not start                                                Externe + I/F            following VPN installation, remove of IPSEC from
                                        because the remote application does not answser.                                                 IGS                      TTFEE has to be tested before AR closure -
                                                                                                                                                                  02/12/04: Solution with IP tunel works fine,
                                                                                                                                                                  nevertheless some security issues has to be
                                                                                                                                                                  treated -28/06/04: Tests between ATV-CC & DLR
                                                                                                                                                                  have started today -27/04/04: Investigations/tests
                                                                                                                                                                  regarding IPsec and NAT done by DLR -06/04/04:
                                                                                                                                                                  Work around (NAT disable) set for SVT4A with
                                                                                                                                                                  Houston
    10125 SYSTEM VALUES INCONSISTENCY   During SVT4B dry run, an incompatibility appears            SysVal -      SVT4B       mi - minor 230000 -       ESA       01/06/07 : CNES System team check for System
          BETWEEN COP1 PROTOCOL IN      between ground and flight segments : On the vehicle the System                                   System &                 ARB-OMT : No specific remarks
          ATVCC, AND TIME               time authentication window for TCs is set to 60 s whereas Validation                             Interfaces               06/04/06: On-Board time authentication will be
          AUTHENTICATION WINDOW ON      in the GS the COP-1 protocol is set to 5 retries each with                                                                increase from 60 to 100 sec in Reference R3 -
          THE ATV VEHICLE               a 20 s time-out. If a TC is successfully sent on the 4th or                                                               24/01/05: Some elements has been answered by
                                        5th retry it will be rejected on-board (as time authent.                                                                  EADS, but complete schema is to be defined by
                                        exceed)                                                                                                                   Mission operations authority.
                                                                                                                                                                  # Remarks : Une OCR-052 proposée par
                                                                                                                                                                  D.Cornier sur le COP1 en mars 2006, échanges
                                                                                                                                                                  de mail sur le sujet
    10136 REDU MODEM: GARBAGE DATA      when the INSNEC Modems in Redu are configured to            Test - Test   SAT G       Ma -        232300 -      ESA       28/11/05: modem problem still exists (tests on
          WHILE OUTPUT IS DISABLED      play telemetry files and have their telemetry output                                  Major       Redu                    21/10/05) -ESA RfC being answered by In-Snec.
                                        disabled, there is still some data sent to the R-AFEE. On                                         Modem                   11/03/05: Some data is received by both R-AFEE
                                        the nominal chain, the R-AFEE stay (bit) locked at 64kbps                                                                 and produces error messages (TTFEE)
                                        and on the redundant chain, the R-AFEE try to (bit) lock at
                                        a rate varying from 8kbps to more than 200kbps!


    10234 INCOHERENT MASS PROPERTIES    The Following data extracted from the                                     V13B & R1   mi - minor 292100 -       ASTRIUM    15/02/06: Two mass are required by IRN44D,
          IN VDI                        ATV_VDI_CONTENT file of MDB V13B both represent                                                  MDB files                which aim was to have a complete set of
                                        the mass of the ATV at injection, but have different                                                                      mechanical data (mass, cog, inertia) in both SGS
                                        values: VDI_GLOATV_SGS_DEPL_MASS : 19276Kg                                                                                situation. The 2 mass values will be updated after
                                        VDI_PRO_ATV_MASS_INIT: 19448Kg                                                                                            KOUROU operation and will be put equal at that
                                                                                                                                                                  time -26/01/06: EADS ST agrees the 2 VDIs are
                                                                                                                                                                  not currently consistent in MDB-ODB R1

    10325 CHECKSUM TC WITH AN ODD       A checksum request TC ( PUD_TC_CHECK_MEMORY) Test - Test                              C - Critical 230000 -     ROVSING   01/06/07 : CNES System team check for System
          START ADRESS OR LENGTH IS     has been sent on AGCS with a dummy odd start address,                                              System &               ARB-OMT : No specific remarks
          NOT REJECTED BY FCC           this has lead to a FTC reset. The FCC was activated and                                            Interfaces             19/02/07: AR still opened and CP 3587 on-going
                                        did not rejected this incorrect checksum TC. It seems that                                                                (FCC v2.4 integration). 05/10/06: FCC behaviour
                                        FAS is not protected for this case of error, and FCC do                                                                   is confirmed to be in line with its requirements. A
                                        not cover this lack.                                                                                                      CP3587 has been issued to add a protection at
                                                                                                                                                                  FAS level.
    10330 INCORRECT UNITS AND DATA      In the DaSS catalogue V10, - the units of the ISS            SysVal -     ETE 1.2     Ma -        232130 -      ESA       Mapping of unit code (russians) covered through
          TYPES IN DASS CATALOGUE V10   parameters in the table 1 below are incorrect. - the data    System       DRY RUN     Major       Catalogue               ECR-182 for DaSS kernel 3.5 and UMI cat14
                                        type of the ISS parameters in the table 2 below are          Validation   OF 08/08/06             UMI                     13/11/2006: Issue in investigation; impact noticed
                                        incorrect                                                                                                                 for the ETE 1.2 test on 14/11/2006
    10347 FAILURE OF TWO CONNECTIONS    During the M&C-FCC test, a connection issue occurred         SysVal -                 Ma -        232400 - Fas ROVSING    19/02/2007: 2 solutions are proposed to solve this
          OF MCW (USING DIFFERENT       when 2 clients tried to connect simultaneously to the fcc1   System                   Major       Command                 AR, during the FCC v2.4 integration: either an
          CHAINS) TO THE SAME FCC       in the same mode (real time for example). Indeed, we         Validation                           Checker                 M&C implementation, or operational procedures to
                                        tried to connect to fcc1 in simulated mode while an other                                                                 be written. 04/10/2006:In fact, 2 simultaneous
                                        user was already connected to fcc1 in the same simulated                                                                  connections to the same fcc in the same mode
                                        mode. Then the 1 connection failed, and the user saw that                                                                 should not be allowed, (maybe there is a lack of
                                        the fcc1 sta                                                                                                              information: alarm message, pop-up, message in
                                                                                                                                                                  the fcc report and to M&C).
                                                                                      14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                             JOINT AR

                                                                                                                       Context    Criticalit Configurati Entity in
Reference               Title                                       Description                            Phase      reference        y         on Item      charge                      Comments
    10352 INCONSISTENCY IN COVARIANCE        The A5 ICD provides the dispersions at injection /                                   C - Critical 290000 -     ESA
          MATRIX OF A5 ICD (DCI 10/478 01)   separation and the accuracy of the CVI diagnostic under                                           OPS
                                             the form of covariance matrix (in Cartesian and keplerian                                         definition &
                                             form). The conversion of one form into the other shows                                            prep
                                             that an inconsistency exists. For the CVI diagnostic
                                             accuracy, the matrix are not complete, correlation terms
                                             are missing.# Element of Origine : DCI 10/478 01

    10365 GROUND ALARM                       In the VCPs VCPC_STR_03_01 and VCPC_STR_03_02,                                       Ma -      292100 -     ASTRIUM       27/02/07: Will be closed in MDB R4d
          STR_GAL_TEMP_FAIL MISSING IN       the triggering conditions (i.e. conditions to use the                                Major     MDB files
          MDB R4                             concerned VCPs) contain : "This procedure shall be
                                             executed in case of the ground alarm raising
                                             STR_GAL_TEMP_FAIL (¿)", But the GAL
                                             STR_GAL_TEMP_FAIL is not defined in MDB R4.

    10369 THE GROUND ALARM                   In the VCPs VCPC_VDM_01_01 and                                                       Ma -      292100 -     ASTRIUM       06/04/2007: VDM_GAL_TEMP_FAIL is not coded
          VDM_GAL_AL_COHER AND               VCPC_VDM_01_02, the triggering conditions (i.e.                                      Major     MDB files                  because thresholds TBD.
          VDM_GAL_TEMP_FAIL ARE              conditions to use the concerned VCPs) contain : "This                                                                     27/02/07: VDM_GAL_AL_COHER is OBSOLETE.
          MISSING IN MDB R4                  procedure shall be executed in case of alarm raising                                                                      An NF-NCR-0116 was raised on VCP to delete the
                                             VDM_GAL_AL_COHER or VDM_GAL_TEMP_FAIL (¿)",                                                                               reference. VCP problem to be handled through
                                             But the ground alarms VDM_GAL_AL_COHER and                                                                                VCP ARB.
                                             VDM_GAL_TEMP_FAIL are not defined in MDB R4

    10370 THE GROUND ALARMS                  The ground alarm concerning the FU/SU ECLS, EMA and                                  Ma -      292100 -     ASTRIUM       All codable GAL specified for these FU/SU will be
          CONCERNING THE FU/SU ECLS,         WGD are missing in MDB R4.                                                           Major     MDB files                  provided, except those for which thresholds are
          EMA AND WGD ARE MISSING IN                                                                                                                                   still TBD. Partially closed in R4D.
          MDB R4                                                                                                                                                       27/02/07: Will be closed in MDB R4d
    10373 INCORRECT VALUES OF TYPE 1         During the ETE 1.2 performed on 14/11/2006, all the ISS     SysVal -     ETE 1.2     Ma -      232100 -     DLR           Corrected in Kernel 3.5, under test at DLR today
          ISS PARAMETERS, ALL ARE            type 1 parameters received were equal to 0. (i.e.           System       PROCESSE    Major     DaSS
          EQUAL TO 0.                        parameters IU0006 and IU0007 observed at 08:33 GMT          Validation   D DATA
                                             on M&C displays).                                                        PART 1
    10374 INCONSISTENCY BETWEEN ISS          During the ETE 1.2 performed on 14/11/2006, ATV-CC          SysVal -     ETE 1.2     Ma -      232130 -     DLR           Standard table refers (see e-mail from Austin) UMI
          PROCESSED DATA UNITS AND           observed discrepancies concerning the ISS parameter         System       PROCESSE    Major     Catalogue                  14
          VALUES.                            IJ0007 (RRGT00TC1002R -                                     Validation   D DATA                UMI
                                             RSMCS_SM_Inertial_Rate_X), the displayed value was in                    PART 1
                                             rad/s at ATV-CC and MCC-H sides but the DaSS unit
                                             specified was in deg/s, whereas at MCC-M side the value
                                             and the unit were in deg/s.
    10375 INCORRECT DESCRIPTION (NON-        In DaSS catalogue V11.1, the description of the 2                                    Ma -      232130 -     DLR
          PRINTABLE CHARACTERS) IN           following parameters contains non-printable characters :                             Major     Catalogue                  To be fixed in UMI 14, seems to be treated at
          DASS CATALOGUE V11.1               RSMCS_SM_XMTR_2AR_Ant,                                                                         UMI                        coordination level. OPS database issueARB-
                                             RSMCS_SM_XMTR_AKR_Ant                                                                                                     03/04/2007 : CNES to check if this AR affects the
                                                                                                                                                                       S/W performance. If not this AR is to be
                                                                                                                                                                       reclassified as minor. If yes the S/W is to be
                                                                                                                                                                       checked.
10382     2 PARAMETERS OF THE TC(3,2)        The SID_TC_DIAG and COLL_INTERV parameters of                                        Ma -      292100 -     ASTRIUM       06/04/2007 (Release note R4D): Debate has
          ARE NOT DEFINED IN MDB AS          TC(3,2) are not defined in MDB as described in ICD-                                  Major     MDB files                  already been conducted during ATV-CC 167
          DESCRIBED IN ICD-1016.             1016.The SID_TC_DIAG parameters are described as                                                                          anomaly analysis and IRN133 on ICD1016: - SID
                                             enumerated in ICD-1016 while as unsigned integer in                                                                       parameters have identical calibration curve,
                                             MDB. The COLL_INTERV parameters are described as                                                                          because no name was associated to packet
                                             unsigned integer in ICD-1016 while as enumerated in                                                                       number. Their label are therefore equal to their raw
                                             MDB.                                                                                                                      value (UI), and because IRN128A on ICD1016
                                                                                                                                                                       proposes to declare an enumerated as an
                                                                                                                                                                       unsigned integer, SID parameters have
                                                                                                                                                                       enumerated values which are UI.
                                                                                                                                                                       27/02/07: Astrium is proposing to treat it as AR
                                                                                                                                                                       167, by proposing an IRN.
                                                                                       14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          JOINT AR

                                                                                                                       Context    Criticalit Configurati Entity in
Reference              Title                                           Description                         Phase      reference        y       on Item    charge                            Comments
10383     TWO "LIST_REFERENCE" LISTS OF        The following lists of TM_VALIDITY_CONDITIONS table                                mi - minor 292100 -   ASTRIUM      CP3522 introduces MSU derived parameters in
          TM_VALIDITY_CONDITIONS TABLE         are not defined in the table TM_VALID_LIST:                                                   MDB files               Validity list, which is not compliant with ICD1034.
          ARE NOT DEFINED IN THE TABLE         LIST_REFERENCE PARAM_NAME                                                                                             IRN62 on ICD1034 has been rejected by ATVCC.
          TM_VALID_LIST.                       MSU1_TM_MSBAT_VALID                                                                                                   The 2 lists MSUi_TM_MSBAT_VALID are not part
                                               PFS_MSU1_TM_MSBAT_VALID_DER                                                                                           of MDB R4D currently.
                                               MSU2_TM_MSBAT_VALID                                                                                                   27/02/07: Open. New CP to be raised by Astrium
                                               PFS_MSU2_TM_MSBAT_VALID_DER

10384     THE TRIGGER OF THE DERIVED           The trigger of the DP                                                              Ma -     292100 -     ASTRIUM      06/04/2007 (MDB R4D release note): These
          PARAMETER                            'GNC_EULER_ANGLE_GATV_OCF_i_DER' is                                                Major    MDB files                 derived parameters have their own user defined
          GNC_EULER_ANGLE_GATV_OCF_I           'GNC_QUA_EST_J2000_GATV_TM_4' with a                                                                                  trigger parameter (see
          _DER IS NOT THE GOOD ONE.            corresponding period TM = 2s. The calculation formula                                                                 ATV_USER_DEFINED_DP_TRIGGER table)
                                               uses the trigger 'FRMS_OCF_ATT_IN_J2000', period TM                                                                   27/02/07: Action ongoing between CNES and
                                               = 30s: this is the good one that should be used.                                                                      ASTRIUM expert. Might be closed in next MDB
                                                                                                                                                                     release (R4d).
10385     SEVERAL PFS DERIVED          Several PFS derived parameters are declared not valid.                                     Ma -     292100 -     ASTRIUM       27/02/07: Open. New CP to be raised by Astrium
          PARAMETERS ARE ALWAYS        The cause is a wrong code for the derived parameters                                       Major    MDB files
          DECLARED 'NOT VALID'.        which define their validity laws. As matter of fact, it is quite
                                       strange to have the validity condition of a parameter
                                       taking as input the parameter itself. This problem of
                                       validity conditions computation is applicable for both PFS
                                       chains.
10387     LOSS OF DASS CLIENT          The DaSS client connection was lost between M&C and SysVal -                  ETE 1.2      Ma -     232100 -     DLR          ECR-178 was rejected at IOT-level. The subjected
          CONNECTION AFTER 40 MN       DaSS at Col-CC at 05:10:38 GMT on 14/11/2006 after a System                   PART 1       Major    DaSS                      ECR is to be rediscussed at GSCB level if this
                                       40 mn connection. (perhaps Time-out) This behavior of            Validation                                                   problem is to be resolved
                                       M&C connected to the DaSS is reproduceable, as far
                                       many disconnections are observed after a certain delay
                                       (1 hour in general)
10389     MANY TCS ARE FLAGGED         Many TCs are flagged "NOT_AUTHO" whereas these                                             Ma -     292100 -     ASTRIUM      06/04/2007 (MDB R4D release note): RAMS
          "NOT_AUTHO" WHEREAS THESE    TCs are part of toolbox VCPs. The detailed list is provided                                Major    MDB files                 analysis has been done on VCP in R3 reference.
          TCS ARE PART OF TOOLBOX VCPS for information in appendix (2361 occurences).                                                                                The mapping TC/VCP may have changed in R4D,
                                                                                                                                                                     and therefore the TC hazardous flags may be
                                                                                                                                                                     unconsistent with VCP R4D definition. Some TC
                                                                                                                                                                     used in VCP may be declared as NOT_AUTHO.
                                                                                                                                                                     07/03/07: When using MDB R4 flag as is in ATV-
                                                                                                                                                                     CC pre-qualification and qualification exercises,
                                                                                                                                                                     the extended mode has to be permanently
                                                                                                                                                                     activated, which makes the extended mode itself
                                                                                                                                                                     useless and therefore deletes this operational
                                                                                                                                                                     safety barrier.

10390     INCONSISTENCY BETWEEN 2 GAL In MDR R4 the 2 following GAL on DRS subsystem have                                         Ma -     292100 -     ASTRIUM      DRS_GAL_CID_BLOCKED and
          DRS                         inconsistent definitions : DRS_GAL_CID_BLOCKED and                                          Major    MDB files                 DRS_GAL_CID_DEBLOCKED not provided in
                                      DRS_GAL_CID_DEBLOCKED. Indeed, they are                                                                                        R4D, because not codable currently.
                                      concerning the same parameter (DRS_N7D_RBRDS),
                                      are always valid (IS_ALWAYS_VALID = TRUE) but have
                                      different expected values (respectively BLOCKED and
                                      DEBLOCKED).

10391     OCCURRENCE TRIGGER FOR 2             The 2 following GAL are raised quite often during ATV-                             Ma -     292100 -     EADS         to be investigated by Astrium
          PFS GAL                              CC pre-qualification tests :                                                       Major    MDB files                 09/03/07: Therefore, we recommend to change the
                                               PFS_GAL_MSU1_MSU2_ATT_RAT_STATUS,                                                                                     field 'OCC_TRIG_ON' to 2 for these 2 GAL.
                                               PFS_GAL_MSU2_MSU1_ATT_STATUS. For these 2
                                               GAL, the field 'OCC_TRIG_ON' is 1 and ATV-CC gets a
                                               temporary ground alarm when the MSU data change
                                               (alarm based on difference between MSU1 data and
                                               MSU2 data).
                                                                                     14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          JOINT AR

                                                                                                                     Context    Criticalit Configurati Entity in
Reference               Title                                       Description                            Phase    reference        y       on Item      charge                         Comments
10392     BAD LONGDUMP FUNCTION IN         According to the documentation about the DaSS API the                                mi - minor 232110 - API DLR        19/03/07: This function may have been tested and
          DASS C++ API V3.4                function UMI:longdump should retrieve the UMI as an 8-                                          DaSS                    validated on a little-endian system (typically on a
                                           bytes integer. In fact the function retrieve the UMI as a                                                               80x60) , whereas the M&C is set on a big-endian
                                           6bytes integer shift on the left in an 8 bytes integer. The                                                             system (sparc)
                                           consequence on a sparc computer is to retrieve an UMI¿s
                                           value that is 2^16 times the real UMI¿s value.

10393    UNABLE TO ESTABLISH LINK WITH During ETE5.1 final, the DG could not reach the MCC-M Oper - Oper ETE 5.1                Ma -     233000 -      OP-SOL      27/03/07: Corrected during the test. Informations
         MCC-M FROM ATV-CC DATA         drop box. The problem comes from a firewall as MCC-M                                    Major    LANS                      are correct in OPS-ICD-1CCATV-026-GSOC, but
         GATEWAY                        only accepts connection from the IP address                                                      Externe + I/F             a check has to be done if this is reflected in the
                                        (xxx.yyy.zzz.101). This address is a logical address used                                        IGS                       ESA GS to MCC-M ICD.
                                        by partners to connect to the "active" DG (nominal or
                                        redundant), whereas physical IP adress is used when
                                        connection is initiated by ATV-CC.
10394    4 PACKETS CONTAINED ISS        During the ETE 12 FINAL of 15/02/2007 (processed data Oper - Oper ETE 1.2               Ma -     232100 -     PS/SSC
         PARAMETERS DATED FROM          test), several ISS data are received with the old datation        FINAL                 Major    DaSS
         06/01/1980 INTO THE M&C DEX_IN 06/01/1980 according to the M&C Dex_In analysis. These
                                        ISS parameters come from MCC-H and 4 packets only
                                        are concerned, received at the following times: 04h35:49,
                                        05h09:41, 08h45:07, and 08h58:40, as shown into the file
                                        1980.txt.
10395    ERROR ON CALCULATION           The current derived parameters formulas for those DP                                    Ma -     292100 -     ASTRIUM
         FORMULA OF                     return too many times the error value 400 whereas                                       Major    MDB files
         GNC_EULER_ANGLE_GATV_OCF_ correct values can be computed.
         DER
10396    SEVERAL PRO/PFS DERIVED        The UCL definition file for the following derived                                       Ma -     292100 -     ASTRIUM
         PARAMETERS COME FROM AN        parameters is correct but the XML conversion (used by                                   Major    MDB files
         INCORRECT CONVERSION OF THE M&C) is not :
         UNIT OF THE PARAMETERS         PWS_PCDUi_RB_TEMP_INCOHERENT_DER i;
                                        PRO_PDEi_DELTAP_xxx i;
                                        PRO_MMH/MON_PMEAN_DER;
                                        PRO_PCA1/PCA2_PHEL_VALID_DER;
                                        PRO_MON/MMH_VALID_DER;
                                        PRO_TANK_PRESSURES_DOMAIN_DER;
10397    ERROR IN                       The GNC_RANGE_RANGEC_DER parameter uses as                                              Ma -     292100 -     ASTRIUM      12/06/07: Nouvelle FA faite sur le même sujet
         GNC_RANGE_RANGEC_DER           trigger parameter GNC_RGPS_POS_EST_LVLH_3                                               Major    MDB files                 (83973): une des 2 sera withdrawn à la prochaine
                                        which is downloaded only in FFI_1 and FFI_2. Since in S3                                                                   ARB
                                        the FFI_3 is commanded, starting from this point the DP is
                                        no more computed. Before S3, this derived parameter
                                        uses as inputs, GNC_RGPS_POS_EST_LVLH_i and
                                        GNC_POS_CMD_LVLH_i.

10398    NAT SERVICE FOR WEB TOOLS         The ATV-CC must use some web tools provided by our            Oper - Oper ETE 5.1   Ma -      246100 -     OP-SOL
         ACCESS                            partners (ESA and NASA).Those tools must be available                     PREPARATI Major     LANs
                                           from all OAW.As described by "Appendix E ,Col-CC to                       ON
                                           ATV-CC ICD"(ICD-026-GSOC), the IGS provides 2 IP
                                           address for these accesses, but the NAT service is not
                                           yet operational at CNES.
10399    6 TC PARAMETERS HAVE A            The 6 following TC parameters of                                                     Ma -     292100 -     ASTRIUM
         DEFAULT VALUE OUT OF THE          ATV_TC_PACKET_CONTENT have a default value out                                       Major    MDB files
         INTERVAL DEFINED BY RAW_MIN       of the interval defined by RAW_MIN and RAW_MAX :
         AND RAW_MAX (IDENTICAL            GNC_LLC_CONFIG_AN_DRIFT_DTGi ( i= 1 to 4),
         DECALIBRATION)                    ACCA_LLC_CALIB,
                                           GNC_LLC_AADE_OMEGA_MAX_ADU
                                                                                       14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                            JOINT AR

                                                                                                                         Context    Criticalit Configurati Entity in
Reference              Title                                           Description                      Phase           reference        y       on Item    charge                        Comments
10400     A TC PARAMETER HAS A DEFAULT        The following TC parameter of                                                         Ma -       292100 -   ASTRIUM
          VALUE OUT OF THE INTERVAL           ATV_TC_PACKET_CONTENT has a default value out of                                      Major      MDB files
          DEFINED BY MIN AND MAX              the interval, after a polynom decalibration, defined by
          (POLYNOM DECALIBRATION)             RAW_MIN and RAW_MAX :
                                              MSU_PSD_INV_ACM_23A_SET_12
82797    Many disconnections from FSF TM      During the SVT2B tests, too many disconnections of TM SysVal -            SVT2B       C - Critical 233000 -
         flow at 64 kbps rate due to IGS      flow at 64 kbps were observed, due to IGS instability.  System                                     LANS
         bandwidth instability                Therefore this network issue involved intermittent      Validation                                 Externe + I/F
                                              connections to the TM flow on the MCWs.                                                            IGS
                                                                                                                                                 IGS
                                              Analysis on 09/11/2006:
                                              DLR investigated on this serious issue to solve the TM
                                              flow stability at 64 kbps. Apparently several ISDN parts
                                              have to be allocated to allow TM receiving at 64 kbps, but
                                              during the tests the IGS configuration was not correct as
                                              far the bandwidth was insufficient. However the use of
                                              ISDN link is not an operational way to get TM/TC flow; so
                                              this ISDN Bchannel issue should not occur. This is a
                                              lesson learnt for next SVT4C: switch tests from 8 kbps to
                                              64 kbps shall be performed to check the IGS status.


82874    Losses of TC link between ATV-CC     The TC Q013_0803 of step 9 was blocked on the TC             SysVal -     SVT2B       C - Critical 230000 -              01/06/07 : CNES System team check for System
         and LMX                              stack due to a loss of TC link.                              System                                System &              ARB-OMT :The Keep Alive implementation should
                                              This problem of losses of TC link occured several times      Validation                            Interfaces            correct this problem. To be checked after the DM
                                              during the SVT2B campaign, but has still not been                                                  v115                  ATV-CC 469 implementation
                                              explained.

                                              Conf used:
                                              at ATV-CC side: M&C v5.1.1, FCC v2.3, ODB based on
                                              MDB R3 patch and TTFEE v3.0 / at LMX side: FAS v3.0
                                              missionized with MDB BV41_D3 (refer to ATV-AS-IIR-
                                              1258 1C)

                                              Analysis:
                                              In fact, the low level of FSF RF signal was strongly
                                              suspected to make the TC link fail, but after some
                                              investigations at ASTRIUM-ST side on FSF, the results
                                              seem to show that it would not be the cause of the
                                              anomaly.

82879    Vehicule behaviour during tumbling   During re entry phase, ATV doesn‟t keep his tumbling         Oper - Oper PO_REEN_ Ma -            230000 -               Point adressed in Top Technical Question meeting
         unexpected-SIF N°3                   motion and it switch to survival mode before the end of                  N_1      Major           System &               (TTQ). The Flight Segment will investigate reasons
                                              the OMP “deorbitation_boost_2".                                                                   Interfaces             for high angular rates, and if the tumbling be shall
                                                                                                                                                                       maintained in re-entry baseline
                                              The SIF enclosed is created to gathered all the
                                              information obtained by VET team during the investigation
                                              done after the Reentry Pre-Qualification Test .
                                                                                                  14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                            JOINT AR

                                                                                                                               Context       Criticalit Configurati    Entity in
Reference                Title                                     Description                         Phase                  reference          y         on Item      charge                          Comments
83388     Dirty TC Frames during OMP loading Dirty TC frames were received during OMP loading during SysVal -                SVT4C                      230000 -                   01/06/07 : CNES System team check for System
                                             CAM test 1 (at 15.50 sim time).                         System                                             System &                   ARB-OMT : ASTRIUM test means suspected. Low
                                                                                                     Validation                                         Interfaces                 level of RF link. Successfully tested with PFM. To
                                             Alarm TC_FAR_Error displayed in the event page ( see                                                                                  evaluation the need to a robustness test and to
                                             attached document ).                                                                                                                  secure transmission ( PUDACK setting on or not ).
                                             OMP TC fails in the same time during the sending in AD                                                                                S-NRB 7004 (19/03/07): Mail de Y.Domaine
                                             mode without PUD ack.                                                                                                                 transmis / Aspect COP protocol completement
                                                                                                                                                                                   dédouané.
                                                    Astrium remarks :
                                                    The FAR and the CLCW were analysed at the com
                                                    function level. The behaviour of the functions was
                                                    nominal. CNES has sent the relevant CLTU log files to
                                                    ASTRIUM. ASTRIUM saw some anomalies in this log
                                                    data and joint CNES/ASTRIUM investigations are
                                                    continuing

                                                    Note: that no FCC errors were seen at this time during the
                                                    test.
83624       GPS PVT measurements during             The SVT_LEOP_3 test (02/04/2007) was conducted with Oper - Oper                          mi - minor 230000 -                   01/06/07 : CNES System team check for System
            warm start with real receivers (Jules   the reel GPS receivers on Jules Verne.                                                              System &                   ARB-OMT : "Complementary investigations waiting
            Verne)                                  They did not converge at the same time, but with the                                                Interfaces                 Validity Condition meeting rescheduling. Analysis
                                                    same behaviour :                                                                                                               in progress on the GPS measurements by System.
                                                                                                                                                                                   Waiting for ASTRIUM feed-back"
                                                    - the GPS date before convergence is 2661.0 but the
                                                    "real" date was earlier. The date was correct for a given
                                                    receiver as soon as measures (yet not set to valid) begun
                                                    to arrive for this receiver. This was not correclty managed
                                                    by the orbit restitution tool, not permitting a restitution with
                                                    only receiver "2" measurements.

                                                    - when measures begin to arrive (say at T0), the 6
                                                    parameters of position and velocity are constant during
                                                    several steps, until the validity flag is set to 1 (say at T1).
                                                    Apparently, the values are correct for the dates T0 and T1
                                                    (and the ones following T1), but not between T0 and T1
                                                    because they "stay" at their initial value (the first one, at
                                                    T0).


83631       Bad TC warm start computed during       During the SVT LEOP tests, the TC warm start computed SysVal -           SVT4C           C - Critical 230000 -                 Astrium test means are suspected
            SVT LEOP tests                          with the FDS means (T-FDB) and loaded to ATV has not System              LEOP                         System &
                                                    allowed the vehicle to hang GPS constellation. The    Validation                                      Interfaces
                                                    results obtained by FDS are so far from the ones                                                      v120
                                                    expected.
                                                    For information the date of the WS for FDS is
                                                    20:15:51.450 + 2753 = 21:05:44.450
                                                                                        14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                      JOINT AR

                                                                                                                       Context  Criticalit Configurati   Entity in
Reference                 Title                                       Description                         Phase       reference     y         on Item     charge                        Comments
83680     Differences between AST and CNES   Just before the SVT4C TPO & CAM , CNES noted that          SysVal -     SVT4C TPO Ma -        230000 -                  01/06/07 : CNES System team check for System
          MCI values and Mass properties     there was difference in the ATV-CC and ASTRIUM values System            & CAM      Major      System &                  ARB-OMT : Request for the initial Mass and the
                                             of the PFM initial mass and the Ixx component of the ATV Validation                           Interfaces                Ixx component of the ATV Inertia Tensor values
                                             Inertia Tensor. These discrepancies did not cause the                                         MCI values                from ASTRIUM to check against ATV-CC side
                                             start of the tests to be delayed but it was suspected that                                                              ones.
                                             the inertia tensor difference could affect the attitude
                                             dynamics of ATV during the CAM. The performance of the
                                             CAM is under investigation to see if there were any
                                             affects on the PFM attitude dynamics. ASTRIUM stated
                                             that there were no differences in the affected mass
                                             property values between the FSF joint dry run (of 30th
                                             January 07) and this test on the PFM.

83685      Bad data for RSMM parameters      During JIS EtE config1, the 19 RSMM parameters were          Oper - Oper JIS EtE #1   Ma -    232100 -
           (received as E1 at ATV-CC)        received at ATV-CC with:                                                              Major   DaSS
                                             - date & time are incorrect: refer to anomaly AR 83686 for                                    RSMM ISS
                                             incorrect russian ISS PD timestamps.                                                          PD
                                             - type is inconsistent and changes from one occurrence to
                                             another
                                             - unit index is false
                                             - values format is incorrect, it should be a floating point.

                                             Please see attached files extracted from our DeX_In.
                                             The explanation of the column is the following:
                                             Name_of_dexIn_file : UMI | timestamp_date |
                                             timestamp_time | type | unit_index | status_bit_field |
                                             value_state | number_of_octet_for_the_value |
                                             value_in_hexa
                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                       JOINT AR

                                                                                                                       Context  Criticalit          Configurati      Entity in
Reference                  Title                                         Description                       Phase      reference      y                on Item         charge     Comments
83686     Bad dates for russian ISS PD (E2        During JIS EtE config 1,                               Oper - Oper JIS EtE #1 Ma -                232100 -
          parameters)                             E2 parameters, simulated by RSMM, were received from                          Major               DaSS
                                                  MCC-M with bad timestamps. Date & time were not the                                               russian ISS
                                                  date & time of the simulation as expected but the                                                 PD
                                                  following behaviour was observed depending on software
                                                  parameters or harware ones:

                                                  - For Hardware Data (for example umi = e20000003167,
                                                  ROS 167)
                                                  The day and the hour of the TimeStamp are in ground
                                                  Time GMT (11th of April)

                                                  - For Software Data (for example umi = e20000003134,
                                                  ROS 134)
                                                  The day of the TimeStamp is in ground Time GMT (11th
                                                  of april) but the hour looks like in simulated time

                                                  See attached file extracted from the DeX_In.
                                                  The explanation of the column is the following:
                                                  Name_of_dexIn_file : UMI | timestamp_date |
                                                  timestamp_time | type | unit_index | status_bit_field |
                                                  value_state | number_of_octet_for_the_value |
                                                  value_in_hexa

                                                  During the Backup of this test, run on 24/04/07, the
                                                  ground date was still received instead of the simulation
                                                  date (for MCC-M only) but the timestamp was also
                                                  changed by MCC-M during the test.
83687      Service disconnection from Central     During JIS EtE config 1,                                     Oper - Oper JIS ETE #1    Ma -       232100 -
           DaSS not seen at Col-CC                                                                                                       Major      DaSS
                                                  At ATV-CC, the ATV facility has been disconnected from                                            DaSS
                                                  central DaSS but the DaSS server was still seeing the
                                                  connection.
                                                  For information, when trying to connect again to central
                                                  DaSS server, a CORba message was displayed and the
                                                  TTS was not responding anymore.
83696      OSTPV Data not updated at Col-CC       During JIS EtE Config 1,                                     Oper - Oper JIS EtE #1    Ma -       232000 -
                                                  it was possible to access to OSTPV website located at                                  Major      Functional
                                                  NASA and at Col-CC.                                                                               I/F
                                                                                                                                                    WebTools
                                                  On the Nasa website, data were available, but the Col-CC
                                                  website did not contain any.

                                                  After discusion, it seems that a manual procedure to
                                                  duplicate data from Nasa to Col-CC had to be performed.

83729      FCC rejects 4 of the 5 possible values The parameter DPS_SPT_PROFILE_ID of buffers                  Prep - Prep PO_PHAS_      C - Critical 232400 - Fas
           for the TC                             CMS_CONTEXT_BUFFER_1 and                                                 C_1                        Command
           "LOAD_TC_SORTIE_SURVIE"                CMS_CONTEXT_BUFFER_2 has got 5 possible values                           preparation                Checker
                                                  into the MDB (current MDB is the MDB R4B):                                                          FCC
                                                  DEPARTURE=0, ATTACHED=1, RDV=2,
                                                  FREE_FLIGHT=3 and CONTEXT=4.
                                                  However, while checking the TC
                                                  "LOAD_TC_SORTIE_SURVIE" (R127_0602), the FCC
                                                  does not allow any other value than the value "0" for this
                                                  parameter DPS_SPT_PROFILE_ID, and consequently
                                                  rejects the TC sending.
                                                                                                   14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                     JOINT AR

                                                                                                                                   Context  Criticalit Configurati Entity in
Reference                  Title                                                Description                             Phase     reference     y        on Item    charge                       Comments
83738     A StateCode Curve has some                    The following Curve_ID                                       Prep - Prep MDB R4-D Ma -         292100 -   ASTRIUM
          identical STATE_CODE values in                "\ATV\FS\VEHICLE\TMTC\SW_DATA\CALIB\T_BUFFER\                            delivery   Major      MDB files
          contradiction with the definition of the      NAME" has some identical STATE_CODE values in
          unique key of ATV_STATE_CODE                  contradiction with the definition of the primary key (unique
          table                                         key defined with CURVE_ID and STATE_CODE).

83739        15 Curves are defined twice in             The 15 following Curve_ID (see attached file) of               Prep - Prep MDB R4-D   Ma -      292100 -     ESA
             contradiction with the definition of the   ATV_CONV_CURVE are defined twice in contradiction                          delivery   Major     MDB files
             unique key of ATV_CONV_CURVE               with the definition of the primary key (unique key defined
             table                                      with CURVE_ID).
83829        Values of PDE voltage and current          After the ACS boost (as part of the TPO), the PDE3 and         SysVal -     SVT4C     Ma -      230000 -     OP/BAR     Waiting Astrium information
             not equal to 0 in HK Telemetry after       PD4 were switched off. The status changed accordingly,         System       TPO&CAM   Major     System &                01/06/07 : CNES System team check for System
             the ACS boost                              but looking at the detailed telemetry in the PDE Monitoring    Validation                       Interfaces              ARB-OMT : Question addressed to ASTRIUM :
                                                        HK TM PRO_PDE1/2/3/4_VOLT didn‟t go to 0 (it stayed                                             HK TM                   simulation limitations ?
                                                        on a value of 0.251 V) and PRO_PDE1/2/3/4_CURNT
                                                        0.065 A.
                                                        PDE4 went correctly to 0V, 0A.
                                                        Looking at MP13_POWER SUPPLY – CHAIN3_V01C00
                                                        we can see a residual voltage on PI301 and PI302 (V=
                                                        0.039 V).
                                                        On MP00_POWER SUPPLY_OVERVIEW_V01C00 on
                                                        the row ISS power there all 0 W except for Chain3 where
                                                        PW303_ is 2.118W.
                                                        On pwr chain 1 off-nominal voltage displayed for TPS1.
83831        Wrong MSU parameter instantiation          During the SVT4C CAM Demo, the vehicle did not                 SysVal -     SVT4C     C - Critical 230000 -    OP/BAR   01/06/07 : CNES System team check for System
             involving a wrong ATV MSU Sun              switched correctly to the MSU SP mode.                         System       TPO&CAM                System &             ARB-OMT : operator error during the manual
             Pointing after the CAM                                                                                    Validation                          Interfaces           process to create instanciation file.
                                                        This wrong behaviour was due to the wrong instantiation                                            FDS-VET I/F
                                                        of the third MSU quaternion parameter
                                                        (MSU_Q_J2000_SASP_SET_3) into the TC
                                                        PFS_LLC_CONFIG_TABLE_BLOCK7. Indeed the value -
                                                        0.670438379 was set instead of the value 0.670438379.
                                                        Consequently the TC for the MSU table uploading was
                                                        badly generated.

                                                        A solution to avoid this kind of typo is to create an
                                                        instantiation file directly sent by FDS via the DG, as it is
                                                        usually done in the OMP and FCPs instaciation process.
                                                        This solution will secure the process, which is currently a
                                                        manual process. It shall take into account the 2 different
                                                        cases of instantiation used during the mission: the MSU
                                                        tables uploading and the GTOD reference quaternion
                                                        updating (FCPN_GPS_06).
                                                                                              14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                               JOINT AR

                                                                                                                        Context  Criticalit       Configurati Entity in
Reference                  Title                                          Description                       Phase      reference      y            on Item     charge     Comments
83833     Difference of dates for the ISS russian During the replay of the JIS ETE RVD on 24/04/07, an    Oper - Oper JIS ETE#1- C - Critical    232100 -    ESA
          parameters (E2)                         issue on E2 parameter IZ0272 (UMI e20000003221) was                 BACKUP                     DaSS
                                                  observed : the TimeStamp and the value showed a                                                ISS
                                                  discontinuity due to the change of value at MCC-M side,                                        Processed
                                                  but the date also changed from 24/04/07 to 23/04/07 :                                          Data

                                                    TimeStamp Value
                                                    Date Time
                                                    24/04/2007 06:46:27.187 00:18:23.007
                                                    24/04/2007 06:46:31.187 00:18:27.005
                                                    24/04/2007 06:46:35.187 00:18:31.005
                                                    24/04/2007 06:46:38.984 00:18:35.003
                                                    24/04/2007 06:46:43.183 00:18:39.003
                                                    24/04/2007 06:46:46.984 00:18:43.003
                                                    24/04/2007 06:46:55.183 00:18:51.005
                                                    23/04/2007 23:42:40.375 23:42:52.037
                                                    23/04/2007 23:44:56.355 23:45:09.161
                                                    23/04/2007 23:46:36.375 23:46:49.037
                                                    23/04/2007 23:47:36.140 23:47:47.973
                                                    23/04/2007 23:49:16.554 23:49:29.097
                                                    23/04/2007 23:50:48.324 23:50:59.933
                                                    23/04/2007 23:54:44.304 23:54:57.011
                                                    23/04/2007 23:56:00.519 23:56:13.033

                                                    The change of date has occurred apparently at Col-CC
                                                    side and shall not occur in operation, if the timestamp
                                                    changed to older values (e.g. due to TM holes).

83837       Russian ISS TM labels contain cyrillic Some UMI given into the xls file attached have wrong         Prep - Prep M&C v6.2     Ma -    232130 -    ESA
            characters                             labels into the state code column: cyrillic characters are               context      Major   Catalogue
                                                   mixed with latin ones.                                                                        UMI
                                                                                                                                                 Catalog UMI
                                                    However the M&C cannot display these kinds of labels.                                        v12d2

83839       Some ISS parameters have not been Some ISS parameters sent by RSMM to Col-CC were not Oper - Oper JIS ETE #1- C - Critical 232100 -              OP/AR
            received at all from RSMM         received during the test, and are given into the attached       BAKUP                    DaSS
                                              list.                                                                                    ISS
                                                                                                                                       Processed
                                              Among these parameters, 3 distinct kinds were observed:                                  data
                                              - E1 parameter (only 1) = ISS parameters from Houston
                                              but simulated by RSMM
                                              - E2 mapped parameters (19) thought to be received like
                                              the mapped E1
                                              - Real E2 parameters (6 "normal" russian parameters)
                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                               JOINT AR

                                                                                                                            Context  Criticalit Configurati Entity in
Reference                Title                                          Description                             Phase      reference      y         on Item   charge    Comments
83840     Type 1 ISS parameters cannot be         During the JIS ETE test, none type 1 ISS parameter was      Oper - Oper JIS ETE#1- C - Critical 232100 -  DLR
          decommuted at ATV-CC side               decommuted at ATV-CC.                                                   BACKUP                  DaSS
                                                  It seems to be a known AR at Col-CC side, as these                                              ISS
                                                  parameters are badly coded.                                                                     Processed
                                                                                                                                                  data
                                                  Here is the list of these type 1 parameters:


                                                  IU0003 e1000004ac1e 1 Second LADP06MD2378W
                                                  USGNC_PS_Pointing_Coarse_Time_Tag
                                                  CDT_PS_PDtimetagCoarse
                                                  IU0006 e1000004aced 1 Millisecond LADP06MDQ006W
                                                  USGNC_GPS1_Deterministic_Nav_Time
                                                  STS_GPS1_NavStateTimDetermin
                                                  IU0007 e1000004ad0b 1 Second LADP06MDQ452W
                                                  USGNC_GPS1_GPS_Time STS_GPS1_GPSseconds
                                                  IU0008 e1000004ad0f 1 Millisecond LADP06MDY006W
                                                  USGNC_GPS2_Deterministic_Nav_Time
                                                  STS_GPS2_NavStateTimDetermin
                                                  IU0009 e1000004ad2d 1 Second LADP06MDY452W
                                                  USGNC_GPS2_GPS_Time_Seconds_Since_06Jan80
                                                  STS_GPS2_GPSseconds
                                                  IU0010 e1000004ada8 1 Second RRGT00TC2014W
                                                  USGNC_RS_SM_Att_And_Rate_Coarse_Time_Tag
                                                  CDT_RS_RussianAttandRateTimeTagCoarse
                                                  IU0011 e1000004ada9 1 Second RRGT00TC2025W
                                                  USGNC_RS_SM_State_Coarse_Time_Tag
                                                  CDT_RS_RSOrbStateTimeTagCoarse




83841      Incorrect ISS attitude data received   During the JIS ETE test, the ISS attitude TM in J2000 was                            C - Critical 232100 -
           through RSMM processed TM              received only once, and then the values and the dates                                             DaSS
                                                  were frozen. It is important to note that the TM was                                              ISS
                                                  received at the same time that the change of date by                                              Processed
                                                  MCC-M (at 06:46:56 and from 24/04 to 23/04/07).                                                   data

                                                  Concerning the ISS attitude in LVLH reference, the TM
                                                  was also incorrectly received: the same data have been
                                                  resent 400 times (same values, same dates).
83842      KURS data received frozen from S3      After the S3 point (at 250 m from ISS), the KURS data       Oper - Oper JIS ETE #1- Ma -        232100 -
           up to docking                          received from RSMM were frozen. The same data were                      BACKUP      Major       DaSS
                                                  received (value/date).                                                                          ISS
                                                                                                                                                  Processed
                                                                                                                                                  TM
83843      Problems on video transmitted from     During the JIS ETE test, the video received of ATV and      Oper - Oper JIS ETE#1-   Ma -       232000 -
           MCC-M to ATV-CC                        ISS had the 3 following anomalies:                                      BACKUP       Major      Functional
                                                                                                                                                  I/F
                                                  - Right and left parts of the video was truncated                                               IGS Video
                                                  - At 09:04 (simu time) the video backgroud image was
                                                  slightly blue colored
                                                  - A frozen image was observed from 09:06 to 09:16
                                                                                      14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                              JOINT AR

                                                                                                                       Context  Criticalit   Configurati    Entity in
Reference                Title                                        Description                          Phase      reference      y         on Item       charge                        Comments
83846     Wrong emission of processed data      During the last JIS ETE, the processed data whose UMI is Oper - Oper JIS ETE    Ma -         232130 -                   This parameter has been said to be incorrectly
          type 11                               E20000003116 has been received with different DaSS                   backup     Major        Catalogue                  assigned to a dass type 11 instead it should be a
                                                data type (only 11 should have been received):                       24/04/07                UMI                        dass type 2.
                                                                                                                                             DaSS UMI
                                                E20000003116 2007/04/24 04:47:12.988 Data Type                                               Catalogue
                                                Index:69                                                                                     v12d2
                                                E20000003116 2007/04/24 04:47:24.808 Data Type
                                                Index:52
                                                E20000003116 2007/04/24 04:47:48.605 Data Type
                                                Index:51
                                                E20000003116 2007/04/24 04:47:56.605 Data Type
                                                Index:51
                                                E20000003116 2007/04/24 04:48:16.003 Data Type
                                                Index:34
                                                E20000003116 2007/04/24 04:48:23.804 Data Type
                                                Index:121
                                                E20000003116 2007/04/24 04:48:47.402 Data Type
                                                Index:69
                                                E20000003116 2007/04/24 04:48:51.000 Data Type
                                                Index:51
                                                E20000003116 2007/04/24 04:48:55.000 Data Type
                                                Index:52
                                                E20000003116 2007/04/24 04:49:02.402 Data Type
                                                Index:51
                                                E20000003116 2007/04/24 04:49:10.398 Data Type
                                                Index:233
                                                E20000003116 2007/04/24 04:49:14.199 Data Type
                                                Index:51
                                                E20000003116 2007/04/24 04:49:53.578 Data Type
                                                Index:48
                                                E20000003116 2007/04/24 04:49:57.574 Data Type
                                                Index:47
83847      FCC Error messages with TC (18,4),   E20000003116 2007/04/24 04:50:01.574 DataTC (18,4), Integ -
                                                During the integration test M&C-FCC, several Type                  M&C V6.1.3- C - Critical 292100 -       ASTRIUM      Comments from Klaus Ludwig on 22/05/07: "Dear
           (8,3) and (2,1)                      (8,3) and (2,1) returned an error message of type   Integration    FCC V2.5.0-              MDB files                   all, plesae find below the analysis from Ziv, which
                                                "ALARM_ID" and "range min and max" (see the error                  MDB R4-D                 TC                          confirms my assumption. There are 2 possibilities:
                                                message file and stack files associated).                                                   parameters                  1. Either ATV-CC accepts the discrepancy
                                                For Example :                                                                                                           between the MDB and FAS/FCC. I would
                                                We tried to send one TC(8,3)with the command                                                                            recommend this only, if the partition of the alarm ID
                                                V_MC_AC_YS_5 and following parameters :                                                                                 range is properly documented in an OPS
                                                ALARM_ID_O1=ACCA_AL_ACM1,                                                                                               document (note: FAS ADD is not suficient) 2. The
                                                AUTHO_FLAG_O2=AUTHO,                                                                                                    MDB is updated with the relevant subranges for
                                                ENABLE_STATUS_O3=ACCA_CALIB_ENABLED                                                                                     each concerned TC. This would be an ATV-CC
                                                The error message produced by FCC was:                                                                                  call.
                                                "V_MC_AC_YS_5(18.4).ALARM_ID = 1, out of                                                                                cheers Klaus"
                                                T_ALARM_ID_TO_PROX_ALARM_TAB'Range, detected
                                                in PROX_TRANSITION.S_SC_AUTHO_AL 1, Min = 101,
                                                Max =111"
                                                but the PROX is not concerned by this TC!!
                                                                                         14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                       JOINT AR

                                                                                                                       Context  Criticalit Configurati    Entity in
Reference                 Title                                       Description                           Phase     reference     y        on Item       charge                         Comments
83881     Wrong ISS simulated quaternion      During the last dry run test for the Rendez-Vous test (dry Prep - Prep OQ_RVD_N C - Critical 2A1100 -                   01/06/07 : CNES System team check for System
          values received by the M&C from the run OQ-RDV-N1) the values for the following quaternions                _1                    AGCS                       ARB-OMT : Covered by SPR 439 / should be
          AGCS                                has been assessed to be wrong at FDS sub-system from                                                                    corrected in the next AGCS delivery scheduled en
                                              an M&C point of view :                                                                                                  of june.
                                              - CDT_RS_RussianlnertAttQ(x) (4 parameters) ISS
                                              Attitude quaternion as ISSA in J2000 reference frame
                                              - CDT_RS_RussianLVLHAttQ(x) (4 parameters) change
                                              coordinate quaternion from LVLH reference frame to
                                              ISSA J2000
                                              with x = 0..3

                                                Those parameter values are coherents between M&C
                                                and its sub-systems. Therefore the wrong values are
                                                coming from the AGCS simulation.

                                                The FDS and GMS subsystems have been unable to treat
                                                these parameters due to their values.

                                                Preliminary investigation:
                                                Vincent Guillard from the AGCS team has discovered that
                                                the quaternions simulated by the AGCS were in a
                                                different reference frame as the ones expected by the
                                                M&C.
                                                Those two simulated quaternions were related to RSA
                                                reference frame instead of ISSA.
                                                So far, it seems that the problem is coming from the
                                                AGCS specification which is stating RSA as the reference
                                                frame instead of ISSA as stated in the received ISS
                                                processed TM (UMI Catalogue description).
                                                For information : Astrium has just raised an SPR (SPR
                                                439) AGCS to fix tje problem internally for R4.3 delivery
83887       Reference Frame computation         (End ofSVT_LEOP test dated on the 02/04/2007, the Orbit SysVal -
                                                During June)                                                           SVT4C        Ma -    230000 -     SB/MS        01/06/07 : CNES System team check for System
                                                Determination produced an ephemeris from Pseudo-          System       LEOP         Major   System &                  ARB-OMT : It should be addressed in a dedicated
                                                Ranges measurements which was compared to the             Validation                        Interfaces                meeting on the 6th of june with Esa ASTRIUM
                                                "reference" one, i.e. the Astrium ephemeris.                                                v120                      attendance.

                                                The result of this comparison is a bias along-track of
                                                around 110 meters, and an oscillation in the out-of-plane
                                                direction of about 30 meters.

                                                This may be due to a difference in computation of the
                                                transformation from ECEF to J2000 : at ATV-CC, the
                                                difference between UT1 and UTC is not taken into
                                                account.

                                                The SVT requirements 741.C2, 758.C4 and 770.C4 are
                                                not fulfilled because of this problem.
                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          JOINT AR

                                                                                                                             Context    Criticalit Configurati    Entity in
Reference                  Title                                      Description                     Phase                 reference        y        on Item      charge                      Comments
83888     time shift between FRMS OCF (in TM) During SVT LEOP and SVT TPO-CAM, we performed the SysVal -                                Ma -       230000 -                   01/06/07 : CNES System team check for System
          and OCF ground reference            monitoring of OCF FRMS (in TM) and the reference OCF System                               Major      System &                   ARB-OMT : To be checked with FDS team.
                                              (predicted on ground with T-OCF). The comparison was Validation                                      Interfaces
                                              performed during several periods of the test, but we                                                 v120
                                              always observed the same behaviour : the two curves are
                                              shifted by a constant time value (around 1s), which can
                                              lead to an error of 0.1 deg in yaw.
                                              The impact is not negligible considering the associated
                                              FDI : OCF FAS validity and OCF propagation monitoring.

                                                 If this delay is taken into account before T-GNC process,
                                                 the OCF error is cancelled (residual error less than 5e-13
                                                 deg)

                                                 So, our conclusion is that the OCF FRMS data present in
                                                 TM are not correctly dated. The investigations indicate
                                                 that the error between FRMS OCF and on ground OCF
                                                 reference is due to:

                                                 - the FRMS OCF attitude given in TM is associated to the
                                                 TM packed time ,
                                                 while it should be the FRMS OCF computation time.

                                                 So, to cancel this systematic error, 2 values are required :
                                                 - an estimation of the delay (between FRMS OCF
                                                 computation time and OCF FRMS TM packed time ),
                                                 - the dispersion associated to this delay,

                                                 see SVT reports.




83899      Incompatibility between polynomial     The following parameters (see attached file) have             Prep - Prep MDB R4-D    Ma -      292100 -       ASTRIUM
           calibration and decalibration for some different RAW values after application of                                 delivery    Major     MDB files
           TC parameters                          calibration/decalibration curves.

                                                 Note : The values used in the attached table correspond
                                                 to RAW_MAX values, but analysis has also been done
                                                 with RAW_MIN or other values and same discrepancies
                                                 has been noticed.
83972      12 GALs DRS in inventory as coded     The following GALs are identified in GAL_ inventory but        Prep - Prep MDB R4-D    Ma -      292100 -       ASTRIUM
           but not delivered in R4D              have not been received                                                     delivery    Major     MDB files
                                                 :DRS_GAL_DVG1_CHANNELS_CONSISTCY
                                                 DRS_GAL_DVG2_CHANNELS_CONSISTCY
                                                 DRS_GAL_DNG_CHANNELS_CONSISTCY
                                                 DRS_GAL_DNPG_CHANNELS_CONSISTCY
                                                 DRS_GAL_DDG1_CHANNELS_CONSISTCY
                                                 DRS_GAL_DDG2_CHANNELS_CONSISTCY
                                                 DRS_GAL_DVO1_CHANNELS_CONSISTCY
                                                 DRS_GAL_DVO2_CHANNELS_CONSISTCY
                                                 DRS_GAL_DNO_CHANNELS_CONSISTCY
                                                 DRS_GAL_DNPO_CHANNELS_CONSISTCY
                                                 DRS_GAL_DDO1_CHANNELS_CONSISTCY
                                                 DRS_GAL_DDO2_CHANNELS_CONSISTCY
                                                                                   14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                       JOINT AR

                                                                                                                    Context  Criticalit Configurati Entity in
Reference                  Title                                  Description                            Phase     reference     y        on Item    charge                        Comments
83973     The parameter                     The condition formula of derived parameter                Prep - Prep MDB R4-D Ma -         292100 -   ASTRIUM      Will be temporarly modified at ATV-CC as a
          GNC_RANGE_RANGEC_DER is not       GNC_RANGE_RANGEC_DER do not consider following                        delivery   Major      MDB files               workaround, waiting for next MDB delivery
          computed in all the GNC mode in   cases :
          which it could be computed        GNC_CURRENT_GLOBAL_MODE = $HOM_YS
                                            GNC_CURRENT_GLOBAL_MODE = $SLW_S2
                                            GNC_CURRENT_GLOBAL_MODE = $SLWS2AUT
                                            GNC_CURRENT_GLOBAL_MODE = $S2SK_YS
                                            As a consequence the parameter is not computed in
                                            these GNC mode.
84094     Unexpected consumption of MMH     Written by : A.Noirhomme                                  SysVal -     SVT4C_RDV Ma -      230000 -
          and MON                                                                                     System                 Major     System &
                                            At the beginning of the SVT RDV joint test, ATV-CC        Validation                       Interfaces
                                            observed that the consumed mass of MMH and MON in
                                            tanks HZ and LZ were not in line with what was expected
                                            :

                                            Parameter Expected value SVT value
                                            PRO_MASS_MMH_HZ_10 167.50 kg 0.166311 kg
                                            PRO_MASS_MMH_LZ_10 167.50 kg 0 kg
                                            PRO_MASS_MON_HZ_10 276.45 kg 0.271981 kg
                                            PRO_MASS_MON_LZ_10 276.45 kg 0 kg


                                            On the HZ tanks, the consumption was about 1/1000 of
                                            what was expected.
                                            On the LZ tanks, the initial consumption had not been
                                            initialised.

                                            Note : The expected values had been transmitted by
                                            AGCS team to PFM team during SVT preparation.
                                                                                          14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                      JOINT AR

                                                                                                                              Context  Criticalit Configurati    Entity in
Reference                 Title                                        Description                               Phase       reference     y         on Item      charge     Comments
84097     Probe length sensor validity          Written by : A. Noirhomme                                      SysVal -     SVT4C_RDV mi - minor 230000 -
                                                                                                               System                             System &
                                                During SVT4C RDV part, ATVCC observed that the 2               Validation                         Interfaces
                                                probe length sensors gave 2 completetly different values :
                                                Sensor1 value (DRS_N7A_LPW1) was around 89mm;
                                                Sensor2 value (DRS_N7A_LPW2) was around 444mm.
                                                The PFM team explained in real time that this is the
                                                normal behaviour of the ATV : when the probe is fully
                                                extended, only one sensor data is valid (by deduction, it
                                                should be the sensor2); when the probe is fully retracted,
                                                only the other sensor data is valid (by deduction, it should
                                                be the sensor1); when the probe is in between, both data
                                                are valid.

                                                Problem1 : The DRS UM is not in line with this behaviour
                                                (both sensors are supposed to be valid together)
                                                Problem2 : The validity laws of telemetry
                                                DRS_N7A_LPW1 and DRS_N7A_LPW2 should be
                                                updated accordingly
                                                Problem3 : The authorized range for probe fully retracted
                                                defined in the DRS UM [453mm;465mm] (cf §7.1) is not in
                                                line with the length observed on the valid sensor (444mm)




84098       Red button Acknowledgement          Written by A.Noirhomme                                         SysVal -     SVT4C_RDV Ma -       230000 -
            received on only one CPF chain                                                                     System                 Major      System &
                                                During SVT4C RDV part, the CAM test 2 was not                  Validation                        Interfaces
                                                successful. As reminder, the procedure used to perform
                                                the CAM test 2 is the VCPN_350; ATVCC observed that
                                                some of the checks failed.
                                                The test was performed 4 times. For the 3 first tests, PFM
                                                team sent the Red Button CAM on CPF1 then immediatly
                                                after on CPF2; for the last test, the PFM team inverted the
                                                order (first TC on CPF2 then immediatly after on CPF1).

                                                The table attached summarizes the observations :

84110       The alarm                           During the second homing boost the alarm             Oper - Oper OQ-RDV-N1 Ma -                  292100 -       ASTRIUM
            GNC_GAL_1_POS_DELTA_1 is            GNC_GAL_1_POS_DELTA_1 raised;                                              Major                 MDB files
            applied during the 4 homing boost   this alarm is supposed to be valid during                                                        GAL
            instead of only the last one        HOMING_YS_BOOST mode and at the end of the 4th
                                                boost.
84111       The alarm                           Before S4, the alarm GNC_GAL_NTVC_VDM_VDM is         Oper - Oper OQ-RDV-N1 Ma -                  292100 -       ASTRIUM
            GNC_GAL_NTVC_VDM_VDM is             raised.                                                                    Major                 MDB files
            raised before S4                    This comes from GNC_TRAN_FAR_CLO_RVDM_IS_OK                                                      GAL
                                                = FALSE (which is nominal) and alarm is valid as per
                                                validity conditions (GNC_CURRENT_MODE used is
                                                GNC_M_FA_1).

84112       The alarm                    As soon as the PROX is set ON, the                     SysVal -                    SVT4C_TPO- Ma -      292100 -       ASTRIUM
            TMTC_GAL_HEARTBEAT_RECEP_ TMTC_GAL_HEARTBEAT_RECEP_CONTROL is raised, System                                    CAM        Major     MDB files
            CONTROL is raised too early. however ISS HEARTBEAT is not yet available (ATV is too Validation                                       GAL
                                         far from ISS).
                                                                          14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                 JOINT AR

                                                                                                       Context       Criticalit Configurati Entity in
Reference                 Title                             Description                   Phase       reference           y       on Item    charge     Comments
84127     Discrepancy for             There is a discrepancy between the                Test - Test                  Ma -       292100 -   ASTRIUM
          VDI_GAB6_DUA_POINT_2_MASS   VDI_GAB6_DUA_POINT_2_MASS value provided in                                    Major      MDB files
          value                       MDB R4D ATV_VDI_CONTENT.dat file,
                                      +2.70000000000000E+004kg, and the expected value
                                      +2.07000000000000E+004 from MASS User Manual ATV-
                                      AS–UM-1040-10 version 6/A.
                                                                                           14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                          SYSTEM 230000

                                                                                                                Context  Criticalit    Configurati     Entity in
Reference                Title                                           Description                    Phase  reference     y           on Item        charge                       Comments
    82598 Unusable ISS Pseudo Range            La comparaison des données MODASN (simulateur GPS Oper - Oper PO_RVD_N C - Critical     231000 -                    S-NRB 7003 (01/03/2007): ISS PR utilisé sur
          measurements for Orbit determination interne AGCS), de la TM AGCS, des paquets TM M&C et            _1                       System                      PO_RVD_N_4. Exploitabilité à confirmer à la CRE
                                               de la TM FDS a montré des anomalies sur les mesures                                     Specification               Impact : Essai PO_RVD_N_1
                                               pseudo-ranges et sur les dates des mesures PVT.                                         s                           S-NRB 6003 (30/11/06 ): Correction confirmée en
                                               Les mesures pseudo-range ISS sont inexploitables pour                                                               R4
                                               la restitution d‟orbite car la liste des numéros des GPS                                                            S-NRB 6001 : CP3603 pour modification du plan
                                               associés à ces mesures est erronée (certains numéros                                                                TM à objectif R4
                                               sont bons, d‟autres sont faux). La TM AGCS, les paquets
                                               M&C et les TM FDS sont cohérents, l‟origine du problème
                                               est donc dans l‟AGCS (c'est soit un pb FAS, soit un pb
                                               MDB).


    82599 FDS Tool timeline output unusable at FDS Timeline output format gives incorrect FOP display          Oper - Oper preOQ_RDV   231000 -                    S-NRB 7003 (01/03/2007): Persistance de
          FOP level                            for the visibilities calculation around manoeuvre times.                                System                      données absentes sur PO_RVD_N_4( Visis
                                               lots of manual corrections are required to have correct                                 Specification               TDRS, Eclipse et STR dazzling sur ) et idem
                                               visibilities displayed by the FOP.                                                      s                           données partielles sur PO_OCS_N_1.
                                                                                                                                                                   S-NRB 6003 (30/11/06 ): Problème corrigé en
                                                 History :                                                                                                         V2.2.1 mais Pb persistant sur PO_RESC_N_1
                                                 In the past months, OPS have had a lot of problems to
                                                 take the FDS timeline as an input to the FOP.
                                                 The timeline SMA3 was genarated in april 2006, and then
                                                 analysed by P.sapède and members of EST Team in may
                                                 2006 and finally manually modified by P.Sapède to
                                                 produce an input for EST tools.
                                                 The same timeline is the input for the FOP tool.
                                                 After that OPS have found out new errors in this timeline :
                                                 we've listed all them and forwarded to FDS team
                                                 (T.Martin, L.Francilloux).
                                                 So far, FDS is not able to produce this format with their
                                                 tools or software.
                                                 We have to resolve this problem very soon, because it's
                                                 much to long for us to modify a timeline in the old format.
                                                 And therefore, it's totally impossible for us to take into
                                                 account a new timeline during operations.
                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                    SYSTEM 230000

                                                                                                                         Context  Criticalit   Configurati     Entity in
Reference                   Title                                     Description                       Phase           reference     y          on Item        charge                          Comments
    82728 Anomaly in ATV PR measurement        This anomaly has been detected only for PRE-OQ tests   Oper - Oper      PO_LEOP_ C - Critical   231000 -                    S-NRB 7007 (03/07/07) : ce n'est pas un pb FDS.
          date (bias of 1s) observed in PRE-OQ LEOP and PHAS_N1.                                                       N_1 &                   System                      En attente d'une nouvelle occurrence
          LEOP and PHAS_N1                     We have found that it was necessary to remove 1 second                  PO_PHAS_                Specification               13/06/07 : Analysis provided by System team
                                               to the ATV pseudo-range measurement time-tag to                         N_1                     s                           joined in attached file
                                               process it correctly. We have checked that FDS and M&C                                                                      S-NRB 7006 (06/06/07 ): SPR to be reopened by
                                               TM were consistent. The AGCS data were not saved for                                                                        AGCS and complementary investigation managed
                                               these tests.                                                                                                                by System team
                                                                                                                                                                           31/05/07 : new problem occured during Pre-QO
                                               Analysis by I.Escané : See attached file                                                                                    Survie PO_PHAS_C_1 ( AGCS R4.1 ) on 27 avril
                                               Conclusion : Pour Pre-QO RDV Escape (plans TM : de S-                                                                       2007.
                                               2 à S0 FFLI_1, de S0 à S3 FFLI_2, après escape                                                                              S-NRB 7002 (14/02/07): SPR 388 soumise à
                                               FFLI_0), les dates des Pseudo-ranges et des PVT sont                                                                        Astrium / Non reproduite - Idem côté ATV-CC ;
                                               cohérentes entre FDS et modèle GPS AGCS.                                                                                    Des dispositions sont prises côté AGCS pour
                                               Pour LEOP (FFLI_1) et EOP (FFLI_1 et FFLI_2), il y a un                                                                     enregistrer les données d'analyse en cas de
                                               biais de 1 seconde entre les dates des PR FDS et AGCS                                                                       nouvelle occurence
                                               (date PR FDS = date PR modèle GPS AGCS + 1                                                                                  S-NRB 7001 (17/01/07): SPR 388 ouverte sur la
                                               seconde). Les dates des mesures PVT sont cohérentes.                                                                        version R3.2 de l'AGCS & FA 83019 envoyée au
                                               Pour EOP, FDS et M&C sont cohérents pour les dates                                                                          Flight Segment
                                               des PR.                                                                                                                     S-NRB 6004 ( 20/12/06 ): Action SO : Rédiger la
                                               Il ne semble pas y avoir de lien direct entre les problèmes                                                                 SPR avec les infos issues de la FA Système
                                               de date PR et le plan TM                                                                                                    Remarque : Lors des essais en boucle fermée le
                                                                                                                                                                           problème n'a pas été reproduit
                                                                                                                                                                           S-NRB 6003 (30/11/06 ): Essai effectué le 30/11.
                                                                                                                                                                           Si le Pb n'est pas reconstaté, prononcer la cloture.
                                                                                                                                                                           CS 6001 : A tester dans le cadre de l'essai
                                                                                                                                                                           spécifique à la FA 82628 ( Champ clocktime
                                                                                                                                                                           erroné dans la TM GPS )

     82732 FDS timeline is non coherent with   The SMA3 timeline contains no visibilities periods around Other -       FOP OPVR        Ma -    231000 -      OP/AR         in waiting SMA4 delivery
           mission requirements concerning     and after docking event.                                  Other                         Major   System
           visibilities events for docking                                                                                                     Specification
                                               In particular, there is no russian ground station visibility                                    s
                                               during docking : this is not in accordance with mission
                                               constraints (docking period must be covered by RGS
                                               visibility up to 8mn after docking). ( This requirement is
                                               removed after OCR 40 )

                                               Analysed by N.LEROY-VIGIE : All scheduled visibilities in
                                               the SMA3 timeline are over before docking. We assume
                                               that the FDS tool doesn't give the result of its visibilities
                                               calculation in case of visibilities straddling the end date of
                                               timeline. Maybe a solution would be to calculate the
                                               timeline on a longer period?


                                               Analysed by P.FERRAGE:
                                               Je propose de maintenir cette anomalie, basée sur la
                                               SMA3 (timeline qui ne va pas jusqu'au docking + 8mn).
                                               En effet, ce n'est pas évident avec nos outils d'aller au-
                                               delà du docking.On doit pouvoir y arriver par procédure:
                                               plusieurs runs t-OPF T-RDV, TEXT, … mais il faut s'y
                                               pencher un peu plus....
                                                                                14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                       SYSTEM 230000

                                                                                                                 Context  Criticalit Configurati       Entity in
Reference                  Title                                Description                  Phase              reference      y          on Item       charge                        Comments
    82798 The TC                         During the SVT2B tests, the TC                    SysVal -            SVT2B      C - Critical 230000 -                    S-NRB 7007 :(03/07/07) : Waiting RFC on MOIS
          “THRU_EC_OPEN_LV_ACS_SET_1”    “THRU_EC_OPEN_LV_ACS_SET_1” was missing in the System                                         System &                    product, no infomation w.r.t implementation
          was missing in the procedure   TC stack (into the FCPN_4200) whereas it was well Validation                                  Interfaces                  planning . The paper review process is in place.
          FCPN_4200                      indicated in the corresponding MOIS VCP.                                                      v115                        S-NRB 7006 (06/06/2007 ): VET points out the
                                                                                                                                                                   needs to implemente this change ASAP
                                         Analysis:                                                                                                                 31/05/07 : RFC for securisation not implemented in
                                         The TC “THRU_EC_OPEN_LV_ACS_SET_1” issued                                                                                 MOIS
                                         from the VCPN_PRO_23_N was not inserted into the                                                                          CR Investigation board on the anomaly raised
                                         FCPN_4200 and thus involved a wrong onboard                                                                               during SVT2B "Missing TC" has been validated
                                         configuration of the vehicle.                                                                                             (cf.OPS-MIN-221000-781-CNES)

    83275 The PPAG chain is not stable   During last IT EST, performed from 22 to 24/01/07, too      Integ -   IT EST Part   C - Critical 230000 -                 S-NRB 7006 (06/06/2007 ): PPAG V1 Patchée
                                         many PPAG resets were done so as to run the telemetry Integration     3                          System &                 déployée depuis le 1/04/07. Comportement
                                         tests between M&C v5.1.1 and GKON v2.                                                            Interfaces               amélioré mais un problème persiste dans la
                                         Besides these PPAG resets are quite systematically done                                          PPAG                     gestion du buffer interne d'entrée dans le cadre
                                         at each test beginning: it was the case for the following                                                                 d'une utilisation en 64kbits/s ( 2 heures bord de
                                         pre-OQ or OQ tests:                                                                                                       stockage max en delayed TM ). Négotiation en
                                         - PO_OCS_N_1 (18/01/07)                                                                                                   cours pour une maintenance évolutive.
                                         - PO_DORE_N_1 (09/01/07)                                                                                                  S-NRB 7003 (01/03/07) : Nombreuses instabilités
                                         - PO_REEN_N_1 (31/10/06)                                                                                                  rencontrées lors du Dry Run de PO_RVD_N_4
                                         - PO_RESC_N_1 (22/11/06)                                                                                                  S-NRB 7002 (14/02/07 ): Mise en place par
                                         - PO_RVD_N_3 (29/11/06)                                                                                                   l'équipe SOL d'une nouvelle méthode de
                                         - OQ_LEOP_N_1 (19/12/06)                                                                                                  démarrage du PPAG. Une amélioration de la
                                         Information fr F.Lasserre ( 26/03/07 )                                                                                    stabilité a été constatée dans le cadre de
                                         Voici la situation actuelle sur le PPAG :                                                                                 PO_CAMT_N_1
                                         Les essais menés au CC ATV ont mis en évidence des
                                         instabilités de fonctionnement aussi bien sur la version 1
                                         que sur la version 2. Ces instabilités apparaissent de
                                         façon non déterministe mais sont relativement fréquentes
                                         et sont extrêmement génantes à l'utilisation. Je me suis
                                         pour l'instant focalisé sur la version 1 en considérant que
                                         les problèmes sur les 2 versions sont vraisemblablement
                                         de même nature.
                                         Après quelques investigations sur la partie logicielle (IHM
                                         de commande), je me suis concentré sur la partie
                                         hardware (composant programmable) parce que après
                                         examen plus approfondi, je me suis rendu compte que les
                                         rapports de compilation et de synthèse du composant
                                         faisaient apparaître des alarmes pour non respect des
                                         timings sur un certain nombre de liaisons internes du
                                         composant. Ce qui peut tout à fait être la cause de ces
                                         instabilités de fonctionnement.
                                         La première chose à entreprendre avant toute autre
                                                                                                  14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                   SYSTEM 230000

                                                                                                                               Context       Criticalit Configurati Entity in
Reference                   Title                                    Description                                     Phase    reference           y       on Item    charge                       Comments
    83414 MOIS spent too much time to insert or MOIS spent too much time to insert or update activities            Other -                   Ma -       245100 -   OP-SOL       S-NRB 7004 (19/03/07) : Cause présumé : Le
          update activities                     For example the procedure called FCPN2020                          Other                     Major      MOIS                    serveur OA s'écroule sous la charge en production
                                                                                                                                                                                à investiguer
                                                    - To insert one activity: between when the button Ok in
                                                    the FOP view is pressed and when the activity is really
                                                    inserted, the duration for this action is 2min08s

                                                    - To update one activity: between when the button
                                                    "Update Activity" is pressed and when the activity is really
                                                    updated, the duration for this action is 2min26s

                                                    - To insert one step: between when the button Ok is
                                                    pressed and when the step is really inserted, the duration
                                                    for this action is 1min20s

                                                    The duration above doesn't take into account the action to
                                                    update the flowchart




     83555 Incorrect time stamping of files on DG During a dry run of the SVT test (March 13th, 2007), the                                   C - Critical 230000 -     OP-SOL   S-NRB 7005 (10/05/2007) : Complementary
           following file transfer using IE       file MCI_MSU_TABLE_PHASING_20070313_161822                                                              System &              investigation to evaluate a Firefox implementation
                                                  was generated with the MCI tool, then exported from the                                                 Interfaces            in addition
                                                  MCI workspace to the MCI account on DG using the DG                                                                           le DG est spécifié pour IE sur la partie WEB
                                                  transfer function of the MCI, then copied to the DG                                                                           seulement mais avec une version antérieure à
                                                  vet_oper account using the Web interface of the DG.                                                                           celle utilisée. Les risques d'incompatibilité avec
                                                                                                                                                                                l'environnement existant sont peu probables.
                                                    The time stamp of the file obtained on the vet_oper
                                                    account was incorrectly set one year back (13th March
                                                    2006 instead of 2007), hence the sort of the files based
                                                    on time which is commonly used to select the files, could
                                                    not be used.

                                                    The time is obtained using IE to browse the
                                                    vet_oper/Private directory.

                                                    About one hour latter, the time of the file was correct
                                                    (13/03/2007 16:26).

                                                    An incorrect time stamping of files may lead to select an
                                                    incorrect file in some instances, has sometimes, files are
                                                    selected based on their time stamp.


     83586 Impossible to use Internet explorer to   With Internet explore, we can get file from private                                      C - Critical 230000 -     OP-SOL   S-NRB 7006 ( 06/06/2007 ): Installation de Firefox
           get files from DG public directory       directory but not from public directory.                                                              System &              autorisé par la Sécurité / autorisation d'un client
                                                    On the data gateway, the public directory is a unix link to                                           Interfaces            FTP du commerce sous condition qu'il ne
                                                    another shared directory.                                                                                                   mémorise pas les môts de passe ( plug in Firefox
                                                                                                                                                                                par exemple ).La commodité opératoire ( selection
                                                    All others ftp client can get file on this direcory.                                                                        multiple )oriente vers un client FTP dédié ( plug in
                                                                                                                                                                                FTP firefox le fait à vérifier )
                                                                                                                                                                                Pas de réponse de l'équipe Systeme concernant
                                                                                                                                                                                les patches eventuels sur IE
                                                                                                                                                                                see AR 83586
                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                    SYSTEM 230000

                                                                                                                              Context    Criticalit Configurati Entity in
Reference                   Title                                         Description                           Phase        reference        y          on Item   charge                      Comments
    83587 Password with "@" are not allowed        If the password contain an "@", internet explorer use this                            C - Critical 230000 -   OP-SOL
          with internet explorer for ftp session   @ on the adress.                                                                                   System &
                                                   This modification of the adress cause a failed during the                                          Interfaces
                                                   ftp connection.
     83632 Strange events causing delays of up     During SVT TPO_CAM held the 30/03/07 and SVT LEOP SysVal -                SVT4C       Ma -     230000 -     OP/AR        S-NRB 7006 ( 06/06/07 : Extraction du DH
           to 30s on parameters on TPO_CAM         held the 02/04/07, important reception delays of up to 30s System                     Major    System &                  effectuée pas de retard constaté au niveau M&C.
           and LEOP                                around 16:15 (simulated time) for TOP_CAM and 16s          Validation                          Interfaces                Analyse à mener sur le DexOut FDS
                                                   around (23:23 simulated time) for LEOP shave been                                              v120                      S-NRB 7005 10/05/2007): Analyser les logs (
                                                   highlighted.                                                                                                             extraction du DH ) pour dédouaner le M&C
                                                   The reason of these delays is unknown for FDS point of
                                                   view.

     83728 Wrong calibration curve value for TC    During the SVT4C TPO & CAM, the TC                          SysVal -      SVT4C TPO Ma -       230000 -     OP/BAR       S-NRB 7007 :(03/07/07) : FCPP to be written
           MM_TC_LOAD_CMDS into OMP                "MM_TC_LOAD_CMDS" from the OMP                              System        & CAM     Major      System &                  S-NRB 7006 (06/06/2007 ): correct FCPP
                                                   "TRANSFER_ONE_BOOST_ACS_SVT4C" did not                      Validation                         Interfaces                accordingly
                                                   change the parameter "ENABLE_STATUS_O1" from the                                               OMP TC                    20/04/2007: currently the way to correct this AR is
                                                   value "DISABLED" to the value "ENABLED".                                                                                 to set the good calibration curve value during the
                                                                                                                                                                            MDB import for this TC, and to take into account
                                                   This was due to the calibration curve value not correctly                                                                the check of this OMP TC into the FCPP.
                                                   set into the OMP TC after the ODB generation: the value
                                                   "ACCA_CALIB_ENABLED" should have been choosen
                                                   instead of the value "ACCA_CALIB_DISABLED".


     83757 Problem related to YUMA almanac         The YUMA files providing by COO are different from           FDSVal -                 Ma -     242000 -                  S-NRB 7007 :(03/07/07) : Une RFC est demandé
           files providing by COO                  those broadcasted by GPS receivers: the TOA (Time of         FDS                      Major    FDS                       côté COO pour adapter le format
                                                   Applicability) in YUMA almanacs is naturally multiple of     Validation
                                                   4096 (2e+12, LSB of TOA) and seems to be the same for
                                                   all GPS spacecrafts ; but in the files providing by COO,
                                                   the TOA is not (generally) multiple of 4096, and it can also
                                                   be different from a spacecraft to another one (In fact the
                                                   COO does not retrieve directly YUMA files, but generates
                                                   them from ephemeris files without taking into account the
                                                   TOA format).
                                                   The files providing by COO does not match what is
                                                   awaited for GPS receiver.

                                                   COO should retrieve the true YUMA almanac in an
                                                   adequat website. (ex
                                                   http://www.navcen.uscg.gov/ftp/GPS/almanacs/yuma/)
                                                   Where the file is identified by the GPS week number, and
                                                   updated every day. the file of the week n+1 is available
                                                   every Thrusday of the week n.
                                                   Our need is to have the last updated file of the curent
                                                   week and the next one.

     83760 Data Gateway is too slow                From FDS, there is some problem to retrieve files from                                         230000 -     OP-SOL
                                                   the DG because the connection take more than 10                                                System &
                                                   second to be establish.                                                                        Interfaces

                                                   25/03/2007, one sime_time_offset took 5 minute (instead
                                                   of 1 minute) because all DG process was busy to scan
                                                   some data handling files.
                                                                                         14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                             SYSTEM 230000

                                                                                                                      Context  Criticalit Configurati Entity in
Reference                Title                                        Description                         Phase      reference      y        on Item    charge                       Comments
    83815 Incoherent TM Gap detection in FDS   Anomaly on Gap detection in FDS Simulated Time mode                             Ma -       242552 - T- OP/AR       S-NRB 7007(03/07/07) : Classification de niveau
          Simulated Time mode and different    and different behaviour between FDS Simulated Time                              Major      RDV                     Systeme à confirmer / A investiguer par FDS
          behaviour between FDS Simulated      and Catch Up mades.                                                                        T-RDV                   13/06/07 : On investigation in the frame of TM hole
          Time and Catch Up mades              See description in attached file AR83815 and OSAR T-                                                               generated by 64 to 8 kb/s change
                                               RDV 6.0 logbook OPS-LB-242552-61754-CNES
    83832 Important drift between AGCS         During the Pre-operatinal test of survival               Oper - Oper PO_PHAS_ mi - minor 230000 -      SB/MS       S-NRB 7006 (06/06/07) : waiting FDS Investigation
          ephemeris and FDS propagation        "PO_PHAS_C_1", the FDS ephemeris prediction                          C_1 (FDS              System &                Une analyse complémentaire doit être menée pour
                                               generated with FDS tools (T-EXT, T-OCF and T-GOD) is                 V2.2.2)               Interfaces              affiner l'identification de ce qui a conduit à cet
                                               characterized by an important drift when compared to the                                                           écart
                                               reference AGCS ephemeris (around 40km of distance
                                               after one orbit).

                                               The AGCS ephemeris used the real ATV attitude of "Sun
                                               Pointing GNC" between 12h23m and 19h30m.
                                               Because of an anomaly raised on PSIMU on this attitude,
                                               FDS tools were used during all the test with an ATV
                                               attitude in Yaw Steering.

    83872 instanciation problem with           During dry run of the RDV QO, an anomaly was observed Prep - Prep OQ_RVD_N Ma -         230000 -     SB/MS         S-NRB 7007 (03/07/07) : organiser ue réunion sur
          FDCET_MSU_TABLE_INTERFACE            during the import of FDS instanciation file (that is named        _1       Major        System &                   les aspects de sécurisation
          file                                 FDCET_MSU_TABLE_INTERFACE.txt                                                           Interfaces                 S-NRB 7006 (06/06/2007 ): Problème identifié
                                               ) in the MSU table in S-1. This anomaly concerns the                                                               dans le définition de l'interface. Nécéssite une
                                               parameters of the TC S110_0202 that are descrived                                                                  conversion date calendaire UTC-OBUT côté M&C
                                               above:                                                                                                             pour les paramêtres MSU ou un traitement adapté
                                                                                                                                                                  côté FDS ( calcul des durées de boost directement
                                               NUMBER=32                                                                                                          en OBUT ).
                                               PARAM=MSU_BOOST_OPEN_DATE_SET_1 VALUE=
                                               FORMAT=UI UNIT=s
                                               NUMBER=33
                                               PARAM=MSU_BOOST_OPEN_DATE_SET_2 VALUE=
                                               FORMAT=UI UNIT=s
                                               NUMBER=34
                                               PARAM=MSU_BOOST_OPEN_DATE_SET_3 VALUE=
                                               FORMAT=UI UNIT=s

                                               Analysis by : V.FRARD
                                               These parameters have to be a date in OBUT time dixit
                                               UM PFS. These parameters are values by FDS team with
                                               a date in calendar time (the unit is s). The problem is that
                                               when this file is received by M&C, this one tries to convert
                                               this calendar time in OBIT time because the unit is s and
                                               the date is a calendar one (as described in the
                                               specification of the M&C) .The values are then false
                                               because expected by ATV in OBUT time. Moreover, the
                                               M&C refuses to instanciate the MSU table with this
                                               instanciation file because the converted value (that is in
                                               OBIT) doesn't respect the allowed thresholds for these 3
                                               parameters.
                                                                                        14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                  SYSTEM 230000

                                                                                                                          Context  Criticalit Configurati Entity in
Reference                 Title                                      Description                               Phase     reference     y         on Item   charge                        Comments
    83890 FTC Reset triggered by MSU Coarse   Les faits :                                                   Prep - Prep SVT4C_RDV Ma -        230000 -   OP/BAR       S-NRB 7007 :(03/07/07): VET a exprimé les
          Monitoring                                                                                                               Major      System &                besoins en terme de sécurisation et
                                              Durant le premier boost de homing du dry run SVT4C                                              Interfaces              d'automatisation des échanges avec FDS
                                              RdV, la fonction Coarse Monitoring des MSU a déclenché
                                              un FTC reset, qui a donné lieu à une CAM et a mis fin à
                                              l'exercice.

                                              L'origine du problème :

                                              L'origine de ce déclenchement est le dépassemement du
                                              seuil accepté pour le chasseur moyen (Zm) estimé par la
                                              MSU; ce Zm était mal estimé, suite à une détection de
                                              boost de homing par les MSU survenue bien trop tôt par
                                              rapport à la réalité (environ 8 minutes avant le boost
                                              commandé par le FAS), ainsi qu'une intégration
                                              d'accélérations totalement anormale (puisqu'aucun boost
                                              en cours).

                                              Il s'avère que la VET a omis d'instancier les valeurs des
                                              "LSB" ACCA contenus dans les tables MSU, partie
                                              variable, chargée peu avant S1 (environ 10 minutes). En
                                              conséquence, c'est la valeur par défaut de ces LSB qui a
                                              été chargée; cette valeur par défaut est environ 2 fois
                                              inférieure à ce qu'elle aurait dû être. Ainsi, le biais des
                                              mesures ACCA n'a pas été complètement compensé
                                              (pour moitié seulement); sachant que le bias ACCA a un
                                              ordre de grandeur équivalent à celui d'une maneuvre type
                                              homing, on comprend aisément pourquoi les MSU ont
                                              "crû" voir un début de boost.

                                              La cause du problème :

    83923 fluctuation TM reception at FDS     La VET reception frequencyles FDS level (difference
                                              the TM a omis d'instancier at valeurs LSB pour plusieurs SysVal -        SVT TPO     Ma -      200000 -    OP/AR        13/06/2007 : Taken into account in the frame of
                                              between two consecutive FDS time recordings for the        System        CAM         Major     ATV-CC                   the global investigation on FDS TM problem
                                              same parameter in FDS flows) is oscillating with the       Validation                                                   managed by System Team
                                              magnitude about +/- 0.7 s. This oscillation is not totally
                                              explains by FDS and a general study involving the full
                                              chain (TTFEE, PPAG, M&C, FDS, ..) is to be led to try to
                                              understand this fluctuation
                                                                                           14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                            SYSTEM 230000

                                                                                                                          Context  Criticalit     Configurati Entity in
Reference                   Title                                       Description                           Phase      reference     y            on Item    charge     Comments
    83996 Risk of attitude overshoot after the   A Transient period with significant overshoot in Attitude  Oper - Oper PO_PHAS_ C - Critical    230000 -    OP/BAR
          OCF update due to OBUT                 was observed after the OCF update after survival exit                  C_1                      System &
          desynchronization                      (gyra alarms, threshold 1°/s), probably linked to the OBUT                                      Interfaces
                                                 delay between AGCS and Ground.                                                                  OPERATION
                                                                                                                                                 S
                                                 Then an analysis allowed to conclude about this problem:
                                                 the attitude overshoot was explained by the OBUT
                                                 desynchronization occurred during the test (refer to AR
                                                 83805), but a major issue remains concerning operations
                                                 safety aspect: during the mission, we will not be aware of
                                                 any OBUT desynchronization after the OCF update and
                                                 thus there is a risk of involving an attitude overshoot for
                                                 ATV. The analysis concludes the following items:

                                                 - The overshoot in attitude observed at OCF update is
                                                 due to M&C bad synchronisation with on-board OBUT
                                                 (anomaly AR 83805)
                                                 - The precise analysis of the value of the synchronisation
                                                 delay was not recorded, so we can not conclude that the
                                                 entire source of error is only due to this problem but it is
                                                 surely the main component
                                                 - One must note that a problem on synchronisation on
                                                 M&C may have serious impact on data uploading and as
                                                 a consequence on ATV commanding.
                                                 - We can also observe that on board GNC is quite robust
                                                 to important gap on OCF on this scenario as the vehicle
                                                 was able to reach its new attitude target within a few
     84028 Abnormal delay observed on            minutes. of delays is stable during two part of run, one
                                                 The mean                                                     SysVal -     SVT_TPO_C Ma -        230000 -
           ATV_FCM_APP, ATV_FCM_COM,             from the beginning to 19:30 and after. The evolution is      System       AM        Major       System &
           ATV_FCM_PT, ATV_FCM_VT                increased at 19:30 reaching about 2.5 s. This                Validation                         Interfaces
                                                 phenomenon is identified for ATV_FCM_APP ,
                                                 ATV_FCM_COM, ATV_FCM_PT, ATV_FCM_VT packets.
                                                 So far this behaviour is unexplained in particular the
                                                 reason why the average delay changes suddenly at 19:30
                                                 (FTC_RESET ?).

     84053 Recovery of imput data provided by    No use of DG to recover partner fields                        Oper - Oper OQ tests   mi - minor 290000 -
           partners is not simulated                                                                                                             OPS
                                                                                                                                                 definition &
                                                                                                                                                 prep
                                                                                         14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                      SYSTEM 230000

                                                                                                                           Context  Criticalit Configurati      Entity in
Reference                  Title                                   Description                                 Phase      reference     y         on Item        charge                       Comments
    84106 Inconsistency between FDS telemetry During the last SVT_RDV operational test, two internal         Oper - Oper SVT_RDV_5 mi - minor 230000 -                      S-NRB 7007 :(03/07/07 ): Additional investigation
          and VDI tables for the GNC internal modes were received in FDS telemetry with suspect                                                System &                     OQ_DD2_N_1
          mode                                values.                                                                                          Interfaces                   Ce problème semble lié à un défaut de mise à jour
                                                                                                                                                                            de la BdD locale.
                                                During the "GNC_M_SOC_SLW=8" mode, the internal
                                                mode "36=GNC_IM_SOC_YS" was received (around
                                                09h23m). According to VDI tables, we expected the
                                                internal mode "35=GNC_IM_SOC_SLW".

                                                During the "GNC_M_SOC_YS=7" mode, the internal
                                                mode "37=GNC_IM_SURV_INIT" was received (around
                                                03h48m). According to VDI tables, we expected the
                                                internal mode "36=GNC_IM_SOC_YS".

                                                During the other GNC global modes, the GNC internal
                                                modes were consistent with VDI tables.

                                                FDS uses the VDI tables
                                                "\ATV\FS\VEHICLE\TMTC\SW_DATA\ENUM\T_GNC_IN
                                                TERNAL_\MODE" and
                                                "\ATV\FS\VEHICLE\TMTC\SW_DATA\ENUM\T_GNC_GL
                                                OBAL_\MODE" from the file "ATV_ENUM_LIST".
     84109 Wrong TC loaded in OQ_RDV_N_1        During OQ_RDV_N_1, The OMP for IF maneuvers which                                   C - Critical 290000 -                   S-NRB 7007 (03/07/2007): Procédure de Cross
           for IF maneuvers                     has been loaded on board the vehicle made the vehcile                                            OPS                        check interne mise en place au niveau de chaque
                                                swith on a wait plan.                                                                            definition &               métier et géréen en interne au FDS. Les
                                                                                                                                                 prep                       corrections des problèmes techniques sont en
                                                The reason is there was a wrong time out duration for IF3.                                                                  cours de résolution et traitées dans les
                                                                                                                                                                            commissions locales adaptées
                                                This is the results of the addition of several problems
                                                1. delay in synchronisation with M&C at the beginning of
                                                the test conducted to skip the the beginning of procedure
                                                FDSN2800 which consist of performing preliminary
                                                maneuever computation
                                                2. three anomalies at tool level (AR83925, AR83926,
                                                AR83928)conducted to change the engine for IF3 : ACS
                                                was choosed at IHM level but OCS was written in the
                                                maneuver plan. This resulted in bad time out computation
                                                and was not detected at TC level because time out is not
                                                written in TC.



     84158 wrong paramters for B_MNVR and       Anomaly : wrong parameters associated to B_MNVR,      Oper - Oper OQ_OCS_N Ma -                 242561 - T-
           E_MNVR                               E_MNVR : phase missing                                            _1       Major                OPF
                                                We should have B_MNVR TPO;TP1; 10.91;Type_OCS
                                                but we have B_MNVR TP1; 10.91;Type_OCS
                                                This timeline can't be used for FOP planning.
                                                For information : some non conformities with OPS-IDD-
                                                242400-60070_0205 E2R5 which seems to be the most
                                                recent issue :
                                                new keywords : B_SAA, E_SAA are not defined
                                                Keywords B_ECLS, E_ECLS and E_ECLS_HL have now
                                                a value where as there was none before (SMA3)
                                                No explaination from FDS team about this.
                                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                        M&C 241000

                                                                                                                                                                                                           Configurati    Entity in
Reference Title                                     Description                                                                                               Phase     Context reference    Criticality    on Item        charge     Comments
                                                    Test : TST_FCT_TV_0040.R
                                                    Points 4 et 5 sans doute lié au composant ATV_MCW.
                                                    Les points 2 et 3 sont les plus importants.
                                                    1) Lorsqu'on choisit un environnement opérationnel au login, ne pas mettre un message
                                                    d'erreur, mais une info.
                                                    2) L'action Save dans monitoring plan après ouverture et modification est inactive.
                                                    3) Dans le monitoring frame, seule la case active (et non la cellule) doit modifier
                                                    l'activation.                                                                                                                                                                     FA reproduite : CRE M1C
          Operational environment management : Seul 4) Noter la mise à jour de la barre de status du MCW du nom de l'environnement.                                                                                                   V6.3.1 : OPS-MIN-241000-
      125 le point 5 reste à corriger               5) pas de mise à jour après un save as du nom de l'environnement                                      Test - Test   TST_FCT_TV_0040.R mi - minor                     CS-SI        50988-CNES

                                                        Test TST_ADM_SY_0020
                                                        Step 9 - Le type d'opération n'est pas modification et la modification n'est pas explicite :
                                                        uniquement un message "Set functions..." comme lors de la création du profil.                                                                                                 CR ATV-CC L-NRB-PS
          IHM SC - Type d'opération modification        Test TST_ADM_SY_0050                                                                                                                                                          n°10 ref:OPS-MIN-240000-
      128 incorrect                                     Step 11 - Idem                                                                                    Test - Test   TST_ADM_SY_0020     mi - minor                   CS-SI        50470-CNES

                                                        Les méthodes suivantes du composant DH ont un nombre cyclomatique et un nombre
                                                        d'instructions supérieur aux seuils fixés. Elles peuvent être simplifiées, car il y a
                                                        duplication de code.

                                                        - Méthode Request_Handler::characters (const XMLCh* const , const unsignedint) :
                                                        nb_ins=82 Vg=35 Tx_comm=0.11                                                                                                                                                  CR ATV-CC L-NRB-PS
          Dépassement de métriques sur du code          - Méthode Request_Handler::startElement (const XMLCh* const , const XMLCh* const ,                                                                                            n°10 ref:OPS-MIN-240000-
      299 C++                                           const XMLCh* const , const Attributes&) : nb_ins=143 Vg=45 Tx_comm=0.50                                                             mi - minor                   CS-SI        50470-CNES

                                                                                                                                                                                                                                      CRE V6.0 OPS-MIN-
                                                     1) Erreur Oracle lorsque deux utisateurs définissent 2 requêtes avec le même nom.                                                                                                241000-50868-CNES :
                                                     (pb détecté en créant une requête puis en la modifiant) - passage du listing en result file)                                                                                     Apres creation des
      350 Problème lorsque nom de requête identique. 2) Il est possible à un utilisateur de créer 2 requetes avec le même nom.                                                              mi - minor                   CS-SI        requetes, message d'erreur
                                                                                                                                                                                                                                      OPS-MIN-240000- 50815-
                                                        Test : TST_FCT_DB_0090                                                                                                                                                        CNES: Demande
                                                        Le message indiquant la bonne sauvegarde devrait avoir une icone d'information et non                                                                                         d'annulation refusée Voir
      414 message de résultat d'extraction              de warning. A première vue on croit que ça s'est mal passé.                                                                         mi - minor                   CS-SI        réponse PS.
                                                        Recette usine v2.0 (15-22/01/04)
                                                        Test : TST_FCT_TM_0010 (recette usine V2.0)

                                                        Step 12 : lors de la sélection de curve_sin, il n?apparaît pas dans le champ file name du
                                                        file chooser, il faut cliquer à plusieurs endroits pour que cela fonctionne.                                                                                                  FA reproduite : CRE M1C
                                                        CS indique que le double-clic fonctionne, et qu'il s'agit sans doute d'un bug dans la librairie                                                                               V6.3.1 : OPS-MIN-241000-
      464 Sélection erratique d'un fichier              externe utilisé (à investiguer).                                                                                                    mi - minor                   CS-SI        50988-CNES

      840 Popup sur path actif après resume sur flux    Step 17 : Le popup sur le path est actif après avoir fait un resume sur le flux                                 TST_FCT_SY_0280.R mi - minor       M&C           CS-SI        L-NRB-PS n°6
                                                                                                                                                                                                                                      CR ATV-CC L-NRB-PS
          Dépassement de métriques sur du code       Nouveaux dépassements de métriques sur du code Java.                                                                                                                             n°12 Réf : OPS-MIN-
     1138 Java                                       Voir liste dans le fichier joint.                                                                                             mi - minor              M&C           CS-SI        240000-50579-CNES
                                                     Step 18, lors du retour sur la définition de requête pour modification, si la page alarm est                                                                                     CR ATV-CC L-NRB-PS
            Incohérence filtre logbook / page alarme coché, il est quand même possible de modifier certaines options (message filter,                                                                                                 n°14 ref:OPS-MIN-240000-
     1624   (mode modification)                      functionnality), alors que cela devrait être inhibé.                                           Accep - Accep TST_FCT_DH_140.R mi - minor              NRB           CS-SI        50719-CNES
            Incohérence gestion SID exp_oper /       step 20 : dans l?IHM gestion des SID de mon_oper, le GROUP0 n?est pas coché alors
     2179   mon_oper                                 qu?il l?est dans l?IHM de exp_oper                                                                           Tests CS         mi - minor              VISUTM        CS-SI
                                                     Le DPCT ne donne pas de message d'erreur au process BD d'import MDB lorsqu'il
            DPCT : manque message d'erreur si pb sur rencontre un pb lors de l'acces aux fichiers externes de definition (.xml) des parametres
     2184   fichiers .xml lors de l'import MDB       derives.                                                                                                     Tests CS         mi - minor              TDB           CS-SI
     2358   Fuites process OMPManagement             Le process OMPManagement fuit de manière assez importante.                                                                    Ma - Major              TC            CS-SI
                                                     Sur une période de 2 jours, l'utilisation mémoire du MCW est très importante sur les
                                                     postes qui traitent des TC. Sans doute lié à la JVM. Cependant, cette période de 2 jours
     2361   Fuites mémoire MCW/TC                    est largement supérieure à une session de travail "normale".                                                                  Ma - Major              TC_MMI        CS-SI
                                                     Dans certains cas (en général quand on rattrape plus de 10 min), la tm reçue pendant le
                                                     rejeu, stockée en mémoire et rejouée juste avant le passage en temps réel, n'est pas
                                                     affichée dans les displays alors qu'elle semble bien être rejouée si l'on se fie à la barre de
     2362   Pb rattrapage temps réel                 statut, qui elle évolue bien.                                                                                                 mi - minor              ATV_MCW       CS-SI
                                                                                                               14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                          M&C 241000

                                                                                                                                                                                                               Configurati    Entity in
Reference Title                                         Description                                                                                            Phase        Context reference    Criticality    on Item        charge     Comments
                                                        Configuration nominal + redondant, scenario SOS_1000. 1. ouverture d'un flot TM RT
                                                        TDRSS avec une requete ISS de 2 paramètres, 2. ouverture de la diffusion FDS, 3.
            Fermeture TMProc lors de la cloture du flow ouverture de la diffusion EST, 4. fermeture de la diffusion FDS => TMAcq et TMProc
       2553 FDS                                         s'arrêtent anormalement (messages d'alarme au logbook)                                                                                  C - Critical                 CS-SI        Corrigée en v6.3.1
       2557 DEX hangs on TC series                      When many TC are sent in series, some threads in DEX hang.                                         Other - Other   TST_STA_SY_0010      C - Critical                 CS-SI
       2559 Le playback ne fonctionne pas               On crée un flot playback, mais aucune TM n'est ingérée en BD.                                                                           Ma - Major                   CS-SI        Patch pour la v6.3.1

                                                      Le mimic mimic_exp2 est ouvert sur un poste expert. On stoppe le flot temps réel sur le
           Sur un mimic, le paramètre ne passe pas en poste monitoring, la status bar du mimic se met bien à "no telemetry attached" mais le                               TST_FCT_TV_0110
      2560 gris après arrêt du flot                   digit affichant la valeur du paramètre reste en vert alors qu'il devrait se griser.                  Other - Other   Step 19              mi - minor                   CS-SI
                                                      Les fenêtres re ouvertes pour l'environnement sont doublées                                                                                                                         FA reproduite : CRE M1C
           Les fenêtres re ouvertes pour                                                                                                                                                                                                  V6.3.1 : OPS-MIN-241000-
     80130 l'environnement sont doublées              Révision 1: la fenêtre de gestion est doublée, triplée ....                                          Accep - Accep TST_FCT_TV_0050.R Ma - Major          VISUTM        CS-SI        50988-CNES
                                                                                                                                                                                                                                          FA re-constatée (CRE V6.0
           Nom de groupe de paramètres limité à 8           Le nom du groupe de paramètres limité à 8 caractères. Nom conforme au test et nom                                                                                             OPS-MIN-241000-50868-
     80139 caractères                                       demandé fonctionnellement.                                                                     Accep - Accep TST_FCT_DB_0060.R mi - minor          TDB           CS-SI        CNES)
                                                            Les messages d'erreurs applicatifs, ne devraient pas utiliser les messages d'exceptions                                                                                       FA re-constatée CRE M&C
           Certains messages sont difficiles à              des autres logiciels (comme oracle par exemple)car ils sont en général trop compliqués.                                                                                       V6.3.1 : OPS-MIN-241000-
     80140 appréhender                                      (voir hard copy en annexe).                                                                    Accep - Accep TST_FCT_DB_0060.R mi - minor                        CS-SI        50988-CNES

                                                            Each time a display is called by pushing a navigation button, it is opened in a new window.
                                                            If the display is already opened, it should not be opened in a new window, but the window
                                                            of this display should be activated and showed on the foreground instead.
                                                            Mécanisme valable pour un même flot TM

                                                            Révision 1 : Pour un même flot, une même fenêtre se rouvre n fois. Une même fenêtre ne
                                                            peut se rouvrir que si elle est attachée à des flots différents.                                                                                                              Revue régulièrement
     80160 Multiple activation of the same window                                                                                                          Test - Test     essai VET            mi - minor                   CS-SI        pendant recette V6.2
                                                            le message d'erreur est un message Oracle et est dédié aux experts Oracle. Il faudrait un                                                                                     CR ATV-CC L-NRB-PS
           Message d'erreur trop complexe lors de la        message plus opérationnel. Le début de message est suffisant. Il n'est pas utile d'avoir la                                                                                   n°10 ref:OPS-MIN-240000-
     80276 suppression d'un profil en cours d'utilisation   description des lignes Oracle.                                                              Accep - Accep TST_ADM_SY_030            mi - minor                   CS-SI        50470-CNES
           Problème d'affichage des fenêtres sur les        Au cours de test, nous avons eu plusieurs fois, le problème d'affichage de la fenêtre                                                                                         CR ATV-CC L-NRB-PS
           MCW suite à un clic sur l'onglet                 relative à l'onglet sélectionné. Il a fallu cliquer plusieurs fois sur l'onglet pour voir                 Plusieurs tests dont                                                n°10 ref:OPS-MIN-240000-
     80285 correspondant.                                   apparaître la fenêtre correspondante                                                        Accep - Accep TST_FCT_SY_0170           mi - minor                   CS-SI        50470-CNES
                                                            TST_FCT_DB_010 :Step 10 : pas de message logbook

                                                            TST_FCT_TM_0040.R : Step 9 : pas de message ajouté au logbook pendant la creation
                                                            d'un groupe

                                                            TST_FCT_TV_0200 : Step 13, 19 et 25 : Pas de message ajouté au logbook sur mise en
                                                            référence d'entités.
                                                                                                                                                                                                                                          CR ATV-CC L-NRB-PS
           Action ne déclenchant pas de message au          TST_FCT_TV_0210 : Step 20, 37 et 43 : Pas de message ajouté au logbook sur                                                                                                    n°10 ref:OPS-MIN-240000-
     80330 logbook                                          application ou modification d'un monitoring plan                                               Accep - Accep                        mi - minor                   CS-SI        50470-CNES
                                                                                                                                                                                                                                          FA re-constatée CRE M&C
           Non-avertissement d'un opérateur DB pour                                                                                                                                                                                       V6.3.1 : OPS-MIN-241000-
     80359 une mise en référence                            Step 9 : L'opérateur DB n'est pas averti lorsque une entité est à mettre en référence.         Accep - Accep TST_FCT_TV_0075        mi - minor                   CS-SI        50988-CNES
                                                                                                                                                                                                                                          FA re-constatée CRE M&C
           Tout traitement d'une requête doit pouvoir       Toute requête en cours d'exécution doit pouvoir être stoppée par son auteur ou par                           Recette V2 -                                                     V6.3.1 : OPS-MIN-241000-
     80423 être stoppé                                      l'administrateur DH.                                                                           Accep - Accep TST_FCT_DH_0040        mi - minor     DH            CS-SI        50988-CNES
                                                            Le taux de commentaire à placer dans le code source doit être d'au moins 30% pour les
                                                            fonctions critiques et d'au moins 20% pour les autres (selon le plan d'assurance produit
                                                            fourni par CS).
                                                            Dans le code fourni pour la V2.0, certaines fonctions ne comportent pas un taux de                                                                                            CR ATV-CC L-NRB-PS
           Taux de commentaire insuffisant dans le          commentaire acceptable.                                                                                                                                                       n°10 ref:OPS-MIN-240000-
     80454 code source                                                                                                                                     Other - Other                        mi - minor                   CS-SI        50470-CNES
           Message logbook non explicite en cas de
     80589 problème de connexion avec la FDS                Etape 13 : Message logbook non explicite en cas de problème de connexion avec la FDS Accep - Accep TST_FCT_SY_1050                  mi - minor     SC            CS-SI        L-NRB-PS n°6
                                                                                                                                                                                                                                          CR ATV-CC L-NRB-PS
                                                            Step 11 : on détruit les data du jour uniquement. Apres avoir execute la requete delete                                                                                       n°10 ref:OPS-MIN-240000-
                                                            from TM_PACKET where TOCHAR(MC_RECEPTIONTIME) = „02/07/2004‟ on a eu un                                                                                                       50470-CNES-FA
           Message d'erreur suite à un delete de            message d‟erreur indiquant que la requete etait incorrecte. Pourtant les enregistrements                     TST_FCT_TM_0020.                                                 Repassant à corriger suite
     80620 paquets TM                                       ont bien été supprimés.                                                                        Accep - Accep R                      mi - minor     M&C           CS-SI        aux tests V3.2
           Problèmes concernant la fiabilité suite à        Le tableau ci-joint présente les autres problèmes de fiabilité rencontrés lors de l'audit de
80952      analyse de code (moins prioritaire)              code réalisé sur la V3.0 du M&C.                                                               Audit - Audit                        mi - minor                   CS-SI        L-NRB-PS#9
                                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                        M&C 241000

                                                                                                                                                                                                            Configurati    Entity in
Reference Title                                          Description                                                                                         Phase       Context reference    Criticality    on Item        charge     Comments
          Problèmes concernant l'automatisation du       Le tableau ci-joint présente les problèmes d'automatisation rencontrés lors de l'audit de
80953     code suite à analyse de code M&C V3.0          code réalisé sur la V3.0 du M&C.                                                                Audit - Audit                       mi - minor                   CS-SI        L-NRB-PS#9
          Problèmes concernant la performance suite      Le tableau ci-joint présente les problèmes concernant la performance rencontrés lors de
80956     à analyse de code du M&C V3.0                  l'audit de code réalisé sur la V3.0 du M&C.                                                     Audit - Audit                       mi - minor                   CS-SI        L-NRB-PS#9
          Problèmes concernant la portabilité suite à    Le tableau ci-joint présente les autres problèmes de portabilité rencontrés lors de l'audit
80958     analyse de code du M&C V3.0                    de code réalisé sur la V3.0 du M&C.                                                             Audit - Audit                       mi - minor                   CS-SI        L-NRB-PS#9
                                                                                                                                                                                                                                       CR ATV-CC L-NRB-PS
                                                                                                                                                                                                                                       n°14 ref:OPS-MIN-240000-
                                                                                                                                                                                                                                       50719-CNES // Peut être
                                                         En utilisant la requete predefinie ATVPAcketsExtraction.sql, avec une minute d' extraction                                                                                    est-ce du à un indice pas
                                                         sur l'Onboard Time, on obtient 10 pages * 400 lignes + une derniere page de 27 lignes.                                                                                        bien remis en place à
                                                         Total = 4027.                                                                                                                                                                 chaque nouvelle page (1à
                                                         En remplacant les colonnes selectionnees par un count(*), on obtient 4037 lignes. Une                                                                                         pages => 10 lignes en
81130       Nb de lignes affichees dans le databrowser   extraction du fichier buffer DEX donne egalement 4037 lignes.                                                   TST_FCT_SY_0130.R mi - minor       M&C           CS-SI        moins)
                                                                                                                                                                                                                                       CR ATV-CC L-NRB-PS
                                                         Si on met le nom de la machine FCC dans le fichier .properties, la connection ne s'établie                                                                                    n°12 Réf : OPS-MIN-
81437       Adresse IP du FCC au lieu de son nom         pas. Alors que si on lui met l'@ IP, la connection s'effectue bien.                             Accep - Accep TST_FCT_TC_0005       mi - minor     M&C           CS-SI        240000-50579-CNES
                                                         Step 12 : Au lieu d’un message d’erreur, un message
                                                         d’information indique 0 rows updated. Malgrès cela, les données ont été modifié                                                                                         FA re-constatée (CRE V6.0
            Message d'information trompeur dans          dans l'IHM de visualisation : le champ a été mis a jour et affiche en bleu.                                                                                                   OPS-MIN-241000-50868-
81487       DataBrowser                                  Idem DB_100 step 18 (modified) et step 20 (rem                                                  Accep - Accep TST_FCT_DB_0050       mi - minor     M&C           CS-SI        CNES)
                                                         Step 27 : Le graphique contient en légende la date de début et de fin, et le nom du                                                                                           CR ATV-CC L-NRB-PS
            Manque définition requête dans fichiers      paramètre. Est-ce suffisant pour la définition de la requête. Il n‟y a pas les conditions. Elle                                                                               n°12 Réf : OPS-MIN-
81513       graphique et autres                          est dans la page HTML, mais pas dans le fichier.                                                Accep - Accep TST_FCT_DH_0070       mi - minor     M&C           CS-SI        240000-50579-CNES
                                                         Sous DH, Trend Analysis/Packet Oriented, dans la saisie de la requete si on choisit
                                                         simple edition , il ne faudrait plus avoir le choix de selectionner les valeurs au format
                                                         Raw/Engineering.                                                                                                                                                              CR ATV-CC L-NRB-PS
            Cohérence des filtres pour une requête       Par contre ce champ value raw/engineering ne devrait etre uniquement disponible avec                                                                                          n°12 Réf : OPS-MIN-
81551       paquet TM                                    l‟option « edition of all parameters ».                                                                       M&C-DG_IAT_1          mi - minor                   CS-SI        240000-50579-CNES
                                                         Observation : Lorsqu‟on fait une requete TC history on peut rentrer le nom du fichier                                                                                         CRE M&C V6.3 : OPS-MIN-
                                                         resultat meme si l‟option "result file" n‟est pas active.                                                                                                                     241000-50958-CNES :
                                                                                                                                                                                                                                       Saisie du nom du fichier
            Saisie du nom du fichier resultat dans le    On devrait ne pouvoir saisir le nom du fichier que lorsqu'on clique sur "result file" et pour                                                                                 resultat dans le champ
81553       champ result pour une requete                tout type de requête.                                                                                           M&C-DG_IAT_1        mi - minor                   CS-SI        result pour une requete

                                                         Pendant les tests d'intégration ATVCC-EST, nous avons constaté que le nombre
                                                         d'enregistrements d'une extraction orientée paquets est différent de celui d'une extraction
                                                         orientée paramètres.
                                                         L'extraction paquets filtré sur l'APID 613 a donné des paquets du Seqcount 14680 au
                                                         Seqcount 225. Lorsque nous analysons l'extraction paramètre avec le même filtre, il nous
                                                         manque les paramètres appartenant aux paquets dont le Seqcount est : 14680, 14684,
                                                         14687, 14689, ..

                                                         Révision 1 : le problème est réapparu pendant les tests QO RDV_N_1
                                                         lorsqu'on fait une extraction DH orientée paquets/paramètres, avec filtre APID=615, nous
                                                         pouvons voir que le paramètres SS039S1 font bien partie des paquets MSU (par contre,
                                                         leur date est systématiquement extrapolée alors qu'elle ne dévrait pas l'être).

                                                         Lorsqu'on fait une extraction orientée paramètres (SS039S1) avec les mêmes filtre et
                                                         dates, alors, le fichier est vide en dehors de l'entête et des statistiques.

            Extraction packet différente d'une extraction                                                                                        Integ -       MC_GKON_ATV_PR
81690       paramètre en nombre d'enregistrement          Voir les fichiers joints.                                                              Integration   OCESSED_TM                    Ma - Major     DH            CS-SI        revue en V6.2
                                                          Avant de commencer le test, nous avons prepare les donnees du FCT_DH_0030. En
                                                          examinant le resultat sous DataBrowser, nous nous sommes apercus, qu‟il manque la
                                                          ligne au changement de page de resultat du DataBrowser. Exemple 400 lignes par page il
                                                          manque la 401 eme en debut de page suivante. Avec 600 lignes par page, on a les 439                                                                                          CR ATV-CC L-NRB-PS
            Perte information au changement de page       lignes attendues                                                                                                                                                             n°13 Réf : OPS-MIN-
81753       Databrowser                                                                                                                          Accep - Accep TST_PER_DH_040                mi - minor                   CS-SI        240000-50623-CNES
                                                                                                           14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                     M&C 241000

                                                                                                                                                                                                       Configurati    Entity in
Reference Title                                        Description                                                                                       Phase      Context reference    Criticality    on Item        charge     Comments
                                                       "Step 8 : certains raccourcis sont affichés dans le menu lui même (Send dans écran de
                                                       courbes).
                                                       Certains choix n‟ont pas de raccourcis (Exit pluggin SC)
                                                       Certains raccourcis ne fonctionnent pas (Exit VisuTM CTRL+Alt+Q).
                                                       Il en est de même pour les icônes.
                                                       "                                                                                                                                                                          CR ATV-CC L-NRB-PS
          Charte graphique des IHM n'est pas partout                                                                                                                                                                              n°13 Réf : OPS-MIN-
81764     la même                                                                                                                                     Accep - Accep INS_010             mi - minor                   CS-SI        240000-50623-CNES
                                                       Step 43 : DH est bien connecte sur ODBS2, mais la requete sur 5 minutes ne se termine                                                                                      CR ATV-CC L-NRB-PS
                                                       pas …                                                                                                                                                                n°14 ref:OPS-MIN-240000-
                                                                                                                                                                                                                                  50719-CNES //
          Echec de requete DH apres bascule sur                                                                                                                                                                                   Contournement :
81806     redondant.                                                                                                                                  Accep - Accep TST_BCK_SY_020      mi - minor                   CS-SI        Arrêt/démarrage du DH
                                                       When inserting keywords into the TC Stack (example wait, comment), we have the                                                                                             CR ATV-CC L-NRB-PS
                                                       possibility to select several at once, although only one will be inserted into the TC stack.                                                                               n°14 ref:OPS-MIN-240000-
81824     Multi-selection of keywords in TC stack      The multi-select possibilty should be removed (as for the TCs).                                                                  mi - minor                   CS-SI        50719-CNES
                                                       Plugin SC, User's Management window.

                                                       - Expand "cmd_oper" and click on password item.
                                                       => "password" and "password confirmation" fields are displayed on the right handside of
                                                       the window. They are empty.

                                                       - Don't modify any of these fields. Instead select the "bas_oper" profile and click on the
                                                       password item.
                                                       => "password" and "password confirmation" fields are displayed on the right handside of
                                                       the window. They are empty.

                                                       - Enter "password" and "password confirmation" for bas_oper. Close User's Management
                                                       window with the "close" button.
                                                       => Two messages are displayed on central logbook :
                                                       "changed password of user cmd_oper (changed by atv_sys using system profile)"
                                                       and
                                                       "changed password of user bas_oper (changed by atv_sys using system profile)"
                                                                                                                                                                                                                                  CR ATV-CC L-NRB-PS
          wrong user's password change report in the The first message is wrong : cmd_oper password was not changed (we verified).                                                                                                n°14 ref:OPS-MIN-240000-
81835     logbook                                                                                                                         Test - Test              Free test            mi - minor                   CS-SI        50719-CNES
                                                     When sending a stack of TCs in automatic mode, in mode AD, with COP ACK, several
                                                     attempts were made to pause and restart the TC flow.
                                                     After the restart, several anomalies occurred. The anomalies seem to depend on the
                                                     moment when the pause occured. Examples of problems include:
                                                     -TC was blocked in the “in progress” zone and had to be forced. After
                                                     restarting to send the TCs the following message appeared “TC Checking failed,
                                                     RHIK check failed. Detailed errors displayed here after”. No message appeared
                                                     there after.
                                                     -The TC was displayed in histo TC with a COP check rejected and DEX check NOK. This
                                                     TC had not been rejected by the user.
                                                     -Error message occurred concerning the Time out of FCC check. When restarting the
                                                     sending of TCs, the following message occurred: “Cannot send TC, a fatal error
                                                     occurs calling server services. Server may be stopped…” In fact
                                                     TCEmission had unexpectedly terminated with exit code 139.
          Several problems observed when pausing a Note in the last case, TC emission continued to terminate after reconnecting a TC flow                                                                                         CR ATV-CC L-NRB-PS
          TC flow during TC sending in AD and        (even after a restart of TTS and ODBS). Although no TC remained in the ‘in                                                                                             n°14 ref:OPS-MIN-240000-
81837     automatic mode                             progress” zone in TC plugin. A TC was found to exist in the “in                                                        mi - minor                   CS-SI        50719-CNES

                                                       Pendant les tests d'intégration, nous nous sommes aperçus que la déconnexion d'un flot
                                                       ne se passait pas de la même manière qu'on soit connecté au TTFEE ou qu'on soit
                                                       connecté à l'AGCS. Les traces snoop nous montrent que l'arrêt du flot connecté au
                                                       TTFEE se passe bien (tts1 demande la déconnexion) :
                                                       le tts1 demande la déconnexion qui est acceptée par le TTFEE.
                                                       Lorsqu'on ce déconnecte de l'AGCS on ne voit pas la demande venant du tts1, par contre
                                                       l'AGCS fait une déconnexion en premier, le reste de la déconnexion se passe mal.
          Arrêt flot TTFEE différent d'un arrêt flot   Voir les deux traces snoop jointes.                                                    Integ -
81894     AGCS                                                                                                                                Integration                               C - Critical   SC            CS-SI        FA reproduite V6.1
                                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                      M&C 241000

                                                                                                                                                                                                         Configurati    Entity in
Reference Title                                          Description                                                                                       Phase      Context reference    Criticality    on Item        charge     Comments

                                                         When we loaded a FCP in the Telecommand Dialog in the Preparation Mode tab and also
                                                         in the Operational Mode tab, The policy applied for the "Ready" column checkbox
                                                         managementis not the same. There is a checkbox for every line (operational mode) or
                                                         only for the TCs and the "verify" and the "stop" (preparation mode).
          Inconsistency between the operational Mode                                                                                                                                                                                CR ATV-CC L-NRB-PS
          and the Preparation mode in the            The table column names should also be the same on both tabs (for example "expected   Integ -                                                                                   n°15 ref:OPS-MIN-240000-
81926     Telecommand Dialog                         values" on the operational side, and "values" on the preparation side).              Integration                                     mi - minor                   CS-SI        50742-CNES
                                                     From plugin TDB, we imported several FCPs. When we imported again the same FCPs at
                                                     the same time, an error occurs :
                                                     "failed to propose MOIS file DG_PRIVATE@FCPN_TDRS_12_015.dat as a reference in
                                                     ODB_1_1 on going). Possible reason : import of entity FCPN_TDRS_12_01 failed" in the
                                                     logbook and the window popup is displayed (see the attached file).

                                                    Au lieu du popup, mettre un message explicite au logbook et remplacer l'ancienne FCP                                                                                            CR ATV-CC L-NRB-PS
          After several import of the same FCP from dans l'ODB.                                                                                        Integ -                                                                      n°15 ref:OPS-MIN-240000-
81930     plugin TDB, a error ORA message appeared                                                                                                     Integration                        mi - minor                   CS-SI        50742-CNES
                                                    When opening/saving an sql request, the default directory is in C:documents and                                                                                                 CR ATV-CC L-NRB-PS
                                                    settings/<user> and not D:/<version>/plugins_data/TDB. Any request stored in this                                                                                               n°14 ref:OPS-MIN-240000-
81933     TDB- wrong default directory              directory will only be stored locally on the MCW.                                                                                     mi - minor                   CS-SI        50719-CNES
                                                                                                                                                                                                                                    CR ATV-CC L-NRB-PS
          The name of the scheduled request is           When a scheduled request is going to be processed by DH, a message is displayed in the               IAT M&C V4.1.3-                                                       n°14 ref:OPS-MIN-240000-
81962     missing in the logbook message                 logbook but the request name is missing.                                               Accep - Accep DGV2.1.1                    mi - minor     DH            CS-SI        50719-CNES
                                                         Le M&C est démarré avec le véhicule AGCS :
                                                         - simulateur sur pause donc sans envoi de parametres ATV,
                                                         - flux TM (AGCS/SIMU) ouvert,
                                                         - flux diffusion vers l'extérieur ( port ATV simplement ouvert).
                                                         Un message de type WARNING s'affiche dans le logbook ( the sender is
                                                         ATVCOMP_DEX) et dont le contenu est le suivant :
                                                         "message : No TM message received for ffffffff73c04770 -- (1/10)"

                                                         Révision 2 : ajout des fichiers de log et de contexte de la réapparition de cette FA. Cette
                                                         fois ci avec l'ATV.
          Message d'erreur s'affiche si flux diffusion                                                                                                 Integ -                                                                      OPS-MIN-240000- 50815-
81995     activé et AGCS sur pause                                                                                                                     Integration   IT EST               mi - minor                   CS-SI        CNES
                                                         Si sur un MCW, on soumet une requete ISS, un utilisateur sur un autre MCW n'a pas de                                                                                       CR ATV-CC L-NRB-PS
          Probleme de rafraichissement de requete        visibilité de la requete dans l'onglet "current request".                                     Integ -                                                                      n°15 ref:OPS-MIN-240000-
81998     ISS entre différents MCW                                                                                                                     Integration   IT EST               mi - minor                   CS-SI        50742-CNES
                                                         Once the FDS diffusion flow status is red: seen in the left window of Flow management in                                                                                   CR ATV-CC L-NRB-PS
          Detail of FDS diffusion connections not        SC, the connection detail is not updated (right window).                                      Integ -       M&CV4.1.3 -                                                    n°14 ref:OPS-MIN-240000-
82029     updated                                        It is necessary to apply refresh command to modify the status of each connection.             Integration   FDSV2.0IAT           mi - minor                   CS-SI        50719-CNES
                                                                                                                                                                                                                                    CR ATV-CC L-NRB-PS
                                                                                                                                                                                                                                    n°15 ref:OPS-MIN-240000-
82150     Le texte de la fenêtre detail TC, est trop petit Step 7 : Le texte de la fenêtre detail, est trop petit.                                     Accep - Accep TST_FCT_TC_0070.R mi - minor        TC            CS-SI        50742-CNES
                                                           Arret flot TC a la fin du test case. Pas de message sur l‟arret deu flot TC au logbook,
                                                           mais 4 messages au logbook ; “Failed t update configuration on TTS server. Fatal error                                                                                   CR ATV-CC L-NRB-PS
                                                           occurs calling Server. Server could be stopped , you should close your dialog and consult                                                                                n°15 ref:OPS-MIN-240000-
82185     Messages au logbook a l'arret du flot TC         your logbook for more details.‟                                                             Accep - Accep TST_FCT_SY_0140.R mi - minor        DEX, SC       CS-SI        50742-CNES
          Message d‟erreur                                                                                                                                                                                                          CR ATV-CC L-NRB-PS
          „atv.sc.flows.iss.ISSRequestParameterExce Message d‟erreur „atv.sc.flows.iss.ISSRequestParameterException‟ dans la fenetre ISS                                                                                            n°15 ref:OPS-MIN-240000-
82191     ption‟ dans la fenetre ISS Request.              Request. Mais on soumet la requete et elle semble acceptee.                                 Accep - Accep TST_FCT_SY_0230.R mi - minor        DEX, SC       CS-SI        50742-CNES
          les erreurs de TMProc sont rangées dans la                                                                                                                                                                                CR ATV-CC L-NRB-PS
          catégorie SESSION MANAGEMENT au lieu Step 16 : les erreurs de TMProc sont rangées dans la catégorie SESSION                                                TST_FCT_TM_1020.                                               n°15 ref:OPS-MIN-240000-
82218     de Proc_TM_Anomaly                               MANAGEMENT au lieu de Proc_TM_Anomaly.                                                      Accep - Accep R                    mi - minor     SC            CS-SI        50742-CNES
                                                           Vitesse de rejeu local trop lente sur le Local replay                                                                                                                    CR ATV-CC L-NRB-PS
          Vitesse de rejeu local trop lente sur le Local Constate en recette x2 ou x3                                                                                                                    VisuTM,                    n°15 ref:OPS-MIN-240000-
82220     replay                                           Constate a CS x6 ou x7                                                                      Accep - Accep TST_PER_TV_0020      Ma - Major     TMProc        CS-SI        50742-CNES
                                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                        M&C 241000

                                                                                                                                                                                                            Configurati    Entity in
Reference Title                                          Description                                                                                           Phase     Context reference    Criticality    on Item        charge     Comments
                                                         Step 23 : avec les traces nous avons déterminé que le temps moyen d‟ingestion ete de 7
                                                         secondes. Par contre, nous nous sommes aperçus que les premiers paquets du flot et les
                                                         derniers n‟étaient pas mis en databamk.
                                                         Step 26 : 1er paquet reçu 2120 (snoop tts_sosie) 1er paquet en base 2457
                                                         dernier paquet reçu 9458 (snoop tts_sosie), dernier paquet en base 9396
                                                         pas de fichier dans le répertoire bad.

                                                         Révision 1 :
                                                         reproduit avec la V6.2
                                                         - 1er seq_count snoop : 16050 en base : 16316
                                                         - last seq_count snoop : 843 en base : 825
          les premiers et les derniers paquets du flot
82229     ne sont pas mis en databank                                                                                                                      Accep - Accep TST_PER_TM_0010     C - Critical   TMAcq, TDB CS-SI           Revue en V6.2
                                                                                                                                                                                                                                       CR ATV-CC L-NRB-PS
          pas de messages d‟alarme indiquant le                                                                                                                                                                                        n°15 ref:OPS-MIN-240000-
82237     switch TTS (voir aussi ODBS)                   Step 12 : pas de messages d‟alarme indiquant le switch.                                    Accep - Accep TST_BCK_SY_0010            mi - minor                   CS-SI        50742-CNES
                                                         Step 10 : Bascule demandée a 08 :35 :00
                                                         Il serait bien d‟avoir un message informatif au Logbook (ou warning) indiquant la demande
                                                         de bascule ( et aussi indiquant du serveur odbsX vers odbsY).
                                                         Essai d‟envoi TC OK
                                                         Fin Dataguard : 08 :39 :40sec -> Durée : 4 min 40 sec.                                                                                                                        CR ATV-CC L-NRB-PS
          Messages logbook tracant le debut et la fin    Il serait bien d‟avoir un message informatif (ou warning) indiquant la fin de bascule ( et                                                                                    n°15 ref:OPS-MIN-240000-
82250     de bascule ODBS                                aussi indiquant du serveur odbsX vers odbsY).                                              Accep - Accep TST_BCK_SY_0020            mi - minor                   CS-SI        50742-CNES
                                                                                                                                                                                                                                       CR ATV-CC L-NRB-PS
          Vitesse de rejeu central trop lente et on ne   Step 21 : il n‟y a pas de différence entre les différentes allures, a peu près deux fois le                                                                                   n°15 ref:OPS-MIN-240000-
82261     distingue pas les differentes vitesses         temps réel (30 secondes pour une minute de données).                                          Accep - Accep TST_PER_SY_0050         Ma - Major                   CS-SI        50742-CNES
                                                         Au bout de plusieurs déconnexions, reconnexions TC, quand on réouvre un flot TC, le                                                                                           CR ATV-CC L-NRB-PS
          le popup „Opening flow‟ reste ouvert alors     popup „Opening flow‟ reste ouvert alors que le flot TC est établi. On est obligé de fermer le                                                                                 n°15 ref:OPS-MIN-240000-
82266     que le flot TC est établi.                     popup par le bouton Mask. FA a faire.                                                         Accep - Accep TST_STA_SY_0020         mi - minor                   CS-SI        50742-CNES
          Les IHM 'TC data preparation' et 'TC                                                                                                                                                                                         CR ATV-CC L-NRB-PS
          description' peuvent masquer le bandeau du Les IHM 'TC data preparation' et 'TC description' peuvent masquer le bandeau du MCW si                                                                                            n°15 ref:OPS-MIN-240000-
82317     MCW.                                       l'utilisateur les déplace, contrairement aux autres IHM.                                                                                mi - minor     TC            CS-SI        50742-CNES

                                                         Dans l'IHM 'TC detaillee', on visualise les paramètres 'SPARE' alors que dans l'IHM 'TC
                                                         data preparation' il ne s'y trouve pas. Ce qui peut entrainer une certaine confusion.                                                                                         CR ATV-CC L-NRB-PS
          Différence d'affichage entre IHM 'TC                                                                                                                                                                                         n°15 ref:OPS-MIN-240000-
82319     detaillee' et 'TC data preparation'.           Il faut supprimer ces 'SPARE' dans les IHM et les impressions                                                                       mi - minor     TC            CS-SI        50742-CNES
                                                         Dans l'IHM 'TC detaillee' la longueur (length in bits) 'Engineering data', dans l'IHM de détail
                                                         d'une TC, d'un paramètre de type énuméré ou state code est de 1 bit. Cette longueur ne
                                                         peut-être déterminée, puisque variable (fonction de l'énuméré).
          Mauvais affichage de la longueur                                                                                                                                                                                             CR ATV-CC L-NRB-PS
          'Engineering data' dans l'IHM de détail d'une De plus pouvez vous mettre 'Raw size in bits' au lieu de 'Raw size' pour la longueur 'Raw                                                                                      n°15 ref:OPS-MIN-240000-
82320     TC                                            data'?                                                                                                                               mi - minor     TC            CS-SI        50742-CNES
                                                        During the Pre-QO PHAS_N1, on one MCW, several problems occured wrt to the curves
                                                        displayed in VisuTM. Several displays were open (~7), for two curves the following
                                                        anomolies occured:
                                                        -it was impossible to close the curve. On replying no the question "do you want to save.."
                                                        nothing happened the curve stayed open.
                                                        -by replying yes to the question and attempting to save the curve, the error message
                                                        "Java.lang classCastException" appears.
                                                        -it was ipossible to edit the curve

                                                         The two curves continued to be updated. The other displays on the same MCW (including
82326     timeservice                                    curves) where not effected.                                                                                                         mi - minor                   CS-SI        FA revue en tests V6.1
                                                         Pendant la création de groupe de paramètres, nous avons pu vérifier que les paramètres
                                                         internes M&C (TM, SID_HK, BZ_xx, DUMMYx, ...) sont disponibles dans les listes de
                                                         sélection de paramètres.                                                                                                                                                      CR ATV-CC L-NRB-PS
          Disponibilité des paramètres interne M&C       Si certains sont sélectionnés dans un groupe, un message d'erreur au logbook sera émis Integ -                                                                                n°15 ref:OPS-MIN-240000-
82346     dans écran TDB                                 pour chaque paramètre, lorsque l'opérateur connectera VisuTM au flot TM.               Integration                                  mi - minor     TDB           CS-SI        50742-CNES
                                                         Contexte : test libre.

                                                         observation :                                                                                                                                                                 CR ATV-CC L-NRB-PS
          Manque de cohérence d'affichage des flag       Les paramètres flaggés ready en Prépa OMP n'y sont plus en suivi OMP.                                                                                                         n°15 ref:OPS-MIN-240000-
82360     "ready" entre suivi OMP et prépa OMP                                                                                                             Test - Test                       mi - minor                   CS-SI        50742-CNES
                                                                                                           14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                      M&C 241000

                                                                                                                                                                                                        Configurati    Entity in
Reference Title                                         Description                                                                                       Phase      Context reference    Criticality    on Item        charge     Comments

                                                        Nous avons ouvert la fenêtre de suivi des OMP sans problème puis nous l'avons fermée.
                                                        Lorque nous avons voulu la réouvrir, une fenêtre d'erreur 'CORBA Timeout' est apparue.
                                                                                                                                                                                                                                   Anomalie réapparue en
          Erreur CORBA timeout sur ouverture suivi      Pour pouvoir revisualiser la fenêtre de duivi des OMP, il a fallu retirer les fichiers du                                                                                  V6.2 pendant Dry Run QO
82382     OMP                                           répertoire: /MC_APPS/TC/data/ATV/OMPfiles                                                     Test - Test                        Ma - Major     TC            CS-SI        RDV_N_1
          Impossibilité de stopper une requete          Il nous est impossible d'arreter une requete TM_Packet (contenant une périodicité de          Integ -                                                                      OPS-MIN-240000- 50815-
82426     TM_Packet sous DataBrowser                    recherche très grande)lancée sous dataBrowser (profile db_oper)                               Integration   IAT M&C - TTFEE      mi - minor     Databrowser CS-SI          CNES
                                                        Apres une bascule d'ODBS, l'ODBS redondant est mal renseigné dans le bandeau du
                                                        MCW :

                                                        - Apres bascule vers l'ODBS backup , le nouvel ODBS apparait à la fois pour la
                                                        configuration nominale et redondante dans le bandeau du MCW.

                                                        En configuration backup il n'y a pas de redondance, donc on devrait avoir "---" pour l'odbs
                                                        redondant.
                                                                                                                                                                                                                                   FA reproduced during IAT
          Info ODBS redondant éronnée dans              - Le meme probleme existe dans la bascule ODBS vers le redondant : le nouvel ODBS             Integ -                                                                      (OPS-MIN-234000-50923-
82436     bandeau MCW apres bascule ODBS                apparait aussi en nominal et en redondant.                                                    Integration   IAT M&C - TTFEE      mi - minor     MCW           CS-SI        CNES)

                                                        When the systematic analysis for TC history (not like TM systematic request) is activated
                                                        on DH, a message is displayed on the logbook but some information are missing :
                                                        &#8226; kind of analysis : systematic analysis,
                                                        &#8226; the user (all users, DG only, all users & DG),
                                                        &#8226; kind of request : TC history                                                          Integ -                                                                      OPS-MIN-240000- 50815-
82487     Missing information on the logbook                                                                                                          Integration   IAT M&C-DG           mi - minor                   CS-SI        CNES
                                                        Pour visualiser les erreurs du système, on ouvre la fenêtre « System logger ». Le
                                                        répertoire /var est plein (voir document joint FA_system_logger.zip), mais aucune
                                                        information n&#8217;apparaît des la fenêtre « System logger ». Cette information
                                                        n&#8217;apparaît qu&#8217;au bout de 5 minutes environs ( ce qui est long pour ce type
                                                        d&#8217;information). Si on ferme la fenêtre « System logger », et qu&#8217;on la
                                                        réouvre, le message n&#8217;y est plus présent, alors qu&#8217;il devrait le garder en
          Problème d&#8217;affichage dans le            mémoire. Le message ne va apparaître qu&#8217;au bout de 5 minutes environs (voir                                                                                          OPS-MIN-240000- 50815-
82498     System Logger                                 document joint).                                                                                                                 mi - minor                   CS-SI        CNES
                                                                                                                                                      SysVal -
                                                        A mimic which display a jauge, the value isn&#8217;t well updated (see print screen).         System                                                                       OPS-MIN-240000- 50815-
82608     Problem of display for mimic                  A blank square appears in the middle of the jauge (see RL009 jauge)                           Validation    VALT-1.F             mi - minor                   CS-SI        CNES
                                                        Configuration used:
                                                        tts1 odbs1
                                                        Central replay of ATV and diffusion to nominal FDS.

                                                        We try to make a pause on the replay ATV TM flow. We click on pause button.
                                                        The action pause is not immediate (about 5 second to stop): the replay is stopped on MC
                                                        at 08:54:27 and FDS saw the stop at 08:54:34 : 7 seconds are necessary to stop the TM
                                                        replay.
                                                                                                                                                      Integ -       M&C V5.02 patched 1                                            OPS-MIN-240000- 50815-
82625     Stopping TM replay is not immediate           The stop should be immediate.                                                                 Integration   FDS V2.2            mi - minor                    CS-SI        CNES
                                                        Wheel on mouse do not work to scroll displays (mimics, alphanumeric page) which
          Wheel on mouse do not work to scroll          contain scroll bars.                                                                                                                                                       OPS-MIN-240000- 50815-
82647     displays.                                                                                                                                                                      mi - minor                   CS-SI        CNES
                                                        No appearence of help (tooltip) information when mouse remains located on an icon.

                                                        This phenomenon always occurs on the "Exit" icon of the DH plugin.

          No appearence of help (tooltip) information   For other icons, this phenomenon is not systematic.
82648     when mouse remains located on an icon.        May be this problem is due to available CPU.                                                                                     mi - minor                   CS-SI
                                                                                                           14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                          M&C 241000

                                                                                                                                                                                                           Configurati    Entity in
Reference Title                                         Description                                                                                       Phase      Context reference       Criticality    on Item        charge     Comments

                                                        Integration M&C-MOIS :
                                                        An problem occurred when importing the FCP FCP_IT_MOIS_MC_correct_V2.dat : M&C
                                                        cannot import the procedure. An error message is displayed (See the file
                                                        PB_Block_FCP.rtf)
                                                        In fact, this procedure contains block step which are imported as lines with no actions
                                                        (blank line).

                                                        The request was :
                                                        Note in case a Step or Statement type are not listed in the following it is assumed that no
                                                        lines will be created therefore the CNES M&C system will not be executing it.
                                                        In any case the overall FCP shall not be rejected.

                                                        Révision 2 : priority change from P2 to P1, because DM 82332 doesn't correct the
                                                        problem.

                                                        Révision 3 : FA revue en V6.1 avec les détails suivant
                                                        Détails:
                                                        Si le block se situe en début de procédure alors l'import est un succés                                                                                                       CRE M&C V6.3 : OPS-MIN-
                                                        Si le block se situe dans le corps de la procédure sans être précédé d'un commentaire                                                                                         241000-50958-CNES : The
                                                        alors l'import est un échec                                                                                                                                                   block without keyword in
          The block without keyword in the FCP is not                                                                                                 Integ -                                                                         the FCP is not recognized
82656     recognized by the M&C                                                                                                                       Integration                           Ma - Major                   CS-SI        by the M&C
                                                        Cette anomalie est liée à l'import des paramètres dérivés par le M&C V5.1
                                                        Elle concerne les paramètres dérivés DUMP_WORD_1_DER à DUMP_WORD_5_DER.
                                                        (voir le document joint DUMP_WORD_1_DER.XML)
                                                        Il semblerait que cette erreur soit liée au test suivant : delta(RZ122) != 0
                                                        Or le paramètre RZ122 est de type UI et sa courbe de calibration est IDENTICAL
                                                        Voici l'erreur extraite du fichier mdbImport.err :
                                                        ** TM derived parameter (param_name, category_label) * (DUMP_WORD_1_DER, DER)
                                                        * Error : The derived param 's definition is wrong. Delete all dependences and this derived
                                                        parameter :
                                                        ** RB021_
          Erreur lors de l&#8217;import des
          paramètres dérivés DUMP_WORD_1_DER Dans le document joint traces.doc, on trouve les traces extraites du fichier                                                                                                             OPS-MIN-240000- 50815-
82676     à DUMP_WORD_5_DER                     DerivedParams.log                                                                                                                           mi - minor                   CS-SI        CNES
                                                L'écran de gestion des profils (et surement l'écran de gestion des utilisateurs) n'a pas une
                                                présentation (comportement) homogène avec les reste de l'application:
          Non Homogénéité des écrans de gestion - si on le déplace, il peut rester au dessus du bandeau.                                              Integ -
82706     des profils                           - il n'y a pas d'icone dans la barre de tache pour pouvoir y accéder directement.                     Integration   IAT Basic Integration   mi - minor     DH            CS-SI
                                                On DH when we want to add a ATV parameter with it first letters, the parameters are not               SysVal -
                                                in alphabetical order.                                                                                System
82863     Problem of selecting parameters in DH                                                                                                       Validation    VALT-1.E                mi - minor     DH            CS-SI

                                                        3 ISS parameters are displayed in yellow on PI00 display (ISS overview alphapage) which
                                                        corresponds to alarm color, whereas these alarms should not exist: ISS parameters
                                                        IV0002, IV0003 and IV0004.
                                                        When trying to display the alarm page, the page is empty but in the logboog a Warning
                                                        msg is displayed: “Error while attempting to add alarm in alarm page (param IV0002 to 4)”

                                                        During the test JIS ETE#1 on 11/04/2007, this AR was reproduced with the 3 ISS
                                                        aprameters IZ218, IZ219 & IZ220. These parameters were displayed with alarm flag
                                                        whereas they should not, and the raw values were "0xFFFF..." whereas it should not.
                                                        (refer to attached file orange_et_rawnotFFF.jpg).
                                                                                                                                                                                                                                      Reproduite en V6.1 :
82870     Alarms on ISS parameters should not exist     Révision 1 : FA reproduite en V6.1. Nouveaux fichiers joints.                                 Test - Test   EtE 1.2                 mi - minor     TMProc        CS-SI        nouveaux fichiers attachés
                                                                                                     14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                       M&C 241000

                                                                                                                                                                                                   Configurati    Entity in
Reference Title                                     Description
                                                    On a effectué plusieurs requettes WEB via de DH :                                               Phase       Context reference    Criticality    on Item        charge     Comments
                                                    1) 01/05/2007 05:09:00 à 06:08:59
                                                    2) 01/05/2007 06:09:00 à 07:08:59
                                                    3) 01/05/2007 07:09:00 à 08:08:59
                                                    4) 01/05/2007 08:09:00 à 09:08:59
                                                    5) 01/05/2007 09:09:00 à 10:08:59
                                                    6) 01/05/2007 10:09:00 à 11:08:59
                                                    7) 01/05/2007 11:09:00 à 12:08:59
                                                    8) 01/05/2007 12:09:00 à 13:08:59
                                                    9) 01/05/2007 13:09:00 à 14:08:59
                                                    10) 01/05/2007 14:09:00 à 15:08:59
                                                    11) 01/05/2007 15:09:00 à 16:08:59
                                                    12) 01/05/2007 16:09:00 à 17:08:59
                                                    13) 01/05/2007 17:09:00 à 18:08:59
                                                    14) 01/05/2007 18:09:00 à 19:08:59
                                                    15) 01/05/2007 19:09:00 à 20:08:59
                                                    16) 01/05/2007 20:09:00 à 21:08:59
                                                    17) 01/05/2007 21:09:00 à 22:08:59
                                                    18) 01/05/2007 22:09:00 à 23:08:59
                                                    19) 01/05/2007 23:09:00 à 00:08:59
                                                    20) 01/05/2007 00:09:00 à 01:08:59
                                                    21) 01/05/2007 01:09:00 à 02:08:59
                                                    22) 01/05/2007 02:09:00 à 03:08:59
                                                    23) 01/05/2007 03:09:00 à 04:08:59
                                                    Elles ont toutes été fructueuses sauf les requêtes 9 et 18 (sans raison apparente). Voici le
                                                    fichier error.xml pour la requête 9 :
                                                    <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
                                                    - <result>
                                                    <request_status>Not_accepted</request_status>
                                                    <reject_reason>Unable to process DH's FolderDispatcher's response - FolderDispatcher
                                                    exception: Some error(s) occured with FolderDispatcher: title="Socket connexion",
                                                    message=" Socket connection problem in Data Handling.".</reject_reason>
82897     Requette WEB se terminant en erreur.      - <analysis_request>                                                                                                            mi - minor     DH            CS-SI
                                                    During the QO EOP test, a TC Diffusion Window on the Training Instructor screen was
          Diffusion frozen with a TC in "Progress   frozen with a TC in "progress zone".
82974     Zone"                                     We closed and opened the TC Diffusion Window to repair it.                                   Oper - Oper   OQ_EOP_N_1           mi - minor                   CS-SI

                                                    On DH request TM parameter oriented , PUD and sub-PUD are not always filled and
                                                    some packets HLTM are repeated several times. ( file Perf_PUD_6_20061211_153933)
                                                    To be noticed 2 real time TM ( both are ATV real time ) but we have only one real time     SysVal -
                                                    flow and one playback flow.                                                                System
83082     Packets HLTM are repeated several times                                                                                              Validation      Test Perf : Perf_9   mi - minor     DH            CS-SI

83087     Test de la FA 82575                       On ne peut pas modifier la liste des trigger pour un paramètre dérivé issu de la MDB        Accep - Accep TST_FCT_DB_0060.R mi - minor                       CS-SI        Filtered by M&C team
                                                    databrowser n‟a pas pu s‟ouvrir (voir hard copie). Arrêt par la croix. Réouverture OK Suite
                                                    a une deuxième apparition de cette fenêtre presque vide, le databrowser n‟est plus
                                                    disponible (menu ODB/MDB Browser grise). Il a fallu fermer/ouvrir le pluggin TDB pour
83088     Databrowser                               résoudre le problème                                                                        Accep - Accep TST_FCT_DB_0050.R mi - minor                       CS-SI        Filtered By M&C Team
                                                    soucis d‟affichage de l‟arborescence du data browser, solution arreter et redemarrer le
83090     Arborescence de databrowser               pluggin TDB                                                                                 Accep - Accep TST_FCT_DB_0065.R mi - minor                       CS-SI        Filtered By M&C Team
                                                    L‟acces a l‟espace de reference ne se fait pas facilement (il faut connaitre l‟arborescence
                                                    du M&C). Le M&C doit positionner l'utilisateur dans l'espace de référence … na faudrait-il
                                                    pas un double accès ?

                                                    Révision 1 : l'accès à l'espace de référence ne se fait que par navigation dans les
                                                    réperoires. Il faut un double accès, exactement comme il est proposé à l'utilisateur dans la
                                                    partie TC. Lorsque l'opérateur veut ouvrir une stack, une FCP, une OMP, ... on lui propose
83118     Accès à l'espace de référence difficile   un double accès reference/local.                                                             Accep - Accep TST_FCT_SY_0120.R mi - minor                      CS-SI        Réouverte en V6.1.3

          Pas de message au logbook concernant                                                                                                               TST_FCT_SY_0170.R
83121     l‟arret des connexions DaSS ISS           Step 16 : Pas de message au logbook concernant l‟arret des connexions DaSS ISS.            Accep - Accep , TST_FCT_SY_0180 mi - minor                        CS-SI        Filtered By M&C Team
                                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                      M&C 241000

                                                                                                                                                                                                          Configurati    Entity in
Reference Title                                       Description                                                                                  Phase       Context reference Criticality               on Item        charge     Comments
                                                      Step 10 : Apres avoir ouvert un flot playback par erreur (sans fichier playback), des
                                                      messages critiques sont ajoutes au logbook a l‟ingestion de la TM (Sender :
                                                      ATVCOMP_TDBSERVER) :
                                                      « [FTPTransfert ::FtpGetFiles] Impossible to delete remote file. »
                                                      « [FTPTransfert ::FtpGetFiles] Rename failed from temporary file
                                                      TM_2007_01_03_14_25_59_988.ftping to TM_2007_01_03_14_25_59_988 : No such file
                                                      or directory”
                                                      ”/home/mcinst/ATV-MC/gen/6.0/ATVMC/TDB/Server/src/cpp/Ingestion/Ingestion.cpp :
                                                      418 Error moving TM packet TM_2007_01_03_14_25_59_988 from
                                                      /MC_INT_EXCHANGES/TDB/ATV_RawTM
                                                      to/MC_INT_EXCHANGES/TDB/ATV_RawTM/BAD No such file or directory”
                                                      ”Error moving TM packet TM_2007_01_03_14_25_59_988 from
                                                      /MC_INT_EXCHANGES/TDB/ATV_RawTM
                                                      to/MC_INT_EXCHANGES/TDB/ATV_RawTM/BAD No such file or directory”
83122     Probleme apres ouverture d'un flot playback Contournement : Il a fallu redemarrer la conf (TTS/ODBS)                                  Accep - Accep TST_FCT_TM_1010 mi - minor                                CS-SI        Filtered By M&C Team
                                                      Hors test : sur arret de session par Start > Log Off <user_name> (arret session windows),
                                                      l‟applicatif s‟arrete dessuite sans sauver les donnees utilisateurs (plugins_data,
                                                      mcw_manager_data)

          Perte des donnees utilisateurs lors de la      Révision 1 : la session ne s'enregistre pas bien + message d'erreur de récup de la                                                                                          Reproduite en complément
83123     deconnexion utilisateur avec MCW actif         session à la réouverture                                                               Accep - Accep TST_FCT_TC_0240 mi - minor                                CS-SI        validation recette V6.2
          Format de date incorrect pour un message       Step 8 : la date UTC est exprime en seconde.millisecond au lieu de jj/mm/aaaa hh:mm:ss
83126     logbook                                        dans le message logbook.                                                               Accep - Accep TST_FCT_TC_0140.R mi - minor                              CS-SI        Filtered By M&C Team

                                                        Poste 1 connecte mon_oper sur AGCS, les flux viennent d‟etre fermes. Poste 2
                                                        deconnexion du poste mon_oper sur ATV. A la deconnexion du poste 2 pour se connecter
                                                        db_oper sur ATV, des erreurs critiques sont affichees « Inexpected error while getting
                                                        state of ingestion processes (suspend and resume actions will be disabled) :
                                                        SCServiceTTS.ISessionPackageDataNoSet :IDL :SCServiceTTS/ISession/DataNotSet :1
                                                        :0 ». Idem a la deconnexion de db_oper. La sequence pour reproduire la FA est :
                                                        - login db_oper, vehicule ATV, next, back, back, choix AGCS, next, erreur “max nb of db
          Erreurs critiques à la deconnexion de poste reach”, back, ATV, next, puis connexion.
83130     MCW                                           - login au plugin TDB, probleme d‟acces a l‟etat des processes d‟ingestion.                        Accep - Accep TST_FCT_SY_0150     mi - minor                 CS-SI        Filtered By M&C Team
                                                        Lorsque un paquet HK ou diag est disabled par TC ou IHM, les parametres associes
          Incoherence entre la significativite des      passent a non significatif. Si on recoit tout de meme le paquet, les parametres passent en
          parametres et l'etat                          significatif mais l‟etat du paquet diag reste au niveau de l‟IHM a l‟etat disabled … il faudrait
83136     d'activation/desactivation des SID            assurer cette coherence                                                                            Accep - Accep TST_FCT_TV_0250     mi - minor                 CS-SI        Filtered By M&C Team
          Clignotement de la zone Connection detail     Step 17 : lorsqu‟on suspend (ou resume) le flot TC, l‟IHM de gestion des flots (partie
83138     de l'IHM de gestion des flots                 connection detail) clignote plusieurs fois avant de se stabiliser                                  Accep - Accep TST_FCT_SY_0280.R mi - minor                   CS-SI        Filtered By M&C Team
                                                        Step 19
                                                        Fenetre pop up est affichee avec le message Error Building EditorWindow, see log
                                                        window for detail
                                                        La fenetre permettant l‟update n‟est pas affichee : Il faut selectionner un enregistrement
83139     message pas assez explicite                   pour faire un update, delete (idem pour cas de delete)                                             Accep - Accep TST_FCT_DB_0100.R mi - minor                   CS-SI        Filtered By M&C Team
          Le message indiquant qu‟un refresh est        Step 22
83140     necessaire est tronque ou mal positionne      Le message indiquant qu‟un refresh est necessaire est tronque ou mal positionne                    Accep - Accep TST_FCT_DB_0100.R mi - minor                   CS-SI        Filtered By M&C Team
                                                        Step 4 :
                                                        Suite a l‟affichage du message via F2, l‟ascenseur propose ne bouge pas, bien que le
83141     Probleme d'ascenseur suite a F2               texte defile correctement                                                                          Accep - Accep TST_FCT_DB_0110.R mi - minor                   CS-SI        Filtered By M&C Team
                                                        During the LEOP exercise of 19/12/2006, the OBUT time was not displayed at the top left
          The OBUT time was not displayed on 1          of the MCW (refer to the M&C screenshot joint).
83203     MCW during the whole OQ test of LEOP          Only the GMT time was displayed.                                                                   Oper - Oper   OQ_LEOP_N_1         mi - minor   VISUTM        CS-SI
                                                        On Web DG we create an incorrect data request to M&C. Then the M&C sent the result to
          Bad filename of result file when an error has explain the dom parsing error. This file is named TA_result_xxx_.xml.xml. But the correct          Integ -
83210     been done                                     name should be : TA_result_xxx_.xml                                                                Integration   Basic Integration   mi - minor   DH            CS-SI
                                                        On DG we send a request based on parameters values without statistics.
                                                        But, the results DG and DH contain the list of parameters and the associated statistics.
                                                        The filter on DG “Parameters without Statistics” doesn't have any effect for DH results :
                                                        statistics are at the bottom of the page.

                                                         Not in line with IDD 070 Ed 3 Rev 1
                                                                                                                                                           Integ -
83235     Problem of statistics result file on DG        See attached files                                                                                Integration   Basic Integration   mi - minor   DH            CS-SI
                                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                        M&C 241000

                                                                                                                                                                                                            Configurati    Entity in
Reference Title                                         Description                                                                                           Phase      Context reference    Criticality    on Item        charge     Comments
                                                        In the header of the result file, in the field Request's execution date, the value is
                                                        “2007/01/17 16:27:15:1169051235”. The format should be compliant with the expected
                                                        date format (JJ/MM/AAAA HH:MM:SS) This error format is also in the HistoTC and the                Integ -
83243     Bad format of date on M&C                     TM Parameters results.                                                                            Integration   Basic Integration    mi - minor     DH            CS-SI

                                                        We create a parameter request with more than 28 parameters (max allowed is 50).
                                                        We save the request and we return to "User request" item to modify it: the request is
                                                        empty. There is no time period, no selected parameters, no filter etc...

                                                        But with 20, 25 parameters it works!
                                                                                                                                                                                                                                       CRE M&C V6.3 : OPS-MIN-
                                                        Révision 1 : nous avons créer une requête avec 5 paramètres que nous avons sauvés                                                                                              241000-50958-CNES :
                                                        (OK)                                                                                                                                                                           Problem on DH to create a
          Problem on DH to create a parameter           Nous avons modifier la requête afin de passer à 25 paramètres. Au moment de sauver                Integ -                                                                      parameter request with
83267     request with more than 28 parameters          cette requête, le M&C à renvoyé un message d'erreur. La requête n'a pas été sauvé.                Integration   Basic integration    mi - minor     DH            CS-SI        more than 28 parameters
                                                        If we create a request oriented parameters, it can be possible to select a same
                                                        parameters several times: there is no check on the set of selected parameters.
          No check in the list of required parameters                                                                                                     Integ -
83268     on DH for a parameters request                                                                                                                  Integration   Basic Integration    mi - minor     DH            CS-SI

          TC non bleutée dans la zone "active stack"    Dans l'IHM de Diffusion TC, la TC F107_1804 a été jouée (présente dans la partie
83287     de l'IHM diffusion TC                         "Historic"), mais n'est pas bleutée dans la partie "Active Stack" alors qu'elle devrait l'être.   Oper - Oper   SVT4C                mi - minor     TC            CS-SI

                                                        there is a loss memory on ODBS server when systematic analysis request is activated.
                                                        (see the curve file ODBS_CPU-MEMORY-12-12-16h-13-12.jpeg). The systematic request
                                                        is based on TM packets with edition of all parameters for a time period=2h beginning of
                                                        scheduling at 11h30, first result at 11h56: 26 min of processing, second result at 13h26:
                                                        26 min of processing, size=365 Mbytes and 7,8 million of lines
                                                        After a while we stop server : the memory recovers its orinal level.
                                                                                                                                                          Integ -
83324     memory loss on odbs server                                                                                                                      Integration   Test Performance     Ma - Major     DH            CS-SI
                                                        Lors de l'essai SVT4C, la mise à jour de l‟heure simulée (en haut a gauche dans le
                                                        bandeau) a pris 2 minutes sur le MCW du commander
                                                        (NB : Auparavant, la poste Commander a du se déconnecter à deux reprises du M&C
                                                        suite à des problèmes d‟acquittement de TC).
          Problème de mise à jour de l'heure simulée    Sur les autres MCW (expert, monitoring) la date s'est mise à jour au bout d'une minute
83340     sur le poste Commander                        (dès la récéption de la TM(10,1))                                                                 Oper - Oper   SVT4C                mi - minor     SC            CS-SI
                                                        Lorsque l'on essaie de configurer 2 repositories avec le même utilisateur durant la même
                                                        opération (sur le même MCW, et sur la même fenêtre d'IHM), une erreur java apparaît et
          Plantage du M&C lors de la configuration      le l'application M&C se plante sur le MCW.
83391     des repositories                              Par contre la configuration de ces 2 repositories en sortant de cette IHM fonctionne.             Prep - Prep   PO_CAMT_N_1          mi - minor                   CS-SI

                                                        TEST:
                                                        ETE_1.2

                                                        Description:
                                                        On est connectés avec le DaSS server de Col-cc.
                                                        On part d'une situation où une requête DaSS ("full request") est activée dans le current
                                                        request de la fenêtre ISS TM configuration.
                                                        On efface la requête en cours -> elle disparaît de l'espace "current request".
                                                        On envoie depuis l'onglet "parameter groups" une requête plus petite appelée "partial
                                                        request". Deux problèmes :
                                                        1/ les paramètres de la "full request" qui ne sont plus dans la "partial request" restent
                                                        affichés en vert sur les displays déjà ouvert. Ils ne changent toutefois pas de valeur,
                                                        comme attendu.
                                                        2/ si on ouvre un nouveau display avec les mêmes paramètres, même comportement.

                                                        On s'attend plutôt à voir des tirets à la place de valeurs, indiquant que le paramètre ne
                                                        figure pas parmi la liste des paramètres de la nouvelle requête.

                                                     Noter que cette anomalie n'a concerné que les MCW 13, 15, 16, 17 et 18 et n'a pas été
                                                     remarquée sur les postes 50, 25, 02, 46 (sans doute les postes où ces valeurs n'étaient
                                                     pas affichées avant d'avoir procédé au changement de requête).                                                                                                                    FA reproduite V6.3.1 : CRE
          Paramètre DaSS affiché malgré l'annulation Voir copie d'écran.                                                                                                                                                               M&C V6.3.1 : OPS-MIN-
83395     de la requête                                                                                                                                                                      Ma - Major     TMproc        CS-SI        241000-50988-CNES
                                                                                                           14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                         M&C 241000

                                                                                                                                                                                                           Configurati    Entity in
Reference Title                                          Description                                                                                        Phase     Context reference      Criticality    on Item        charge     Comments

                                                         Un paramètre dérivé est calculé chaque fois que l'APID redescend. Il n'est valide que
                                                         quand cet APID vaut 116. De plus ce paramètre dérivé est monitoré (en alarme lorsque >
                                                         28) et quand il est significatif, il vaut 122 (et donc en alarme).
          Paramètre en alarme à chaque retour de         A chaque fois que l'APID vaut 116, il y a un message d'erreur au logbook, alors que nous
83416     significativité                                nous attendions a n'avoir qu'une seule alarme car la valeur significative ne change pas. Other - Other                             mi - minor     VISUTM        CS-SI

                                                         Des messages d'erreurs apparaissent lors de la mise en référence unitaire de displays.
                                                         (voir fichier ci-joint ).

                                                         Révision 1 : problème revu avec le minics MS01_PFS_GENERAL_CONFIGURATION.jlz.
                                                         Après analyse, il apparait quand retirant un lien vers un autre mimics, la mise en référence
                                                         se passe bien.                                                                                                                                                               FA reproduite V6.3.1 : CRE
                                                                                                                                                                                                                                      M&C V6.3.1 : OPS-MIN-
83456     Mise en référence des diplays                                                                                                                                              C - Critical          VisuTM        CS-SI        241000-50988-CNES
          Ouverture erronee de l'IHM de preparation   une TC est selectionne dans l‟active stack, lors d‟un double click sur une zone expand
83498     de TC                                       („+‟) d‟une stack, l‟IHM de preparation TC est ouverte pour la TC selectionne.                 Accep - Accep TST_FCT_TC_0170.R mi - minor                          CS-SI
                                                      Dans le fichier public.properties, si il y a un espace apres le nom de la machine, alors, lors
          Probleme avec des espaces dans les noms de la configuration, l‟espace est pris en compte et la machine n‟est plus connue.
83505     des machines dans public.properties         (FDS_nominal_DNS_name au moins pour cette ligne)                                               Accep - Accep TST_FCT_TM_0030 mi - minor                            CS-SI
                                                      Step 5 : on ne voit aucun message d‟erreur dans le logbook => om remodifie
          Probleme de visibilite de certains messages CCSDSPacket.fcf pour mettre la date extrapolee au 13/01/2006.PB de categorie de
83509     sur les retours arrieres dans le temps      messages ? (ni monitoring, ni expert ne les voit)                                              Accep - Accep TST_FCT_TM_0130 mi - minor              VISUTM        CS-SI
                                                                                                                                                                                                                                      FA reproduite V6.3.1 avec
                                                         A la fin du switch pour faire les tests de completude, nous nous sommes apercus qu‟il y                                                                                      le process TMIngestion
                                                         avait des milliers de fichiers dans les repertoires d‟ingestion du tts et de l‟odbs. Apres                                                                                   toujours actif CRE M&C
          Degradation de l'ingestion TM lors des         avoir fonctionne tout le weekend, il y a toujours des fichiers TM qui n‟ont pas ete ingeres                                                                                  V6.3.1 : OPS-MIN-241000-
83515     bascules TTS                                   sur TTST1.                                                                                     Accep - Accep TST_BCK_SY_0010       mi - minor     TDB           CS-SI        50988-CNES
          Probleme d'etat de l'ancien tts suite a        Apres arrêt et rebranchement de l‟ancien TTS nominal, le TTS est marque OK (icône
83516     bascule, dans le bandeau                       machine verte) dans la status bar du bandeau MCW, alors qu‟il n‟est pas démarre                Accep - Accep TST_BCK_SY_0010       mi - minor     SC            CS-SI
                                                         Le choix "---" dans le filtre vehicule lors de la creation d'une requete logbook signifie
                                                         "None" (message non attache a un vehicule) au lieu de "All" (Tous les messages pour une
                                                         meme fonctionnalite par exemple). Le probleme est qu'il faut gerer par exemple la
          Selection du filtre vehicule dans les requetes coherence entre la fonctionnalite et le vehicule. Il faut que dans le filtre vehicule le "---"
83518     d'extraction logbook                           signifie "All vehicles" et il faut ajouter la valeur "None".                                   Accep - Accep Validation FA 81754   mi - minor                   CS-SI

                                                         Anomalie vue pendant essai PO_RVD_N4:
                                                         Lors d'un dump de Table MSU, sur un controle KO, le message d'erreur affiché etait :
                                                         "Error on block 11 (...) TM parameter SZ640S1: expected 0000 but received 00 00 00 00
                                                         00 00 be 55 ff ff ff ff 46 36 a0 a9 00 06 00 00 00 00 00 01 bf e0 6a e0 d5 c1 ab 84 6e 64
                                                         6c 65 00 00 f2 d8 00 00 00 00 00 00 00 41 00 00 00 01 00 d8 f2 f0 ff ff ff ff 7a d3 0e b8"
                                                         La valeur de SZ640S1 etait BE 55, le message aurait donc du être :
83531     Message d'erreur dans l'IHM table MSU          "TM parameter SZ640S1: expected 0000 but received BE 55"                                       Test - Test                         mi - minor     TC            CS-SI
                                                         Step 20 : il manque les derniers (avant arret requete) paquets ISS dans la databank.
                                                         Probleme de l‟envoi du buffer de paquets TM ISS incomplet ?
          Il manque les derniers (avant arret requete)                                                                                                                                                                                FA reproduite V6.3.1 : CRE
          paquets ISS dans la databank lors de la      Révision 1 :Suite à recette V6.2 nous avons vu qu'il manquait également des paquets                                                                                            M&C V6.3.1 : OPS-MIN-
83536     bascule ainsi que des paquets ATV            ATV dans la databank après bascule. A reclasser P1                                          Accep - Accep TST_BCK_SY_0040            Ma - Major     TDB, DH       CS-SI        241000-50988-CNES
                                                       Des paquets ont ete perdus vers la diffusion EXT pendant la bascule
                                                       Analyse des DEX_Out de la diffusion EXT lors de la bascule back-up TTS du 07/03/2007
                                                       a 10h30:
                                                       dernier seqcount sur TTST1: 712
                                                       premier seqCount sur TTSTB1: 734                                                                                                                                               FA reproduite V6.3.1 : CRE
          Des paquets ont ete perdus vers la diffusion Par contre 20 paquets sont diffusés en double vers la diffusion EXT sur le ttst1 nominal au                                                                                    M&C V6.3.1 : OPS-MIN-
83538     EXT pendant la bascule                       moment de la bascule                                                                        Accep - Accep TST_BCK_SY_0040            Ma - Major     SC            CS-SI        241000-50988-CNES
                                                       Dans un premier demarrage les connexions ont ete refuses. Apres quelques minutes, il
                                                       n‟y a pas eu de probleme. Ce phenomene fait suite a un redemarrage complet des
          Dans un premier demarrage les connexions serveurs et des bases. Les messages affiches au logbook ne sont pas assez explicite :
83541     ont ete refuses                              „Cannot login user xxxxx : null.                                                            Accep - Accep TST_BCK_SY_0060            mi - minor     SC            CS-SI
                                                                                                                                                                                                                                      FA reproduite V6.3.1 : CRE
          Durée trop importante dans les actions         11h pour l‟export/nettoyage de la databank (pour environ 24h de TM issue du test                                                                                             M&C V6.3.1 : OPS-MIN-
83543     d'export et nettoyage de la databank           STA_SY_010), 16h pour l‟import, ce n‟est pas exploitable operationellement                     Accep - Accep TST_FCT_DB_0120       mi - minor     TDB           CS-SI        241000-50988-CNES
                                                                                                        14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                         M&C 241000

                                                                                                                                                                                             Configurati Entity in
Reference Title                                       Description                                                                                   Phase      Context reference Criticality   on Item    charge     Comments
                                                      le restore_TMTC_databank du test DB_0120 empeche l‟historisation des TC car il a
                                                      introduit des cles primaires incompatibles avec le numero de sequence courant de
                                                      l‟historisation TC. Message d‟erreur au logbook : Erreur d‟historisation de la TC dans
                                                      HISTO_TC ORA000001 :constraint violated En regardant dans la base on voit que le
          le restore_TMTC_databank du test            restore_TMTC_databank du test DB_0120 introduit des cles primaires incompatibles avec
83546     DB_0120 empeche l‟historisation des TC      le numero de sequence courant de l‟historisation TC.                                      Accep - Accep TST_FCT_TM_0110 mi - minor     tdb        CS-SI
                                                      Sequence executed on a MCW :
                                                      1) Creation of a sub-plan TOTO
                                                      2) Application of sub-plan TOTO
                                                      3) Modification of the sub-plan TOTO with the Editor and save it
                                                      4) Application of the modified sub-plan TOTO
                                                      Problem n°1 : The new sub-plan TOTO is NOT taken into account in the Current
                                                      Monitoring.
                                                      Then the following sequence was executed :
                                                      5) Unload sub-plan TOTO
                                                      6) Application of sub-plan TOTO
                                                      The sub-plan TOTO is then correctly updated but :
                                                      Problem n°2 : The modified monitorings are not all displayed in the dedicated font in the
83558     Problems with monitoring sub-plans          view “Current Monitoring”.                                                                Test - Test   PO_RDV_N4          mi - minor  VisuTM     CS-SI
                                                      Some critical messages on M&C‟s logbook give no reference of the DG request ::”init
                                                      Request: too many results: the packet numbers exceeded …”.

                                                      The user don't know what he has to do with this such DH message?

                                                      The message should be more explicit, giving at least the destination (Data Gateway), the
                                                      reference of the request (type, time period) like the other informative message (the print
          Message on logbook from DH process not      screen).                                                                                     Integ -
83572     explicit                                    FA liée à la 83576                                                                           Integration   IAT M&C-DG      mi - minor   DH       CS-SI
                                                      When we submit a parameter request or a TM packet request with edition=graphics and
                                                      value type=raw, a critical message displayed in the logbook is: “Cannot plot raw data”
                                                      (See join file print screen). Information about the type a request, time period... are
                                                      missing. The M&C shall control this kind of inconsistency

                                                      In DH‟s result file, in tag <reject_ reason> we can see a long non useful message
                                                      beginning by: “folder dispatcher …..”.
          Reject reason message on DH result too      It ends with “Cannot plot raw data” and this last information part is enough.                Integ -
83573     long                                        The critical level is not necessary for this kind of error. Warning severity is enough.      Integration   IAT M&C-DG      mi - minor   DH       CS-SI
                                                      When we create a parameter request or a TM packet request on DG WW side, DH
                                                      returns a
                                                      TA_Result_xxx.xml and TA_Request_xxx.xml files. The value inside of vehicle tag is 1
                                                      (enumerated value) instead of "ATV" : the real name of vehicle should be displayed to be
                                                      checked by DG user as requested in IDD070 ED3Rev1
                                                      Révision 1 : le problème survient uniquement lorsqu'on fait une requête systématique de      Integ -
83575     Enumerated value of vehicle in DH request   type paquets ou paramètres avec comme destinataire le DG.                                    Integration   IAT M&C-DG      mi - minor   DH       CS-SI
                                                      Configuration: odbst1 nominal and odbst2 redundant

                                                      Switch to redundant ODBS server: the new primary data base is now ODBST2.
                                                      The popup to notify the odbs switch in progress is never closed and we must hide it.
                                                      The banner of MCW is not updated with the correct odbs server name: odbst1 is still in
          MCW top banner not updated after ODBS       nominal status.                                                                              Integ -
83577     switch                                      But, if we connect another MCW, the banner is OK.                                            Integration   IAT M&C-DG      mi - minor   SC       CS-SI
                                                      Problem TM context on TTSt2 (redundant): DASS processed failed to read the operational
                                                      context ODB_UMI_and_UMI.xml because the operational context wasn‟t deployed on
                                                      it(redundant) and same as for backup.
                                                      Why did the context not deploy automatically on redundant and backup whereas the             Integ -
83579     Operationnal context dispatch problem       context is available on nominal and we are configured in hot redundancy?                     Integration   IAT M&C-DG      Ma - Major   DH       CS-SI
                                                      In ISS request management window, we delete an empty current ISS request : the pop up
                                                      is frozen and a message is displayed on the logbook: “ISS request null was cancelled by
                                                      user ….”.                                                                                    Integ -
83580     Problem to delete a null ISS request        We had to close the ISS TM configuration window.                                             Integration   IAT M&C-TTFEE   mi - minor   SC       CS-SI
                                                                                                          14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                   M&C 241000

                                                                                                                                                                                                      Configurati    Entity in
Reference Title                                      Description                                                                                         Phase     Context reference    Criticality    on Item        charge     Comments
                                                     Switch from ttst1/odbst1 to ttst2/odbst2 reundant
                                                     on TTST2 kill of processes DEX and TCEmission, the process window is correctly
                                                     updated.
                                                     on ODBS2 kill of process MainSC
                                                     Switch from TST2/odbst2 (new nominal) to TSTB1/odbstb1 (backup)
                                                     On the nominal MCW (attached to TTST2), after a switch on M&C backup, no way to
                                                     close the MMI MCW (VisuTM with displays and SC (flow management window) were
                                                     opened )of monitoring user.
          Problem to close VisuTM window on nominal Unable to close the MCW with both logout and exit commands, we use task manager                  Integ -
83589     MCW after a backup switch                  window for closure.                                                                             Integration   IAT M&C-TTFEE       mi - minor     VisuTM        CS-SI
                                                     On M&C, when a parameter oriented request is submitted to DH via a DG user (same
                                                     behavior from DH), we have the CRITICAL message regularly in logbook, “TMProcessing
                                                     could not load file
                                                     %s/MC_INT_EXCHANGES/DCS/ATV/20070308_171236_UTC0847884421_TMPackets_
                                                     0.xml” (see file join errorTMTrendAnalysis.bmp). Several files
                                                     20070308_171236_UTC084788421_TMAffectations_x.xml or
                                                     20070308_171236_UTC084788421_TMPacket_x.xml appear in the directory
                                                     /MC_INT_EXCHANGES/DCS/ATV +
                                                     20070308_171236_UTC084788421ID250000_rqtHKDiag.bin concerning previous context
                                                     used during M&C V6.1 validation (issued from CS MDB) are present on odbs server even
                                                     though they are regularly suppressed manually (they are downloaded in this directory
                                                     every time M&C is started).                                                                     Integ -
83602     Old diagnostic packets files are loaded    The TrendAnalysis process shall not stop in that case.                                          Integration   IAT M&C-DG          C - Critical   DH            CS-SI
                                                     we send via www-dg a parameter request (see file res_perf_param_null.xml) with a period
                                                     selected does not contain data. The result file .png is created but empty. It is not possible
          Create a png file when the period selected to read the contents of the file.                                                               Integ -
83604     does not contain data                      Context backup switch with FDS nominal and backup diffusion of ATV and ISS real time            Integration   IAT M&C-DG          mi - minor     DH            CS-SI
                                                     data:
                                                     Servers used: ttst1 nominal, ttst2 redundant, ttstb1 bu

                                                       In DEXConnection file of ttst1 and ttst2 we define :
                                                       fdb1 as nominal fdb2 as redundant fdbb1 as bu

                                                       In DEXConnection file of ttstb1 we define:
                                                       fdbb1 as nominal, fdb2 as redundant and fdb1 as backup

                                                       on TTST1 kill of MainSC and Acquisition
                                                       on ODBST1 kill of TC ingestion and TM ingestion
                                                       on TTST2 kill of TMacq and Dex
                                                       on ODBST2 kill of MainSC

                                                       In the logbook we can see that in the following order :
                                                       10 connections tentative are made on fds redundant on ports 1500 (ATV real time) and
                                                       then 10 other on port 1501 (ISS real time).
                                                       10 connections tentative are made on fds nominal on ports 1500 (ATV real time)
                                                       10 connections tentative are made on fds redundant on ports 1501 (ISS real time)
                                                       10 connections tentative are made on fds nominal on ports 1501 (ISS real time)
                                                       At the end the connection is established between M&C and fds backup on ports 1500
                                                       (ATV real time)

                                                       And after 3min and 35 sec connection are established on M&C: the backup switch is
                                                       finished.
                                                       For FDS, connections are established after 6 minutes later after switch.Certainly due to
                                                       the many tentative to connect to fds back up server.

                                                       Detail:
                                                       Switch of ODBS 14:10:00 -> 14:13:40.
          Problem to connect to FDS backup after a     During switch 3 seconds of lack on ISS and 6 min 02 sec on ATV.                               Integ -
83605     switch                                                                                                                                     Integration   IAT M&C-FDS         Ma - Major     SC            CS-SI
                                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                  M&C 241000

                                                                                                                                                                                                       Configurati    Entity in
Reference Title                                        Description                                                                                       Phase      Context reference    Criticality    on Item        charge     Comments


                                                       Test sur une chaine stand-alone.
                                                       Au début du test nous avions : les flots TM, TC et les diffusions vers EST et FDS ouverts.

                                                       Les process TMProc et MSUManagement sont tombés simultanément lors d'un dump de
                                                       donnees MSU unconfirmed. La fermeture et la reouverture du flot TM n'a pas suffit a
                                                       relancer TMProc. Nous avons du arrêter et redemmarrer TTS et ODBS. Voir fichiers
                                                       joints :
                                                       SVT4C-TPO-CAM_070330_123704_ttsb2_logs.tar.gz,
                                                       SVT4C-TPO-CAM_MSU.problemRestart.tar.gz
                                                       SVT4C-TPO-CAM_problemDecom.zip

                                                       Après avoir redémarré les serveursTTS ODBS, et relancé le flot TM, le process
                                                       MSUManagement est tombé dès l'ouverture du flot TC à la relecture de son contexte.

                                                       On a continué le test avec le process MSUManagement tombé.

                                                       Contexte utilisé :
          TMProc et MSUManagement tombent lors         1_1.ChainB2.MC-6-0-2.R4-0_D12-Draft2_C_3.2007-03-05.tar.gz (envoyé à CS au travers
83618     d'un dump de données MSU                     d'uranus)                                                                          Oper - Oper              SVT4C_TPO_CAM        Ma - Major                   CS-SI

                                                       Une des IHM de suivi TimeTAG affiche 3 fois l'OBIT et 3 fois avec des valeurs differentes,
                                                       de plus un des OBIT clignote. Traces récupérées dans le fichier joint.

                                                       Test sur une chaine stand-alone.
                                                       Flots TM, TC, diffusions vers EST et FDS ouverts.
                                                       Contexte disponible dans la FA 83618 : SVT4C-TPO-CAM_MSU.problemRestart.tar.gz

83620     Problème avec l'IHM de suivi TimeTAG         Révision 1 : rajout de la priorité                                                            Oper - Oper   SVT4C_LEOP           mi - minor     TC            CS-SI
                                                       Si le FCC utilisé par la tache TC est en timeout, l'execution d'un Verify ou d'un Wait and
                                                       Verify tombe en timeout alors que les bonnes valeurs de TM sont recues.

          Probleme sur l'execution d'un Verify ou d'un Test sur une chaine stand-alone.
          Wait and Verify si le FCC utilise par le tache Flots TM, TC, diffusions vers EST, Central DaSS et FDS ouverts.
83621     TC est en timeout                              Contexte et logs disponible dans la FA 83618                                               Oper - Oper    SVT4C_LEOP           mi - minor     TC            CS-SI
                                                         On a connecté une 20aine de MCW avec les IHM "TCDiffusion" et "suivi OMP" ouvertes.
                                                         Au moment de l'ouverture de la diffusion vers FDS, Tous les voyants dans la fenêtre de
                                                         supervision des flows étaient au vert, le FDS se voyait bien connecté mais ne recevait pas
                                                         de TM. Le process DEX est tombé simultanément avec le message applicatif "Out Of
                                                         Memory Error". Il nous a été impossible de fermer/ouvrir un flot. On a du arrêter les
                                                         serveurs (stop_TTS, stop_ODBS)

                                                       Temps simu : 10h13 Temps TU sol : 06h08

                                                       Test sur une chaine stand-alone.
          Process DEX tombant à l'ouverture de la      Flots TM et TC ouverts.
83622     diffusion vers FDS                           Contexte et logs disponible dans la FA 83618                                                  Oper - Oper   SVT4C_TPO_CAM        C - Critical   DEX           CS-SI
                                                       Nous nous sommes apperçu qu'il y avait des fichiers commençant par un point dans le
                                                       répertoire /MC_APPS/server_root/data_www/dynamic/<user>, qui ne sont jamais détruit
83652     Fichiers résiduels DH                        (voir fichier joint)                                                                          Test - Test                        mi - minor     DH            CS-SI

                                                       Logbook request containing following parameters :
                                                       period N°1: 07:00:00.000 20/04/2007 - 08:00:00.000 20/04/2007
                                                       Vehicle: ATV
                                                       Result file : test_bd
                                                       Issuing this request, a result file is created and contains all informations (see join file
                                                       test_bd_20070420_080020)
                                                                                                                                                     SysVal -
          Problem retrieving datas from Databank via For the same logbook request with the "listing" option, display can't be done, an error         System
83725     logbook extraction request on DH           message is displayed in DH result window (see the file requestlogbookwithoutfile)               Validation    Test_Perf            mi - minor     DH            CS-SI
                                                                                                          14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                      M&C 241000

                                                                                                                                                                                                       Configurati    Entity in
Reference Title                                         Description                                                                                       Phase     Context reference    Criticality    on Item        charge     Comments
                                                        Test:
                                                        IT_EST_V_part2

                                                        configuration:
                                                        M&C diffuse de la TM temps réel ATV+ISS ainsi qu'un replay vers entité "Ext"

                                                        description:
                                                        - on ouvre le flot TM ATV real => on reçoit de la TM ATV real côté M&C
                                                        - on fait une requète ISS real => on reçoit la TM ISS real côté M&C
                                                        - on ouvre la diffusion vers Ext => les paramètres ATV et ISS real sont diffusés à Ext.
                                                        Deux logs "DEX_Out" sont créés sous
                                                        /MC_EXT_EXCHANGES/DEX_Out/EST_ATVProcessedTM/ et
                                                        /MC_EXT_EXCHANGES/DEX_Out/EST_ISSProcessedTM/
                                                        - on laisse la diffusion tourner et on lance un replay de données ATV+ISS, et on coche la
                                                        case de diffusion vers "Ext" => sous visuTM on visualise correctement les données
                                                        rejouées et Ext reçoit correctment les données ATV.
          pas de log DEX_Out créé pour un replay de                                                                                                   Integ -
83736     donnée ATV temps réel                         Problème : aucun log DEX_Out n'est créé côté M&C                                              Integration   IT_EST_V2_part2     mi - minor     TMProc        CS-SI
                                                        "Step 16 :
                                                        Sur les 4 mises en référence acceptées, une seule a sa date de proposition renseignée.
                                                        Les autres ont une date « null » : the proposed entity has been accepted on null by
                                                        db_oper
                                                        Le premier message est bon mais pas les autres.
                                                        On reteste a nouveau.
                                                        En cliquant avec qq sec d‟ecart sur l‟acquittement de l‟overwrite, les dates sont
                                                        renseignées.
          Sur les 4 mises en référence acceptées, une En cliquant rapidement, la seconde date n‟est pas renseignée
83785     seule a sa date de proposition renseignée                                                                                                   Accep - Accep TST_FCT_DB_0065     mi - minor     TDB           CS-SI
                                                        quand on récupère une stack initialisee par le commander, qu‟on la modifie et que l‟on fait
          le nom du user dans la status bar d'une local un save as sous expert, la status bar de la fenêtre de préparation des TC ne se met pas a
          stack n'est pas modifie si la stack est       jour pour le nom d‟utilisateur (tjs cmd_oper au lieu de exp_oper)
83787     modifiee par un autre user                                                                                                                  Accep - Accep TST_FCT_TC_0020     mi - minor     TC            CS-SI
          Pour les displays courbes, la zone de la
          status bar se redimensionne                   Pour les displays courbes, la zone de la status bar se redimensionne dynamiquement a
83794     dynamiquement                                 cause de la taille des champs affichees. Cela ne se produit pas sur les autres displays       Accep - Accep TST_FCT_SY_0010     mi - minor     VISUTM        CS-SI
                                                        Les iss de type 4 ne s‟affiche pas sur les courbes ce qui est normal mais par contre les
          Les iss de type 4 s‟affichent en gris au lieu valeurs s‟affichent en gris au lieu de s‟afficher en vert comme dans la quick page.
83795     de vert sur les displays courbes.                                                                                                           Accep - Accep TST_FCT_SY_0010     mi - minor     VISUTM        CS-SI
                                                                                                                                                                                                                                  CRE M&C V6.3 : OPS-MIN-
                                                                                                                                                                                                                                  241000-50958-CNES :
                                                                                                                                                                                                                                  Apres
                                                                                                                                                                                                                                  deconnection/reconnection
          Apres deconnection/reconnection du flot                                                                                                                                                                                 du flot VisuTM, les lignes
          VisuTM, les lignes oranges ne sont plus       Step 21 : On modifie une loi de monitoring (ligne marquee en orange), apres                                                                                               oranges ne sont plus
83798     marquees                                      deconnection/reconnection du flot VisuTM, la ligne n‟est plus marquee en orange.               Accep - Accep TST_FCT_SY_0010    mi - minor     VISUTM        CS-SI        marquees
                                                        " Le monitoring plan n‟a pas suivi la bascule correctement, sur le nouveau TTS nominal, il
                                                        n‟y a plus les fichiers des plans et sous plans. Seul un fichier qui décrit la modification
                                                        d‟une loi de référence (loi modifiee via l‟interface) a suivi la bascule. Apres deconnexion
                                                        reconnexion de VisuTM au flot, le monitoring est resete y compris la loi modifiee.
                                                        Contournement : reappliquer le plan
                                                        Note : après redémarrage du redondant et reapplication du plan, les fichiers de plan et
                                                        sous plan sont recopies
                                                        Note 2 : on s‟est aperçu que le redémarrage en redondant d‟un serveur ne recupere pas
                                                        le monitoring plan ce qui q pour effet de perdre le monitoring en cas de nouvelle bascule
                                                        (car on ne peut pas reappliquer un plan tant qu‟il est actif sur le nominal) Par contre, si on
                                                        applique un sous plan, TMProc, sur le redondant, tombe car il essaye d‟appliquer un sous
          Le monitoring plan n‟a pas suivi la bascule   plan sur un truc inexistant."
83799     TTS correctement                                                                                                                             Accep - Accep TST_FCT_SY_0010    C - Critical   VISUTM        CS-SI
                                                                                                      14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                    M&C 241000

                                                                                                                                                                                                   Configurati    Entity in
Reference Title                                      Description                                                                                     Phase      Context reference    Criticality    on Item        charge     Comments


                                                     "Lors du test de stabilité, des fuites mémoires importantes de javaw.exe ont été
                                                     constatées.
                                                     Le process javaw.exe prennent 1170 MOctet en Memory Usage sur un MCW (MCWT03)
                                                     avec quickpage, courbes, alphapage et OMP monitoring et sur un MCW (MCWT02) avec
                                                     quickpage, courbes, 2 mimics . Un autre MCW (MCWT05) ne contenant que des quicks
                                                     page et des courbes affiche un Mem Uage de 300MOctets pour javaw.exe.
                                                     Je ferme l‟alpha page sur le MCWT03 avec un javaw.exe a 1 169 432 kOctets de Mem
                                                     usage : la mem usage continue de monter.
                                                     Je ferme l‟OMP monitoring sur le MCWT03 avec un javaw.exe a 1 169 796 kOctets de
                                                     Mem usage : la mem usage se stabilise.
                                                     Je ferme 1 mimic sur MCWT02 avec un javaw.exe a 1 175 252 kOctets de Mem usage :
                                                     la mem usage continue de monter, fermeure de la deuxieme mimic a 1 175 420 Ko : la
                                                     mem usage continue de monter
83801     Fuite mémoire importante de javaw.exe      Je ferme le plugin TC 1 175 800 Ko : la mem usage fait un saut de 1 Mo puis redescend." Accep - Accep TST_STA_SY_0010          Ma - Major     MCW           CS-SI
                                                     FA 83247 : validée : En validant cette FA, en proposant (clic dans IHM de proposition de
                                                     requete systematique) une requête au db_oper, le DH sur le poste du mon_oper est
                                                     tombe sur un ecran d‟erreur (voir fichier joint). Par contre , le db_oper a bien recu cette
          En proposant une requête systematique au   demande et a pu l‟acceptée. (requête jointe). Apres un stop_DH/start_DH, le phénomène
          db_oper, le DH sur le poste du mon_oper    ne s‟est pas reproduit.
83802     est tombe sur un ecran d‟erreur                                                                                                        Accep - Accep TST_FCT_DH_0050      mi - minor     DH            CS-SI
                                                     Lors du test PO_PHAS_C_1, le M&C n'a pas calculé le time offset et ne l'a donc pas
                                                     diffusé au FDS. Il n'y a pas eu de fichier généré sur le TTS sous
                                                     /MC_APPS/System/data/ATV (la date de test était le 25/04/2007 et la date simulée le
                                                     18/04/2007).

                                                     Contexte : Une chaine démarrée en stand-alone, flots TM et TC ouverts, diffusions vers le
                                                     FDS et le local DaSS ouvertes

                                                     Fichiers joints :
                                                     070427_075844_ttsb1_logs.tar.gz : logs du TTS sauvés en cours de test
                                                     Logfiles_TTS_PHAS_C_1.tar.gz : logs du TTS sauvés après le test
                                                     Logfiles_ODBS_PHAS_C_1.tar.gz : logs de l'ODBS sauvés après le test
                                                     1_3.ChainB1.MC-6-1-3.R4-0_D12-Draft2_A_1.20070424.tar.gz : contexte utilisé (déposé
83803     Pas de génération du fichier time offset   sur Uranus dans le répertoire /from_cnes/FA83803/)                                          Oper - Oper   PO_PHAS_C_1          Ma - Major                   CS-SI

                                                     Pendant les essais JIS, nous avons eu des messages (cannot compute on board time ....)
                                                     dans la vue „alarm logbook‟, qui indiquaient la même chose, sauf que l‟un est en
                                                     „WARNING‟, l‟autre en „CRITICAL‟. Les „WARNING‟ étant générés par le tts nominal et
                                                     les „CRITICAL‟ par le tts redondant. Pourquoi une telle différence de traitement ? Le
                                                     même message peut-être une fois „WARNING‟ et une fois „CRITICAL‟ ?
83807     Message logbook de criticité différente                                                                                                Oper - Oper   JIS_ETE              mi - minor     Logbook       CS-SI
          Les paramètres du header ne sont pas
          décommutés dans une extraction de type     Les paramètres du header (ainsi que le checksum) ne sont pas décommutés dans une
83809     paquet                                     extraction de type paquet décommuté.                                                        Accep - Accep TST_FCT_DH_0050      Ma - Major     DH            CS-SI
          Les messages %s packets waiting to be      Lorsque des paquets sont 'dumpés' de la fifo DEX, les messages "%s packets waiting to
          send to %s et %s packets are being         be send to %s" et "%s packets are being dumped" sont mélangés dans un même
83810     dumped sont mélangés                       message.                                                                                    Accep - Accep TST_FCT_DH_0050      mi - minor     DEX           CS-SI
                                                     We insert a local stack in operational mode and then we want to cancel the load while the
          No explicit error message in Pop up        M&C is retrieving chosen stack. We have no explicit error message in pop up windows :       Integ -
83859     windows when cancelling stack load         see ErrorWhenCancellingStackInsertion.jpg                                                   Integration   Basic Integration    mi - minor     TC            CS-SI
                                                     Context : TM and TC flows opened with redundancy TTS and ODBS
                                                     TC flow connected to FCC4, FCC3 is redundant FCC.
                                                     When we are switching FCC on cmd_oper MCW , as the FCC 3 (redundant) was not OK,
                                                     a message was displayed to propose to switch on redundant TTS. On cmd-oper MCW,
          Loss of information on SC flow             switching back to FCC4 or closing TC flow was no more possible ( see file
          managerment window when switching to       switchtoFCCnotconnected ).                                                                  Integ -
83862     redundant FCC                                                                                                                          Integration   Basic Integration    Ma - Major                   CS-SI
                                                                                                          14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                  M&C 241000

                                                                                                                                                                                                     Configurati    Entity in
Reference Title                                          Description                                                                                Phase         Context reference    Criticality    on Item        charge     Comments
                                                         Pendant les essais SVT4C, nous avons enregistré de la TM HLTM, qui a la particularité
                                                         d'avoir une date OBUT toujours à 0.
                                                         Lorsque l'on fait une extraction paquet avec décommutation de tous les paramètres, nous
                                                         avons parfois une date à 0 (1980) et parfois des dates OBUT en tant que date des
                                                         paramètres.
                                                         On s'aperçoit que le changement de date s'applique à une heure entière. De 10h00 à
                                                         10h59 date à 0 (05/01/1980 23:59:46.000), de 11h00 à 14h59 date OBUT, de 15h00 à
                                                         15h59 date à 0 (05/01/1980 23:59:46.000)....
          Datation de paquets HLTM non cohérente         Le M&C recevait toute les minutes un paquet de correspondance OBIT/OBUT (aux
83863     suite à extraction DH                          alentours du 18/04/2007 10:00).                                                         Oper - Oper     SVT4C_TPO_CAM        Ma - Major     DH            CS-SI

                                                         TC Diag context is containing ODB_UMI informations.
                                                         Therefore it can be possible that inconsistency may happen when inserting a DIAG ( DIAG
                                                         is rejected as operational context is n), created when operational context n-1 was
                                                         activated.

                                                         Rév 1 :
          Probable inconsistency for DIAG and DaSS
          API ISS request between two different          DaSS API Request is containing ODB_UMI informations.                                      Integ -
83867     operational Context                            Therefore, is not possible to use created ISS DaSS request with two different context.    Integration   Basic Integration    Ma - Major                   CS-SI
                                                         Quand on a voulu couper le flot de diffusion EST, un message CORBA timeout s'est
                                                         affiché, on a perdu les flux sous cmd_oper, et on est bloque pour quitter fenetre sous    SysVal -
                                                         mon_oper.                                                                                 System
83873     Perte des flux lors de l'arret diffusion EST                                                                                             Validation    Test perfo V125      Ma - Major                   CS-SI
                                                         En faisant une transformation de date OBIT -> OBUT-> OBIT, la valeur finale ne redonne
                                                         pas la valeur initiale à 1s près…
                                                         Contenu du fichier ObitObut.data
                                                         obit=42600
                                                         obut_coarse=860967153
                                                         obut_finetime=71
                                                         ....
                                                         Les résultats obtenus sont:
                                                         Obit Obut
                                                         100009 --> 860972893.80
                                                         100001 <-- 860972893.80
          Erreur dans la conversion du temps             La différence est de 8/10 de seconde. La différence maximum de ce genre de
83876     OBIT/OBUT                                      manipulation ne peut excéder 1/10 de seconde.                                             Prep - Prep                        mi - minor     System        CS-SI

                                                     Apres analyse de fichiers DEX_out apres diffusion EST de TM ATV SIMU, nous avons
                                                     remarqué des différences de temps OBUT "paquet" (ie donné par le YSTIME1 et le
                                                     YSTIME2) et paramètre (<OnBoardTime> donné pour chaque paramètre diffusé dans la
                                                     partie <data>). Apres analyse il semble que que les valeurs coarse et fine du
                                                     <OnBoardTime> soient inexactes, cf PJ1.
                                                     En PJ2 un extrait (10 premiers paquets) du fichier DEX_OUT converti en ascii.
                                                     Le temps OnBoardTime ne correspond pas à la conversion YStime1+YStime2 pour les
                                                     paquets 2, 3, 9 et 10 (voir PACKET SUMMARY)
                                                     NB : Pour les paquets 4, 5, 6 et 7, la conversion YStime2 en millisec est différente car
          différence entre temps obut paquet et      effectué avec rint (arrondi à l'entier le plus proche)
          paramètre dans la diffusion EST de paquets => il semblerait que l'anomalie ne concerne que les paquets MSU (APID 615 et 616).
83877     MSU                                        n'y aurait-il pas un probleme d'extrapolation intempestif du temps sur ces paquets ?          Test - Test                        Ma - Major     TMProc        CS-SI
                                                     L'affichage du SID est mal géré dans les entêtes des résultats de requêtes DH orientées
                                                     paquets:
                                                     1 - pour un paquet HK, lorsque le SID vaut 0, il n'estp as du tout affiché dans l'entête.
                                                     2 - pour les paquets HTML (APID=116), le SID est affiché.
          Affichage SID mal géré dans l'entête des   Rappel de la règle: le SID n'est affiché que pour les paquets HK (APID=613, PUD=3,
83878     extractions orientés paquets               PUDS=25) et quelque soit sa valeur.                                                           Oper - Oper   SVT4C_TPO_CAM        mi - minor     DH            CS-SI
                                                     When preparing a stack, we are updating parameter MSU_Q_J2000_SASP_SET_3 of TC
                                                     S108_0202(see InitialTCvalue_effetRebond.bmp), we enter new engineer value : -3 (see
                                                     ChangeValueEffetRebond.bmp). No control seems to be done (see
                                                     AfterChangeValueEffetRebond.bmp): we expect error message as new raw value is lower
                                                     than min value authorized for the TC, and the calculated engineering value after rebond
                                                     effect doesn't correspond to introduced value : -3.0 introduced and around -1.0 after
          No control done when updating engineering rebond effect.                                                                                 Integ -
83886     value for TC parameter                     See also joined files CalibrationFunction.xml and S108_0202.xml                               Integration   Basic Integration    Ma - Major     TC            CS-SI
                                                                                                         14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                    M&C 241000

                                                                                                                                                                                                      Configurati    Entity in
Reference Title                                        Description                                                                                      Phase      Context reference    Criticality    on Item        charge     Comments
                                                       Le filtre Catégorie : "TM Events and Alarms" ne fonctionne pas lors d'une extraction
          Filtre "TM Events and Alarms" ne             "Central Logbook Extraction"
83893     fonctionnant pas sur le DH                   Le résultat obtenu donne toutes les catégories.                                              Prep - Prep                        mi - minor     DH            CS-SI

                                                       Context : TTST1/ODBST1 in redundancy with TTST2/ODBST2
                                                       maintenance and switch failures have been done on both TTS and ODBS
                                                       TM and TC flows are opened.
                                                       After closing TM and TC flows, we try to quit from VisuTM plugin on cmd_oper, mon_oper
                                                       and exp_oper MCWs. This was not possible.                                                    Integ -
83921     Unable to quit VisuTM plugin                 P.S Is it similar to AR relating that it is sometimes not possible to close Curve displays ? Integration   Basic Integration    Ma - Major     SC            CS-SI

                                                Test sur une chaine stand-alone.
                                                Au début du test nous avions : les flots TM, TC et les diffusions vers EST et FDS ouverts.
                                                Le process MSUManagement est tombé lors du premier dump de données TC MSU. Voir
                                                fichiers joints :
                                                QO_RVD_N_1_process_down_MSUManagement.jpg (copie d‟écran)
                                                1_4.tar.gz (contexte:déposé sur //uranus/from_CNES/ESSAIS/OQ_RVD_N_1/)
                                                070525_121202_ttsb1_logs.tar.gz (logs sur le TTS)
          MSUManagement tombe lors d'un dump de OperationnalStack.xml.old
83929     données MSU                           PS : à rapprocher de la FA 83618                                                           Oper - Oper            OQ_RVD_N_1           Ma - Major                   CS-SI


                                                       En cours de test, l'IHM de diffusion TC et l'IHM de diffusion suivi OMP ne se sont plus mis
                                                       à jour régulièrement. On a constaté des ralentissements puis des gels de ces IHM, qui
                                                       rendaient impossible le suivi de l'envoi de TC et le suivi de l'OMP. Ce problème a été
                                                       constaté sur la plupart des MCWs pendant l'essai et à plusieurs reprises.
                                                       La fermeture / ouverture de l'IHM de diffusion des TC ne permettait pas de retrouver un
                                                       état stable : l'historique est rafraichi mais pas les parties In Progress and Active stack.
                                                       Au redemarage d‟une diffusion, il relit un état courant mais ne reprends rien
                                                       dynamiquement.
                                                       On n'a pas pu arreter et redémarrer les fenêtres de suivi OMP.
                                                       Par contre, à un moment du test on avait : 20 MCW avec la diffusion OMP figée et 1
                                                       MCW avec la diffusion OMP fonctionnant correctement.
                                                       Entre 12:05 et 12:08 (heure système), nous sommes passés en mode trace.
                                                       PS : le process MSUManagement était déja tombé lors du premier dump de données TC
                                                       MSU (voir FA 83093).
                                                       Voir fichiers joints de cette FA 83093 :
                                                       1_4.tar.gz (contexte)
          Problemes de diffusion TC et de diffusion    070525_121202_ttsb1_logs.tar.gz (logs sur le TTS)
83931     suivi OMP                                    OperationnalStack.xml.old                                                                   Oper - Oper    OQ_RVD_N_1           Ma - Major     TC            CS-SI
                                                       En cours de test, le process Notify Service est tombé en Unexpected termination.
                                                       Exactement au même moment, en essayant d'acquitter des alarmes, le MCW
                                                       "Monitoring" à perdu le flot TM et s'est crashé.
                                                       Voir fichier joint :
83932     Perte du process NotifyService               070525_161110_ttsb1_logs_NotifyService.tar.gz                                               Oper - Oper    OQ_RVD_N_1           Ma - Major     SC            CS-SI

                                                        Connecté avec le profil "system" le system logger est lancé pour suivre les éventuels
                                                        soucis systeme sur les serveurs. L'onglet ODBS est créé mais il manque l'onglet "TTS".
83935     absence de l'onglet tts dans le systen logger Cf PJ.                                                                                      Test - Test   SVT4C dry run        mi - minor     SC            CS-SI
                                                        For some parameters (direct or derived), some problems on the curve displays:
                                                        The parameter is declared valid in the inspector and in the alphanum pages, but "NOT
                                                        VALID" in the curve: it is displayed in grey and not plotted.
                                                        Here after you'll find an hard copy of the screen where you one can see:
                                                        - in the inspector view: DS102PI is valid and the last occurrence is 20:08:15
                                                        - in the quick page the parameter is displayed in green: it is valid!
                                                        - In the curve it's value is correct (LPRECSOF) but displayed in grey and not plotted.
83974     Problem of parameters' validity                                                                                                           Prep - Prep                        Ma - Major     VISUTM        CS-SI
                                                        VET support has instanciated the TC FRMS_SC_ORB_SET_ACTIVATE with a time tag
                                                        command at 14/04/2007 23:19:51.5

                                                     Then the FCP has been proposed to the commander which has inserted in the
          Slight modification (a few 1/10th of a     Operational stack but the time tag time was 14/04/2007 23:19:51.0 instead of 14/04/2007
          second) in the execution date of a TTAG TC 23:19:51.5                                                                                     SysVal -
          between the proposed stack and the stack                                                                                                  System
83977     available to the Commander                 Remark : The precision required for on-board execution is never less than 1 second.            Validation    OQ_LEOP              mi - minor     TC            CS-SI
                                                                                                           14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                         M&C 241000

                                                                                                                                                                                                          Configurati    Entity in
Reference Title                                         Description                                                                                         Phase     Context reference     Criticality    on Item        charge     Comments
                                                                                                                                                        SysVal -
          L‟impression d‟une courbe se fait sur 2       L‟impression d‟une courbe se fait sur 2 pages lorsque un des axes contient plusieurs            System
83986     pages                                         paramètres.                                                                                     Validation   OQ_RDV_N_1            mi - minor     VisuTM        CS-SI

                                                          Anomalie sur dates contenues dans le fichier d‟instanciation OMP des FCM_SC_BOOST :
                                                          Date originale / date convertie à partir de l‟OBIT calculé par M&C
                                                          02:18:02.8 / 02:18:01.9                                                                    SysVal -
          Erreur lors de l'instanciation d'un OMP : biais 03:03:39.6 / 03:03.38.9                                                                    System
83987     dans les dates instanciées                      03:48:05.7 / 03:48:04.9                                                                    Validation      OQ_RDV_N_1            C - Critical   TC            CS-SI
                                                          Suite à la DM 83142, il a été noté qu'un seuil paramètrable manquait. Ce seuil concerne le
                                                          nombre de paramètre dans la requête faite par les partenaires.
                                                          Rappel de l'énoncé de la DM:
                                                          A la réception de chaque requête ATV
                                                          * Le M&C affiche déjà au logbook la liste des UMI demandés par les clients.
                                                          * Il faudra en plus :
                                                          - ajouter un message de warning supplémentaire au logbook indiquant le nombre de
                                                          paramètres demandés.
                                                          - si ce nombre dépasse une valeur configurable, ajouter un message en alarm de niveau
                                                          warning rappelant le nombre de paramètre demandés et le nombre de paramètres
          Seuil manquant dans la limitation des           maximum conseillé : DaSS request for <XXX> ATV parameters has been received, which
83991     paramètres ATV diffusés au DaSS                 is superior to <YYY>. All the parameters may not be distributed.                                                                 Ma - Major     DEX           CS-SI
                                                                                                                                                     SysVal -
          Acquittement centralisé des alarmes n‟est       L'acquittement centralisé des alarmes par le profil Monitoring n‟est pas répercuté sur les System
83997     pas répercuté (non systématique)                autres MCW héritant du plan de surveillance en question.                                   Validation      OQ_RDV_N_1            Ma - Major     VISUTM        CS-SI

                                                        Le time-out des post-control TC est trop court. En effet, il est de l'ordre de 20 secondes,
                                                        donc il échoue souvent lorsqu'il porte sur des TMs raffraîchies toutes les 60 secondes.
                                                        La VET propose de le passer à 70 secondes.
                                                        Remarque : Avec le time-out actuel, le post-control TC est très souvent failed faute d'avoir
                                                        reçu une valeur de la TM pendant le time-out, et il faut donc que l'opérateur le relance très   SysVal -
          Le time-out des post-control TC est trop      souvent, ce qui représente une charge inutile et même une perte de temps si on loupe à          System
84000     court                                         nouveau l'occurence de la TM.                                                                   Validation   SVT EXV               Ma - Major     TC            CS-SI
                                                        A 12h45 (heure locale), lors d'un changement de set HK, trou TM vu sur 3 MCW :
                                                        MCW24, 29 et 45 et pas sur les autres.                                                          SysVal -
          Trou TM sur 3 MCW lors d'un changement                                                                                                        System
84002     de set HK                                    MCW24 était loggé en vet_exp, MCW29 en Monitoring et MCW45 en Commander.                         Validation   SVT EXV               C - Critical                 CS-SI
                                                       Sur la vue alarme, des alarmes acquittées sur des paramètres passés depuis non
          Des alarmes acquittées sur des paramètres significatifs restent dans la vue alarme.                                                     SysVal -
          passés depuis non significatifs restent dans Ces paramètres ne doivent disparaitre de la vue alarme que lorsque une valeur valide est System
84004     la vue alarme.                               reçue.                                                                                     Validation         SVT EXV               C - Critical   TMProc        CS-SI
                                                       Heure simulée : 1/5/07 à 10h00, SV746S1_ (qui est un paramètre dérivé) vaut 0,43V.
                                                       Sa surveillance vérifie que > 29V (avec un filtre de montée à 3 et un paramètre
                                                       redescendant au moins 1 fois par minute). Or aucune alarme n'est levée. Un inspector sur
                                                       SV746S1_ permet de vérifier que sa surveilance >29V est bien active.
          Suite modifs état de surveillance via IHM                                                                                               SysVal -
          Current Monitoring, un paramètre en          N.B. : 15 minutes auparavant, la surveillance de ce paramètre a été désactivée puis        System
84008     anomalie ne lève plus d'alarme               réactivée via l'IHM Current Monitoring.                                                    Validation         SVT EXV               C - Critical   TMProc        CS-SI
                                                       Heure simulée : 1/5/07 à 11h40.
                                                       Au bout d'environ 12 heures de fonctionnement, "TM LOSS" est affiché de manière            SysVal -
          "TM LOSS" affiché de manière erronée sur 5 erronée sur 5 postes MCW de la VET (sur 6). Le 6ème poste est le profil Monitoring qui       System
84009     postes MCW de la VET (sur 6).                continue de voir la TM correctement raffraîchie.                                           Validation         SVT EXV               C - Critical   TMproc        CS-SI
                                                       When asking for a local replay on exp_oper MCW, we have error message : "no telemetry
                                                       archives available for this period time, vehicle and environment"
                                                       Environment = on-going
                                                       vehicle = ATV
                                                       periode = 12/06/2007 12:04:03 - 12/06/2007 13:04:03
                                                       Using Databrowser, we check that telemetry is correctly put in Databank for this period
                                                       and vehicle : it's OK
                                                                                                                                                  Integ -
84010     Local Replay is not possible                 We check that central replay can be done : it's OK for this period and ATV vehicle         Integration        Basic Integration V135 Ma - Major    VISUTM        CS-SI
          TMProc et TMAcq sont tombes a la             TMProc et TMAcq sont tombes a la fermeture de la diffusion FDS (ordre d‟ouverture
84014     fermeture de la diffusion FDS                important : diff FDS puis diff EST puis fermeture diff FDS)                                Accep - Accep      TST_FCT_SY_0190.R C - Critical                     CS-SI        Filtered
                                                       Hors test: on ouvre la mimic des groupes de paramètre sans connecter visuTM au flot,
          Problème d'accès aux descripteurs de         dans l‟inspector, il ne trouve plus les descripteurs de groupe (adresse mémoire java) Voir
84015     groupe si pas de flot connecté               capture d‟écran.                                                                           Accep - Accep      TST_FCT_TV_0115       mi - minor                   CS-SI        Filtered
                                                                                                                14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                             M&C 241000

                                                                                                                                                                                                                   Configurati    Entity in
Reference Title                                               Description                                                                                         Phase      Context reference       Criticality    on Item        charge     Comments
          Sur l‟ouverture du dialog, ce n‟est pas la          Step 25 : sur l‟ouverture du dialog, ce n‟est pas la regle active qui est affichee par defaut
84016     regle active qui est affichee par defaut            (idem dans l‟editeur de sous plan)                                                              Accep - Accep TST_FCT_TV_0260         mi - minor                   CS-SI        Filtered
                                                              Step 19: On ne peut pas imprimer l‟editeur de sous plan. On essaie sur la page alarme,
            On ne peut pas imprimer l‟editeur de sous         limpression a lieu. On reessaie avec lediteur de sousplan et cela ne fonctionne toujours
84017       plan.                                             pas. FA à ouvrir P2 (voir err.log)                                                              Accep - Accep TST_FCT_TV_0265         mi - minor                   CS-SI        Filtered
                                                              A la neuvième ouverture de flot, le TMProc redondant est tombé. La raison reste obscure
                                                              : pas de core. (voir hard copy du logbook et des alarmes + .txt extraction Dh du logbook)
            A la neuvième ouverture de flot, le TMProc juste avant : fermeture en switchant TDRS/ARTEMIS role(principal/secondaire). Pas
84018       redondant est tombé.                              reproduit.                                                                                      Accep - Accep TST_STA_SY_0020         Ma - Major                   CS-SI
                                                              Step 3 :A la 8eme reconnection, l‟IHM SC de central flow attend toujours le demarrage du
            A la 8eme reconnection, l‟IHM SC de central flot de TC alors qu‟il est bien lance sur ttst1 et ttst2. On est oblige de faire Mask dans
            flow attend toujours le demarrage du flot de l‟IHM de lancement du flot. Dans le logbook on voit le message TC flow1 is available pour
84019       TC alors qu‟il est bien lance sur ttst1 et ttst2. ttst2 mais pas pour ttst1. idem dans le log de SC du ttst1.                                     Accep - Accep TST_STA_SY_0020         mi - minor     SC            CS-SI
                                                              On arrete le tts redondant apres avoir tue le SC, on ferme les flots TC, DaSS et diffusion.
                                                              On rouvre le flot de diffusion DaSS. Le process DEX tombe et fait un core. Pas de traces
84020       Le process DEX tombe et fait un core              dans les logs.                                                                                  Accep - Accep TST_STA_SY_0020         Ma - Major     DEX           CS-SI
                                                              suite à la recette, un certain nombre de définition de DIAG étaient en base (0,1, 2, 3, 4).
                                                              Nous avons défini et envoyé une TC de définition du diag 19 (17:30 heure UTC).
                                                              Nous avons fait une requête orientée paquet avec filtre 3,26. Nous avons pu voir des
                                                              paquets dont le SID allait de 0 à 19.
            Le DH ne décommute pas tous les paquets Nous avons fait la même requête en décommutant tous les paramètres des paquets. Seul
84026       de DIAG                                           le diag 0 était décommuté.                                                                      Oper - Oper   SVT4C                   Ma - Major     DH            CS-SI
                                                              Impossible d'attacher un display (mimic, courbe, page alpha) à un bouton de navigation
84031       Anomalie bouton de navigation                     dans les mimics. Le popup contenant la liste des display n'apparait.                                                                  Ma - Major     VisuTM        CS-SI
                                                              Vehicle : ATV,
                                                              Database : On-Going,
                                                              Version : 1_14
                                                              When we open one TC flow, the informatif message displayed in the logbook doesn't
                                                              contain the FCC name, whereas the name is well known because shown in the column
                                                              FCC of the window central flow.
            The FCC name is not displayed in the              ( see file : UnknownFCCmessage)                                                                 Integ -
84034       logbook                                                                                                                                           Integration   Basic Integration V135 mi - minor      Logbook       CS-SI
                                                              Vehicle : ATV,
                                                              Database : On-Going,
                                                              Version : 1_14
                                                              On cmd_oper , on pluggin TC, when we open OMP Monitoring window, after few moment,
                                                              we click on cancel button, the window closes normally.
            Error message when we reopen the OMP              If we reopen OMP Monitoring window, a popup „OMP initialisation‟ displays with the              Integ -
84037       Monitoring                                        message "org.omp CORBA TIMEOUT "                                                                Integration   Basic Integration V135 Ma - Major      TC            CS-SI
                                                              Vehicle : ATV,
                                                              Database : On-Going,
                                                              Version : 1_14
                                                              On cmd_oper , on pluggin TC, we insert the TC Enable RID (R001_1413) but when we
            the list of the values proposed in engineering select an engineering value, the list of the values proposed in engineering value is not in        Integ -
84039       value is not in the alphabetical order.           the alphabetical order.                                                                         Integration   Basic Integration V135 mi - minor                    CS-SI
                                                              Contexte : AGCS, on-going , login db_oper
                                                              When creating a TC histo DH request with parameter ATV as vehicle and choosing option
                                                              "result file" in Result Section, it is not possible to enter name for result file.
                                                              Same problem when creating TMPacket request or creating TC Histo request with
                                                              another MCW (atv_sys profile).
            DH new source files are not taken into            After investigation, DH source files concerning V6.3 have not been taken into account
            account because of .original files present in because of the presence of files ".original" in the same directory during installation of M&C       Integ -
84041       same directory                                    product on ODBS Server.                                                                         Integration   Basic Integration V135 C - Critical    DH            CS-SI
                                                              Contexte : AGCS, on-going , login db_oper
                                                              When creating a scheduled TC History request, we enter file name result that contains
                                                              less than 5 characters. When we launch it, it is not submitted and no error message
                                                              window appears during saving or launching this request. Only warning message is
                                                              displayed in logbook that is not visible when plugin DH is open (see join file
            When result file name have less than 5            longueur_fichier_resul_pour_DG).
            caracters, request is not activated and only A control must be done during the input of result file name and a pop up message window              Integ -
84043       warning message in logbook is displayed           must notify the operator of the error.                                                          Integration   Basic Integration V135 mi - minor      DH            CS-SI        PPz
                                                                                                           14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                        M&C 241000

                                                                                                                                                                                                         Configurati    Entity in
Reference Title                                         Description                                                                                      Phase      Context reference      Criticality    on Item        charge     Comments
                                                        On atv_sys MCW
                                                        we add some functions to cmd_oper profile but we forget to trigger "apply".
                                                        We go on another profile function window (exp_oper) to see if function's profile are OK
                                                        and we return on cmd_oper's one because we are not sure we made apply when updating
                                                        cmd_oper profile's function. We see it's OK : the function chosen before appear in profile's
                                                        function part and no more on available functions part.
                                                        So we get out of atv_sys plugin and when connecting whith cmd_oper one, we realize that
                                                        chosen functions are not available for this profile : Too bad !
          Apply is not done but IHM shows function in   When coming back on cmd_oper profile's window we should not see the function's               Integ -
84044     profile's function part                       updated in profile's function part when "apply" is not triggered.                            Integration   Basic Integration V135 mi - minor     SC            CS-SI
                                                        Test sur deux chaines: nominale et redondante.

                                                        Lors du test OQ_RVD_N_1, aux alentours de 7:43 heure système, le process
                                                        MSUManagement est tombé sur la chaine redondante (TTS2) et une minute plus tard, le
                                                        même process est tombé sur la chaine nominale (TTS1).

                                                        PS : à rapprocher de la FA 83618 et de la FA 83929 mais cette fois sur deux chaines
          MSUManagement tombe sur le serveur            (nominale et redondante), et pas de TC de load MSU juste avant.
84051     redondant et ensuite sur le serveur nominal                                                                                               Oper - Oper    OQ_RVD_N_1_BIS         Ma - Major     TC            CS-SI
                                                        Vehicle : ATV
                                                        Database : On-Going
                                                        MDB : R4D
                                                        After closing all flows (TC and TM), it is not possible to quit Visu TM plugging on         Integ -
84052     not possible to quit Visu TM plugging         cmd_oper, mon_oper, exp_oper                                                                Integration    Basic Integration V130 Ma - Major                   CS-SI        Identique à la FA 83921
                                                        Lorsqu'on fait un stop_srv.ksh, on a le message :
                                                        " You are about to stop the NOMINAL ODBS application on odbs "

84054     stop_srv.ksh : message incohérent             Le stop_srv.ksh n'arrête pas l'ODBS mais le message est inquiétant.                 Prep - Prep                                   mi - minor     DH            CS-SI
                                                        Error message seen when triggering on "Definition" label on DG server is :
                                                        "Socket connection proble...".
                                                        No result file is created
                                                        A core file is created on ODBS Server in /MC_APPS/DH/exe concerning TrendAnalysisTr
                                                        process

                                                        request Definition seen on DG (when it works)
                                                        <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
                                                        - <result>
                                                        <exec_date>15062007_030500</exec_date>
                                                        <result_file>TPK_MC_Resul_15062007_030500.txt</result_file>
                                                        - <request data_type="tm_packet" edition="resultfile" filename="ResulTMPackno1">
                                                        - <tm>
                                                        - <period>
                                                        <begin_date>D-48h</begin_date>
                                                        <end_date>D-45h</end_date>
                                                        </period>
                                                        </tm>
                                                        - <filter>
                                                        <vehicle>1</vehicle>
                                                        </filter>
                                                        <sampling type="NoSampling" />
                                                        <treatment>Simple</treatment>
                                                        <odb>ON_GOING</odb>
                                                        <value_type>engineering</value_type>
          Error message when submitting TM Packet       </request>                                                                                  Integ -
84055     sheduled request from DH to DG                </result>                                                                                   Integration    IAT Basic+ V135        mi - minor     DH            CS-SI
                                                        Scheduled TMparameter Request have been submitted (1h30 frequency) and Error
                                                        Window opens :
          Error message when submitting TM                                                                                                          Integ -
84056     Parameter sheduled request from DH to DG For error message see joined file : Error_in_request_treatment.jpg                               Integration    IAT Basic+ V135        mi - minor     DH            CS-SI
                                                                                                               14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                      M&C 241000

                                                                                                                                                                                                              Configurati    Entity in
Reference Title                                           Description
                                                          Error message seen when triggering on "Definition" label on DG server is :                            Phase      Context reference    Criticality    on Item        charge     Comments
                                                          "Check TM Hole: TmHoleIndex overlimits.". see joined files
                                                          No result file is created

                                                          Request Definition concerning TMparameter request (when it works)
                                                          <?xml version="1.0" encoding="UTF-8" standalone="no" ?>
                                                          - <result>
                                                          <exec_date>15062007_025523</exec_date>
                                                          <result_file>TPA_MC_ResPa_15062007_025523.txt</result_file>
                                                          - <request data_type="tm_parameter" edition="resultfile" filename="ResParam">
                                                          - <tm>
                                                          - <period>
                                                          <begin_date>D-48h</begin_date>
                                                          <end_date>D-45h</end_date>
                                                          </period>
                                                          </tm>
                                                          - <filter>
                                                          <vehicle>1</vehicle>
                                                          </filter>
                                                          - <parameter>
                                                          <name>YPUDS</name>
                                                          </parameter>
                                                          <sampling type="NoSampling" />
                                                          <odb>ON_GOING</odb>
                                                          <value_type>engineering</value_type>
                                                          </request>
                                                          </result>

                                                             in other case result file produced with folder dispatcher error and request status rejected.
                                                             Concern also TMPacket request via DG.
          Error message when submitting TM Packet Systematic when the period includes a TM Hole, and if the extraction date begins before
          or TM Parameter sheduled request from DH the TM Acquisition.                                                                                      Integ -
84058     to DG                                              In the .processfile , the TM Hole is detected and tagged in the file with the date of the TM   Integration   IAT Basic+ V135      Ma - Major     DH            CS-SI
                                                             In TM Parameter scheduled request result file, first line contains '***' instead of numeric
                                                             value in parameter value column
          In TM Parameter scheduled request result
          file, first line contains '***' instead of numeric See joined file : DH_result_TMParam_Scheduled_Req.txt                                          Integ -
84059     value in parameter value column                                                                                                                   Integration   IAT Basic+ V135      mi - minor     DH            CS-SI
                                                             L'exigence SY_RT_TMAPL_471 dit :
                                                             (...) After a telemetry reception loss, a new alarm shall not replace an existing one except
                                                             if the control raising the alarm is not the same.
          Non-respect de l'exigence                                                                                                                         SysVal -
          SY_RT_TMAPL_471 concernant les                     Or, suite à un trou TM, toutes les alarmes remontent systématiquement alors que les            System
84062     alarmes suite à un trou TM                         télémesures surveillées n'ont pas changé de valeur.                                            Validation    SVT EXV              Ma - Major     VisuTM        CS-SI
                                                             On the MCW Monitoring, during SVT_4C test : there was a shift between columns and
                                                             lines on Event Page.
                                                             For instance Opscode TE10H should have corresponded to Packet FS Name =
                                                             TCC_RID_HEATER_FAIL. And Opscode for RID_5_4 should have been in red.
                                                             We tried to close on open the Event Page. We also tried "Sort Packet OBIT and delete
                                                             rundundant packet", but it didn't work.
                                                             10 minutes later there was no shift between columns any more.
84067     Shift between columns on Event Page                Hard-Copy : SVT4C_EV2_OnEvent.doc                                                              Oper - Oper   SVT_4C               Ma - Major     VisuTM        CS-SI
                                                             Vehicle : ATV
                                                             Environment : On_Going
                                                             Two telemetry flows opened (Artemis & TDRSS)                                                   SysVal -
                                                             The time offset file is transmitted several times to DG (see trace file                        System                                            TimeService
84071     Lot of transmission of Time offset file            TimeOffset__dg1_sdv.xls and configuration file TimeOffset.fcf ).                               Validation    VALT3.C              Ma - Major     s           CS-SI
                                                             Au cours du test OQ_RVD_N_1, le process TCEmission_ATV est tombé sur le TTS
                                                             redondant (tts2) à environs 15 :15 (heure système).
                                                             Alarm message Warning : [TCEmission] TC redundancy stopped (from tts1 host to tts2
                                                             Redundant host)
                                                             Contexte : les process MSUManagement sur les chaînes nominale et redondante, et le
                                                             process TimeServices étaient déjà tombé (voir FA 84051 et 84050). Les fichiers xml
                                                             avaient pourtant été nettoyés sur le TTS redondant (dans le répertoire
84074     TCEmission_ATV process down                        /MC_APPS/TC/data/ATV).                                                                         Oper - Oper   OQ_RDV_N_1_BIS       Ma - Major     TC            CS-SI
                                                                                              14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                             M&C 241000

                                                                                                                                                                                    Configurati    Entity in
Reference Title                                 Description                                                                              Phase   Context reference    Criticality    on Item        charge     Comments

                                                L'utilisation de groupe de paramètre (groupe composé de qlq milliers de paramètres)
                                                dans un display connecté à un flux TM provoque une consommation anormale du CPU.
                                                -Au bout de quelques minutes la consommation CPU est à 100% ,le rafraichisement des
                                                valeurs se fait de façon sporadique.
84088     Groupe de parametres et performance   il faut rebooter la M&C                                                                                              Ma - Major     VisuTM        CS-SI
                                                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                    FDS 242000


                                                                                                                                                                                       Configuration  Entity in
Reference                Title                                                 Description                                  Phase             Context reference          Criticality       Item        charge                                   Comments
  30065   Number of statements in a function        Metric “Number of statements in a function” is out of threshold in      Audit       ATV-CC FDS Quality Report      mi - minor         T-FDB      GMV          CR - Coding rules
                                                    C++ code and it has to be corrected in some complex functions.                      for FDS 2.0 (T-CVI, T-CMP
                                                                                                                                        and T-FDB.) 20/01/2004,
                                                                                                                                        Issue 1, Rev. 0 OPS-RP-
                                                                                                                                        242500-60513-GMV
  30067    Cyclomatic number in a function          Metric “Cyclomatic number in a function” is out of threshold in C++      Test       ATV-CC FDS Quality Report      mi - minor         T-FDB      GMV          CR - Coding rules
                                                    code and it has to be corrected in some complex functions.                          for FDS 2.0 (T-CVI, T-CMP
                                                                                                                                        and T-FDB.) 20/01/2004,
                                                                                                                                        Issue 1, Rev. 0 OPS-RP-
                                                                                                                                        242500-60513-GMV
  31025    Threshold visualisation in translating   When the plot is in translating mode and we deactivate the               Integ      INTEGRATION FDS                mi - minor         T-GNC      GMV          MMI - MMI           11/10/05 : this anomaly shall be treated in the frame
           mode (determined alarm)                  threshold visualization the xtrace plot displays the beginning of the               Test 110 (AR-8)                                                                               of the display update
                                                    plot until a new data are received. This behaviour is not observed
                                                    when the thresholds are activated again.
  32087    Foresys: F90 rules for ATSLIB            Report from Foresys on F90 rules. See attached                           Test       ATV-CC FDS QUALITY             mi - minor        ATSLIB      GMV          CR - Coding rules
                                                    IRR_F90_ATSLIB_V5.0                                                                 REPORT FOR FDS 2.0
                                                                                                                                        (03.00)
  32118    Foresys: F90 rules for TOCF              Report from Foresys on F90 rules. See attached                           Test       ATV-CC FDS QUALITY             mi - minor         T-OCF      GMV          CR - Coding rules
                                                    IRR_F90_TOCF_V2.0                                                                   REPORT FOR FDS 2.0
                                                                                                                                        (03.02)
  32120    MMI Review on TOCF                       IRR on GENESIS rules. See attached file                                  Test       ATV-CC FDS QUALITY             mi - minor         T-OCF      GMV          CR - Coding rules
                                                    IRR_GENESIS_TOCF_V2.0                                                               REPORT FOR FDS 2.0
                                                                                                                                        (03.02)
  32153    Foresys: F90 rules for FDBLIB            Report from Foresys on F90 rules. See attached file                      Test       ATV-CC FDS QUALITY             mi - minor        FDBLIB      GMV          CR - Coding rules
                                                    IRR_F90_FDBLIB_V3.0                                                                 REPORT FOR FDS 2.0
                                                                                                                                        (03.03)
  32155    Foresys: F90 rules for T-FDB             Report from Foresys on F90 rules. See attached file                      Test       ATV-CC FDS QUALITY             mi - minor         T-FDB      GMV          CR - Coding rules
                                                    IRR_F90_TFDB_V3.0                                                                   REPORT FOR FDS 2.0
                                                                                                                                        (03.03)
  32157    MMI review on T-FDB                      Report from Foresys on F90 rules. See attached file                      Test       ATV-CC FDS QUALITY             mi - minor         T-FDB      GMV          CR - Coding rules
                                                    IRR_GENESIS_TFDB_V3.0                                                               REPORT FOR FDS 2.0
                                                                                                                                        (03.03)
  32184    MMI review on T-FDB                      See IRR_GENESIS_TFDB_V4.0                                                Test       ATV-CC FDS QUALITY             mi - minor         T-FDB      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.1
                                                                                                                                        (04.02)
  32216    Foresys: F90 rules for T-FDB             See IRR_F90_TFDB_V4.0                                                    Test       ATV-CC FDS QUALITY             mi - minor         T-FDB      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.1
                                                                                                                                        (04.02)
  32218    Foresys: F90 rules for FDBLIB            See IRR_F90_FDBLIB_V4.1                                                  Test       ATV-CC FDS QUALITY             mi - minor        FDBLIB      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.1
                                                                                                                                        (04.02)
  32219    Foresys: Metrics for FDBLIB              See IRR_F90_FDBLIB_V4.1                                                  Test       ATV-CC FDS QUALITY             mi - minor        FDBLIB      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.1
                                                                                                                                        (04.02)
  32220    Foresys: F90 rules for ATSLIB            See IRR_F90_ATSLIB_V6.3                                                  Test       ATV-CC FDS QUALITY             mi - minor        ATSLIB      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.1
                                                                                                                                        (04.02)
  32222    Logiscope: C++ rules for T-FDB           See IRR_C++_TFDB_V4.0                                                    Test       ATV-CC FDS QUALITY             mi - minor         T-FDB      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.1
                                                                                                                                        (04.02)
  32231    MMI review on T-OCF                      See IRR_GENESIS_TOCF_V3.0                                                Test       ATV-CC FDS QUALITY             mi - minor         T-OCF      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.1
                                                                                                                                        (04.02)
  32232    Foresys: F90 rules for T-OCF             See IRR_F90_TOCF_V3.0                                                    Test       ATV-CC FDS QUALITY             mi - minor         T-OCF      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.1
                                                                                                                                        (04.02)
  32276    MMI review on T-FDB                      See IRR_GENESIS_TFDB_V5.1                                                Test       ATV-CC FDS QUALITY             mi - minor         T-FDB      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.2
                                                                                                                                        (05.01)
  32287    Foresys: F90 rules for T-FDB             See IRR_F90_TFDB_V5.1                                                    Test       ATV-CC FDS QUALITY             mi - minor         T-FDB      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.2
                                                                                                                                        (05.01)
  32296    Logiscope: C++ rules for T-FDB           See IRR_C++_TFDB_V5.0                                                    Test       ATV-CC FDS QUALITY             mi - minor         T-FDB      GMV          CR - Coding rules
                                                                                                                                        REPORT FOR FDS 2.2
                                                                                                                                        (05.01)
  32297    Logiscope: C++ rules for                 See IRR_C++_FDB_SERVER_V5.0                                              Test       ATV-CC FDS QUALITY             mi - minor      FDB_SERVER GMV             CR - Coding rules
           FDB_SERVER                                                                                                                   REPORT FOR FDS 2.2
                                                                                                                                        (05.01)
  35243    TDRS name                                The spacecarft identifier is set to "TDR" instead of "TDRS"             Accep       TP_FDB_VAL_181                 mi - minor         T-FDB      GMV          Log - Software      08/12/2006 : to be discussed for FDS v2.3

                                                    28/08/2006:                                                                                                                                                                       19/03/2007 : to be discussed for FDS v2.4

                                                    We would wish to have the name of spacecraft fully written :
                                                    "TDRS" for TDRS and not "TDR"
                                                                                                                          14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                        FDS 242000


                                                                                                                                                                                     Configuration  Entity in
Reference                 Title                                            Description                                     Phase          Context reference            Criticality       Item        charge                                       Comments
  35246   consistency of ephemeris file         What is the checking performed after the merge in order to                 Accep      TP_FDB_VAL_341                 mi - minor         T-FDB      GMV          Log - Software         28/082006 :
                                                guarantee ethe consistency of ephemeris merging (orbit number ?,                                                                                                                       Visula inspection is not enough , a way to garantee
                                                daily orbit number ?)                                                                                                                                                                  the consistency of the ephemeris generated should
                                                                                                                                                                                                                                       be done : (i.e : orbit number/daily orbit number shoudl
                                                                                                                                                                                                                                       be sequential)

                                                                                                                                                                                                                                       08/12/2006
                                                                                                                                                                                                                                       The checking should be performed y T-FDB on the
                                                                                                                                                                                                                                       resultant ephemeris file.
                                                                                                                                                                                                                                       The modification is not required before FDS 2.3.
35256      TM status panel                      OPS-RfC-242512-83357-CNES validated => to be closed                    Accep          TP_FDB_VAL_110                 mi - minor         T-FDB      GMV          Log - Software

                                                The TM delay included in the TM panel status seems bad
                                                computed => we obtained a huge value whereas the real delay is
                                                around 100 ms
                                                What are the difference between (sync and SYNC ?)

                                                The FDB_TM_PARAM_LIST file is missing from the FDB delivery
                                                package


35257      ISS Sdemi entity generation          ISS Sdemi entity : the entity is bad computed : the sv is well         Accep          TP_FDB_VAL_150                 Ma - Major         T-FDB      GMV          Log - Software         25/05/2007 : To be tested in FDS 2.3.1
                                                generated from SV at F1 format but the entity is not an real
                                                ISS_SDMI entitybu an ISS ABS SV entity : "Statevector_ISS = {                                                                                                                          20/06/2007 : still open : by using T-FDB v6.3 the
                                                …." insteas of "FDB_ISS_SDEMI_SV = { …". The consquence is                                                                                                                             entity produced contents "StateVector_ISS"
                                                that T-ORM can not be used this entity.                                                                                                                                                insted of "ISS_SEDMI"
35261      data package                         With the data contained in the FDB package , we are not able to        Accep          TP_FDB_VAL_184                 Ma - Major         T-FDB      GMV          Validation package -
                                                check the good implementation if this fonction. After having read                                                                                               Validation package
                                                your email it is clear that we get a case where the attitude is null
                                                but what we need is to check (and it was the goal of the RfC
                                                82047) that the merge function works.
35262      FDB server robtness                  This FDB SERVER seems less robust than the previous one.               Accep          TP_FDB_VAL_600                 Ma - Major         T-FDB      GMV          Log - Software         13/06/2007 : Impact is Degradation and not Total
                                                Some times (it is very hard to reproduce the phenomenom) the                                                                                                                           Loss because FDS is not totaly down. Moreover , this
                                                server blinks from" OK "to" no answer " causing problems to run                                                                                                                        AR has not been reproduced since its first
                                                the tools. Moreover, during ATEGUI run (from other machines from                                                                                                                       appearance in system test.
                                                FDB SERVER one), this problem of robustness occurs problems
                                                and a relaunch of tools have been needed.
  35450              Ephemeris name             The name of the ephemeris taken into account for the bulletin          Accep          LOC_TP_ENT_VAL_BULL_B mi - minor                  T-ENT      GMV          Log - Software
                                                computation is not included in the entity ATV_ABSSV generated                         oth_data_eph

  35451                 Source used               The information related to the source used to compute the entity  Accep             LOC_TP_ENT_VAL_MASS_A mi - minor                  T-ENT      GMV          Log - Software
                                                  should be included in the MASS entity                                               TV_Pred
  35452    No error message if the date is in the If we set a date to 01/01/2010 whereas the predicted file stops   Accep             LOC_TP_ENT_VAL_MASS_A mi - minor                  T-ENT      GMV          Log - Software
              future compared to the input files  earlier, no error message appears the computation is done and the                   TV_Pred_err
                                                  results is nul.
  36605    plot of ground track                   the events should appear on the curve and the map on the Earth          Test        TP_DEM_VAL_240                 mi - minor         T-DEM      GMV          MMI - MMI              Please indicate in which version of T-DEM this
                                                  should appear as background                                                                                                                                                          anomaly will be fixed (V2-0 ? )

                                                                                                                                                                                                                                       Each event should be notified with a cross or a point
                                                                                                                                                                                                                                       on the curve (beginning and end of all manœuvres,
                                                                                                                                                                                                                                       fragmentation, impact)

                                                                                                                                                                                                                                       16/01/06 (TDEM v3.0) : beginning and end of
                                                                                                                                                                                                                                       manoeuvre are still not marked with points on plots

                                                                                                                                                                                                                                       08/08/06 : ok for impact and fragmentation points.
                                                                                                                                                                                                                                       there are 3 or 4 cross marks by maneuver point, only
                                                                                                                                                                                                                                       one mark is requested.
                                                                                                                                                                                                                                       for maneuver marks, a diamond ( try L 0.03 in
                                                                                                                                                                                                                                       XTRACE) is preferable to X cross

                                                                                                                                                                                                                                       19/10/06 : In TDEM V4.0, plot is ok for entire track a,
                                                                                                                                                                                                                                       but events aren't notified on partial track plot

                                                                                                                                                                                                                                       07/03/2007: this AR is reclassified minor
                                                                                                                          14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                       FDS 242000


                                                                                                                                                                                     Configuration  Entity in
Reference                    Title                                         Description                                    Phase           Context reference            Criticality       Item        charge                                     Comments
  36606   plot of altitude                       the events should appear on the curve                                     Test       TP_DEM_VAL_240                 mi - minor         T-DEM      GMV          MMI - MMI             This should be corrected in V2.0

                                                                                                                                                                                                                                      Each event should be notified with a cross or a point
                                                                                                                                                                                                                                      on the curve (beginning and end of all manœuvres,
                                                                                                                                                                                                                                      fragmentation, impact)

                                                                                                                                                                                                                                      16/01/06 (TDEM v3.0) : beginning and end of
                                                                                                                                                                                                                                      manoeuvre are still not marked with points on plots
                                                                                                                                                                                                                                      and manœuvres curves are too thick

                                                                                                                                                                                                                                      08/08/06 : same as AR36605 (ok for impact and
                                                                                                                                                                                                                                      fragmentation points.
                                                                                                                                                                                                                                      there are 3 or 4 cross marks by maneuver point, only
                                                                                                                                                                                                                                      one mark is requested.
                                                                                                                                                                                                                                      for maneuver marks, a diamond ( try L 0.03 in
                                                                                                                                                                                                                                      XTRACE) is preferable to X cross)

                                                                                                                                                                                                                                      19/10/06 : In TDEM V4.0,plot is ok for entire altitude,
                                                                                                                                                                                                                                      but events aren't notified on partial attitude plot
                                                                                                                                                                                                                                      07/03/2007: this AR is reclassified minor

  36705     AR36705                              TP_DEM_VAL_011 need 45mn to be computed, which is not                    Accep       freetest TP_DEM_VAL_011        mi - minor         T-DEM      GMV          Log - Software
                                                 compliant with the spec of 25mn
  36833     Modify the test T2200 & T2220        AR on the Validation report: the interesting ephemeris comparison        Accep       TP_GPS_VAL_T2200 &             mi - minor         T-GOD      GMV          Validation package - CNES : 11/05/2007 :
                                                 is the one between T-GOD input ephemeris and the estimated                           TP_GPS_VAL_T2220                                                          Validation package AR36833 related to validation test cases 2200 and
                                                 ephemeris.                                                                                                                                                                          2220 and analysis in validation report has not been
                                                 Remark: the objective of using the same model test was to use an                                                                                                                    taken into account correctly in T-GOD V5.0 delivery.
                                                 ephemeris without noise in order to check that the estimated                                                                                                                        The adjustment should be performed on perfect
                                                 ephemeris is consistent with the input. For the next delivery, the                                                                                                                  ephemeris without any noise (as clarified in AR Excel
                                                 test should be modified (no noise).                                                                                                                                                 sheet) and this is not the case
  36834     Modify the test T2210 & T2230        AR on the Validation report: the interesting ephemeris comparison        Accep       TP_GPS_VAL_T2210 &             mi - minor         T-GOD      GMV          Validation package - CNES : 11/05/2007 :
                                                 is the one between T-GOD input ephemeris and the estimated                           TP_GPS_VAL_T2230                                                          Validation package AR36834 related to validation test cases 2210 and
                                                 ephemeris.                                                                                                                                                                          2230 and associated analysis has not been taken
                                                                                                                                                                                                                                     into account correctly. The notios of “input
                                                                                                                                                                                                                                     ephemeris”, “reference ephemeris”, “bad-modeled
                                                                                                                                                                                                                                     ephemeris” and “estimated ephemeris” are confusing.
                                                                                                                                                                                                                                     The objective of these tests was to use 2 different
                                                                                                                                                                                                                                     models for input ephemeris generation and orbit
                                                                                                                                                                                                                                     determination and to compare input ephemeris with
                                                                                                                                                                                                                                     the estimated one
  37072     TM File is not empty                 TM File is not empty                                                     Accep       TP_ATT_VAL_180                 mi - minor         T-ATT      GMV          Doc - Document       acceptance testing (AOD 20.11.2006), process
                                                                                                                                                                                                                                     output shows "Transition to use attitude from
                                                                                                                                                                                                                                     ephemeris file at epoch 01/11/2003 00h00m00s000"
                                                                                                                                                                                                                                     so AR is almost fixed. The objective of the test
                                                                                                                                                                                                                                     needs to be updated to state the source of ISS
                                                                                                                                                                                                                                     attitude is from the ephemeris file. relative attitude is
                                                                                                                                                                                                                                     actually computed.

                                                                                                                                                                                                                                      29/01/07 : validation plan is to be updated +
                                                                                                                                                                                                                                      tracability of the associated RfC

                                                                                                                                                                                                                                      16/04/2007 T_ATTT V5, AR37072: TEST VAL_180
                                                                                                                                                                                                                                      documentation TP,VR. The test objective states that
                                                                                                                                                                                                                                      "relative attitude cannot be performed".
                                                                                                                                                                                                                                      This statement is false. In the test run, relative
                                                                                                                                                                                                                                      attitude is calculated using sensor inputs and ISS
                                                                                                                                                                                                                                      attitude from ephemeris file. GMV to update TP, VR
                                                                                                                                                                                                                                      as requested in AR 37072 (20.11.2006)
  37076     Gyro drift estimates in ADU are in   AR.37076.Gyro drift estimates in ADU are in error during angular         Accep       TP_ATT_VAL_100                 Ma - Major         T-ATT      GMV          Log - Software        30/11/06 : ACT1: An action is raised to try to define
            error during angular acceleration.   acceleration. See TP TATT 4.0 Figure 5, at 9000 seconds, the                         TP_ATT_VAL_190                                                                                  the raison of the problem :
                                                 effect of this problem can be seen here, in this particular case it is                                                                                                               Problem coming from either algorithm defined in
                                                 not very serious but at larger slews rates the effect leads to                                                                                                                       specification / tunning of the filter or TATT coding
                                                 impossibly high gyro drift estimates.                                                                                                                                                14/12/2006 : IAP again until the end of investigation

                                                                                                                                                                                                                                      27/01/2007 : investigation in progress at CNES side
                                                                                                                          14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                     FDS 242000


                                                                                                                                                                                     Configuration  Entity in
Reference                  Title                                              Description                                 Phase           Context reference            Criticality       Item        charge                                    Comments
  37080   30 degree attitude jump with different AR.37080.There is a jump in the attitude measurments on use of           Accep       TP_ATT_VAL_110                 mi - minor         T-ATT      GMV          Log - Software      30/11/06 : ACT 2 : The problem seems to provide
          sets of gyro in ADU mode               different sets of gyro in ADU mode (5.6.7.1.6.) 30 degree jump                                                                                                                     from the values of covariance matrix set from this set
                                                 appears unreasonable. Please verify and confirm that the code is                                                                                                                   case. A. ODwyer takes the action to perform this test
                                                 doing exactly the correct matrix element initialisations as defined in                                                                                                             case by changing these values.
                                                 the T_ATT specification requirement 2536 for the ADU to ADU
                                                 transition ?                                                                                                                                                                       05.12.2006 AOD acceptance TEST 110
                                                                                                                                                                                                                                    Time of problem 940 seconds.
                                                                                                                                                                                                                                    See section 5.6.7.1.6 of TP "different sets of gyro in
                                                                                                                                                                                                                                    ADU mode".

                                                                                                                                                                                                                                    I have tested changing/tuning the diagonals in the
                                                                                                                                                                                                                                    initialisation matrix for the covariance Papu and Padu
                                                                                                                                                                                                                                    to a various value sets such as
                                                                                                                                                                                                                                     (-0.1, -0.4, -10^4,-10^-7,-10^-8,10^-9.)

                                                                                                                                                                                                                                    The results appears worse in many cases with the
                                                                                                                                                                                                                                    spikes at 940 seconds always present.AR OPEN.
                                                                                                                                                                                                                                    This AR Appears very similar to 37073.

                                                                                                                                                                                                                                    12.01.2007 AOD the problem persists in the release
                                                                                                                                                                                                                                    4.01 of jan 2007 test 110. status changed SO ? to
                                                                                                                                                                                                                                    IAP

                                                                                                                                                                                                                                    16.04.2007 acceptance test VAL_110T_T_ATT V5,
                                                                                                                                                                                                                                    spike problem still evident at 940seconds. To be
                                                                                                                                                                                                                                    analysed by GMV and CNES.

  37627     AR-10                                  When lowing the ballistic's sampling time, the run takes more          Accep       TP_OCF_VAL_100; _101;          mi - minor         T-OCF      GMV          Log - Software      Yeah, but what we try to explain is that the previous
                                                   than1mn.                                                                           _250                                                                                          problem is reproduced here,
                                                                                                                                                                                                                                    Of course it's normal the run takes more time!
  37685     Unability to check the proper          Validation                                                             Accep       TP_OCF_VAL_071                 mi - minor         T-OCF      GMV          Doc - Document      22/02/2007 : the excel sheet is not modified, see the
            information that concern the yaw       The excel sheets 71 shows just some plots related to yaw reversal                                                                                                                file FEPS_EJ_TOCF_V4.3_{01.01.cnes}.xls
            reversal event                         event, but no information is given in order to properly check the
                                                   beta value, the yaw reversal date and the solar angle sign change                                                                                                                EJ, 19/06/07: correction plan agreed for T-OCF V5.1
                                                   date.
  37738     Inconsistency data for the test        INTPUT : MANEUVER PLAN                                                 Accep       TP_OCF_VAL_1500                mi - minor         T-OCF      GMV          Log - Software      22/02/2007 : The validation plan is not corrected
                                                   There is an inconsistency between the data of the Validation Plan                                                                                                                (version 2.2)
                                                   and the configuration file concerning the maneuvers start date.
                                                   The "start condition" window displays 0 for all the parameters value                                                                                                             EJ, 19/06/07 : Ok for correction in the V4.2 of the
                                                   and the dates don't correspond.                                                                                                                                                  validation plan.

  37739     Inconsistency values                   OUTPUT : OCF DATA Set file                                             Accep       TP_OCF_VAL_1500                Ma - Major         T-OCF      GMV          Log - Software      EJ, 28/03/2007 : Not corrected on TOCF V5.0
                                                   The values that are display for OCF_DIFF entity are wrong taking
                                                   into account the input data. For instance the DIFF_OCF_GOM =                                                                                                                     EJ, 19/06/07: correction plan agreed for T-OCF V5.1
                                                   289deg and DIFF_OCF_Aol = -1384deg.
  37746     differences between TOCF and           OUTPUT : POST-PROCESSING / plots                                       Accep       TP_OCF_VAL_1510                Ma - Major         T-OCF      GMV          Log - Software
            EADS dates                             There is a difference about 30 min, in beta angle sign change date
                                                   computed by TOCF and the one provided by EADS.
                                                   There is a difference about 3 min, in yaw reversal date computed
                                                   by TOCF and the one provided by EADS.
  37760     Validation Test Plan                   The last maneuver start date is 10h33min20s instead of                 Accep       TP_OCF_VAL_1060                mi - minor         T-OCF      GMV          Doc - Document      22/02/2007 : The validation plan is not corrected for
                                                   10h33min22s as written in the document.                                            TP_OCF_VAL_1070                                                                               test 1060 (version 2.2). Tests 1070 & 1080 are
                                                                                                                                      TP_OCF_VAL_1080                                                                               correct.

                                                                                                                                                                                                                                    EJ, 14/03/2007 : the VP 4.2 is for the next version of
                                                                                                                                                                                                                                    T-OCF ?

                                                                                                                                                                                                                                     EJ, 19/06/07 : Ok for correction in the V4.2 of the
                                                                                                                                                                                                                                     validation plan.
  37763     Non relevant test                      This test is not coherent with the actual baseline. The sequence       Accep       TP_OCF_VAL_1080                mi - minor         T-OCF      GMV          Validation package - EJ, 28/03/2007 : so what ? Will we have a
                                                   should be YS-SLW-BCM-SLW-EP-SLW-BCM-SLW-YS and not EP-                                                                                                       Validation package modification of the VP and the TP_OCF_VAL_1080
                                                   YS-SLW-BCM-SLW-YS-EP-SLW-YS-EP.                                                                                                                                                   context ?

                                                                                                                                                                                                                                    EJ, 19/06/07: correction plan agreed for T-OCF V5.1
                                                                                                                                14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                     FDS 242000


                                                                                                                                                                                           Configuration  Entity in
Reference                  Title                                                    Description                                 Phase             Context reference          Criticality       Item        charge                                       Comments
  37980   High level description                     It is important to present in this section the 2 main functions of T-      Accep        User manual review            mi - minor         T-GNC      GMV          Doc - Document      11/10/05 : to be corrected for the next delivery of the
                                                     GNC :                                                                                                                                                                                SUM of T-GNC
                                                         - to ensure an automatic monitoring of some paramers (FDI                                                                                                                        -----------------
                                                     monudule to be intriduced)                                                                                                                                                           23/02/2007
                                                         - to present to the operator real time information (alphanumerical
                                                     data, displays)                                                                                                                                                                      In section 2.1 of SUM 3.0 indicate more clearly which
                                                                                                                                                                                                                                          is the functionality of the tool:
                                                                                                                                                                                                                                          - to ensure an automatic monitoring of some
                                                                                                                                                                                                                                          paramers (FDI monudule to be intriduced)
                                                                                                                                                                                                                                          - to present to the operator real time information
                                                                                                                                                                                                                                          (alphanumerical data, displays)

  38293    RF_LINK display                           When trying to display RF_LINK, an error window is displayed on            Accep        GRA_VAL_060_4                 mi - minor         T-GRA      GMV          Log - Software      13/03/2006 on TGRA_1,8 the RF link don't appear
                                                     OPALE.                                                                                                                                                                               30/08/2006 : again true on TGRA_2.2

                                                                                                                                                                                                                                          29/01/2007 : OPALE PB
  38295    Velocity vector                           Velocity vector does not seem to follow ATV. It shall be decided if        Accep        GRA_VAL_060_4                 mi - minor         T-GRA      GMV          Log - Software      14/09/05
                                                     this vector representation shall be kept or not.                                                                                                                                     Ok, but even this is a OPALE pb, GMV should driwe
                                                                                                                                                                                                                                          the pb with Mercury.
                                                                                                                                                                                                                                          30/08/2006 : again true on TGRA_2.2 and this is
                                                                                                                                                                                                                                          GMV who should manage this AR


                                                                                                                                                                                                                                          29/01/2007 : OPALE PB
  38418    coding rule: Type.RedefTypeBase           Type (int, const, char …) must be redefined                                 Audit       Software audit:               mi - minor      FDB_SERVER, GMV            CR - Coding rules
           (Utilisation de type de base)             (see Excel file Non_Conformites_ATV_CC_FDS V2.xls                                       DQLS/CNES/AD/04.05.400                           ATSLIB,
                                                                                                                                             §5.5.4 (PC29)                                    FDBLIB
  38427    DON(9) (étiquette inutilisée)             The unused objets must be removed                                           Audit       Software audit:               mi - minor         ATSLIB,     GMV         CR - Coding rules   07/10/2005 : I understand that GMV agrees to
                                                     (see Excel file Non_Conformites_ATV_CC_FDS V2.xls                                       DQLS/CNES/AD/04.05.400                        FDBLIB, T-RDV,                                 perform the corrections so why is it REF ?
                                                                                                                                             §5.6.4 (PC-36)                                    T-EXT                                      04/07/2007 : To be corrected
  38435    Local-Info-226 (le resultat de            remove the useless assignment                                               Audit       Software audit:               mi - minor         ATSLIB,     GMV         CR - Coding rules
           l'affectation de iCovMatrixSize n'est     test the error status                                                                   DQLS/CNES/AD/04.05.400                           FDBLIB
           pas utilise)                               (see Excel file Non_Conformites_ATV_CC_FDS V2.xls                                      §5.6.4 (PC-46)
  38436    Local-Info-232 (la variable out_arDxy     Comment the use case of declared parameter 'out'                            Audit       Software audit:               mi - minor         ATSLIB,    GMV          CR - Coding rules
           est declaree avec l'attribut 'out' mais    (see Excel file Non_Conformites_ATV_CC_FDS V2.xls                                      DQLS/CNES/AD/04.05.400                           FDBLIB
           sa valeur d'entree est peut etre                                                                                                  §5.6.4 (PC-47)
           utlisee)
  38446    add comment for error treatment           add comment for error treatment to justify the lack of try/catch            Audit       Software audit:               mi - minor      FDB_SERVER, GMV            CR - Coding rules   07/10/2005 :I understand then that GMV agrees to
                                                     block. To be generalized.                                                               DQLS/CNES/AD/04.05.400                           ATSLIB,                                     comment the usage and absence of try catch block in
                                                                                                                                             §5.8.4 (PC-51)                                FDBLIB, T-RDV,                                 the code; so why is it REF ?
                                                                                                                                                                                               T-EXT                                      04/07/2007 : To be corrected
  38447    Empty catch instruction                   justify empty catch instruction. To be generalized.                         Audit       Software audit:               mi - minor      FDB_SERVER, GMV            CR - Coding rules
                                                                                                                                             DQLS/CNES/AD/04.05.400                           ATSLIB,
                                                                                                                                             §5.8.4 (PC-51)                                FDBLIB, T-RDV,
                                                                                                                                                                                               T-EXT
  38508    Gen(8)                                    Rule Gen (8) is not respected in five cases                                 Audit       See file FDSGLIB-V5.1-       mi - minor         FDSGLIB      GMV         CR - Coding rules
                                                                                                                                             Genesis-rules-violations.xls
                                                                                                                                             See FDSGLIB V5.1 code
                                                                                                                                             analysis LEQUAL-RE-015-CN
                                                                                                                                             01.00 29/03/2005 page 42
                                                                                                                                             §8.4.5
  38682                  AR 38682                    in TOCF if we forget to load one file the error displayed in the MMI        Integ              TP_FDS_INT_080        mi - minor          T-OCF      GMV          Log - Software      EJ, 03/04/2007 : Ok for ATV event and ATV
                                                     log window should be more explicit. For the time being only a “?                                                                                                                     ephemeris, but not for the ISS ephemeris.
                                                     File” appears.
                                                                                                                                                                                                                                          EJ, 19/06/07: correction plan agreed for T-OCF V5.1

  38830    Alarm akwnoledgement test                 In the validation report there are no verifications of the alarm             Accep      TP_GNC_VAL_190                mi - minor         T-GNC      GMV          Doc - Document      10.01.2007 Version 3.2
                                                     aknwoledgement activation and deactivation                                                                                                                                           Anomaly not corrected
  38844    Usage of buffering (virtual plot) in      In the Xtrace utilisation, an increased use of "masquer/-masquer"       Accep - Accep                                 Ma - Major         T-GNC      GMV          Log - Software      25/05/2007 : To be tested in FDS 2.3.1
           Xtrace                                    functions shall be done. Today at any user interaction, the xtrace
                                                     graphical frame flickers a lot. This is due to the fact that any action                                                                                                              -----------
                                                     is directly performed on the phisical window without the necessary                                                                                                                   12/06/2007 T-GNC 4.2. Anomaly Partially corrected.
                                                     bufferisation. At any possible user interaction, T-GNC has to force                                                                                                                  A more deep revision of the sequence of commands
                                                     xtrace to compose the plot on the virtual window and to show the                                                                                                                     sent to xtrace shall be done. This in order to
                                                     result only at the and on the physical frame. This is very important                                                                                                                 suppress the remaining imperfections.
                                                     when charger/-charger operations are performed but also for the
                                                     other actions.
  38855    Beep function                             When an or more alarms are raised, T-GNC starts to produce a            Accep - Accep                                 Ma - Major         T-GNC      GMV          Log - Software      25/06/2007 : Waiting for correction
                                                     beep sound. When T-GNC is stopped, the beep doesn't stop. It
                                                     should. At the same time, if the user aknowledges all the alarms,
                                                     the beep sound shall stop up to new alarms are raised.
                                                                                                                               14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                   FDS 242000


                                                                                                                                                                                          Configuration  Entity in
Reference                   Title                                                  Description                                Phase              Context reference          Criticality       Item        charge                               Comments
  38856   Interpolation of attitude parameters      Some different approaches are used to interpolate angular             Accep - Accep                                   Ma - Major         T-GNC      GMV          Log - Software   25/05/2007 : To be tested in FDS 2.3.1
                                                    parameters. For example for ephemeris files a 8 deg. Polynomial
                                                    law is used. For OCF_MON_EPH and OCF_ATT_OCF linear                                                                                                                               ------------
                                                    interpolation for quaternions is used and finally for TM flows linear                                                                                                             12/06/2007
                                                    interpolation for euler angles is used. When in an FDI different                                                                                                                  T-GNC 4.2 We will wait for the final solution without
                                                    kinds of interpolations are performed, delta values have                                                                                                                          discontinuities to close the anomaly.
                                                    discontinuities. It shall be avoided.
  38913     Memory allocation                       When the number of maneuver location combination is too large, T-          Accep       Memory allocation              mi - minor         T-ORM      GMV          Log - Software   11/04/2007 : T-ORM 6.0 ; Partially corrected - add a
                                                    ORM failed with an error message not clear. Furthermore, could it                                                                                                                 clearer error message when the number of
                                                    be possible to print the total number of combinations before the                                                                                                                  combination is greater than the maximum allowable
                                                    allocate instruction.                                                                                                                                                             integer value.

39013       AR 39013                                Based on test6_2, maneuver defined in N,aol just after the date of      Accep          Free test test6_2              Ma - Major         T-EXT      GMV          Log - Software
                                                    state
                                                     vector, "GO" then nothing happen
39014       AR 39014                                Cutting date before initial SV , in tool data, Ephemeris from cutting   Accep          Free_test test6_5              mi - minor         T-EXT      GMV          Log - Software
                                                    date to
                                                     "no", but output ephemeris starting at cutting date….(see conf file
                                                    test6_5)
39017       AR 39017                                The view xtrace output has no effect, open an almost empty              Accep          Free_test test6_5              mi - minor         T-EXT      GMV          Log - Software
                                                    locked file.
  43021     OCS instead of OCF                      Error in config file of T-GRA. OCS instead of OCF                               Oper   PRE-OQ ACS_ACS29               mi - minor         T-GRA      GMV          Log - Software   29/01/2007 : to be corrected

                                                                                                                                                                                                                                      17/04/2007 not corrected
                                                                                                                                                                                                                                      Only " dessa_Event_027" have to changed in the
                                                                                                                                                                                                                                      conf file
  81403     Post processing and activity changing If post processing window is activated and the activity of the tool is                   SMA 2                          mi - minor          FDS       GMV          General MMI -    30/06/2006 - FDS V2.1 integration -GMV is waiting
            in tool                               changed, the post processing window must be first closed                                                                                                           General MMI      for further information from CNES
                                                                                                                                                                                                                                      28/08/2006: We agree with the proposal

                                                                                                                                                                                                                                      27/01/07 : always agree
  81857     exponential atmospheric model in        In TSAF, in ephemeris mode, when considering an exponential                     Test   free test                      mi - minor         T-SAF      GMV          Log - Software   03/05/2006 - TSAF V4.0
            TSAF                                    atmospheric model, the density is not correctly taken into account.
                                                    Tow problems appear : - in the MMI, the format does not allow to                                                                                                                  Genesis problem : In PSIMU the same field is
                                                    display densities lower than 1E-8, zero is displayed instead. - when                                                                                                              displayed with the same format, but a unit change
                                                    runing 2 cases, one with a 0 density and one with a realistic                                                                                                                     (ng/m^3 by default, and then ug/m^3, g/m^3, mg/m^3,
                                                    density, the results are exactly identical, which seems to indicate                                                                                                               kg/m^3) allows to display values lower than 1E-8
                                                    that the atmospheric drag is not computed. The attached                                                                                                                           kg/m^3.
                                                    configuration file uses a density of 0.35E-12 (MAID value) which is
                                                    not displayed in the MMI.                                                                                                                                                         The altitude in the configuration file is the ATV one,
                                                                                                                                                                                                                                      and the density value is a typical one (MAID annex,
                                                                                                                                                                                                                                      §5,2) and thus there should be an effect.

                                                                                                                                                                                                                                      The configuration file will be sent by email.

                                                                                                                                                                                                                                      02/06/2006 - TSAF V4.1
                                                                                                                                                                                                                                      Configuration file to be sent by email

                                                                                                                                                                                                                                      11/07/2006 - TSAF V4.3
                                                                                                                                                                                                                                      When computing the same trajectories with PSIMU,
                                                                                                                                                                                                                                      different results are obtained. This shall be the same
                                                                                                                                                                                                                                      with TSAF.

                                                                                                                                                                                                                                      05/9/2006 - TSAF V4.4
                                                                                                                                                                                                                                      This AR is to be associated with T-EXT instead of T-
                                                                                                                                                                                                                                      SAF
                                                                                                                                                                                                                                      ------------------------------------
                                                                                                                                                                                                                                      08/12/2006
                                                                                                                                                                                                                                      CNES will invetigate the possible problem in PSIMU.

  82528     Abnormal GENESIS messages in the In the log window of the MMI, when using the "post-processing"             Test                                              mi - minor         T-GOD      GMV          MMI - MMI        27/04/07 It happens regularly during test at ATV-CC.
            log window                             button, some messages sometimes appears like "gsbouton :
                                                   window not exists".
  82637     the change of ATV configuration        When we move the ATV configuration from ATV-SA ( or from ATV-       Other                                              mi - minor         T-GRA      GMV          Log - Software   01/02/2007
            affects the color of the earth station body) to ATV-SA-ACS the earth station zone change of opacity.                                                                                                                      Verlyckr desagree, it is a AR, Javier Carro saw it
            zone
82804       Two OCS manoeuvres too closed          When two manœuvres are positioned too close that even the slews FDSVal                  Test                  mi - minor                  T-OCF      GMV          Log - Software   13/03/2007 : correction plan agreed for T-OCF V5.0
                                                   cannot be performed, T-OCF does not generate any error and the                          FDS_FUNCT_PREPA_TESTS
                                                   output attitude is completely wrong (Entire attitude in OCF).                           _GTC_MAN step 6                                                                            EJ, 03/04/2007 : not corrected on TOCF V5.0

                                                                                                                                                                                                                                      EJ, 19/06/07: correction plan agreed for T-OCF V5.1
                                                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                 FDS 242000


                                                                                                                                                                                     Configuration  Entity in
Reference                 Title                                            Description                                  Phase                 Context reference   Criticality            Item        charge                                Comments
82807     Mission Plan: Characteristics not      When something is changed in the Mission Plan definition structure FDSVal               Test                   mi - minor              T-OCF      GMV          Log - Software   EJ, 21/03/2007 : ok, for the next version
          computed after definition modification (in degraded mode), characteristics are not updated.                                    FDS_FUNCT_PREPA_TESTS
                                                                                                                                         _GTC_MAN step any                                                                       EJ, 19/06/07: correction plan agreed for T-OCF V5.1

82810       Discontinuity between YS and Slew      In some specific cases, when running with two consecutive OCS         FDSVal - FDS    Test                    Ma - Major             T-OCF      GMV          Log - Software
                                                   manœuvres, a discontinuity is obseved between the yaw steering        Validation      FDS_FUNCT_PREPA_TESTS
                                                   and one of the slews of the manœuvres.                                                _GTC_MAN step 4/7
82814       attitude and separation in mission     Attitude page and separation page of the mission plan are             Oper            PRE-OQ DEORB          mi - minor               T-OCF      GMV          MMI - MMI        21/03/2007 : it's really an AR. It has never been
            plan                                   sometimes erased after the user modified OTHER FDB DATA or                                                                                                                    written that the template should modify the data in
                                                   TOOL DATA.                                                                                                                                                                    MISSION PROFILE. Especially as the template holds
                                                                                                                                                                                                                                 the flag "from input mission plan atv".

                                                                                                                                                                                                                                 28/03/2007 : to be tested with the right template

                                                                                                                                                                                                                                 EJ, 25/04/2007 : not completely corrected, when the
                                                                                                                                                                                                                                 template doesn't contain any attitude law, the attitude
                                                                                                                                                                                                                                 in MP is still erased.

                                                                                                                                                                                                                                 EJ, 19/06/07: correction plan agreed for T-OCF V5.1

82815       wrong origin for modified mission plan In waiver mode, when the loaded mission plan is modified in TOCF, Oper                PRE-OQ DEORB                   mi - minor      T-OCF      GMV          Log - Software   18/01/07 : this is a T-OCF anomalie.
                                                   the created one has for origin TEXT instead of TOCF.
                                                   18/01/07 : this is a T-OCF anomalie.                                                                                                                                          EJ, 28/03/2007 : so the modified mission plan is
                                                                                                                                                                                                                                 marked with the tool that originally created it. And
                                                                                                                                                                                                                                 after validation, how should we know that it was
                                                                                                                                                                                                                                 modified ?
82878       Odd error message in T-GOD             During T-GOD validation tests,                                        FDSVal          Test 3.5 step 2                mi - minor      T-GOD      GMV          MMI - MMI
                                                   following message in often displayed -with T-GOD RT in Kalman
                                                   mode) :

                                                   Cannot create an ephemeris file with this%parEphemDate
                                                   parameter (error code : ATS_INVAL_EPHPAR_ERR)

                                                   Except this message, t-GOD seems to work nominally.


82892       TGOD AR - Results obtained in two      Comparing results obtains from Step 2 and 4 the retained solution FDSVal              FDS_FUNCT_TGOD_LSM_A mi - minor                T-GOD      GMV          Log - Software   26/01/07 I. Escané - GMV explanation is insufficient.
            consecutive runs of T-GOD are          is not the same.                                                                      TV_DV_BRDC step4                                                                        Deeper analysis to be done by Cnes and GMV
            different                              The second run starts with the mission profile generated by the first
            (FDS_FUNCT_TGOD_LSM_ATV_DV             one (estimation of Cd and DV components).
            _BRDC)                                 The configuration files are LSM_ATV_DV_PR and
                                                   LSM_ATV_DV_S4
82902       Configuration leads to tgra.exe to     FDS Time: 01/05/2007 - 05:40:00                                       Oper            PO_RDV_N_3                     Ma - Major      T-GRA      GMV          Log - Software   01/02/2007
            stop without message                   Configuration: conf_rdv                                                                                                                                                       verlyck : desagree : it is a AR, javier Carro saw it with
                                                                                                                                                                                                                                 me
                                                   The tgra_opt.exe is suddently stopped witput providing any
                                                   information about the reason of the stop.

                                                   The operator have saved the configuration (conf_rdv) he was
                                                   running before, moreover if we load the configuration defined
                                                   above and we perform a "Go". The tgra_opt.exe is launched but it
                                                   does not run and the message "tgra_opt.exe died" appears.

                                                   No core file has been detected.

                                                   It is possible that the configuration is not correct. The conf file
                                                   should be compared against the pre_oq_rdv_28112006 that works,
                                                   to detect the source of the anomaly.

                                                   Anyhow the anomaly is not that tgra_opt.exe refuses to run, but
                                                   that is does not provide any information about the configuration
                                                   problem.
  82909     Management of W/O for event            The management of Event entities is not well done. Only one event                                                    mi - minor     FDSGLIB     GMV          Log - Software   12/12/06 : still IAP. The flag "O" is well set for this
            entities                               file can be set as W/O not the others, however, this entities can                                                                                                             entities. However, we cannot retrieve with a simple
                                                   have at the same time several producer.                                                                                                                                       click all event entities set as W/O from differents
                                                                                                                                                                                                                                 tools.

                                                                                                                                                                                                                                 27/01/07 : same remark as above

                                                                                                                                                                                                                                 19/03/07 : same remark as above
82919       Mission profiles with null maneuvers   T-GNC is not able to handle mission profiles with null maneuvers. Oper                OQ_EOP_N1                      Ma - Major      T-GNC      GMV          Log - Software   24/04/2007-T-GNC V4.1-Anomaly not corrected
            (maneuver placeholders) in T-GNC       In particular it has been experienced for mission profiles generated                                                                                                          -----------
                                                   by T-ORM.
                                                                                                                                                                                                                                 13/06/2007
                                                                                                                                                                                                                                 To be reviewed in next L-NRB
                                                                                                                                 14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                 FDS 242000


                                                                                                                                                                                            Configuration  Entity in
Reference                  Title                                                 Description                                  Phase               Context reference           Criticality       Item        charge                                Comments
82926     Attitude in OCF not correctly           The computation of attitude in OCF is not correctly performed. The Test                                                   mi - minor         T-OCF      GMV
          computed                                global behaviour seems to be good. But if raw data are plotted,
                                                  they show some points on vertical lines that are not corresponding
                                                  to real data. In the joined file it is represented a comparison of the
                                                  yaw angle wrt a reference file produced by T-OCF. The blue line
                                                  shows this anomalous behaviour.
82927       TGNC: Monitoring of TRDV boost        The displayed values in TGNC of cummulated DV in LVLH for the FDSVal                       FUN_GNC_DV_DYNAMIC             Ma - Major         T-GNC      GMV          Log - Software   24/04/2007-T-GNC V4.1-Anomaly not corrected
                                                  TRDV RT flow are not in line with the actual computation of TRDV.
                                                  In TRDV up to 8 different boosts are computed while in TGNC only
                                                  one is displayed
82938       Important attitude difference between During the rendez-vous test PO_RDV_N3 the absolute attitude            Oper - Oper         PO_RDV_N3                      Ma - Major         T-ATT      GMV          Log - Software
            on-board and T_ATT output             attitude difference between ATV on-board and T_ATT output
                                                  became larger than 20 degrees in roll, pitch and yaw.

                                                     The explication could be due to AR 37076 "Gyro drift estimates in
                                                     ADU are in error during angular acceleration."

82948       Management of gaps in RT tools           The detection of gaps in the FDS tools when the speed factor is     FDSVal              FUN_TVDA_TVTG_NOM              mi - minor          FDS       GMV          Log - Software
                                                     increased is not correctly managed. Fake TM gaps are detected
                                                     The detection of gaps should be performed using a unique time
                                                     scale (FDB time) to avoid any problem in the delay of reception.
82953       Incoherence in input data for TVTG       It seems that the matrix concerning the orientation of TGMs and     FDSVal              FUN_TVDA_TVTG_NOMINAL mi - minor                  T-VTG      GMV          Autre - Other
                                                     the TGM flow used in the FDS Validation are not coherent. At least,
                                                     the results with TGMs are different from the one with VDMs.
                                                     Nevertheless, if the input TGM matrix is changed to the one used in
                                                     the validation of the tool, VDMs and TGMs generate same results.


82960       Header of T-OPF event file hinders    The header of T-OPF event file produced by T-OPF is not                                    Pre OQ EOP 1                   Ma - Major         T-OPF      GMV                           09/05/2007 - T-OPF 4.0 - Corrected
            the merging of event files            compliant with the event files produced by T-EXT, T-OCF, T-RDV.                            (PO_EOP_N_1)                                                                               25/05/2007 - AR reproduced in T-FDB v6.2
                                                  The consequence is that with this header no merging from T-FDB
                                                  is possible.
82961       maneuver definition by relative epoch In manual or automatic mode, TDEM doesn't work when                                                                       Ma - Major         T-DEM      GMV          Log - Software   26/04/2007: In TDEM V5.0, from test case #150, if
                                                  maneuvers are defined by relative date.                                                                                                                                               you change the maneuver date format from absolute
                                                                                                                                                                                                                                        to relative, TDEM exits in abnormal end of the
                                                                                                                                                                                                                                        process.
82967       TGNC: TRDV flow in RT                    TGNC is not able to monitor the TRDV output flow. The tool waits        FDSVal          FDS_FUN_TGNC_DV_GNCG Ma - Major                   T-GNC      GMV          Log - Software   24/04/2007-T-GNC V4.1-Anomaly not corrected
                                                     for TRDV output flow though the flow is correctly generated                             UI. E_FAR/FDIval                                                                           ----------

                                                                                                                                                                                                                                        13/06/2007 : Under Observation
82983       exerec file                              When user loads TOCF results that have been validated in FDB in         Oper            OQ_EOP_N_1                     mi - minor         T-OCF      GMV          MMI - MMI        21/03/2007 : ok, for the next version
                                                     the post-processing, graphics are not available, the error message
                                                     is 'exerec file'.                                                                                                                                                                  EJ, 19/06/07: correction plan agreed for T-OCF V5.1

83020       No possibility to run T-GPP locally in   At the ATV-CC, in the context "OQ_LEOP_N_1-1", the ATV_ATT,             Oper - Oper     DryRun OQ_LEOP_N_1             Ma - Major         T-GPP      GMV          Log - Software
            DryRun OQ_LEOP_N_1                       the ATV_GPSMEAS, and the ATV_GPSNAV were saved locally
                                                     with the DATA_BROWSER.
                                                     In the activity "SYNCHRONISED" or "RT_DRAFT", when trying to
                                                     run T-GPP locally with these files, the T-GPP software does not
                                                     process any measurement. Nothing happens on the MMI or in the
                                                     temporary files, but the process does not die. The initialization is
                                                     not even indicated.

83021       With TM dump on event, strange           With a navigation message flow impacted because of dump on              Oper - Oper     DryRun OQ_LEOP_N_1             mi - minor         T-GPP      GMV          Log - Software
            behaviour of T-GPP in catch-up           event, the behaviour of T-GPP is different according to the catch-
                                                     up date.

                                                     With a catch-up date at 21h20, T-GPP dies with an error message.
                                                     In the log window, it indicates that the attempt to attach a
                                                     navigation flow with a date lower than the currently date has failed.
                                                     With a catch-up date at 00h00m, T-GPP seems to run correctly.

                                                     For information, the first navigation message is received at
                                                     21h06m.
                                                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                       FDS 242000


                                                                                                                                                                                        Configuration  Entity in
Reference                 Title                                                Description                                       Phase        Context reference           Criticality       Item        charge                                     Comments
83022     Stop of T-GOD in RT with an initial     Just after ATV injection, T-GOD is run in RT with an initial state      Oper           DryRun OQ_LEOP_N_1             Ma - Major        T-GOD       GMV          Log - Software
          covariance matrix for CVI               vector far from the real position of 24km (CVI conditions). So, the
                                                  initial covariance matrix must be tuned by the user in order to take
                                                  into account the dispersion.

                                                  But when the covariance matrix is set to 9.10e+12 (m)² for the
                                                  position and 100(m/s)², T-GOD stops after the first iteration with no
                                                  warning or error message.

                                                  But when the covariance matrix is set to 9.10e+10 (m)² for the
                                                  position and 10000(m/s)², T-GOD stops after the first iteration with
                                                  no warning or error message.

83048       TM Qinit before STR TM flow goes to Dry run of operations test LEOP of 15.12.2006                             Oper                                          mi - minor         T-ATT      GMV          Log - Software       16.04.2007 in the test in the ATC-CC SVT_LEOP_3
            a strange state.                                                                                                                                                                                                            02.04.2007 the display did not freeze so precisely
                                                T_ATT 4.0.1 was employed on post GNC2 in ATV-CC. Template                                                                                                                               this problem is not repeatable however, it was noted
                                                name PPaduapu (06.12.2006)                                                                                                                                                              that the ATT is using invalid STR measurement thus
                                                                                                                                                                                                                                        this may explain the freeze. see AR 83617
                                                  A T_ATT was launched before a STR became active and valid
                                                  (with automatic method to take the quaternion from the STR TM
                                                  stream), it did not produce an output flow nor graph anything in the
                                                  displays, the tool remained active during the test. Time of launch
                                                  was near 20h20m (Tsep 20h19m51s). Appears to be an anomaly
                                                  with implementation of RFC 82074, the T_ATT with auto TM Qinit
                                                  before STR is active/before STR TM flow goes to a strange state.




83069       T-OCF Working occurence               The load of working occurence does not work for the structure           Oper           QO_LEOP_N_2                    mi - minor         T-OCF      GMV          MMI - MMI            13/03/2007 : correction plan agreed for T-OCF V5.0
                                                  "Injection parameters".
                                                  The substructures DELTAT_INJ and INJECTION PARAMETERS                                                                                                                                 EJ, 28/03/2007 : one of the entity is not in blue in the
                                                  created by T-ORM are not loaded.                                                                                                                                                      "INJECTION Parameters" panel.

                                                                                                                                                                                                                                        EJ, 19/06/07: correction plan agreed for T-OCF V5.1

83168       Problem with acces to "LEOP           For test TP_OCF_VAL_071. In the Post-Processing MMI, there is           Accep          TP_OCF_VAL_071;TP_OCF_ mi - minor                 T-OCF      GMV          MMI - MMI            13/03/2007 : do you mean that the line "LEOP
            Parameters" file                      the possibility to view the file "LEOP Parameters". The file is not                    VAL_072;TP_OCF_VAL_510                                                                         Parameters" will always be in the post processing
                                                  generated, because the "A5 sep" flag is not selected in the "TOOL                                                                                                                     window, even when the flag "A5 sep" is not active ? If
                                                  DATA" entity, so there's no need to have the possibility to view it.                                                                                                                  so why ?

                                                  On the other hand, for test TP_OCF_VAL_510, the "A5 sep" flag is                                                                                                                      EJ, 28/03/2007 : the file is not available in the post-
                                                  selected, the "LEOP Parameters" is generated, but it's not possible                                                                                                                   processing window, neither in the TP_OCF_VAL_071
                                                  to view it directly in the Post-Processing MMI.                                                                                                                                       nor in TP_OCF_VAL_510.


                                                                                                                                                                                                                                        EJ, 19/06/07: correction plan agreed for T-OCF V5.1

83171       Wrong yaw angle in the beginning of   The yaw angle, on the yaw steering profile is about 40° and is -40° Accep              TP_OCF_VAL_1080                mi - minor         T-OCF      GMV          Validation package - 13/03/2007 : ok. We need correction of the validation
            the first slew                        at the beginning of the slew.                                                                                                                                    Validation package plan, but why for 5.1 version ?

                                                  Exactly, in the ATT_OCF file, the yaw angle shift from                                                                                                                                EJ, 19/06/07: correction plan agreed for T-OCF V5.1
                                                  34.9475507245363deg to -34.9475607424489deg at the
                                                  beginning of the slew (time 1725.3723415994).
                                                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                               FDS 242000


                                                                                                                                                                                    Configuration  Entity in
Reference                  Title                                             Description                                   Phase            Context reference    Criticality            Item        charge                                  Comments
83172     Modification of OCF data set file        In the test TP_OCF_VAL_105, T-OCF is in "Attitude computation       Accep            TP_OCF_VAL_105,TP_OCF_ mi - minor              T-OCF      GMV          Log - Software   13/03/2007 : not agree, the correction made on the
          loaded, during run without OCF           only" mode, but the OCF data sets are modified.                                      VAL_1500                                                                                4.3 version, is not good. When "attitude mode only" is
          computation                                                                                                                                                                                                           selected, you only made a copy of the "OCF data set"
                                                   Exemple in the first OCF, we can read in the input file :                                                                                                                    that is loaded. You have to compute the new LOF
                                                   OUT_PLANE = [ 0.00582341974108624 ~deg,                                                                                                                                      differences, which depend on the ATV ephemeris file.
                                                   0.0150976232753922 ~deg,                                                                                                                                                     If we don't change the ephemeris, the "OCF data set"
                                                   0.0150976232753922 ~deg ]                                                                                                                                                    does not change, but if the ephemeris change, so
                                                   and in the post-processing :                                                                                                                                                 does the LOF differences in the "OCF data set"
                                                   OUT_PLANE = [ 509.111235510828 ~deg, 509.113751384305                                                                                                                        28/03/07 : Third point to be checked
                                                   ~deg,
                                                   359.986877600379 ~deg ]                                                                                                                                                      EJ, 19/06/07: correction plan agreed for T-OCF V5.1

                                                   Perhaps it's because the ATV Ephemeris used to create the input
                                                   is different from the one used in the test.

                                                   In the test TP_OCF_VAL_1500, also in "Attitude computation only",
                                                   the OCF in the first interval is totally wrong :
                                                   start_date_cal = "21/06/2007 05h19m40s100" ~cal
                                                   end_date = 2728.48966435185 ~j
                                                   end_date_cal = "21/06/2007 11h45m07s000" ~cal
                                                   mean_inc = 0 ~deg
                                                   aol_origin = 0 ~deg
                                                   aol_slope = 0 ~deg/s
                                                   asc_origin = 0 ~deg
                                                   asc_slope = 0 ~deg/s
                                                   In the input there is :
                                                   start_date = 2728.221875 ~j
                                                   start_date_cal = "21/06/2007 05h19m30s000"
                                                   end_date = 2728.4896064815 ~j
                                                   end_date_cal = "21/06/2007 11h45m02s000"
                                                   mean_inc = 51.5679641103 ~deg
                                                   aol_origin = 55.1198883761 ~deg
83178       Problems in the attitude computation   In the plot "Entire attitude in OCF/Yaw angle", the end of the red    Accep          TP_OCF_VAL_530                 mi - minor      T-OCF      GMV          Log - Software   13/03/2007 : ok
            when the law is Earth Pointing         line (for the slew post first boost) is not connected to the blue one
            between boost                          (for the EP pointing).                                                                                                                                                       EJ, 19/06/07: correction plan agreed for T-OCF V5.1

                                              When the parameter "Maximum duration for slew to EP" is set to
                                              the real value of the slew, the plot is correct (the initial value is
                                              zero).
83180       TP_OCF_VAL_170 : differences with In the validation test plan, OPS-AIT-242525-60683-GMV V2.2, it is Accep                   TP_OCF_VAL_170                 mi - minor      T-OCF      GMV          Doc - Document   14/03/2007 : ok, but why do you correct it for v5.1 ?
            the results of test case 130      written that the results of test 170 should be the same as the 130
                                              ones.                                                                                                                                                                             EJ, 19/06/07: correction plan agreed for T-OCF V5.1
                                              The beginning of the second OCF (end of the first one) is 10s
                                              earlier in the test 130. It's a difference in the inputs. In "OTHER
                                              FDB DATA/OCF & Slew Parameters" the "Delay ACS" is equal to
                                              10s in test 130 and zero in test 170.
83181       problem when rotating camera      For the Cam_3d_EF vhen we apply the rotation around Z to 30.0         Oper                PO_OCS_N_1                     mi - minor      T-GRA      GMV          Log - Software   15/03/2007
            around Z                          TGRA stops its execution.                                                                                                                                                         Ok we will test it
83259       Wrong Begin / End sequence for    There is an error in the sequence of OCF Events in the following      FDSVal              FDS_FUNC_TFDB_Timeline, mi - minor             T-OCF      GMV                           14/03/2007 : correction plan agreed for T-OCF V5.0
            OCF event in ATV_EVENTS file from ATV_EVENTS file generated by T-OCF:                                                       Timeline for ASCENT Mission,
            T-OCF in PHASING period           Context: SMA3_SEPARATION                                                                  STEP 2                                                                                  EJ, 03/04/2007 : not corrected on TOCF V5.0
                                              Activity: PRE_PHASING
                                              Name /comment: "PHA_OCF_Slew_Nom"                                                                                                                                                 EJ, 19/06/07: correction plan agreed for T-OCF V5.1

                                                   At the date "26/04/2007 07h25m55s386", the sequence should be
                                                   "E_OCF" and then "B_OCF". The contrary is recorded.

83261       Display stop after long pause of FDS After a very long pause of the FDS (i.e. 48 hours), and after         Oper             pre QO PO_OCS_N_1              mi - minor      T-GRA      GMV          Log - Software   15/03/2007
                                                 continuation of the execution, the MMI of T-GRA continues the                                                                                                                  Ok, cnes will try to reproduce this AR, but by waiting
                                                 execution (the FDS time restarts), but OPALE remains frozen. It is                                                                                                             we can cancel it
                                                 required to stop and restart T-GRA to continue with the normal                                                                                                                 17/04/2007
                                                 execution.                                                                                                                                                                     CNES will wait for a long run test to try to reproduce
                                                                                                                                                                                                                                this anomaly.
83276       Impossible FDB validation for TGOD     After a nominal run of TGOD in a Non Real Time Acivity, the         Oper             PO_OCS_N_1-3                   Ma - Major      T-GOD      GMV          Indet -          CNES 11/05/2007 :
                                                   results were saved localy without any problem.                                                                                                              Undetermined     to be checked with GMV team based at CNES
                                                   Then when trying the results validation, TGOD tool was
                                                   permanently frozen and no validation was performed.

                                                   This validation was tryed again from another TGOD MMI, leading to
                                                   the same result : tool frozen without validation.
                                                                                                                               14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                  FDS 242000


                                                                                                                                                                                          Configuration  Entity in
Reference                     Title                                                Description                                  Phase            Context reference          Criticality       Item        charge                                 Comments
83288     Load configuration local file and load    In general MMI "load configuration" panel, a "local file" is selected, Oper                                           mi - minor          FDS       GMV          MMI - MMI
          results loacl file filter uncorrect       the filter at the top of "select a file" panel is wrong and has to be
                                                    modified each time. Idem in the "load results - local file". It would be
                                                    better to have no filter at all than a wrong one like this.

83294       Unexpected unmodified maneuver          When maneuver are not estimated by T-GOD or input maneuver            Oper             PO_OCS_N_1                     Ma - Major         T-GOD      GMV
            plan entity creation as output          plan values are not modified through tool data panel, T-GOD
                                                    should not create a new entity, but link the output mission profile
                                                    with the input mission plan entity.

                                                   This creates a conflict in W/O in operational sequential.
83317       T-OCF active star tracker selection in In T-EXT / tool data/ Attitude mode: The selection of the active star Oper              SVT4S                          mi - minor         T-OCF      GMV          Log - Software   22/05/2007 : Cnes to propose some preventive
            attitude mode uncorrect                tracker: north or south has no influence on the ATV attitude. This is                                                                                                              actions ' update of procedures and or training)
                                                   uncorrect
83318       Boost start date in MISSION            There is two informations about the boost start date of each          Accep             TP_VAL_OCF_100                 mi - minor         T-OCF      GMV          MMI - MMI        14/03/2007 : there is no computation to be made.
            PROFILES                               manoeuvre in MISSION PROFILES / Mission Plan ATV /                                                                                                                                 The boost start date is present in the config file, why
                                                   Manoeuvre Plan.                                                                                                                                                                    it is not possible to view it ?

                                                    And if the position mode is "N and alpha", the second date has a
                                                    non determined value : "N/A".

                                                    The AR appears also in T-RDV.
83321       The "Sun ephemeris file" sub-entity     With respect to V4.1 of T-OCF specifications, the "Sun Ephemeris      Accep            TP_OCF_VAL_100                 mi - minor         T-OCF      GMV          MMI - MMI        14/03/2007 : ok for the next version.
            not correctly placed                    file" sub-entity, must be placed in "OTHER FDB DATA" instead of
                                                    "TOOL DATA".                                                                                                                                                                      EJ, 19/06/07: correction plan agreed for T-OCF V5.1

                                                    Placed in "TOOL DATA", the file is not actualized when the
                                                    operator makes a global loading of the last working occurence.
83327       PSIMU: Ergols mass                      The mass of ergols provided by PSIMU as output is always null         Test - Test                                     mi - minor         PSIMU      GMV          Log - Software
83332       kos not load during the configuration   When we load a configuration file, the W/O kos file is loaded but     Oper             free test                      mi - minor         T-GRA      GMV          Log - Software
            loading                                 with all values equal at 0.

                                                    VM 30/03/2007 : deployment pb
                                                    RV 17/04/2007 : Not a deployment pb. Actual AR : It is necessary
                                                    to click again on the Working Occurence button
83343       Mission profiles coming from T-GOD      During last SVT test only mission profiles coming from T-GOD were Other                SVT_TPO_CAMD                   Ma - Major         T-GNC      GMV          Log - Software   24/04/2007-T-GNC V4.1-Anomaly not corrected. For
                                                    available. T-GNC was able to select them but xtrace was unable to                                                                                                                 SVT-TPO CAMD I was not able to plot a delta v and
                                                    plot them (Delta V plots). No errors were shown by T-GNC.                                                                                                                         for SVT LEOP there are no manoeuvres.

83346       TM gaps and plots of Delta V's from     During the test PO_OCS_N_1 a TM gap occurred during a Delta V Other                    PO_OCS_N_1                     mi - minor         T-GNC      GMV          Log - Software   13.03.2007
            mission profiles.                       up to the end of the boost (UTC JD2000 2661.1923 -> 2661.1932).                                                                                                                   Not Agreed: Even this is a particular case, this
                                                    The plot of Delta V showed a strange behaviour, in particular for                                                                                                                 behaviour is hiding a more general problem, where a
                                                    the delta V coming from mission profile. In fact T-GNC traced a line                                                                                                              correct definition of TM gap alarms should be
                                                    between the beginning of TM gap (at around 6 m/s on DVx) to 0                                                                                                                     managed to give consistency to the plotted results.
                                                    that was the right value at the end of TM gap. TM gaps should be                                                                                                                  So, in response to this anomaly I would like to see at
                                                    handled in the FDI plot for Delta Vs coming from mission profiles                                                                                                                 least the possibility to define different TM gap alarm
                                                    (or mission plans if T-GNC will use those)                                                                                                                                        levels targetted to the most critical FDI's.
                                                                                                                                                                                                                                      24/04/2007-T-GNC V4.1-Anomaly not corrected. A
                                                                                                                                                                                                                                      management of TM gaps shall avoid this behaviour.
83363       Not detection of end of manoeuvre:      T-GRA is not able to detect properly the end of the 4th boost         FDSVal           SMA3_SEPARATION                mi - minor         T-GRA      GMV          Log - Software   15/03/2007
            use of ATV wrong configuration          period of homing in the following displays:                                                                                                                                       Ok we will test it
                                                    - DISP_2D display (planisphere)
                                                    - D_ATV_L_Ydisplay (ATV)
                                                    - D_ATV_L_Z display (ATV)
                                                    - D_3D_J2_x display (Earth)
                                                    The consequence is that ATV is plotted with the solar panels
                                                    deployed and the vehicle boosts active

                                                    A similar problem has been detected during de-orbitation phase
83390       Proble with T-OPF event file for        T-OPF event file is not read by T-FDB for timeline building                                                           Ma - Major         T-FDB      GMV          Log - Software
            timeline computation

83419       Translating function for plots in T-    The translating function doesn't work after a zoom in the xtrace      Oper             PO_RDV_N_3                     mi - minor         T-GNC      GMV          Log - Software
            GNC                                     window. In particular, if the user zooms at the end of the curve
                                                    where new data are going to be plotted, the translating function
                                                    stops to work.
83423       bad values in footer of atlest the ATV- This Ar was know but it has been closed. Now we have to open it       Oper             PO_RDV_N_4                     mi - minor         T-GRA      GMV          Log - Software
            ISS range                               again because during this test we were able to see that the values
                                                    are always bad. For a good value of the ATV-ISS range at 300m
                                                    we observe that the value fluctuate between 10km and 1km.

                                                    Perhaps we can bring close this ar to the ar_82903 and the
                                                    ar_82893
                                                                                                                                    14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                             FDS 242000


                                                                                                                                                                                            Configuration  Entity in
Reference               Title                                       Description                                                     Phase            Context reference     Criticality          Item        charge                                Comments
83424     TGOD: Problem with TGOD OD flow. Context: Jules_Verne/PO_RDV_N_4 du 20/02/07,                                      Oper               PO_RDV_N4-               Ma - Major           T-GOD       GMV          Log - Software
                                           SYNCHRONISED, conf:nominal_rel                                                                       2/SYNCHRONISED/nominal_r
                                                                                                                                                el
                                                     During RDV phase, TGOD several times stopped his output flow
                                                     (TGOD output flow red Flow status window and there is no more
                                                     RT_TGOD flow). The input flow is TGGP flow which looks correct.
                                                     In TGOD the error "Cannot get the ephemeris record since
                                                     interpolation date is lower than lowest or greater than the greatest
                                                     date included in file" is raised (for example at 4h48m01s in FDS
                                                     simulated time).

                                                     When we stopped the run, then pressed go (without catch-up
                                                     mode), the run has restarted correctly but the problem occured
                                                     again after about 20 minutes.


     83432 Droits permissifs sur certains fichiers   Les droits du fichier de journalisation /var/x11vnc/log sont trop       Test - Test        test securité de la recette    mi - minor      T-OPS      CNES
           X11VNC                                    permissifs (-rw-rw-rw-) et autorisent une modification par tous les                        3.2/2.4
                                                     utilisateurs.
                                                     Les droits du fichier des mots de passe /etc/x11vnc.passwd sont
                                                     trop permissifs (-rw-r--r--) et autorisent une lecture par tous les
                                                     utilisateurs

                                                     Des investigations doivent être menée coté équipe projet CNES
                                                     afin de voir si le système peu fonctionner avec des droits plus
                                                     restreints. Dans le cas contraire une demande dérogation doit être
                                                     faite auprès de DCT/SA/SI
83439       TDRS visibility circles in T-OPF post    TDRS and ARTEMIS visibility periods do not match the visibility    Accep                   TP_OPF_VAL_220                 mi - minor      T-OPF      GMV          General MMI -    CNES-19/03/2007
            processing window                        circles on planisphere.                                                                                                                                           General MMI      Please fill column AT

                                                                                                                                                                                                                                        CNES-T-OPF 4.0- 04/04/2007
                                                                                                                                                                                                                                        AR not corrected reproduced in test 140 and 220
83452       Pre-homing calculation in Events files The pre-homing date in the events file is not coherent with the one       Oper               PO_RDV_N_4                     mi - minor      T-RDV      GMV          Log - Software
                                                   given in the input data file.
83471       Problem in measurements counting in During test PO_DRV_N4_5, the total number of measurements                    Oper - Oper                                       mi - minor      T-GPP      GMV          Log - Software
            TGPP                                   treated by TGPP and displayed sometimes decreased suddenly. It
                                                   appears for ISS and ATV measurements.

83472       Overlaping dates of manoeuver on         During test PO_RDV_4_5, an overlaping error message was raised                                                            mi - minor      T-GOD      GMV          Log - Software
            TGOD                                     by TGOD when loading a RendezVous manoeuver plan. This
                                                     problem appeared on nav1 station but not on nav2, altough the
                                                     same manoeuver plan was loaded on both stations.

83482       TSAF : Phasing Absolute: Bad             After a run in Phasing Absolute mode, the plotting of the results (in   Test               Free test                      Ma - Major      T-SAF      GMV
            dispersions over X position              post-processing window) looks strange.
                                                     In the test we have ISS SV before ATV SV.
                                                     If we have a look into DEF_EIGEN files, the first line gives the
                                                     dispersions at initial ATV SV date (it seems the dispersions take
                                                     into account only absolute ATV dispersions).
                                                     Then the second line gives a dispersion over X position very
                                                     important :
                                                     - dispersion on X pos = 70m at initial ATV SV (first line)
                                                     - dispersion on X pos = 15643713m 15second later (second line)
                                                     The second line takes into account the ISS dispersion due to
                                                     covariance propagation.
                                                     But the projection on X axis of this covariance looks bad. The
                                                     dispersions looks shifted along X axis on the plotting.
83485       TCL script error in T-GNC                During preparation for run, genesis interface in T-GNC has shown        Oper               PO_RDV_N_4                     mi - minor      T-GNC      GMV          Log - Software   24/04/2007-T-GNC V4.1-So, nothing has been done.
                                                     the following error: "Error in TcL script -- Invalid command name                                                                                                                  Is it a genesis internal anomaly?
                                                     .frm2.panel114.bt1161.menu1161". This during the selection of a
                                                     new ATV_ABSEPH file as a reference in attitude, the user pressed
                                                     the button "select" and on the selection window, choosing any on
                                                     the activity popup menu. It has been necessary to restart T-GNC to
                                                     have it working.
83549       Wrong start date for MSULOF              When performing MSULOF propagation, the date of the QLOF                Oper               PO_RDV_N_4                     Ma - Major      T-OCF      GMV          Log - Software   13/06/2007 : to be reworded
            propagation                              quaternion is considered to be the start date of the prediction
                                                     interval requested. This is not correct and the date to be
                                                     considered as initial for the propagation of MSULOF is the date of
                                                     the QLOF quaternion.
83550       Manual generation of attitude plan       In TOOL DATA/Attitude mode, when clicking in "T-OCF Attitude            Other              Any                            mi - minor      T-OCF      GMV          Log - Software   EJ, 19/06/07: correction plan agreed for T-OCF V5.1
                                                     Mode Building", Attitude plan is not initialised to the values
                                                     contained in the Attitude Plan of the mission profile. This behaviour
                                                     is specified in requirement SW_TOCF_1600/1605.
                                                                                                                               14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                  FDS 242000


                                                                                                                                                                                          Configuration  Entity in
Reference                 Title                                                 Description                                    Phase            Context reference           Criticality       Item        charge                                 Comments
83554     Pop-up warning in endless loop           When filling a manouver plan in TGOD where the manouver is             Test                                            mi - minor        T-GOD       GMV          General MMI -
                                                   'variable defined by two points', if the date for the second point (in                                                                                            General MMI
                                                   second from the start of the boost) is greater than the thruster max
                                                   duration, then a warning pops-up.
                                                   The problem is that as soon as the user clicks 'OK ', the pop-up
                                                   disappears but reappears immediatly. There seems to be no way to
                                                   end this, unless by killing TGOD, which is not wanted.
     83562 Scellement Tripwire incomplet           Les fichiers et répertoires des outils FDS ne sont pas inclus dans la Accep - Accep                                    mi - minor         T-OPS      CNES         Log - Software
                                                   politique de scellement Tripwire du serveur (test FDS-SCELL-01 du
                                                   document OPS-RP-242000-747-CNES)
                                                   Les fichiers et répertoires de l‟outil X11VNC ne sont pas inclus
                                                   dans la politique de scellement Tripwire du serveur (test X11VNC-
                                                   SCELL-01 du document OPS-RP-242000-747-CNES)

83565      TBAC problem in case of on board        During first hour of SVT test LEOP, TBAC did not produce any        Oper                SVT LEOP                       Ma - Major         T-BAC      GMV          Log - Software   13/06/2007-L-NRB 21 - criticity to be reviwed with a
           coarse acca bias estimation             result, even if it was running. it begun produce the RT_TBAC flow                                                                                                                  period of utilisation of T-BAC
                                                   at 21h23 (TM time). After TM analysis, it appears that the
                                                   fine/coarse flag in TM flow ATV_ACCABIAS changed its value at
                                                   21h23, from 0 (coarse) to 1 (fine).
                                                   It seems to be the origin of the problem, but has to be verified.
                                                   This behavior is not normal, since TBAC must not used this TM
                                                   flag.


83571      upload flag in mission plan is always   The flag to be uploaded in mission plan is always changeable                                                           mi - minor        FDSGLIB     GMV
           changeable                              whereas it should be only in waiver mode
83578      Too many cores prodice by TGNC          On GNC1 sun station during the SVT-4C_LEOP test of 23th march Oper                      SVT-4C_LEOP                    Ma - Major         T-GNC      GMV          Log - Software   12/06/2007
                                                   2007 T_GNC produced 6 core files during 1h40. The 6th core file                                                                                                                    T-GNC 4.2 Agreed. It is a problem of workstation
                                                   has saturated the /var/core of gnc1.                                                                                                                                               configuration. Part of the anomaly is still open but not
                                                                                                                                                                                                                                      affected to T-GNC. For an example of configuration
                                                   In the log windows we receved this message :                                                                                                                                       one can type "man core".

                                                   Mar 23 11:31:36 Running process
                                                   /applications/FDS_v02_02_02/TGNC/tgnc_opt.exe error writing
                                                   "file4" no space left on device

                                                   The ls commande on gnc1 give :
                                                   -rw------- 1 root fds 174087148 Mar 23 08:54
                                                   core.tgnc_opt.exe.22923.gnc1.32268.30000.1174640056
                                                   -rw------- 1 root fds 174087148 Mar 23 08:59
                                                   core.tgnc_opt.exe.24423.gnc1.32268.30000.1174640357
                                                   -rw------- 1 root fds 174087148 Mar 23 09:01
                                                   core.tgnc_opt.exe.24576.gnc1.32268.30000.1174640455
                                                   -rw------- 1 root fds 174087148 Mar 23 09:02
                                                   core.tgnc_opt.exe.24658.gnc1.32268.30000.1174640513
                                                   -rw------- 1 root fds 174005228 Mar 23 09:05
                                                   core.tgnc_opt.exe.24817.gnc1.32268.30000.1174640725
                                                   -rw------- 1 root fds 147914752 Mar 23 10:40
                                                   core.tgnc_opt.exe.29877.gnc1.32268.30000.1174646450
                                                   -rw------- 1 root fds 6569452 Mar 21 15:00
                                                   core.xtrace.exe.13592.gnc1.32268.30000.1174489204


83600      Recovering of time offset on server     As soon as we try to recover a time offset from T-FDB tool          integ               IAT M&C FDS v125               mi - minor      FDB_SERVER GMV                              On the other hand, T-GNC shall not crash at any
           set as slave                            connected to a slave FDB server, the slave server crashes                                                                                                                          error. A better handling of errors shall be done.
                                                   generating a core dump.
83601      Crash server when using CTRL S /        This anomaly is not an operational one, it has been raised during   integ               iAT MC FDS v125                mi - minor      FDB_SERVER GMV
           CTRL Q commands                         IAT M&C IAT v125 test using non recommanded command.
                                                   As soon as we excute both commands CTRL S (to stop the the
                                                   defilading of FDB_SERVER output) and CTRL Q (to restart the
                                                   defilading) the server crashes.
                                                                                                                         14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                FDS 242000


                                                                                                                                                                                    Configuration  Entity in
Reference               Title                                               Description                                 Phase            Context reference            Criticality       Item        charge                            Comments
83614     T-GOD : no computation but          During a period where the receiver "2" was giving valid PVT          Oper - Oper       SVT_LEOP_3                     Ma - Major        T-GOD       GMV          Indet -
          measures present                    measures, and receiver "1" was invalid (non converged), the LSM                                                                                                  Undetermined
                                              restitution was not possible, the tool claiming that there was "no
                                              measurement".
                                              The start and end dates for the filtering window where covering the
                                              period with receiver "2" valid meausrements, but the dates
                                              associated to the receiver "1" invalid measurements were always
                                              2661.0, thus in the futur and outside the filtering window.
                                              Maybe T-GOD is checking the belonging of the date of
                                              measurement to the filtering window with receiver "1" and not with
                                              the valid receiver ?
                                              This could be a serious problem in real flight in case of receiver 1
                                              failure.
                                              If not, then the problem could be that the check of validity is made
                                              only for receiver "1"...



83615      T-EXT Output load W/O results      in T-EXT, Post-processing panel, when loading a result file, the   Oper - Oper         SVT-LEOP                       mi - minor         T-EXT      GMV          MMI - MMI
                                              result file corresponding to the Working Occurence does not
                                              appear in blue in the results file list
83617      T_ATT in ADU when ATV STR TM is    During the SVT4 LEOP test, on post GNC2 in ATV_CC1, the tool       Oper                                               mi - minor         T-ATT      GMV          Log - Software
           invalid                            was started with a manual start at separation (20h19m51s) and
                                              entered ADU at 20h 21m and many other times after. During this
                                              time period after separation the STR was declared invalid in ATV
                                              TM flow. The ADU mode should not have been entered by T-ATT
                                              before 20h 45m 5 (STR valid)but it did. Appears to be problem with
                                              active and valid logic in T_ATT V4.1 Appears to be non-
                                              conformance to RFCs 82075, 82073.

                                              SVT LEOP test has been played again and same behaviour is
                                              evident.
                                              see:
                                              Serveur : HARDY / Vol : Jules_Verne / Contexte : SVT_LEOP_3
                                              (FDS_v2.2.2 : conf nominale)

                                              seriousness: deterioration
                                              importance: important
                                              severity: minor


83628      FCM TM and TGOD incoherency        The results for relative trajectory provided by TGOD are not in line   FDSVal - FDS    FUNC_TGNC_POSVEL_FCM mi - minor                   T-GOD      GMV          Log - Software
                                              with the values of the FCM TM. The configuration "nominal_rel"         Validation      (PO_RDV_4_5 context)
                                              from the PO_RDV_4_5 context has been used. The residuals for
                                              ATV measurements generated by the tool are over 1 km, so it may
                                              be the source of the problem
83629      TVTG and FCM TM incoherency        The VTG results are not totally coherent with FCM TM. Transverse       FDSVal - FDS    FUN_TGNC_POSVEL_FCM_ mi - minor                   T-VTG      GMV          Log - Software
                                              velocity terms have differences of about 0.1 m/s and the approach      Validation      S3DOCK (PO_RDV_4_5)
                                              angle is totally different (while the one from TVTG seems to be the
                                              correct one)
83639      MSULOF: Incoherency between T-     MSU LOF attitude from T-OCF and T-GOD are not coherent as              FDSVal - FDS    FDS_FUN_TGNC_ATT_LOFM Ma - Major                  T-GOD      GMV          Log - Software
           OCF and T-GOD                      shown in TGNC.                                                         Validation      SU (E_ACS)
                                              This problem may be an anomaly in any of the tools above, a
                                              problem in the generation of input data, a problem of definition
                                              within TGNC... To be investigated
83643      TGOD: Incoherent results for       The results of TGOD seem to be incoherent with those from RGPS         FDSVal - FDS    FUN_TGNC_POSVEL_RGPS mi - minor                   T-GOD      GMV          Log - Software
           FUN_TGNC_POSVEL_RGPS               TM.                                                                    Validation
                                              Used data from context JV/PO_RDV_4_2
83647      VAL_ATT_150/155 inactive STR is                                                                           Accep           TP_ATT_VAL_150                 mi - minor         T-ATT      GMV          Validation package -
           inhibited, test update needed AR   The delivered vaidation test 150/155 inhibits the inactive STR. The                                                                                              Validation package
           resurected#2                       test plan and validation report are not updated.
                                              The action to do this was given in ODARS of V4.0 AR 37081.

                                              For acceptance the validation setup has been modified by CNES,
                                              the active STR (STR1) has been inhibited and the T_ATT has
                                              entered AP as expected so the previous code error mentioned in
                                              (AR37081)with STR inhibition has been fixed. BUT the test plan
                                              and VR and test setup still need to be update as requested in
                                              OSARS TATT V4 action.
                                                                                                                              14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                       FDS 242000


                                                                                                                                                                                         Configuration  Entity in
Reference                Title                                              Description                                       Phase           Context reference            Criticality       Item        charge                                      Comments
83650     Warnings ending TDRS visibility        At the end of ATV forecast computation, the following messages           Accep - Accep   TP_OPF_VAL_150_1               mi - minor         T-OPF      GMV          Log - Software
          computation                            appear in T-OPF log window (and logbook file) :

                                                 Mar 28 15:58:10 TOOL-messages
                                                 1 :*** WARNING: (OPF_CalculerEcrire_TDRS)
                                                 -> Problem propagation: No additional information available.
                                                 (warning code : ATS_PROPAGATION_PROBLEM)
                                                 2 :*** WARNING: (OPF_calculPlani)
                                                 -> can't manage to converse catesian parameters to orbital
                                                 parameters (warning code : PASS_CART_KEP)

83653      transition message to use ISS attitude AR is related to validation and acceptance test VAL_180 and the     Accep               TP_ATT_VAL_180                 mi - minor         T-ATT      GMV          Validation package -
           from ephemeris file missing "ISS"      warning massage (in process output)to the operator on transition to                                                                                               Validation package
           qualifier                              use ISS attitude input from ephemeris file when ISS TM is not
                                                  available.

                                                 The content of the T_ATT warning message to indicate ISS attitude
                                                 is inputted from an ephemeris file is "transition to use attitude from
                                                 ephemeris file at epoch 01/11/2003 0h00m00s". This implys the
                                                 T_ATT attitude computation is not done and ATV attitude is read
                                                 from a file. Please modify message to state "transition to use ISS
                                                 attitude from ephemeris file at epoch 01/11/2003 0h00m00s".

83662      Incorrect DO number for test cases    The Daily Orbit numbers (ISS and ATV)defined in some tests seem FDSVal - FDS             Test 200 to Test 8100          mi - minor         T-ORM      GMV          Validation package -
                                                 to be wrong. There is no consequence for maneuver calculation        Validation                                                                                    Validation package
                                                 but that give incoherent values when SV are printed.
                                                 The input data of the tests must be checked and corrected.
83663      Erroneous synthetic file generation   Load TP_200 in waiver mode.                                          Accep - Accep       Test 200                       mi - minor         T-ORM      GMV          Log - Software
                                                 Switch ISS SV to keplerian SV.
                                                 Change True anomaly to 113.5139 deg (+10deg vs. initial test).
                                                 Then, the final ISS SV in synthetic file is wrong (the DV's are OK).

83664      VAL_190 should go from TM and/or      The validation test VAL_190 name states "degraded case. ISS              Accep           TP_ATT_VAL_180                 mi - minor         T-ATT      GMV          Validation package -
           ephemeris to no ISS attitude          absolute attitude from ephemeris is not available for interval"                                                                                                    Validation package
           ephemeris and back !                  The test does not have an interval even though mentioned in the
                                                 name and analysis section. The test is always in a situation where
                                                 there is no ISS ephemeris file.

                                                 The test (as the name suggests) should go from TM (ISS attitide)
                                                 and/or ephemeris file (ISS Attitude) to no ISS attitude ephemeris
                                                 file and back again inorder to do a proper test of code and past
                                                 RFCs.
83665      ATT process output transition         valiadtion test 190:                                                  Accep              TP_ATT_VAL_190                 mi - minor         T-ATT      GMV          Log - Software         invent new well phrased process output message for
           message for no ISS attitude available                                                                                                                                                                                           transition to situation where no ISS attitude is
           case is same as the transition to     The content of the T_ATT warning message (in process output) to                                                                                                                           inputted and thus no relative attitude is possible in
           ephemeris file ?                      indicate ISS attitude is not available is "transition to use attitude                                                                                                                     T_ATT.
                                                 from ephemeris file at epoch 01/11/2003 0h00m00s". This is the
                                                 same message as for transition to use the ephemeris input file. (as
                                                 seen in val_180 at start).

                                                 note also it is also missing the acronym "ISS" (needed to avoid non
                                                 expert operator confusion with ATV attitude)
83674      Unusual magnitudes in DUADUP          The validation test VAL_100. misalignment outputs in browser flow. Accep                 TP_ATT_VAL_100                 mi - minor         T-ATT      GMV          Validation package -
           misalignments outputs T_ATT           related to RFC 82681.                                                                                                                                              Validation package

                                                 The outputs 177 to 181 show some unusual magnitudes for the
                                                 newly added misalignments (RFC82681).
                                                 177 DUPDUP_MISAL.rangleMod reaches 250 degrees.
                                                 178 DUPDUP_MISAL.arrtaes reaches -0.12 deg/s
                                                 181 DUPDUP_MISAL.rRateTrMod has a spike near time 1400.03

83678      crash of displays function in T_ATT   The validation test VAL_110.                                             Accep           TP_ATT_VAL_100                 mi - minor         T-ATT      GMV          Log - Software         28.06.2007 Problem confirmed. With the zs option
                                                                                                                                                                                                                                           activated, after around 20 zooms on one of the STR
                                                 On doing a zoom (ZS command) about 20 times it is possible to                                                                                                                             Meas graphics, the xtrace process dies
                                                 crash the displays function during T_ATT execution. nothing                                                                                                                               (Segmentation fault-core dump)
                                                 appears in the displays.

                                                 it is possible to repeat the error. it has occured on the STR meas in
                                                 TATV graphic
                                                                                                                              14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          FDS 242000


                                                                                                                                                                                         Configuration  Entity in
Reference                   Title                                              Description                                     Phase          Context reference            Criticality       Item        charge                      Comments
83688     Redundant data in the RT_TACC            The output flow RT_TACC for T-ACC V5.0 is not strictly identical       SysVal - System TP_ACC_VAL_125_2               mi - minor         T-ACC      GMV          Log - Software
          output flow for the validation test      with the one of T-ACC V4.2.                                            Validation
          TP_ACC_VAL_125_2                         At the end of the RT_TACC output flow, at the date of
                                                   1975.12614699074, ACCA measurements seem to be treated
                                                   twice (two lines at the same date in the output flow) by the
                                                   software.

83689       Messages of not real gap detection in For several validation tests, some messages appear in the process Accep - Accep         Validation tests               mi - minor         T-ACC      GMV          Log - Software
            the process output of T-ACC           output: "Not real TM gap", "ACCA TM loss at "... when using
                                                  ATEGUI or when running unitary validation tests.
                                                  That's the case for tests 135_2, 135_5, 135_7, 135_8, 135_9.

                                                   For these tests, we are not in FDS simulated time, but in catch-up
                                                   mode. We usually do not have this kind of messages when using
                                                   the catch-up mode. Why these messages are emitted ?
83692       color of event status                  we can modify the events status but the "Nominal terminaison" and Accep                TP_GRA_VAL_050                 mi - minor         T-GRA      GMV          Log - Software
                                                   "Futur" are the same color (green)

83693       save current template during           It is not possible to save only the templates                          Accep           TP_GRA_VAL_152                 mi - minor         T-GRA      GMV          Log - Software
            processing
83695       COLOR OF DEGRADED CASE                 "PAST" and "NEXT" are the color (green)                                Accep           TP_GRA_VAL_060_6               mi - minor         T-GRA      GMV          Log - Software
            ALERT PAGE
83698       Problem on the DV cumulating in        After comparing the flows RT_TACC from TP_ACC_VAL_135_3                Accep - Accep   TP_ACC_VAL_135_3               mi - minor         T-ACC      GMV          Log - Software
            validation test 135_3                  and TP_ACC_VAL_135, it appears that some difference can be
                                                   observed.

                                                   The Homing start date is defined with the value of 281.2073727,
                                                   using the MMI offset and the first boost date. But the DV
                                                   cumulating begins only at 281.20739583415, and no cumulating is
                                                   performed for the dates of 281.207372686002 or
                                                   281.207384260076. Indeed, the cumulating begins two seconds
                                                   after the beginning date of the GNC period, at the date of
                                                   281.20739583415. Even if some numerical differences can explain
                                                   why the ACCA and the thrusters measurements at the date of
                                                   281.207372686002 are not taken into account in the cumulating, it
                                                   can not explain that the date of 281.20739583415 is not taken into
                                                   account.

                                                    Start and end dates of periods are correct.
83699       Wrong start and end dates for the       The Homing start date and the first boost start date are set by the   Accep - Accep                                  mi - minor         T-ACC      GMV          Log - Software
            first Homing boost period in validation manual date of the MMI : "08/10/2000 04h58m00s004" which
            case 135_8                              corrresponds to 281.20694449074074. Therefore no drift period is
                                                    considered.
                                                    But in the GNC_SYNTH file, the start date for the first Homing
                                                    period is "04h58m01s000" instead of "04h58m00s004", and the
                                                    end date is "05h08m01s000" instead of "05h08m00s004".
                                                    Therefore, dates for the first Homing boost period are not correct.

                                                   The other data seem correct in the GNC_SYNTH.... file.

83700       FDB disconnection during the run of    During the run of a validation test, some messages appeared in the Accep - Accep                                      mi - minor         T-ACC      GMV          Indet -
            T-ACC validation tests                 log window :                                                                                                                                                     Undetermined
                                                   "FDB_disconnect", "Error peeking message header
                                                   (EWOULDBLOCK: Resource temporarily unavailable) (error code :
                                                   FDB_SOCK_RECP_ERR)".

                                                   The same behaviour was encountered with the ATEGUI at the ATV-
                                                   CC back-up for several test cases.
83702       The taking into account of the         The half-light and eclipse computation taking into account the Accep - Accep           TP_OPF_VAL_100_1_atm890 mi - minor                T-OPF      GMV          Doc - Document
            atmosphere layer in eclipse            atmosphere layer height is not documented (neither in Software                         00
            computation must be documented         User Manual OPS-UM-242561-61556-GMV Ed 1.2 nor in any
                                                   Design Technical Note)
                                                   The knowledge of the implemented algorithm is necessary to
                                                   explain the discrepancy between Marmottes and TOPF eclipse
                                                   times
                                                                                                                                   14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                      FDS 242000


                                                                                                                                                                                              Configuration  Entity in
Reference                   Title                                           Description                                 Phase                      Context reference            Criticality       Item        charge                                      Comments
83705     Incorrect latitude/longitude range in In "Parameters" Page of "TOOL DATA" panel :                         Accep - Accep              TP_OPF_VAL_150                 mi - minor         T-OPF      GMV          MMI - MMI
          MMI definition of TDRS satellites and
          SAA crossing                          - "TDRS/ARTEMIS" section :
                                                Authorized latitude range must be ]-90 ; 90[ deg.
                                                Negative longitude values should be authorized. Longitude
                                                definition at MMI should be authorized in ]-360 ; 360[ deg (without
                                                changing the internal range the current source code is working with
                                                -180,180 or 0,360)

                                                  - "SAA crossing" section :
                                                  Authorized latitude range must be ]-90 ; 90[ deg.
                                                  The same authorized range as in TDRS longitude definition should
                                                  be used.
                                                  If setting minimum latitude/longitude greater than the maximum
                                                  one, no error message is displayed and TOPF can be launched. A
                                                  pop-up window should prevent wrong SAA definition.
83706       Unsufficient validation for antenna   - Redundant TP_OPF_VAL_150_1 test should be removed in the Accep - Accep                     TP_OPF_VAL_150_1/2             mi - minor         T-OPF      GMV          Validation package -
            mask implementation                   validation plan since it is exactly the same test as                                                                                                                   Validation package
                                                  TP_OPF_VAL_150.
                                                  - One test should be added with "partial" masking to check attitude
                                                  computation by making use of Marmottes sensor (Using an
                                                  antenna mask with several azimuth range and minimum elevation
                                                  between 0 and 90 deg)
                                                  - In the antenna input file provided for tests VAL_150_1 & 2, coma
                                                  ";" separators should appear in "ant_mask" array (defined in
                                                  "antenna" structure)
83707       Erroneous analysis in eclipse and     The ephemeris step to compute events is set to 60 sec so the        Accep - Accep            TP_OPF_VAL_260                 mi - minor         T-OPF      GMV          Validation package -
            dazzling dates validation             actual discrepancies (less than 60 seconds) between the TOPF                                                                                                           Validation package
                                                  and Marmottes computed dazzling dates can not be assessed.
                                                  The test must be modified and computation step set to 1 second to
                                                  better assess the discrepancies.
83708       Negative SP-GNC Angle Bias in T-      It is impossible to enter a negative bias for SP-GNC mode as MMI Other - Other               Any                            Ma - Major         T-OCF      GMV                                 EJ, 19/06/07: correction plan agreed for T-OCF V5.1
            OCF                                   requires this field to be positive while entering the 360°
                                                  complementary angle provokes this message : "Value of SP-GNC
                                                  Angle Bias should be within (-35 deg, +35 deg) (error code :
                                                  OCF_SPGNC_BIAS_ERR)".

83716       Abnormal visibility hole above KUK    During ATV pass above KUK station, when ATV site from ground                 Accep - Accep   TP_OPF_VAL_370                 mi - minor         T-OPF      GMV          Log - Software
            ground station on orbit 4             station reaches its maximum (about 20 deg), the visibility type
                                                  changes from half-lobe to geometrical, then back to half-lobe.

                                                  see plot of constraints on planisphere for orbit 4 / daily orbit 9 or file
                                                  OPF_CONF_OPFVIEW :

                                                  "VISI_STA" "Stations" 1725.55253472222 1725.5550462963
                                                  1725.55253472222 172
                                                  5.5550462963 -61.4337460723553 -49.1855662580729 -
                                                  61.4337460723553 -49.1855662580729 4 4 0
                                                  0 "Visibility type: HALF LOBE" ""
                                                  "" "" ""
                                                  "VISI_STA" "Stations" 1725.55614583333 1725.55799768518
                                                  1725.55614583333 1725
                                                  .55799768518 -44.0480100132343 -35.6219817780808 -
                                                  44.0480100132343 -35.6219817780808 4 4 0
                                                  0 "Visibility type: HALF LOBE" ""
                                                  "" "" ""

83721       TCMP_4.0 : wrong name displayed       In FDS_v2.3, TCMP_v4.0 has a problem of display in Relative                  FDSVal - FDS                                   mi - minor         T-CMP      GMV          MMI - MMI
            for ISS abs. ref. ephemeris           mode, concerning the ISS absolute reference ephemeris :                      Validation
                                                  - there is no display of the file infos if it is the first file choosen
                                                  (before choosing the ATV Rel. Ephem. files to be compared)
                                                  - the infos are those of the ATV Rel. Reference Ephem if this one
                                                  has been selected before.

                                                  In any case, if the user presses "view", the file edited in nedit is the
                                                  expected one, the problem is only in the non/wrong display of the
                                                  infos of the file on the panel of the MMI.
                                                                                                                          14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                      FDS 242000


                                                                                                                                                                                     Configuration  Entity in
Reference                Title                                            Description                                Phase                 Context reference           Criticality       Item        charge                                      Comments
83722     TCMP_4.0 validation : wrong name of In test FDB_TP_CMP_VAM_020, the ISS absolute ephemeris file FDSVal - FDS                                               mi - minor         T-CMP      GMV          Validation package -
          ephemeris                           is named ATV_RELEPH....                                           Validation                                                                                      Validation package
                                              Its content seems to be the one of an ISS absolute ephemeris, and
                                              the test passes, but the wrong naming of the file is disturbing.

                                                  This file is used in other tests, such as
                                                  FDB_TP_CMP_VAM_310_2,...

83735      TCMP_4.0 : error                       AR similar to the 35910 one, but concerning ISS absolute          FDSVal - FDS       TP_CMP_VAL_130                mi - minor         T-CMP      GMV          Log - Software
           messagesincomplete when                ephemeris comparison : when reference frame for PV or attitude is Validation
           comparing ISS abs eph.                 wrong (not ECEF/J2000), then the error message of the tool should
                                                  indicate which ephemeris is concerned (the reference or the non-
                                                  reference one).


83742      Wrong events sequence in some          -General remark: Events B_ECLS/E_ECLS and                             FDSVal - FDS   FDS_FUNC_TFDB_Timeline        mi - minor         T-FDB      GMV
           timeline and ATV_EVENTS files,         B_ECLS_HL/E_ECLS_HL should not have any duration                      Validation
           particularly about orbit numbers       description. But in all the ATV_EVENTS files generated by T-FDB,
           sequence.                              we can find, in the column 5, values such as : " 0.000", " 60.000", "
                                                  1980.000", " 2160.000", " 10.000", " 8.000", " 360.000" etc…

                                                  - POST_ESCAPE1 period: The orbit and daily orbit numbers are
                                                  wrong at the date "27/04/2007 14h57m29s357" ("E_VISI",
                                                  "TDRS1304") and the date "27/04/2007 19h31m29s357" ("E_VISI",
                                                  "TDRS1309") : it corresponds to the orbit just before the EQTR
                                                  crossing. It seems that there is a discrepancy between TOPF and
                                                  other tools about orbit numbers.
                                                  - Sequence B_CHPH/E_CHPH not closed for "B_CHPH" "TIV" at
                                                  the date "28/04/2007 21h43m09s117": there is no the
                                                  corresponding E_CHPH in the event file generated (the event
                                                  B_CHPH comes from T-EXT).


                                                  - POST_ESCAPE2: The number of orbit and daily orbit is wrong at
                                                  the date "30/04/2007 13h07m14s437" ("E_SLEW",
                                                  "AFTER_BOOST") : it corresponds to the orbit just before the
                                                  EQTR crossing. This problem s

83746      Problems to update the interval time   CTX_TOCF_ManTP : the automatic mode is working, but not the                                                        mi - minor         T-OCF      GMV          Log - Software         EJ, 19/06/07: correction plan agreed for T-OCF V5.1
           sequence in some configurations        "update dates" button in this test. It's necessary to select "Manual"
                                                  then "Automatic" to have the dates updated.

                                                  CTX_TOCF_OrbExc : from the config file, select "Manual" &
                                                  "Duration", with a start date after the beginning of the ephemeris
                                                  and a duration shorter then the duration of ephemeris. To click on
                                                  "Update dates" makes the beginning date correct but not the
                                                  duration.

                                                  There is some problem with the display of the options “Start Date:
                                                  From the 1st Manoeuvre of MP” and “End Date: From the last
                                                  manoeuvre of MP”:
                                                  - loading CTX_TOCF_ManTP: "Automatic" mode selected, but the
                                                  line "Star date…" does not appear. We have to select "Automatic"
                                                  another time to make it appears. It's the same for the line "End
                                                  Date…" which should appear in "Automatic" mode, with "Relative
                                                  date" selected.
                                                  - and next, loading CTX_TOCF_OrbCirc, the lines don't disappear.

                                                  CTX_TOCF_ManMC2 : "Automatic" from the 1st man of the plan,
                                                  "Absolute epoch". => The button "Update dates" does not work,.

                                                  The "update dates" button does not update the "Computation end
                                                  date" or the "Relative end date".
                                                                                                                              14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                FDS 242000


                                                                                                                                                                                         Configuration  Entity in
Reference                  Title                                              Description                                        Phase        Context reference            Criticality       Item        charge                                Comments
83747     Problem to load the W/O of "TORM        On flight Jules Verne, context QO_LEOP_N_1, activity LEOP, the          Oper            QO_LEOP_N_1                    mi - minor         T-OCF      GMV          Log - Software   EJ, 19/06/07: correction plan agreed for T-OCF V5.1
          INJECTION PARAMETERS"                   frame computation is modified so that the "A5 sep" would be
                                                  available.

                                                  "A5 Sep" is selected and after loading WO, the "INJECTION
                                                  Parameters" button turns blue, but in the panel, it's not the case of
                                                  the "TORM INJ..." line.

                                                  The W/O for this specific entity exists.


83748      Inconsistency between the end of the   The run is not stopped when the end interval is before the end of     Accep             TP_OCF_VAL_1600                mi - minor         T-OCF      GMV                           EJ, 19/06/07: correction plan agreed for T-OCF V5.1
           computation interval and the last      the last manoeuvre and when this last manoeuvre has his upload
           manoeuvre to be uploaded in deorb      flag to "yes". The tumbling mode is connected at the end of the first
           mode                                   manoeuvre instead.
83749      Computation of test                    The run takes a very long time, up to 6 minutes. It is very long in   Accep             TP_OCF_VAL_1600                mi - minor         T-OCF      GMV                           EJ, 19/06/07: this AR should be corrected for T-
           TP_OCF_VAL_1600 takes more than        the Solar Array orientation angle computation.                                                                                                                                     OCF V5.1
           1 minute
83751      Wrong release name on the MMI          When launching the T-ACC software from the activity                     Accep - Accep                                  mi - minor         T-ACC      GMV          Log - Software
           panel                                  "TACC_05_00", the MMI panel appears with "TACC V04_01"

83752      generics data for targeted point       tolerance for date and minimum drift for first maneuver are             FDSVal - FDS                                   mi - minor         T-DEM      GMV          MMI - MMI
                                                  generics for the impact targeting, so these inputs should be set just   Validation
                                                  between "target impact point?" and "first choice for impact point
                                                  definition" in the MMI
83753      longitude iterations                   In target impact panel, when orbit number is selected, the MMI          FDSVal - FDS                                   mi - minor         T-DEM      GMV          MMI - MMI
                                                  should ask for "maximum iterations for orbit number" instead of         Validation
                                                  "maximum iterations for longitude"

83754      DO and longitude algo                  when the targeted point is defined by longitude and daily orbit         FDSVal - FDS                                   mi - minor         T-DEM      GMV          Log - Software
                                                  number, TDEM iterates on longitude then on daily orbit and finally      Validation
                                                  on longitude. Computation duration can be shortened if it iterates
                                                  first on daily orbit and then on longitude.

83755      targeted perigee                       in maneuver definition, TDEM should allow to target perigee lower       FDSVal - FDS                                   mi - minor         T-DEM      GMV          Log - Software
                                                  than 0km                                                                Validation

83756      no convergence                         When impact point is targeted by longitude and daily orbit, TDEM        FDSVal - FDS                                   Ma - Major         T-DEM      GMV          Log - Software
                                                  doesn't converge for some values. For example, from test case           Validation
                                                  410, it doesn't converge if we change the targeted longitude by
                                                  355°, 0° or 10°.

83767      Computation of                         There are two ways to compute P_RT_SLEW_BOOST in TC:         FDSVal - FDS               FDS_FUNCT_TFDB_GTC_O           mi - minor         T-FDB      GMV
           P_RT_SLEW_BOOST in OCS_OCS             P_RT_SLEW_BOOST (OBIT) = (slew duration to boost +           Validation                 CS_OCS
           TeleCommand                            SLEW_STABILIZATION_EP + CONTINGENCE_MARGIN ) * OBIT,
                                                  for TC skeletons without YS
                                                  = (slew duration to boost + SLEW_STABILIZATION ) * OBIT, for
                                                  TC skeletons with YS

                                                 In the case of OCS_OCS skeleton, the first formula (without YS)
                                                 should be use. But it seems it is not the case for OCS_OCS, and it
                                                 should be checked also for skeleton
                                                 TRANSFER_TWO_BOOST_NO_YS.
83769      TATV/LVLH value range appear          Angle magnitudes in TATV/LVLH do not appear normal for this        Accep - Accep         TP_VDA_VAL_50                  mi - minor         T-VDA      GMV          Log - Software
           abnormal                              phase of the mission (near RDV).
                                                 The TISS and LVLH of the station are expected to be nearly
                                                 superimposed yet the TATV/LVLH and TATV/T_ISS are very
                                                 different. possible bad LVLH file in test.
83776      T_VTG residual calc for red sensor is free test acceptance VTG V4                                        Accep - Accep         acceptance free test           mi - minor         T-VTG      GMV          Log - Software   29.05.2007 error confirmed by GMV. To be fixed in
           bad when nom is inhibited                                                                                                                                                                                                 code for next release of VTG.
                                                 when the nominal sensor ( be it TGM or VDM) is inhibited from the
                                                 calculation chain the residual calculated by the tool for the
                                                 redundant sensor is bad. This is most evident on x axis at S3 (
                                                 250m)
83789      T-GOD AR: Process output saturated In kalman mode, convergence messages are written in process           Accep - Accep         RP_GPS_VAL_2010                mi - minor         T-GOD      GMV          Log - Software
           with convergence messages in rEKF output at each filter step. The process output is saturated with
           mode                                  "Filter convergence at date ..." lines.
                                                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                FDS 242000


                                                                                                                                                                                       Configuration  Entity in
Reference                 Title                                             Description                                     Phase           Context reference            Criticality       Item        charge                                Comments
83813     Questions/Points on VDA V3 val test     1)The test should make tool use the ephemeris file for ISS attitude   Accep - Accep   TP_VDA_VAL_86                  mi - minor         T-VDA      GMV          Log - Software
          86                                      not stop/die.

                                                  2) as there is no ephemeris in test setup why is there no error
                                                  message to indicate the ehpemeris is not available ? This error
                                                  message actually occurs in test 87 but should also appear in this
                                                  test 86.

                                                  (note the anomaly number AR83770 is incorrectly referenced for
                                                  this AR in the logbook for VDA 3 acceptance)
83814      STR North and south values in T-       In the context in reference, using T-OCF in survival mode, attitude   Oper - Oper     PO_PHAS_C1                     Ma - Major         T-OCF      GMV          Log - Software   EJ, 19/06/07: correction plan agreed for T-OCF V5.1
           OCF                                    only, the output euler angles have strange behaviour in attitude
                                                  mode SP-GNC. With STR north activated, the third euler angle is
                                                  always constant , equal to exactly 55. With STR south activated,
                                                  the third euler angle is varying a lot. Which one is good /wrong?
                                                  the exact value of 55 is a bit strange. Is it normal?

83815      Incoherent TM Gap detection in FDS Anomaly on Gap detection in FDS Simulated Time mode and                                                                  Ma - Major         T-RDV      GMV          Log - Software   13/06/2007-L-NRB 21 - On going performance
           Simulated Time mode and different  different behaviour between FDS Simulated Time and Catch Up                                                                                                                          analysis on T-RDV robustness and discusisons with
           behaviour between FDS Simulated    mades.                                                                                                                                                                               GMV on -gjoing
           Time and Catch Up mades            See description in attached file AR83815 and OSAR T-RDV 6.0
                                              logbook OPS-LB-242552-61754-CNES
83816      Waiver mode is not maintained when When incrementing version of simulation context, waiver defined in Oper - Oper            PO_PHAS_C1                     mi - minor      FDB_SERVER GMV             Log - Software
           incrementing version               an activity is not maintained in subsequent versions.

                                             In the context provided, the problem has been found in the DRAFT
                                             activity.
83817      T-RDV RT: Wrong initialization of When the "Two boost solution analysis" is not performed by T-RDV                                                          mi - minor         T-RDV      GMV          Log - Software   25/05/2007 : To be tested in FDS 2.3.1
           output flow parameter             , this output flow parameter TRDV_2BOOSTS_COMPARED should
           TRDV_2BOOSTS_COMPARED(-)          be equal to 9 (See Remark n° 2 in the file attached to OPS-RfC-                                                                                                                       20/06/2007:
                                             242552-82655-CNES "T-RDV: Update of Output flow in RT mode                                                                                                                            AR partially corrected in T-RDV 6.1 (FDS 2.3.1)
                                             and update of relative trajectory display"). The analysis of Output                                                                                                                   See last document
                                             flow shows that this initialization to value equal 9 is not correctly                                                                                                                 "Ar_Review_83452_83815_83817_gmv_04.doc" 5
                                             applied.                                                                                                                                                                              june 2007 - exhanged wit Alfredo M. Anton)
                                             See description OSAR T-RDV 6.0 logbook OPS-LB-242552-61754-
                                             CNES.
83820      T-RDV NRT: Two simultaneous       Scheduler MMI panel and Tuning Parameters MMI panel define the Accep                       OSAR T-RDV                     mi - minor         T-RDV      GMV          MMI - MMI
           definition of some MM parameters  same two parameters "End Pre-Homing" and "End S2SK" and no
                                             coherence is made between these MMI inputs.
                                             See description in attached file AR_83820_T-RDV-6.0.pdf and
                                             OSAR T-RDV 6.0 logbook OPS-LB-242552-61754-CNES.
83822      T-RDV NRT (Warm Start): Anomalies In some cases of warm start date in closing , T-RDV produces          Accep                OSAR T-RDV 6.0                 Ma - Major         T-RDV      GMV          Log - Software   25/05/2007 : To be tested in FDS 2.3.1
           on closing maneuvers management erroneous ATV trajectory and ATV maneuver plan.
                                                                                                                                                                                                                                   20/06/2007:
                                                  See description in attached file AR_83822_T-RDV-6.0.pdf and                                                                                                                      AR partially corrected in T-RDV 6.1 (FDS 2.3.1).
                                                  OSAR T-RDV 6.0 logbook OPS-LB-242552-61754-CNES.                                                                                                                                 The "second anomaly encountered" within AR 83822
                                                                                                                                                                                                                                   (See Acceptance logbook of FDS tool T-RDV 6.0) is
                                                                                                                                                                                                                                   not corrected.
83823      Error on MCI date when saving a        After saving a configuration file in T-GOD or in T-EXT, when we try Oper - Oper                                      mi - minor        ATSLIB      GMV          General MMI -
           configuration file in T-EXT or in T-   to load this configuration file in the MMI, an error is sent to the user,                                                                                       General MMI
           GOD (FDS V2.3)                         and the MCI date does not correspond to the real date.

                                                  Error message:

                                                  *** ERROR: Acces (acc_get_type): non existent data
                                                  'ATV_MP.MCI_ATV.UTC_date'
                                                  *** ERROR: Acces (acc_get): <report erreur interne>
                                                  --> non existent data 'ATV_MP.MCI_ATV.UTC_date'
                                                  May 07 11:08:11 ENTRY_DATE UTC date : change unit error
                                                                                                                                 14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                     FDS 242000


                                                                                                                                                                                            Configuration  Entity in
Reference                Title                                             Description                                           Phase           Context reference            Criticality       Item        charge                                    Comments
83824     T-GOD unable to save results in FDB After the run in NRT for the configuration file                               Oper - Oper      PO_PHAS_C_1                    mi - minor        T-GOD       GMV          MMI - MMI
          after LSM run.                      "post_nalayse_avec_sv_agcs", the saving in local works well, but
                                              the saving in FDB failed with the message :

                                                    1 :*** WARNING: (FDB_validate_results)
                                                    -> Validation process aborted (warning code :
                                                    FDB_VAL_ABORT_INF)
                                                    2 :*** ERROR: (FDB_unpack_res_header)
                                                    -> Refused msg: Unknown type GOD_ATV_PVTR (error code :
                                                    FDB_MSG_RETURN_ERR)
                                                    3 :*** ERROR: (FDB_recv_msg)
                                                    -> Problem propagation: No additional information available. (error
                                                    code : ATS_PROPAGATION_PROBLEM)
                                                    4 :*** ERROR: (FDB_send_msg_param)
                                                    -> Problem propagation: No additional information available. (error
                                                    code : ATS_PROPAGATION_PROBLEM)
                                                    5 :*** ERROR: (FDB_validate_results)
                                                    -> Problem propagation: No additional information available. (error
                                                    code : ATS_PROPAGATION_PROBLEM)
                                                    6 :*** ERROR: (_FDBvalidate_file_or_flow)
                                                    -> Problem propagation: No additional information available. (error
                                                    code : ATS_PROPAGATION_PROBLEM)
                                                    7 :*** ERROR: (FDB_get_file_format)
                                                    -> Problem propagation: No additional information available. (error
                                                    code : ATS_PROPAGATION_PROBLEM)
                                                    8 :*** ERROR: (FDB_unpack_res_param)
                                                    -> Refused msg: Unknown type GOD_ATV_PVTR (error code :
                                                    FDB_MSG_RETURN_ERR)
                                                    May 07 11:28:59 Validation in FDB failed

83825       Impossible to execute tests             It's impossible to execute the test 1700, ATV ephemeris, ATV            Accep            TP_OCF_VAL_1700;TP_OCF mi - minor                 T-OCF      GMV          Validation package - EJ, 19/06/07: correction plan agreed for T-OCF V5.1
            TP_OCF_VAL_1700 and 1700_1 of           events and ISS ephemeris files are not available.                                        _VAL_1700_1                                                               Validation package
            the T-OCF Validation Plan
83826       Inversion of events "B_SLEW" and        ATV events: event "B_SLEW" before "E_ATT_MODE" for each                 Test - Test      CTX_TOCF_ManTP                 mi - minor         T-OCF      GMV          Log - Software      EJ, 19/06/07: correction plan agreed for T-OCF V5.1
            "E_ATT_MODE" in the ATV EVENTS          boost. Not reproduced on TP_OCF_VAL_100, because the
            file from T-OCF                         parameter "Predelay of Slew beginning" is not null.
83827       Wrong OCF DIFF computation with         The OCF_DIFF at the beginning of the OCF are different of those         Test - Test      CTX_TOCF_ManTP                 mi - minor         T-OCF      GMV                              EJ, 19/06/07: the active OCF should be OCF5 not
            loading an on-board OCF in OCF and      of the on-board OCF. It's the same OCF and the same orbit as the                                                                                                                       OCF6. In this test the OCF6 will be replaced by a
            ATT computation mode                    ones used to compute the on-board OCF.                                                                                                                                                 new one at exactly the same date, so the OCF6
                                                                                                                                                                                                                                           will never be taken into account. The discontinuity
                                                    We have on the on-board OCF, the sequence                                                                                                                                              between the old and the new OCF should not be
                                                    [OCF1,OCF2,OCF3,OCF4,OCF5,OCF6,...]. With the same                                                                                                                                     calculated with OCF6.
                                                    ephemeris and mission plan, this specific test makes a new
                                                    computation of the 6th OCF. The OCF_DIFF at the beginning of
                                                    this OCF6 are quite null.

                                                    It seems that the OCF_DIFF is computed against OCF6 of the on-
                                                    board OCF_DATA_SET instead of OCF5.
83834       LOF computation during OCF              - According to CP 30299 there should be a new frame flag for LOF Accep                   TP_OCF_VAL_1700;TP_OCF mi - minor                 T-OCF      GMV                              EJ, 19/06/07:
            computation wrt ISS ephemeris           in the panel "Frame Computation".                                                        _VAL_1700_1                                                                                   - there's no need of a flaf for LOF computation but
                                                    - The file OCF_LOF is not generated in test 1700_1 (it's impossible                                                                                                                    you wrote it on the CP. If you do not create it, you
                                                    to select LOF frame in the MMI, see above)                                                                                                                                             have to update the CP
                                                    - According to the RfC (and the CP) it should have been added the                                                                                                                      - I'm referring to the test 1700, sorry.
                                                    LOF comparison, in the ATT_ACC_OCF file. The RfC demand a
                                                    new structure, it's not the case. There is only differences on the
                                                    existing structures.
83835       No verification of the "update delay"   From the test PO_RDV_4_5, we determine the last OCF wrt ISS         FDSVal - FDS         PO_RDV_4_5                     mi - minor         T-OCF      GMV                              EJ, 19/06/07: correction plan agreed for T-OCF V5.1
            in T-OCF, delay between 2 OCF           ephemeris. This OCF has a beginning date 1 ms after the             Validation
                                                    beginning of the on-board OCF (determined wrt ATV ephemeris).
                                                    See TOCF_V5.0_anomaly-logbook for more details.

                                                    There is no warning message in the PROCESS OUTPUT. The
                                                    "update delay" is equal to 120s and the flag "Consider constraint" is
                                                    selected.

                                                    The others constraint are verified (out-of-plane, in-plane, angular
                                                    rate dicontinuities)
                                                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          FDS 242000


                                                                                                                                                                                       Configuration  Entity in
Reference                Title                                           Description                                         Phase          Context reference            Criticality       Item        charge                      Comments
83836     TOCF : wrong determination of the      From test PO_RDV_4_5, different run are made, see                      FDSVal - FDS    PO_RDV_4_5                     mi - minor         T-OCF      GMV
          OCF_DIFF value                         TOCF_V5.0_anomaly-logbook for more details.                            Validation

                                                 We have on-board : Beginning last OCF : 01/05/2007
                                                 03h51m57s607
                                                 - First run : Beginning of the new OCF : 01/05/2007
                                                 03h51m57s607
                                                 - Second run : Beginning of the new OCF : 01/05/2007
                                                 03h51m57s606
                                                 - Third run : Beginning of the new OCF : 01/05/2007
                                                 03h51m57s608

                                             We call the on-board OCF diff OCF6-OCF5 = -0.0789°.
                                             - with the first run we have NewOCF-OCF6 = 0.362°,
                                             we should have NewOCF-OCF5 = 0.362 - 0.0789 = 0.283°.
                                             Instead, with the second run NewOCF - OCF5 = 0.441°
                                             (0.362+0.0789).
83838      Redundant messages in the process When processing GPS measurements from the flow                             Oper - Oper     PO_PHAS_C_1                    mi - minor         T-GPP      GMV          Log - Software
           output when GPS measurements are "ATV_GPSMEAS.18042007_105431.18042007_213253", some
           rejected                          redundant messages of rejection are written in the process output.

                                                 Extract of this messages :
                                                 "
                                                 ATV GPS TM gap beginning at epoch: 2664.512891
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 28 / P-R : 23670820.270 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 19 / P-R : 20808487.000 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 2 / P-R : 23271507.870 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 10 / P-R : 23519756.270 m / Res : 0.5429387E+02 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 3 / P-R : 23776734.700 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 31 / P-R : 21746659.080 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 1 / P-R : 22273859.090 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 8 / P-R : 20994801.520 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 13 / P-R : 20574639.030 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 28 / P-R : 23670820.270 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 19 / P-R : 20808487.000 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
                                                 PRN : 2 / P-R : 23271507.870 m / Res : 0.0000000E+00 m
                                                 Measurement rejected: Date : 2664.513006 / Vehicle : ATV / GPS
83845      No possibility to load a reference    With T-CMP release V4.0, the user must choose the origin tool for                                                     mi - minor         T-CMP      GMV          MMI - MMI
           ephemeris file without ignoring its   ephemeris file in order to browse files. Therefore, when the user
           origin                                ignores the origin of a file but knows just the 'user comment', he
                                                 must choose one by one the origins in order to find the file.

                                                 Please, add 'ANY' in the FDB data panel in order to give the user
                                                 the possibility to suppress the filter by origin.

83854      winking of KOS/AE                     The KOS/AE can be seen but there appear and desappear.                 Accep - Accep   test 151                       mi - minor         T-GRA      GMV          Log - Software
                                                 Event you don't move nothing.
83879      Plot refresh and change of graphic    In T-RDV RT, during the run, if the user switches from the "boost                                                     mi - minor         T-RDV      GMV          Log - Software
           frame in T-RDV RT                     timeline" graphic frame to the "Relative trajectory" one, the xtrace
                                                 plot shows some non existing curves that are erased if the the
                                                 refresh button is pushed. This behaviour shall be fixed by
                                                 performing a refresh command at any change of graphical frame.
                                                 More in general, at any time only the last propagated trajectory
                                                 shall be shown and only when applicable.
                                                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                FDS 242000


                                                                                                                                                                                       Configuration  Entity in
Reference                  Title                                             Description                               Phase                 Context reference           Criticality       Item        charge                                Comments
83883     Impossible to execute TOCF in "ATT      In the activity CAMDEMO, it has been selected the PFM_30032007 Test - Test            Jules_Verne/SVT_TPOCAM_        mi - minor         T-OCF      GMV
          only" with a computation end date       ephemeris and we would have liked to determine accuracies wrt                         6
          lower than the end date of the PFM      LOF and MOOF on a part of the second OCF the on-board OCF.
          ephemeris
                                                  The beginning date of this OCF has been putten in the "Interval
                                                  time sequence" panel; the computation end date was 18/04/2007
                                                  20h00. The process aborted with the message "Cannot append the
                                                  ephemeris record since date is lower than greatest already
                                                  existing".

                                                  The config file was saved with the name AR_ATTonly_TOCF.

83884      The T-OCF Attitude Mode Building is      A specific attitude was created in "TOOL DATA/Attitude Mode"         Oper - Oper    Jules_Verne/PO_RDV_4_2         mi - minor         T-OCF      GMV                           EJ, 19/06/07: correction plan agreed for T-OCF V5.1
           not working                              from the attitude of the mission profile:
                                                    - when selecting "T-OCF Attitude Mode Building" we don't have the
                                                    any attitude law, not even the YS of the mission profile
                                                    - the attitude laws defined in this section (initial YS plus EP and
                                                    RELATT) are not take in the computation. The plot "Entire attitude
                                                    in OCF" shows only the YS law.
                                                    - when selected "RELATT" for a new law, it's impossible to write its
                                                    start date.
                                                    The config file and the results were saved with the name
                                                    AR_ATTBuilding_TOCF.
83891      Missing identification of FDS librairies run the UNIX command "what" on any FDS tool .exe or .ihm does Audit - Audit         FDS installed configuration      mi - minor        FDS       GMV          Autre - Other
           versions in .exe and .ihm files          not show the versions of FDS libraries used to make these files.

                                                  The version and date of FDS libraries : ATSLIB, FDBLIB,
                                                  FDSGLIB, CNES_CFI and if used EXTLIB, GNCLIB, ORMLIB shall
                                                  be displayed by the command 'what'

                                                  GMV shall also clarified what are the rules for numbering CI
                                                  versions
                                                  in particular
                                                  the rules :
                                                  to increment the first figure
                                                  to increment the second figure
                                                  to add a third figure in a version number.

83892      Time in the alphanumerical page of T- At present time it is possible to add time as a parameter to the T-     Oper - Oper    OQ_RDV_N_1                       Ma - Major       T-GNC      GMV          MMI - MMI
           GNC                                   GNC alphanumerical frame. It has been verified that if time is
                                                 added to the panel, T-GNC increases hugely the cpu load request
                                                 up to the saturation of the whole machine. For this reason it shall
                                                 not be allowed to add time to the alphanumerical panel. In any
                                                 case it is not useful due to its format.
83905      Bad identifier definition in the "ISS The "ISS requested epoch" has to refer to ISS identifier and not                                                                         T-FDB      GMV
           requested epoch" file                 ATV :
                                                 the name convention should be : txxisxxm.XXX and not
                                                 txxatxxf.XXX
                                                 Moreover, the line 3 should conent ISS rather than ATV
83906      ISS_SDEMI creation from ISS orbite The ISS_SDEMI entity created when the ISS orbit file is recovered                                                                           T-FDB      GMV
           element recovered from DG             from DG contains a StateVector structure rather than ISS_SDEMI
                                                 structure
83908      Doppler computation from T-OPF        The doppler compensation file produced by T-FDB needs a T-OPF                                                           mi - minor       T-FDB      GMV
           event file                            event file containing the visibilities of ARTEMIS satellite. The labels
                                                 associated to visi event are B_VISI and E_VISI rather than
                                                 B_RFLK and E_RFLK . Moreover, the nominal procedure for T-
                                                 OPF is to compute these visibilities in 1/2 LOBE definition and not
                                                 in Geometric, the computation has not to take into account the
                                                 second parameter but only the kind of event (B/E_VISI) and the
                                                 name of the satellite (ARTEMIS) to compute the doppler .


83915      Wrong caracter in text file "TC MSU"   When we generate the TC MSU file by TFDB it is not possible to       Other - Other    Dry Run SVT_RDV                  mi - minor       T-FDB      GMV          Log - Software
                                                  print via a2ps because it is see as executable file.
                                                  If you look this generate file by vi you can see "^M" caracter. We
                                                  have used dos2unix but wihtout effect.
                                                  lp commande can not print this file.
                                                                                                                              14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                 FDS 242000


                                                                                                                                                                                         Configuration  Entity in
Reference                   Title                                            Description                                       Phase           Context reference           Criticality       Item        charge                                Comments
83916     impossibility to modify dates of a new In TGOD non real time, activity DRAFT (with waiver) :                                                                     mi - minor      T-GOD       GMV          MMI - MMI
          manoeuvre in TGOD tool data
                                                 When adding a new manoeuver in Mission plan, via MMI, a new
                                                 manoeuuvre is added in tool data (Initial state) : OK
                                                 The start and end dates of the new manoeuvre in tool data are
                                                 equal to 01/01/1950 00h00.
                                                 The problem is that these dates can not be modified, because of
                                                 MMI warning ("manoeuvre overlapping").

                                                 by pass : creation of a MP with TEXT or modification in a local
                                                 CONF file.
83918       Input ephemeris and covariance files At STEP 10.3, it was asked to generate a TLE file from a Format          Oper - Oper     ETE 5.1                        mi - minor         T-ARC      GMV          Log - Software
            required though not needed to create #7 F7_NASA_MSG conjunction file.
            TLE from NASA Format 7               To execute, T-ARC also requires an ephemeris file and a
                                                 covariance-ephemeris file in FDB DATA, though the tool does not
                                                 use these dile in the computation.
83920       Second parameter "?" of sensor       At Step 6.1.b, in the ATV events output file used for Timeline, the      Oper - Oper     ETE 5.1                          mi - minor       T-OPF      GMV          Log - Software   CNES - 28/06/07
            dazzling events must be an empty     second parameter related to sensor dazzling events must be "" as                                                                                                                    Refusal not agreed :
            chain ""                             required in IDD specification.                                                                                                                                                      It is impossible for the operator to choose an empty
                                                                                                                                                                                                                                     string as the second parameter for the event.

83925       T-ORM : Wrong pop-up warning          After a nominal T-ORM execution,in Post-processing/Result              Oper - Oper      QO_RDV_N_1                       mi - minor       T-ORM      GMV          MMI - MMI
            message in post-processing            file/Mission Plan a wrong pop-up warning message is readable on
                                                  screen:
                                                  "Maneuver duration greater than thruster max duration"
83926       T-ORM : Import/Export Template        If Import a template without Mission Profile/Thruster ATV and if the Oper - Oper        QO-RDV-N-1                       Ma - Major       T-ORM      GMV          MMI - MMI
                                                  template contains data in the the thruster name field this data is not
                                                  loaded and is lost even if after the "Mission Profile/Thruster ATV "
                                                  is activated.

                                                   Implement an error message to award the user.
83927       T-OCF : Update of the maneuver         In Waiver mode, if a mission Plan is modified - for instance the       Oper - Oper     OQ-RDV-N-1                       Ma - Major       T-OCF      GMV          MMI - MMI
            duration                               Thruster type - the boost duration and max boost duration are not
                                                   updated.
83930       Erroneous display of forecast timeline in case of END events at the beginning of forecast time range or       Oper - Oper     QO_RVD_N_1                       mi - minor       T-OPF      GMV          Log - Software
            in Post-Processing window              BEGIN events at the end of time range, the associated forecast
                                                   display may be erroneous showing a continuous line as if the
                                                   forecast was the same on the entire time range.
83933       Using "Update dates" Button in TOPF Using the "update dates" Button in TOOL Data Parameters frame             Oper - Oper     QO_RVD_N_1                       mi - minor       T-OPF      GMV          Log - Software
            MMI                                    of TOPF MMI to adjust the opportunity calculation begin and end
                                                   simulation dates to the ones of the ISS Ephemeris file loaded in
                                                   FDB Data frame does not prevent anormal end of calculation.
                                                   Begin and end dates should be properly adjusted so that they are
                                                   inside the time range defined by the input ephemeris file.

                                                  Reference context :
                                                  Flight : Jules_Verne
                                                  Context : RVD_N1_4
                                                  Activity : EOP
                                                  Load config winRDV
                                                  Update dates then GO


83937       Creation of ATV ephemeris file from   During ETE 5.2 test, the process allowing to create the ATV                                                              Ma - Major       T-FDB      GMV
            F12 file                              epehemris file from F12 format provided by MCCH has been failed.

83938       Erroneous parameter for Artemis       The first parameter of Artemis visibility events in the events output   Oper - Oper     ETE 5.2                          mi - minor       T-OPF      GMV          Log - Software
            visibility related events             file created by TOPF must be "ARTEMIS" (uppercase) as required
                                                  by IDD.

                                                  Nota :
                                                  For this ETE 5.2 test, Artemis position were known through an
                                                  input Ephemeris file selected in the "FDB Data Ephemeris/SV"
                                                  Frame.
                                                  But the test must be run in batch mode (because of limitation AR
                                                  83608)
83939       Deorb: High value in out of plane     When computing OCF and detailed attitude information during          FDSVal - FDS       Step 2 of                        mi - minor       T-OCF      GMV          Log - Software
            accuracy                              deorbitation, out of plane accuracy values during the last OCF are Validation           FDS_FUNCT_FULL_REENTR
                                                  not inside expected thresholds. The maximum value obtained is 29                        Y_MISSION
                                                  degrees, which seems strange. It should be analysed if this value is
                                                  correctly computed.
                                                                                                                              14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          FDS 242000


                                                                                                                                                                                         Configuration  Entity in
Reference                Title                                                 Description                                     Phase             Context reference         Criticality       Item        charge                      Comments
83940     T-ORM: Synthetis File                  In the synthetic file, the maneuver data are given related to their      Oper - Oper                                      mi - minor      T-ORM       GMV          Log - Software
                                                 middle (time, aol), for operational simplication and robustness, it is
                                                 necessary to print them related to their beginning. Is it possible to
                                                 change the values (date, N, DO, aol) in the "synthetis file"?

                                                 Futhermore, the total burn mass is printed in the output file but is
                                                 not available in the synthetis file. Could you add this data below the
                                                 print of "Total DV" data?

83941      T-RDV: gap between archive files in   For test SVT-RDV-N-1 dry-run, two archive files has been created         Oper - Oper     SVT-RDV-N-1                      Ma - Major       T-RDV      GMV          Log - Software
           WS                                    during the 2-day test.
                                                 It is not possible to use T-RDV option Warm-start (error, when the
                                                 date of the WS is in the archive number 2.
83943      Forma of F3 files produced by T-FDB Some discrepencies on F#3 files produced by T-FDB have been                                                                 mi - minor       T-FDB      GMV
                                                 detected by MCCH :
                                                 - blank missing after the dates
                                                 - "Manoeuvre" is to be replaced by "Maneuver"
83945      Generation of ISS state vector during When T-FDB recovered from T-FDB the F13 file provided by                                                                  mi - minor       T-FDB      GMV
           F13 file covering                     MCCH , it should generate a SV ISS corresponding to the 1st
                                                 record (same behavior as for F9 covering).
83949      Allocate/Deallocate error in T-GNC    During the execution of T-GNC, if modify configuration and after                                                          Ma - Major       T-GNC      GMV          Log - Software
                                                 save configuration are pressed, often T-GNC crashes giving the
                                                 allocation error in attachment.
83954      None reference loaded for entity      When clicking "Load W/O", none reference is loaded for                   Oper - Oper     SVT_RDV                          mi - minor       T-OPF      GMV          MMI - MMI
           MP_SUNEPH                             MP_SUNEPH entity.
83960      Wrong identifiers in the flow status  The identifiers in the flow status for videometers and                   Oper - Oper     SVT_RDV                          mi - minor       T-VTG      GMV          Log - Software
           frame                                 telegoniometers are interchanged.

                                                 Activity:SYNCHRONISED
                                                 Config:nominal
83961      Imposible to run TVDA when there is   Imposible to run TVDA when there is no name for the ISS attitude         Oper - Oper     SVT_RDV                        mi - minor         T-VDA      GMV          Log - Software
           no name for the ISS attitude flow     flow.

                                                 Activity:SYNCHRONISED
                                                 Config:nominal
83962      Wrong frame identifiers in TVDA       Wrong identifiers of frames in RT_TVDA (all the identifiers are 0).      Oper - Oper     SVT_RDV                          mi - minor       T-VDA      GMV          Log - Software
           output flow
                                                 Activity:SYNCHRONISED
                                                 Config:nominal

83966      T-OPF: Unexpected end of execution TOPF tool stops in an uncontrolled way when half-lobe visibility is Test - Test             Free test                        Ma - Major       T-OPF      GMV          Log - Software
                                              requested and no antenna is defined.
                                              A message should be displayed to the operator and the tool should
                                              end in a controlled way
83968      Files tarc.param and               These files contain variables which should be available at MMI      Test - Test                                            mi - minor         T-ARC      GMV          Log - Software
           tarc_constant.param                level or are already considered in general libraries (ATSLIB).

                                                 All variables in tarc_constant.param are already available in
                                                 ATSLIB, therefore, this file should disappear and T-ARC should
                                                 use the corresponding variables in ATSLIB.

                                                 In tarc.param: variables "Time Step" and "Stage of planning"
                                                 should be available in TOOL DATA panel. The rest of variables
                                                 (quasi-constant, provided generally by a MP entity) can remain in
                                                 this file.
83970      TARC: TLE rejected file               The TLE rejection file is always empty. Furthermore, it's not         Test - Test        Free test                        mi - minor       T-ARC      GMV          Log - Software
                                                 available in the PP of TARC
83971      TARC: F7 file contents                The NORAD F7 file only contains the information for the last          Test - Test        Free                             mi - minor       T-ARC      GMV          Log - Software
                                                 danger interval while it should contain the data for all the detected
                                                 danger intervals
83975      T-OCF in ISS mode are checking        In T-OCF, When calculating an OCF vs ISS ephemeris ( Task 2900 Oper - Oper               SVT_RDV 2900 step 8            Ma - Major         T-OCF      GMV          Log - Software
           ATV ephemeris dates                   / step 8), ATV ephemeris begin and end dates dates are checked
                                                 and OCF building is refused if not in these dates. This is not
                                                 coorect: Only ISS ephemeris dates shall be tested and taken into
                                                 account in "Interval time sequence" dates.

83978      T-SAF started in the middle of a      In T-SAF, When the initial state vector ATV is a date after       Oper - Oper            SVT_RDV-5                      Ma - Major         T-SAF      GMV          Log - Software
           maneuver plan                         maneuvers defined in the mission plan, the calculation is
                                                 performed but results are not good. It is not known what kind of
                                                 maneuver is taken into account. If 2 maneuvres are defined before
                                                 the SV and 2 maneuvers are defined after, and that we define to
                                                 run T-SAF on 4 maneuvre smax, T-SAF gives results on 4 / 5
                                                 cases , which is not possible.
                                                                                                                              14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          FDS 242000


                                                                                                                                                                                         Configuration  Entity in
Reference                 Title                                                  Description                                Phase             Context reference            Criticality       Item        charge                      Comments
83984     T-SAF No alarm raised for entry in       Running T-SAF in Non real time, in SVT_RDV-5, configuration         Maint - Maint      SVT_RDV-5 RDV                  Ma - Major         T-SAF      GMV          Log - Software
          keep-out sphere                          safCLO, the maximum level of alarms raised is 0 but looking at the
                                                   plots safety2, there are trajectories entring in the KOS. It is
                                                   abnormal that there is no coherency between alarms and plots.
83994       T-RDV OnBoard Threshold                In T-RDV, Other FDB data panel , the OnBoard Threshold              Oper - Oper        SVT_RDV-5                      mi - minor         T-RDV      GMV          Log - Software
            Comparison W/O not correct             Comparison panel, even when W/O has been loaded (in the main
                                                   panel or locally in this panel) remains drak (and not blue ) as it
                                                   should be. When W/O has been loaded the fiorst time globally, it is
                                                   not sure that the W/O values in this sopecific panels are correct

84011       T-GOD Anomaly on output                In relative mode, when single differences are used, the ATV and        Other - Other                                  mi - minor         T-GOD      GMV          Log - Software
            covariance matrix in relative mode     ISS estimated parameters are correlated.
            with single differences                In the current version of T-GOD, the covariance matrix of ODRES
                                                   entities produced by T-GOD contains 0 for the ATV/ISS corelation
                                                   elements.

                                                   I.Llamas analysis has stated that the covariance matrix is correctly
                                                   computed and used in the filtering process and that the anomaly
                                                   concerns only the output entities of T-GOD. T

84022       bad computation of boost duration in   The computation of MSU_BOOST_MON_DURATION_SET of                                                                      Ma - Major         T-FDB      GMV          Log - Software
            TC MSU_TABLE_INTERFACE                 FDCET_MSU_TABLE_INTERFACE TC generated in phase S-1
            generation                             uses the duration value of manoeuver included in the mission plan
                                                   instead of the tout_date value.
                                                   Indeed, the computation must be :
                                                   MSU_BOOST_MON_DURATION_SET =
                                                   GNC_MAX_BOOST_LEN_SOC + Delta_T2.
                                                   with GNC_MAX_BOOST_LEN_SOC = tout_date of mission_plan


84023       T-RDV NRT (Warm Start) and RT:         Within SVT_RDV_JV-5 test                                               Oper - Oper     SVT-RDV-5                      C - Critical       T-RDV      GMV          Log - Software
            Incoherent TM gap(Gap type 3)          (Serveur:DIONE/Vol:Jules_Verne/Contexte:SVT_RDV_5), T-RDV
            detection                              NRT (warm start) and RT detects non-existent gaps (GAP Type 3)
                                                   on
                                                   ATV_GES flow.

                                                   1 :*** ERROR: (RDV_obtain_GES)
                                                   -> Gap type 3 ATV_GES_FLOW TM reception data is not received
                                                   in 10 multiple time
                                                   Time = 10 (error code : RDV_REC_GAP3_FLOW_ERR)
                                                   Jun 14 08:29:16 TOOL-messages
                                                   1 :*** ERROR: (RDV_obtain_GES)
                                                   -> Gap type 3 ATV_GES_FLOW TM reception data is not received
                                                   in 10 multiple time
                                                   Time = 20 (error code : RDV_REC_GAP3_FLOW_ERR)
                                                   Jun 14 08:29:16 TOOL-messages
                                                   1 :*** ERROR: (RDV_obtain_GES)
                                                   -> Gap type 3 ATV_GES_FLOW TM reception data is not received
                                                   in 10 multiple time
                                                   Time = 30 (error code : RDV_REC_GAP3_FLOW_ERR)
                                                   till warm start date.

                                                   The test associated to requirement SW_TRDV_2461 and
                                                   SW_TRDV_2461_01 (see T-RDV software specification 2.4 and
                                                   OPS-RfC-242552-81545-CNES) led to this anomaly:



                                                   Module rdv_tm_mod.F90
                                                   ------------------------

                                                   ! Value nedded to compared real numbers
84024       TGNC: Gap in DV plot                   TGNC doesn't display the whole sequence of TRDV boosts. It only FDSVal - FDS           E_FAR                          mi - minor         T-GNC      GMV          Log - Software
                                                   displays the closing boosts while a gap during all the homing is Validation
                                                   present, though the TRDV RT flow has been tested to contain the
                                                   8 boosts.


                                                   Context: FDS_Val_link/E_FAR
                                                   Activity: FDIVal
                                                   Config: BUP_RP_DV_GNCGUI
                                                                                                                           14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          FDS 242000


                                                                                                                                                                                      Configuration  Entity in
Reference               Title                                            Description                                       Phase           Context reference            Criticality       Item        charge                      Comments
84025     T-RDV RT : Anomalies on behavior of During FDS Monitoring Operational Threshold Assessment                  Other - Other    FMOTA studies                  Ma - Major         T-RDV      GMV          Log - Software
          some parameters in T-RDV Output     (FMOTA) analysis based on TM issued from 1100 trajectories
          flow                                delivered by Astrium as LFN3 FES V10 campaign, we found (with
                                              Carlos Casas-Cuadrado) some anomalies on T-RDV Real Time
                                              output flow.

                                               * First anomaly(See attached file Anomaly_1_T-RDV_FMOTA.pdf):
                                               Components of commanded thrust N°1 issued from TM
                                               (TmCmdThrustComp[1][-]) does not remain constant after the end
                                               of the boost in some test cases (Example for trajectory n° 22).

                                               * Second anomaly(See attached file Anomaly_1_T-
                                               RDV_FMOTA.pdf): At S2SK beginning, components of
                                               commanded thrust N°1 issued from T-RDV (GesThrustComp[1][-
                                               ]parameter computed by GES) reaches strange values in some test
                                               cases (Example for trajectory n° 22).

                                               Inputs T-RDV data (TM, flow, configuration file, ...) associated to
                                               this test (Trajectory n°22) are given in attached file
                                               TEST_0022_T_RDV_FMOTA.zip.

84027      T-RDV RT: Strange behavior of T-    During FDS Monitoring Operational Threshold Assessment                 Other - Other    FMOTA studies                  Ma - Major         T-RDV      GMV          Log - Software
           RDV(GES) vs Onboard TM              (FMOTA) analysis based on TM issued from 1100 trajectories
           comparison algorithm                delivered by Astrium as LFN3 FES V10 campaign, we found (with
                                               Carlos Casas-Cuadrado) some strange behavior of T-RDV(GES)
                                               vs Onboard TM comparison algorithm. This algorithm is specified in
                                               RfC (OPS-RfC-242552-81545-CNES): "Robustness to TM de-
                                               synchronized packets and TM outage phases":
                                               - Isolated point for which comparison gives result upper thresholds
                                               should be deleted in the process comparison,
                                               - In the beginning of boundary, the first point and all its conscutive
                                               points, that are upper the threshold , should be deleted if the firts
                                               point is upper than the thresholds,
                                               - At the end boundary, the two last points are deleted if they are
                                               upper than thresholds.

                                               Some results (See attached file Anomaly_2_T-RDV_FMOTA.pdf )
                                               obtained during FMOTA studies show that these requirements are
                                               not always correctly implemented.

                                               Inputs T-RDV data (TM, flow, configuration file, ...) associated to
                                               this test (Trajectories n°6, n°22 and n° 319) are given in attached
                                               files TEST_0006_T_RDV_FMOTA.zip,
                                               TEST_0022_T_RDV_FMOTA.zip,
84032      Problem with the MSU LOF            When the date of the quaternion in the panel "MSU LOF                                                                  Ma - Major         T-OCF      GMV          Log - Software
           quaternion                          quaternion" is lower than the beginning date of the ATV ephemeris,
                                               the quaternion in the monitoring file in equal to [0,0,0,0] because
                                               there's no propagation.

                                               The quaternion must not be equal to 0, as it deals to a core dump
                                               in the functionnality that used the monitoring file where the
                                               quaternion is normalized. Used the valeu [1,0,0,0] instead.
84035      TGNC: Cummulated DV end when        The reset to zero after the end of manoeuvre for the cummulated        FDSVal - FDS     E_OCS                          mi - minor         T-GNC      GMV          Log - Software
           using MP data                       DV does not consider correctly the change in the GNC global            Validation
                                               mode. It appears to ignore the transition from BCM to SLW.

                                               In the GNC_CUM_DV can be observed that the ATV_CONTROL
                                               derived parameter is correctly reset to 0 while the same parameter
                                               derived in the MP is not reset until the following mode change.

                                               Investigation should be started in the function
                                               "GNC_current_global_mode_changed" to verify that it does
                                               correctly inform the caller function about the mode change.


                                               Flight/Context: FDS_Val_link/E_OCS
                                               Activity: FDIVal
                                               Config: DV_DYNAW_mp

84038      TGNC: Xtrace stdout                 Xtrace output is not correctly redirected in TGNC. It appears in the   Test - Test                                     mi - minor         T-GNC      GMV          MMI - MMI
                                               standard output unit instead of being included in the .tmpXtrace
                                               output file.
                                                                                                                         14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                                  FDS 242000


                                                                                                                                                                                    Configuration  Entity in
Reference                 Title                                          Description                                  Phase              Context reference            Criticality       Item        charge                                 Comments
84042     Manoeuvre detection not consistent     When the T-ACC MMI tuning is defined for manoeuvre detection as Oper - Oper         SVT_RDV_JV-5                   mi - minor         T-ACC      GMV          Log - Software
          with MMI tuning                        follows :

                                                 0.00001m/s for the DV threshold of thrusters,
                                                 1 for the occurrence number of a manoeuvre start,
                                                 1 for the occurrence number of a manoeuvre end,

                                                 the T-ACC software does not detect small manoeuvres (DV norm >
                                                 threshold) with null duration. Why ?

                                                 According to the reason for this behaviour, the T-ACC software will
                                                 :
                                                 - Choice 1 : detect small manoeuvres even with null duration when
                                                 the occurrence number for a manoeuvre start is 1,

                                                 - Choice 2 : if the development for choice 1 is not easily consistent
                                                 with the current T-ACC release V5.0, then the MMI should forbid
                                                 the use of "1" as value for the tuning of "the occurrence number for
                                                 a manoeuvre start".

                                                 In any case, the reason for not choosing the solution no1 should be
                                                 justified.

                                                 Configuration file :
                                                 CONFIG.TACC.13062007_125928.SYNCHRONISED.houllierc.Pos
                                                 t_analyse

                                                 Moreover, when using the tuning of (1;1) for detection occurrences,
                                                 incessant warning messages are sent in the log window :
                                                 "Problem in T-ACC process : sending data to RT_TACC
                                                 warning code : ACC_FORCE_WRITER_WAR"

84057      Wrong gap detection in T-RDV "warm- During the test QO-RDV-N1_6 (15/06/07), it was impossible to use Oper - Oper          QO-RDV-N1-6                    C - Critical       T-RDV      GMV          Log - Software
           start"                              T-RDV mode warm-start. Software detects TM gap from the
                                               beginning to the end (see in DIONE/Jules-verne/QO-RDV-N1_6 file
                                               exelog N°7 (date 01/05/06 creation date 6h50m34s).
                                               The re-do (see file trahHOM_ws in DIONE/Jules-verne/QO-RDV-
                                               N1_6) does not show the same behavior. The results seem to be
                                               right.
                                               It seems that the software does not do the same check during
                                               operation (open archiv file) and after (close archiv file).
84060      Wrong display of beta angle         Wrong display of beta angle constraint in mode opportunity: A         Oper - Oper     OQ_RDV_N_1                     mi - minor         T-OPF      GMV          Log - Software
           constraint in mode opportunity      continuous line is expected from beginning to end of execution due
                                               to the beta angle constraint is fulfilled in all the interval;
                                               nevertheless there is no line. The problem is only at plot level. The
                                               opportunity window is properly computed.

                                                 Activity: TIF_PHASING
                                                 Config: opp
84064      Rotation and Attitude angles wrong    The following abnormal behaviour appears when running TOCF in                                                      Ma - Major         T-OCF      GMV          Log - Software   In the aim to test this behaviour, a folder is created
           computation in T-OCF mode 3           mode 3 "ATTITUDE ONLY":                                                                                                                                                        containing the CONF and the outputs files of a run
                                                 Any computation of attitude angles (Euler angles format) and                                                                                                                   producing the above described behavior. The folder
                                                 rotation angles of OCF around a dedicated reference frame,                                                                                                                     name's MA_04_00_Case3_C2_OCFvsRealTraj.
                                                 presents some errors.                                                                                                                                                          FDB Server used: Dione
                                                 These errors are source of bad interpretation of some results                                                                                                                  Flight: Jules Verne
                                                 during tests (QT, QO, SVT, Dry Run). The output files that are                                                                                                                 Context: SVT_RDV_4
                                                 certainly affected by these errors are : OCF_LOF, OCF_MOOF,                                                                                                                    Activity:DRAFT
                                                 OCF_MLVLH, OCF_LVLH, and the following ones may have been
                                                 affected too : ATT_ACC_OCF, ATT_OCF, ATT_SUM, ATV_EPH,
                                                 OCF_ATV_EPH, OCF_MONIT_EPH, LOF_MSULOF, ATT_LOF,
                                                 ATT_MOOF, ATT_MLVLH, ATT_LVLH.
                                                                                                                            14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          FDS 242000


                                                                                                                                                                                       Configuration  Entity in
Reference                Title                                               Description                                  Phase             Context reference            Criticality       Item        charge                      Comments
84065     Crash of TACC with catchup mode        Activity: SYNCHRONISED                                              Oper - Oper        QO_RDV_N_1-6                   Ma - Major         T-ACC      GMV          Log - Software
                                                 CONF file: estim_CLO_seq
                                                 FDS simulated time : 01/05/2007 07h18m
                                                 Description of the problem:
                                                 Actions and what have been observed are:
                                                 - Catchup at 4h48
                                                 - Press Go (FDS simulated time about 7h18m)
                                                 - In catchup all seems ok
                                                 - When FDS time is reached, the following message appears
                                                 continuously: "Not real TM gap : delay only detected at FDB level".
                                                 - If we compare epoch in "Alphanumeric output" panel (TM epoch)
                                                 with FDS time,TM epoch is in advance of 2 second with respect to
                                                 FDS epoch.
                                                 - When press Stop, no "Nominal end" message and the process
                                                 died with a core dump.
                                                 - The core dump file can be seen in directory /var/core/



84089      Incorrect date in ATV_VDM TM          TM Packet in ATV_VDM flow is incorrectly dated. This can be           Oper - Oper      IAT_24 (Plan TM FF3)           mi - minor      FDB_SERVER GMV             Log - Software
           package                               appreciated directly in T-VTG tool, where a message of
                                                 unexpected frecquency appears (it should be of 2 seconds).

                                                 The reason of this problem is that all the parameters of the
                                                 ATV_VDM flow are received each 2 seconds except the
                                                 parameters VDM1_TTRA_ROLLIN_MEAS and
                                                 VDM2_TTRA_ROLLIN_MEAS, that are received each second. This
                                                 provoques that the TM Packets of the flow are separated 1 second
                                                 and 3 seconds alternatively.

                                                 Solution should be analysed in supervision configuration file or in
                                                 FDB_SERVER.
84090      Alarms raising in T-SAF RT            During the last part of closing (FAR RdV), sometimes T-SAF            Test - Test      OQ_RDV_N1-6                    C - Critical       T-SAF      GMV          Log - Software
                                                 printed in the process output a result like this one:

                                                 Epoch of current update: 01/05/2007 06h34m12s587
                                                 Single security check in progress...
                                                 Computation of relative ephemeris
                                                 CD dispersed trajectories computation
                                                 Computation of trajectories with dispersion on initial SV
                                                 Propagation of the covariance matrix
                                                 ISS safety check
                                                 Single security check completed
                                                 Minimum distance from ATV body to ISS security volume :
                                                 0.113456761380733E+03 (m)
                                                 Date for minimum distance : 01/05/2007 06h39m42s587
                                                 Distance ATV position error ellipsoid to ISS security volume :
                                                 0.000000000000000E+00 (m)
                                                 No alarms raised
                                                 Epoch of next update: 01/05/2007 06h36m12s587
                                                 Nominal end of the computation


                                                 One can see that ATV-KOS distance is 0.00 (like when there is
                                                 entrance in the KOS) but no alarms are raised. This shows an
                                                 anomaly in the calculation or in the alarm generation function. This
                                                 misbehaviour happened a lot of times during the same test.
84092      Temporary files and post-processing   When running T-ACC, in the temporary directory of the process        Oper - Oper       SVT_RDV_5                      mi - minor         T-ACC      GMV          Log - Software
           files are inverted                    number, files .CONF, .acca_dv, ... are all inverted: they do not
                                                 contain the information they are expected to.

                                               When we stop the tool, displays in the post-processing are correct
                                               for the current run. But when we load some previous results in the
                                               post-processing, displays are not correct for the Thr DV in GATV
                                               and the Thr DV in OCF.
84095      TGOD: End of ephemeris file reading The reading of the ephemeris file in LSM mode is not correctly          Test - Test      Free test                      Ma - Major         T-GOD      GMV          Log - Software
           in LSM mode                         ended since the validity flag in this kind of measurements is not
                                               correctly managed.

84099      T-EXT process output nb of orbit      In T-EXT relative mode, when a calculation is performed, in the     Oper - Oper        SMA4                           mi - minor         T-EXT      GMV          MMI - MMI
           limited                               process output window, the ISS number of orbit at equator crossing
                                                 date is not appearing correctly due to its limitation to max 999 (3
                                                 digits): To be extended to 4 digits.
                                                                                                                               14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          FDS 242000


                                                                                                                                                                                          Configuration  Entity in
Reference                 Title                                                Description                                   Phase             Context reference            Criticality       Item        charge                      Comments
84103     T-EXT: Tool data / Mission events        In T-EXT , for TRAJ_DD123 generation of post-escape 1 in ATV-        Oper - Oper        Generation of SMA4             Ma - Major         T-EXT      GMV          Log - Software
          second reference event label always      CC Back-up, 2 reference events have been defined in tool data.
          to "OD"                                  The second reference event label in the output ATV event file is
                                                   always "OD", whatever the input label name is given. (Activity Post-
                                                   Escape1: T-EXT template : Intial_PE1 and Initial_PE1_contourne )
                                                   The first and third Reference event label have a correct name. Not
                                                   the second.

84104      T-EXT : Warning to add: State vector    In T-EXT, when a initial state vector is loaded, it has a daily orbit   Oper - Oper                                    Ma - Major         T-EXT      GMV          Log - Software
           daily orbit number consistency          number loaded at the same time. This daily orbit number may not
           between input data and T-EXT            be consistent with the real value calculated by T-EXT itself, but it is
           calculated daily orbit number           the one taken into account in the further calculation. A warning pop-
                                                   up window shall appear if the daily orbit number in the initial state
                                                   vector is different of the one calculated by T-EXT at the first
                                                   propagation step.
84105      T-EXT : Tool data, mission events,      In T-EXT, Tool data, mission events panel, for SMA4 generation , Other - Other          Generation of SMA4             Ma - Major         T-EXT      GMV          Log - Software
           adding or removing events do not        in phasing and post-escape generation , the template are:
           update the other relative events        Initial_PHA and Initial_PE1. When an event is added or removed,
                                                   the following events refering to other events are not updated. If the
                                                   event 1 is removed and that the event 2 is refering to the event 3,
                                                   then after removing event 1, event become event 1 but is still
                                                   refering to event 3 which is not the right one anymore. Same thing
                                                   when adding events....

84114      Wrong Daily orbit number                Load configuration and results "PHA" in                                 Prep - Prep     TRAJ-DD123                     mi - minor         T-EXT      GMV          Log - Software
                                                   fbb1/JulesVerne/TRAJ_DD123.
                                                   Launch date mode.
                                                   The Daily orbit of the initial ATV state vector is wrong 1 insted of 4.

84118      Wrong MP - attitude plan                In context RDV2.                                                        Prep - Prep     TRAJ_DD123                     Ma - Major         T-OCF      GMV          MMI - MMI
                                                   Load MP from RDV1 then click ATTitude law number 3.
                                                   Then load MP from context PHASING, the previous attitude
                                                   number 3 is still active, The software is not able to load the attitude
                                                   plan. There is no warning message.
84119      Problem of ocf discontinuity            In context RDV2 an ocf is calculated (conf ocfRDV2) Th                  Prep - Prep     TRAJ_DD123                     Ma - Major         T-OCF      GMV          Log - Software
           calculation                             discontinuity compared to the loaded onboard OCF is null. This
                                                   result is wrong.
84120      Order of the incoming gyro              The TM parameter GYRA_RATE_MEAS_DER contains the                                                                       Ma - Major         T-ATT      GMV          Log - Software
           measurements                            measurements of the four gyros. The M&C delivers them in the
                                                   order XYXYXYXY, whereas T-ATT expects them in the order
                                                   XXXXYYYY. Either T-ATT or the packeting function shall be
                                                   modified for coherence.
84121      Irregularity on the arrival date of STR The arrival frequency of STR measurements is even most of the                                                          Ma - Major         T-ATT      GMV          Log - Software
           measurements                            time, but it shows some irregularities from time to time. Thus, the
                                                   way in which the STR TM packets are dated shall be carefully
                                                   looked into.
84122      Yaw discontinuity during the slew.      On the "Slew Man Attitude plot 01" we can see a discontinuity on        Oper - Oper     OQ_OCS_N_1                     mi - minor         T-OCF      GMV          Log - Software
                                                   the "OCF Yaw Angle" plot. This discontinuity is about 0.5°, 11.5
                                                   seconds after the beginning of the plot.

                                                  Flght : Jules Verne
                                                  Context : OQ_OCS_N_1
                                                  Activity : TP_PHASING
                                                  Conf : ephemTP
84123      Time of application of STR innovation When a STR measurement arrives, the innovation is calculated at                                                          mi - minor         T-ATT      GMV          Log - Software
                                                  the arrival time with respect to the attitude predicted with the last
                                                  gyro measurement propagated until that date. But then T-ATT
                                                  applies this innovation to update the attitude at the arrival time of
                                                  the STR measurement and outputs this updated attitude. As the
                                                  STR TM arrival date can fluctuate, and in order to have a more
                                                  regular output, the update shall be synchronised with the 5th gyro
                                                  measurement of the cycle, even if the innovation does not
                                                  correspond exactly to that date.
84124      Estimated drift jumps on sensor filter When there is a reset on one of the sensor filters, a peak appears                                                      mi - minor         T-ATT      GMV          Log - Software
           reset                                  on the estimated drift. This estimate and its covariance should
                                                  remain constant during sensor filter resets.
84125      No warning while Main Event is         At step 8 of PreLaunch FDSN0000 procedure, the main event (the Prep - Prep               TRAJ_DD123                     Ma - Major         T-OPF      GMV          Log - Software
           outside the opportunity range          beginning of ESCAPE manoeuver of Demo Day 1) is defined 11
                                                  min before the end of Russian Ground Stations visibility and
                                                  opportunity is constrained with a 20 min-long RGS visibility and
                                                  offset of 11 min (ie. date inside opp. window if RGS visibility ends
                                                  11 minutes after this date).
                                                  TOPF computation sets the main event just one time step after the
                                                  end of the opportunity window. A warning should have been raised
                                                  to inform the operator.
                                                                                                                         14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                          FDS 242000


                                                                                                                                                                                    Configuration  Entity in
Reference                 Title                                             Description                                Phase             Context reference            Criticality       Item        charge                      Comments
84126     Wrong format for ISS orbit number in The orbit number format in TOPF output ATVISS_EVENTS file is       Prep - Prep        TRAJ_DD123                     Ma - Major         T-OPF      GMV          Log - Software
          output ATVISS_EVENTS file            erroneous causing the loss of information when the ISS orbit
                                               exceeds 1000.
                                               See Opp_DAY1 result files under activity OPP_DAY1 (Jules_Verne
                                               Flight/TRAJ_DD123 context) for step 8 of FDSN0000.
                                               As a result, both eclipse and opportunity flags (col 6 & 7) in the
                                               output ISS position file are always 0.
                                               This seems to be the reason why the Post-Processing tool does
                                               not display "Timeline for constraints" nor "Constraints on
                                               Planisphere" plot.

                                                 Rq: ATV orbit number format must also be checked in the frame of
                                                 this correction.

84128       T-EXT Event defined in rel N,aol (0,0) in test DOQ-DD2, For generation of events in T-EXT,in phasing, an Oper - Oper                                    Ma - Major         T-EXT      GMV          Log - Software
            not well positionned                   event TIF E_CHPH defined in reference to S-1/2 , in N,aol N=0 and
                                                   aol=0, is not at the right place in the ouptput event file. If we put the
                                                   refernce event in relative date, the anomaly does not occur.
                                                                                                  14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                     DG 243000

                                                                                                                                                         Context                   Configurati    Entity in
Reference                     Title                                                 Description                                            Phase        reference    Criticality    on Item        charge                Comments
                                                       On DG, when opening the webmaster administration window, many error
                                                       messages appeared “font specified in font.properties not found”.(print
                                                       screen FApolice.bmp to add).                                                    SysVal -
          Error while opening DG administrator                                                                                         System
    82886 window                                       The MMI works correctly without this font.                                      Validation      VALT-1.E     mi - minor                   THALES
                                                       A transfer rule for systematic TC histo that should be executed every 60s
                                                       hasn‟t been executed for 2 hours (from17/11/2006 09:22 to 17/11/2006
                                                       10:53). We should trigger manually this rule.
                                                       jpg files show some logs :
                                                       - FA_rules17112006_1 show all system archive corresponding to
                                                       configuration change.
                                                       - FA_rules17112006_2 show WEB TREND ANALYSIS
                                                       DG_WEB_TC_HISTORIES rules.
                                                       - FA_rules17112006_3 show all TCH files putted by ftp by M&C.                   SysVal -
          Problem of transfer rule for systematic TC   - FA_rules17112006_4 show activation of the rules                               System
    82887 histo                                        "Bouchon_Systematic_Analysis                                                    Validation      VALT-1.E     mi - minor                   THALES
                                                       We define a set of TM Packet request. After a while, the
                                                       TA_Result_xxx.xml arrive in the result directory. Then the DataGateway
                                                       wait for the TA_Result_xxx.txt file.
                                                       When this file arrive, the Data Gateway rename txt and xml file and
                                                       transfer the txt file to the user's directory.
                                                       After this transfer, an alarme is raised because the TA_Result_709.xml          SysVal -
                                                       can't be renamed neither scanned by sophos. This file is already renamed        System
    82888 Problem of sophos activation                 and used by the datagateway.                                                    Validation      VALT 1 E     mi - minor                   THALES
                                                       After a password change using the administrator console for the MCCM
                                                       account, then the contents of the dropbox is deleted.
                                                       This problem occurs for all external users (with or without dropbox) if we
                                                       change the password using the administration console (without any other
                                                       change on this account).
          Contents of the drop box deleted after a     If we use the Web commande to change the password, the contents of
    82944 password change                              the drop box is not deleted.                                                    Oper - Oper     ETE 5.1      mi - minor                   THALES
                                                       After a creation account, we stop and restart tomcat.
                                                       After this, the web site displays an error with the mysql database.
                                                       We try to stop tomcat and check with a ps command. The tomcat (java)
    82945 Impossible to stop tomcat                    process is not stopped.                                                         Oper - Oper     ETE 5.1      mi - minor                   THALES
                                                       1 - One user starts the administration console (ADM_Lancer.sh)
                                                       2- A second user starts a logbook console (ADM_Lancer.sh jdb)
                                                       3- The first user closes its administration console and tries to open it once
                                                       again.
          Impossible to open the administration        4 - message is diplayed : Impossible to start ADM because the second
    82949 consol                                       user hasalready started it.                                                     Maint - Maint                mi - minor                   THALES
                                                       1 - We create a new ftp login. This ftp login is not a site definition.
                                                       2 - We modified the ftp acess as described on the documentation.
                                                       3 - We create a new account using the administration interface.
                                                       4 - Our modification on the ftp access file are lost. Impossible to use this
    82950 ftp acces file modified by DataGateway       ftp login.                                                                      Maint - Maint                mi - minor                   THALES       Workaround available
                                                       To get a file from an external user, a user define twice the same request
                                                       on the Web interface and validate this request.
                                                       The external user is a user with a local dropbox.
                                                       On the log, we can see :
                                                       1 - the second request is done corectly.
                                                       2 - the first request start (copy the same file)
                                                       3 - at the end of the second request, the source file is deleted
                                                       4 - the first request is stopped with an error : "Impossible to rename file"
                                                       and "Anti-virus failed"
                                                       The source file is deleted and destination is corrupted (partially write by
    82976 File corrupted during a transfert            the first request).                                                                                          mi - minor                   THALES
                                                                                                    14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                   DG 243000

                                                                                                                                                       Context                   Configurati    Entity in
Reference                      Title                                                    Description                                        Phase      reference    Criticality    on Item        charge                 Comments

                                                         One user need to send to the webmaster an SOE file to display on the
                                                         WEB site below the menu planning.
                                                         It's not possible to define the complete name of this file (with the naming
    82985 Impossible to define a complete filename       convention defined on the interface). The field name is too short.            Test - Test                mi - minor                   THALES
                                                         When we use the stop_Mysql command, a password is requested. This
    82986 Enciphered password displayed                  password is directly show at screen.                                                                     mi - minor                   THALES
          Impossible to export system archive to the     After a site modification, the Data Gateway tries to export the System
    82988 backup data gateway                            Archive to DG backup but the ftp connection fails.                                                       mi - minor                   THALES
                                                                                                                                                                                                            DG V3.01 du 01/08/06: Anomalie
                                                         After using the "SD_Arreter.sh" script from a directory different than                                                                             partiellement résolue par l'issue
                                                         shells, some error messages appear :                                                                                                               V3.01 pour le script " SD_Arreter"
          Error message after using the                  "cannot access parent directories / ....../ stopping SDcannot access                                                                               mais persistante pour le script
    82989 SD_Arreter.sh script                           parent directories/cannot access parent directories / SD stopped.            Accep - Accep               mi - minor                   THALES       "SA_Arreter"
                                                         On the xml file, the field "APID" is missing. If we save a TM packet
                                                         request with a value defined for the "apis". The apid value is never sent to
    82990 Apid field is missing and not saved            the monitor and control nor saved.                                           Accep - Accep               mi - minor                   THALES
                                                         Some password can be defined but are not correct for the web
                                                         connection. In this case, after the change : The user can use the ftp
                                                         connection but after typing his password on the web page, a second
                                                         password is necessary.
                                                         At least, this problem occur with password ended by “*” and defined by
                                                         the administrator interface (same password defined by the web interface
                                                         works).
                                                         A specific password “=^$ù*<” does not works AND broken the link with the
                                                         mysql instance. To restart correctly, it was necessary to start the software                                                                       This only can happen on
                                                         without tomcat, kill the account defined with this password and stop/start                                                                         administration console. Low
    82991 Incorrect password fot the web server          the software.                                                                                            mi - minor                   THALES       probability
                                                         After selection of the menu : Product/Systematic Analysis/TM
                                                         Parameter/Previous, we click on the "Download" link of one result.
          Wrong file size indicated in the results       The Size field on the new windows is always "1 ko" and not the real file
    83006 "dowload" window                               size.                                                                                                    mi - minor                   THALES
                                                         When we scan a big zip file (65 Mo), the Data Gateway raised a warning
                                                         “Anti-virus scanning failed”.
                                                         When we used the “scan.sh” manually, the error indicate the file may be a
                                                         “zip bomb”.
                                                         If we try to send the file directly without zip compression (The file is a
                                                         binary TM file), sophos still indicate a “zip bomb”.
    83007 Impossible to scan a binary file               With the ROC anti-virus tool, this file does not contain any virus.                                      mi - minor                   THALES

                                                         Some anti-virus scan may be impossible.
                                                         In this case, the message is: "Anti-virus scanning path/filename failed".
                                                         This message can correspond to two different things:
                                                         - File is corrupted.
                                                         - File appears to be a "zip" bomb.
    83012 iInsufisant detail on a logbook.               This detail is necessary to define the correct action.                                                   mi - minor                   THALES

                                                         A file was put on a DropBox (account EST_GKON, directory
                                                         TEST/FROM_GKON/ARCHIVE).
                                                         A periodic transfert rule try to send this file to another user.
                                                         Despite the "." at the begining, the DG scan this file.
                                                         As the file is corrupted, the DG raise an alarme and add a ".".
                                                         The new name is "..name".
          DG scan a file with "." at the begining of the Each time the transfert rule start, the DG raise an alarme and add a ".".
    83237 name                                           The filename is "...name", "....name " ....                                                              mi - minor                   THALES
                                                                                                   14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                     DG 243000

                                                                                                                                                        Context                   Configurati    Entity in
Reference                      Title                                                    Description                                        Phase       reference    Criticality    on Item        charge                Comments
                                                       To use the DataGateway with several M&C server, we create an account
                                                       by M&C server (dgreq_Servername).
                                                       To use the web request mechanism, we define an automatic rules (each
                                                       50 seconde). This rule get all files from the Request directory and send
                                                       files to dgreq_Servername/IN.
                                                       A second rules get files from dgreq_Servername/OUT to put on Result
                                                       directory.
                                                       After defining a set of TM parameter request from the web interface, the
                                                       DG create 15 request files on the Request directory.
                                                       After the execution of the rule, files are transfered to dgreq_Servername
                                                       except three of them.
                                                       We try to force a new execution but these 3 files are never send to
                                                       dgreq_Servername.
                                                       After a touch on these 3 files, the rule can transfer all files.                Integ -
    83239 File not transferred by a systematic rules   All files are received during the same second.                                  Integration                 mi - minor                   THALES

                                                       On WeB DG, we defined a request (TC Request) with a result filename
                                                       containing some specific characters
                                                       (RQBas_TC_PostCont_/?<Rejected_16 ), at the execution we obtained
                                                       the following message :
                                                       „Data request servlet, anomally detected : java.io.FileNotFoundException:
                                                       /home/tomcat/tomcathome/webapps/ATV_DG/WZ/ToSE/AnalysisRequest
                                                       s/.TA,donadieuj,18012007,163405,test,RQBas_TC_PostCont_/?<
    83251 Incorrect filename for a TM/TC request       maintenance your contact please directory), or file such (No>”                                              mi - minor                   THALES

                                                       During the creation of a new TM/TC request, we define a long name for
                                                       the request name and the result file name (40 character for each).
                                                       When the DG receive the result file from DH, DG raise an alarme :
                                                       Action ImportSynchrone : File or directory does not exist on SA or or
                                                       remote site fo file TA,user,date,heure,name_of_request_name_of_result.
                                                       A new alarme is raise after each execution of the                      Integ -                                                                        Continous alarm is raised on DG
    83253 File Too long on a TM/TC request             WEB_DG_DATA_REQUEST rules.                                             Integration                          mi - minor                   THALES       admin console

                                                       Using the web interface, we make a get request from the directory
                                                       mcch/simulation/planning.
                                                       This directory contains three sub-directory : dly,ostp,stp.
          DG try to get sub-deirectory after a web     The DG raise an alarme because thoses File or directory does not exist.
    83385 request                                      It seems that the DG try to get directories.                                     Test - Test   ETE 5.1      mi - minor                   THALES
                                                       For a TC history result: TA_Result_927.xml, DG is in alarm with the
                                                       message: “anti virus scanning failed” there isn‟t reason for this alarm
                                                       raised because the file was correctly put with “.‟ In front of filename. In
                                                       spite of the alarm, the file has been transmitted to the DG user. TC history
    83582 abnormal anti virus failed                   result: TA_Result_943.xml is in same case.                                                                  mi - minor                   THALES
                                                       SD process is down after receiving a TA_Result_969.xml.
          SD process is down after receiving           This TA_result contain an error message from DH but the xml file seems                                                                                Cas de double erreur : 1 côté
    83584 TA_Result                                    to be well formed.                                                                                          Ma - Major                   THALES       Datahandling + 1 côté DG
                                                       dgb1 in nominal. After switch the configuration is not the good one, port
                                                       8443 instead of 8088.
                                                       The port number was changed to avoid an IGS reconfiguration. This
                                                       change was done only on the active data gateway.
          uncorrect web port number after a switch     We must check if this configuration is saved on the web archive or if we
    83585 DG nominal to backup                         need an rfc to change the port number.                                                                      mi - minor                   THALES
                                                       For TC history result: TA_Result_931.xml DG raises an alarm: “impossible
                                                       to read content of data result header file”. In spite of the alarm, the file has
    83603 impossible to read content                   been transmitted to the DG user.                                                                            mi - minor                   THALES
                                                       Problem after an activation of the rules
                                                       SIMULATION_ISS_ORBIT_EPHEM_MCCH
                                                       Message from DG „The directory in/iss/eph doesn‟t exist in internal zone.
                                                       Error while transferring internal zone„
                                                       - After deleting the rule, and re-creating the rule, it is OK => Action XF to
    83904 Error transferring a file                    open an AR                                                                                                                               THALES
                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                 DG 243000

                                                                                                                                             Context                   Configurati    Entity in
Reference                   Title                                                   Description                                   Phase     reference    Criticality    on Item        charge     Comments
                                                     When we try to start the webmaster consol, we receive a java error and
                                                     the application is frozen.
                                                     This problem occurs only using cygwin from an OAW with a display
                                                     configured with Hih Color (16 bit).
                                                     With cywin and a diplay at "True Color (32 bit), it works.
                                                     The 16 bit mode was chossen to try to correct another anomaly with
                                                     cygwin : Sometimes, the screen is frozen.
    84033 Java error openning the webmaster consol   With Exceed it work at 16 or 32 bit.                                     Test - Test   RVD         mi - minor                   THALES
                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                    VOICE&VIDEO 244000

                                                                                                                                         Context                 Configurati Entity in
Reference                Title                                              Description                                        Phase    reference    Criticality   on Item    charge       Comments
     10334 VOICE RECORDER REINSTALL FAILED This morning, there were no possibility to start a new recording (messages Test - Test                   Ma - Major   244100 -   OP/IO
                                           : Record Init Failed (7) and Record Init Failed (2) for the next unsuccessfull                                        Voice
                                           tries). Furthermore, no possibility to replay a recording : the playing list
                                           was empty.
    10335 REPLAY REQUEST LOCKED IN PENDING After termination of a 48 hours long recording, I request through EMS          Test - Test               Ma - Major   244100 -   OP/IO
          STATE                            software to replay this recording. Once all dialog box filled with correct                                            Voice
                                           answers, the replay line displayed in the Record/Replay window but the
                                           state is definitely locked on "Pending". After that, the software was
                                           "unstable", some errors occurred.
                                                                                                                14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                         FOP 245000

                                                                                                                                                                           Context                   Configurati    Entity in
Reference                       Title                                                               Description                                                Phase      reference    Criticality    on Item        charge        Status          Comments

                                                            Deux dates permettent de définir la date de début d'un planning:
                                                            D0 predicted et Real D0

                                                            Pendant la préparation du FOP, les deux dates sont égales. La SOE affiche donc les
                                                            dates planifiées des événements par rapport à cette date D0 predicted.

                                                            En opération, la date Real D0 permet de définir le reel début du planning, donc les dates
                                                            planifiées des événements doivent se caler sur cette date. La SOE doit donc afficher les
                                                            dates par rapport à la date Real D0. (C'est ce qui est fait dans la version FOPNG 2.0.1)

                                                            Mais la fenêtre d'affichage des informations d'un événement continue d'afficher la date
                                                            calée sur celle de D0 Predicted au lieu de la Real D0.
                                                            Exemple 1:
                                                            D0 Predicted = 01/01/2007 Real D0 = 01/01/2008
                                                            Dans la SOE: Event 1 = 02/01/2008
                                                            Dans la fenêtre info: Event1 = 02/01/2007 (au lieu de 02/01/2008)

                                                            De même, lors de l'ajout d'un nouvel événement, la date proposée est calée sur D0
                                                            predicted au lieu de Real D0, ce qui fait que on pense qu'il faut modifier cette date pour
                                                            entrer dans la SOE, mais quand on enregistre, le décalage est alors appliqué et
                                                            l'événement n'est pas où on le voulait.
                                                            Exemple 2:
                                                            D0 Predicted = 01/01/2007 Real D0 = 01/01/2008
                                                            Dans la fenêtre de saisie: Event1 = 02/01/2008                                                                                                                                  FA réouverte suite à
                                                            Dans la SOE: Event 1 = 02/01/2009                                                                                                                                               recette V2.0.1: CRE
                                                                                                                                                                                                                                ACR - To be FOP NG OPS-MIN-
82370       Utilisation de D0 predit ou réel dans la SOE                                                                                                   Prep - Prep                Major                        CRIL         treated     245000-50978-CNES
                                                            When launching the software, we notice two warning messages about “log4j”. These
                                                            messages were not displayed in previous version of the software.
                                                            This is due to a missing file at the generation of the installation package. This problem is
                                                            due to a mistake in the PGC (Plan de Gestion de la Configuration)
84081       PGC documentation error                                                                                                                        Accep - Accep VT_INS_001 mi - minor       PGC           CRIL         FIL - Filtered
                                                            In the Preference Window, when entering or changing the dates concerning the current                         VT_CFG_00
84082       Error in the preference window                  mission, several JAVA error messages appear in the ErrorLog window                             Accep - Accep 2          mi - minor       PGC           CRIL         FIL - Filtered
                                                            After filtering DAP periods : there are not displayed in the SOE. There are well created but
                                                            a refresh of the “Model” is missing.                                                                         VT_ART_00
84083       Refresh the model after DAP filtering           Closing and re-opening FOP show them.                                                          Accep - Accep 7         mi - minor                      CRIL         FIL - Filtered
                                                            Parameter type for parameter association are checked in the target data base instead of
            Filter : Parameter type checked in target       the source database. This prevent showing a parameter if it is not present in the target
84084       instead of source                               data base. Remark this should not happen                                                       Accep - Accep VT_FIL_002   mi - minor                   CRIL         FIL - Filtered
            Rules : messages for evently spaced             An error message is displayed in the ErrorLog when creating a rule for periodic phases,                      VT_RULES_
84085       periodic phases with condition                  evently spaced, with a conditioning phase.                                                     Accep - Accep 004          mi - minor                   CRIL         FIL - Filtered
            Rules : changes are not always taken into                                                                                                                    VT_RULES_
84086       account in update                               Sometimes, when updating a rule, changes are not taken into account.                           Accep - Accep 008          mi - minor                   CRIL         FIL - Filtered
            Graph : crash the template if zone identifier   When creating a new zone in the FOP template, if the Identifier is left blank this                           VT_FOP_00
84087       is null                                         sometimes crash the template                                                                   Accep - Accep 1            mi - minor                   CRIL         FIL - Filtered

                                                            The software FOPNG has no function to take into account the SimulTime Offset file
                                                            provided by the M&C.

                                                            This file contains the delta time between the date of the Telemetry received by the M&C
                                                            and the Systeme time on the Network.
                                                            The FOPNG shall get this delta time and apply it to provide the "Simulation Time" used in
                                                            the SOETR.
            FOPNG: does not take into account a             It would be nice if the ROPS can browse over the network to open the Simultime offset          Integ -
84101       SimulTime Offset                                file. This functionnality could be add in the "Clock Window" displaying the Simulation Time.   Integration                mi - minor                   CRIL         FIL - Filtered
            FOPNG Import: warning message when              In the Import function, sometimes a warning message is displayed in the ErrorLog when          Integ -
84113       cancel is selected                              the user selects the Cancel button.                                                            Integration                mi - minor                   CRIL         FIL - Filtered
                                                                                                    14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                      MOIS 245100

                                                                                                                                                           Context                    Configurati    Entity in
Reference                     Title                                                     Description                                          Phase        reference     Criticality    on Item        charge                  Comments

                                                       Runtime error occured while trying to expotr FCP to FOP sequence into a                                                                                   17/10/06: will be corrected in v5.3.17
          FCP EXPORT RUNTIME ERROR WHEN                directory with no write access rights for the user. The following error pop-                                                                              or next delivery 04/05/06: will be
    10246 NO WRITE ACCESS ON DIRECTORY                 up is displayed: "Run-time error '5'. Invalid procedure camm or argument". Test - Test                          mi - minor                   RHEA         corrected in v5.3.15
                                                                                                                                                                                                                  05/03/2007: AR redelivered to
                                                                                                                                                                                                                 RHEA: to be corrected urgently
                                                                                                                                                                                                                 17/10/06: correction foreseen with
                                                                                                                                                                                                                 v5.3.17 or next delivery 04/05/2006:
                                                                                                                                                                                                                 Anomaly only partially corrected
                                                                                                                                                                                                                 according to the MOIS v3.5/5.3.14
                                                       Some values of TC parameters defined with Formal Parameters (FP). FP                                                                                      acceptance run on 02/05/06: only the
                                                       value kept when exported, contrary to Requirement R4.1.11 (should be                                                                                      second minor part of the anomaly
                                                       blank instead). If a FP is defined (for a TC parameter) and then valued at                                                                                has not been corrected, anomaly to
                                                       procedure level, one would expect to have the parameter valued in the                                                                                     be fully corrected with the 5.3.15
    10259 EXPORT OF FORMAL PARAMETERS                  export but it is not the case (the FP is kept in the export).              Test - Test                          Ma - Major                   RHEA         version or next.

                                                       Current implementation : There is a warning for a CMD statement inside a
          AR ATV-CC 184 NOT FULLY                      WAIT/IF/SWITCH step, but no message at all for any other unexpected
    10279 CORRECTED                                    statement (ex : DIR) that the statement will or will not be generated.                                          Ma - Major                   RHEA         Not fully corrected in v5.3.16
          THE DIRECTORIES MANUALLY                     In the database import functionality, db files are not correctly imported if
          ENTERED ARE NOT TAKEN INTO                   their access path is entered manually by the user, instead of being                                                                                       05/03/2007: to be corrected in
    10298 ACCOUNT                                      selected from the browser (displayed by clicking on the ¿ button).                                              mi - minor                   RHEA         v5.3.17 or next (low priority)
          FCP SEQUENCE REPORT CREATION                 The report of FCPN3060 is truncated : no data written after the first part                        PREPA                                                   05/03/2007: Minor AR to be
    10331 FAILS : REPORT IS TRUNCATED                  of a long comment (CMT).                                                                          ESSAI RDV mi - minor                       RHEA         corrected in v5.3.17 or next
                                                       Unexpected run-time error got while trying to delete a group in the
                                                       Reporter. Afterwards, MOIS application is blocked and the user session                                                                                    05/03/2007: Minor AR to be
    10333 GROUP DELETION IS NOT POSSIBLE               has to be unlocked by an administrator.                                                                         mi - minor                   RHEA         corrected in v5.3.17 or next
          UNITS OF PARAMETERS ARE NOT                                                                                                                                                                            05/03/2007: not fully corrected: the
          EXPORTED IN THE FCP SEQUENCE                                                                                                                                                                           units of TM are not displayed (only
    10336 REPORT                                       Units of parameters are not displayed in the FCP sequence report.                                               mi - minor                   RHEA         the TC units)
          NO CONNECTION OF AN ACTIVITY                 After insertion of an activity, the first step of the activity is not connected
    10351 AFTER INSERTION                              to the previous step of the "mother" procedure.                                                                 mi - minor                   RHEA

                                                       If a TLM statement contains various checks, those checks are exported
                                                       (M&C export + Report) in an order different from the one defined in the
                                                       procedure.
                                                                                                                                                         FCP
    82723 Export of Verify TLM: order not respected    Cf step 4 of the attached procedure, and line_id 5 of the exported files. Prep - Prep             preparation   Ma - Major                   RHEA         FXG- MOIS ARB 21/02/2007
                                                       The way the decimal separator in a number is not controlled/managed by
                                                       MOIS, and fool values can thus be exported.

                                                       Cf attached procedure step 4, and associated exports files.
                                                                                                                                                         FCP
    82724 Decimal separator format is not managed                                                                                        Prep - Prep     preparation   mi - minor                   RHEA         FXG- MOIS ARB 21/02/07

                                                       If a TLM statement has an associated display (through the „proforma‟
                                                       interface), it is impossible to express the expected value in Raw format.
          Raw value forbidden if there is a „proforma‟
    82726 display selected                             Cf attached procedure, step 4.                                                    Prep - Prep                   Ma - Major                   RHEA         FXG- MOIS ARB 21/02/07
                                                       The TLM statement that indicate the on-event discrimant in the VCP, is
                                                       imported in the BFCP. It should not (cf RfC 267); only the parameters of
                                                       the discriminant should be imported.

          Conversion of On-event TLM during VCP        Possible cause : it seems that the anomaly occurs since the correction of
    82913 import is wrong                              AR ATV-CC 256.                                                            Prep - Prep                           C - Critical                 RHEA         FXG- MOIS ARB 21/02/07
                                                       The "Update Activity" MMI is incomplete : there are only 2 choices,
                                                       'Update' and 'Remove'. A 'Cancel' option should be added.
                                                                                                                                                                                                                 FXG- MOIS ARB 21/02/07
                                                       Need : Going to the Update Activity MMI without necessity to Update or                                                                                    The window cannot be cancelled
                                                       Remove (e.g. to check the current version of the activity, or to cancel a                                                                                 using the upper right cross because
    83000 Update activity MMI incomplete               user error).                                                                      Other - Other                 mi - minor                   RHEA         this cross is disabled.
                                                                                                 14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                              MOIS 245100

                                                                                                                                                  Context                   Configurati    Entity in
Reference                    Title                                                    Description                                      Phase     reference    Criticality    on Item        charge                 Comments



                                                      After a FCP export of a procedure containing branching steps ("IF"), the
                                                      FCP sequence report was correct but the M&C sequence report was not
                                                      correct (.dat): the GOTO commands were missing into the procedure, and
                                                      as a consequence the second branch was not correctly linked (wrong ID
                                                      steps).Thus the procedure could not have been performed on M&C.

                                                      However the RfC 257 specification was clear as far the classic MOIS rules
                                                      should have been applied inside each branch:
                                                      "Then for the Steps that are part of the branch, the included Statements                                                                         First analysis of RHEA: the WAIT
                                                      shall be exported following the rules applied today by MOIS."                                                                                    step cannot be the last step of a
                                                                                                                                                                                                       branch: a PERFORM step (Verify,
                                                       Please find enclosed one of these procedures (FCPN_PRO_32_test) and                                                                             TC, CMT...)has to be added after
          The branching procedure is wrong into the    the exported FCP sequence report (FCPN_PRO_32_test_Report.xls) and                       PO_CAMT_                                               (workaround to use this MOIS
    83369 M&C sequence report                          M&C sequence (FCPN_PRO_32_test_V1.dat).                                  Prep - Prep     N_1      C - Critical       Branching     RHEA         release).
                                                       In the "browse IHM" used to select the aimed folder to export the FCP
                                                       sequence report, the title is wrong; "Select folder for FCP FOP sequence
          The title on the "browse IHM" for the export report files" must be replaced by "Select folder for FCP sequence report                 MOIS
    83387 is wrong                                     files".                                                                  Accep - Accep   v5.3.16 SP2 mi - minor      IHM           RHEA         FXG- MOIS ARB 21/02/07

                                                      MOIS spent too much time to insert or update activities
                                                      For example the procedure called FCPN2020

                                                      - To insert one activity: between when the button Ok in the FOP view is
                                                      pressed and when the activity is really inserted, the duration for this action
                                                      is 2min08s

                                                      - To update one activity: between when the button "Update Activity" is
                                                      pressed and when the activity is really updated, the duration for this action
                                                      is 2min26s

                                                      - To insert one step: between when the button Ok is pressed and when
                                                      the step is really inserted, the duration for this action is 1min20s

                                                      The duration above doesn't take into account the action to update the
                                                      flowchart                                                                                                                                        Magali Delpla - Give an assess
                                                                                                                                                                                                       whether this can be due to the
          MOIS spent too much time to insert or                                                                                                                                                        application or to the local
    83414 update activities                                                                                                 Other - Other                    Ma - Major                   OP-SOL       configuration (use of Citrix)
                                                   During the test of AR 82747 (block insertion), the FCP export of the
                                                   procedure FCPN_MVM_03 worked correctly, however the local export did                   MOIS
    83425 The local export does not work           not work as far the block was not inserted into the procedure.           Accep - Accep v5.3.16 SP2        Ma - Major     Local export RHEA          M. Delpla
          Wrong name of the procedure in the FCP   In the header of a FCP Report, upper left, the name is wrong :
    83459 report header                            FCPxxx_TEMP instead of FCPxxx.                                           Test - Test                      mi - minor                   RHEA         Magali Delpla
                                                   Long comments are not displayed in the FCP Report export, using excel.
                                                   Instead, '###################' is displayed.
          Some comments are not displayed into the Cf attached export, various examples : between line id 26 and 27, 57 and
    83520 FCP export Report                        58.                                                                      Test - Test                      Ma - Major                   RHEA         by FXG
                                                                                                   14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                             MOIS 245100

                                                                                                                                                        Context                   Configurati    Entity in
Reference                     Title                                                     Description                                        Phase       reference    Criticality    on Item        charge              Comments

                                                       Activity displayed at a wrong place after insertion

                                                       Cf attached example :
                                                       If you insert BFCPC_PRO_23_1 as an activity in BFCPC_PRO_13_1,
                                                       after step 9, the activity is "visually" displayed after step 10. This is the
                                                       anomaly.

                                                       After refresh of the flowchart, the activity is correctly displayed between
                                                       original steps 9 and 10; but having the activity at the wrong place before
          Activity displayed at a wrong place after    refresh is totally misleading and lead the operator trying to make
    83524 insertion                                    corrections (thus inducing risk of errors) on a procedure that is correct.      Test - Test                 C - Critical                 RHEA         by FXG

                                                       Context:
                                                       One of the IF branch is directly connected to the end of the procedure.
                                                       MOIS failed during the generation of the export. MOIS stopped the export
          MOIS failed when is performing an export     creation on the IF step on the branch which is directly connected to the
          with if branching directly conected to the   end to the procedure
    83528 end of the procedure                                                                                                         Other - Other               C - Critical                 RHEA         By DS


                                                       There are several mistakes in this procedure, the branching if is badly
                                                       implemented
                                                       - MOIS has implemented an "End of branching" instead of "Start of
                                                       branching" (on step 10 of the export)
                                                       - MOIS does not implemente a GOTO (just before step 14 of the export)
                                                       - MOIS does not implemente a GOTO (just before step 17 of the export)
                                                       - MOIS does not implemente an "End of branching" (just before step 17 of
          MOIS made mistakes on if implementation      the export
    83529 in M&C export                                See enclose this M&C export                                              Other - Other                      C - Critical                 RHEA         By DS

                                                       There are several mistakes in this procedure, the branching if is badly
                                                       implemented.
                                                       MOIS skips steps and keeps the gap along the procedure export.

                                                       Hereafter are comments describing the anomaly in line with files enclosed
                                                       - Step 31 from the proc.body of MOIS FILE
                                                       In the IF branching, the positive branch is wiring to step 32 and the
                                                       negative branch is wiring to step 33. The both steps are verify TMs

                                                       If we compare the previous remarks to the export, there are some
                                                       mistakes

                                                       - Line ID 032 from export file (.dat)
                                                       In the IF branching, the positive branch is wiring to Line ID #36 and the
                                                       negative branch is wiring to Line ID #39. In fact Line ID #36 and #39 are
                                                       incorrect and should be respectively #34 and #37.

                                                       This gap is still along the export as Line ID #36 is wiring to Line ID #47,
                                                       but the last one does not exit and should be #45.

                                                       Another point it's why the flowchart is incomplete in the export but still
          MOIS made mistakes for if implementation     complete in the MOIS FILE.
    83560 on M&C export                                                                                                                Other - Other               C - Critical                 RHEA         By DS
                                                                                               14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                MOIS 245100

                                                                                                                                                     Context                   Configurati    Entity in
Reference                     Title                                               Description                                          Phase        reference    Criticality    on Item        charge                Comments
                                                     On the attached procedure, the following actions are performed :
                                                     - comparison between current version (27) and previous version 13;
                                                     - refresh

                                                     The anomaly : After this sequence of actions, the modifications introduced
                                                     by version 27 over version 26 disappear; i.e., what is displayed after the
                                                     refresh is the procedure in its version 26 state.

                                                     After undo-check-out, then check-out again, the procedure is displayed in
                                                     its version 27 (current) back.

    83564 Visualisation error with the comparison tool Consequence : very confusing for the user.                                  Prep - Prep                  C - Critical
                                                       Description of files enclosed
                                                       First part are composed of 3 FCP MOIS
                                                       - FCPN_PRO_13_N_WithActivity is a FCP with FCPN_PRO_23_N
                                                       inserted as an activity
                                                       - FCPN_PRO_23_N is a FCP inserted as an activity in
                                                       FCPN_PRO_13_N_WithActivity
                                                       - FCPN_PRO_13_N_WithoutActivity as described it's a FCP without any
                                                       activity

                                                     Second part is the FCP export generated for the previous FCP MOIS
                                                     - FCP_M&C is containing the 3 FCP M&C export
                                                     - FCP_Paper is containing the 3 FCP paper sequence report
                                                     - FCP_FOP enclosed but useless

                                                     What was the sequence?
                                                     - Firstly the export for FCPN_PRO_13_N_WithoutActivity,
                                                     FCPN_PRO_23_N were performed and it was a success
                                                     - Secondly for the nominal procedure the export for
                                                     FCPN_PRO_13_N_WithActivity failed

                                                     And as we can see in the ATV_FCP_Export.log the error is "- Invalid
                                                     procedure call or argument" but the export were successful when the FCP
                                                     are managed separately
    83633 MOIS failed during the export generation                                                                                 Other - Other                Ma - Major
                                                     Description of files enclosed
                                                     The FCPN_PRO_23_N.zip is containing MOIS file ,M&C and paper
                                                     sequence of FCPN_PRO_23_N

          MOIS is forgotten GOTO and Stop            If we are looking the M&C export
    83634 branching in FCP with branching            On id 74, 77, 92, 95, 98, GOTO and Stop branching are missing                 Other - Other                C - Critical                              By FR/DS
                                                     Description of files enclosed
                                                     The BFCPC_190_2.zip is containing MOIS file

                                                     In the BFCP, although the flowchart is composed with 64 steps, the
                                                     proc.body does contain only the 32 first steps, nevertheless the VCP is
                                                     containing 64 steps. We can also take note that the import log file does
                                                     not have any error for this VCP/BFCP.

                                                     After (very) preliminary analysis by the operator, this could be linked to the
          The proc. body is not coherent with the    fact that the next statement (just after the BFCP "cut") is a statement of
    83697 flowchart                                  type "CMT" beginning with the character string " => ".                         Other - Other               C - Critical                 RHEA
                                                                                             14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                    MOIS 245100

                                                                                                                                                  Context                   Configurati    Entity in
Reference                     Title                                            Description                                           Phase       reference    Criticality    on Item        charge     Comments
                                                  The attached procedure export is wrong wrt branching :

                                                  Les numeros de step (dans le flowchart FCPE):
                                                  The GOTO is missing after step 100 (corresponding to line_id 156 in the
                                                  export file); the "STOP end of branching" is missing before step 109
                                                  (corresponding to line_id 173 in the export file).

                                                  A manually patched file is also provided with the expected data
    83761 Branching : Export is wrong             (FCPE9230_V2_super_patch.dat).                                                 Prep - Prep                 Ma - Major                   RHEA


                                                  In the FCP report export, description sheet, a print area is defined by
                                                  default, that does not cover the overall information contained in the sheet.

    83764 FCP report export : Print area          There should be no default 'print area', as per the other sheet of the file.   Prep - Prep                 mi - minor                   RHEA
                                                  In the TC statement interface, 'parameters' tab, it is the unit of the
                                                  parameter that is displayed in front of the 'default value' field instead of
    83765 TC default value is not displayed       the default value.                                                                                         mi - minor                   RHEA

                                                  Description of files enclosed
                                                  The BFCPN_505.zip is containing MOIS file without any modifications.

                                                  If the drawing is opened then a pop-up ask to add the difference to be in
                                                  line with the procedure : this procedure is delivered by EADS ASTRIUM
                                                  and no difference should appear.

          On BFCPN_505 the drawing differs from   Plus the modifications added are really inconfortable, MOIS duplicates
    83777 the procedure                           connectors on the flowchart.                                                   Other - Other               Ma - Major                   RHEA

                                                  Description of files enclosed
                                                  The FCPN_505.zip is containing MOIS file

                                                  What was the sequence?
                                                  The BFCPN_505 was saved as FCPN_505 then the drawing was updated
                                                  (means deletion of useless double connectors as shown on the previous
                                                  FT). Right after the drawing closure, the step sequence has changed.

                                                  This procedure is composed by a switch. Previously in the BFCP
                                                  proc.body, the "YES branch" were numbered from 2 to 4 and the "NO
                                                  branch" were numbered from 5 to 9. After saving the BFCP as a FCP and
                                                  modifications added on the drawing, the branch swapped I mean the
                                                  "YES branch" is numbered from 9 to 11 and the "NO branch" is numbered
          On FCPN_505 the step's sequence is      from 4 to 8.It's quite disturbing
    83778 changing after closing the drawing                                                                                     Other - Other               Ma - Major                   RHEA
                                                                                                 14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                     MOIS 245100

                                                                                                                                                       Context                   Configurati    Entity in
Reference                      Title                                                  Description                                         Phase       reference    Criticality    on Item        charge     Comments


                                                       We have imported into Mois database twice the same VCP
                                                       "VCPN_TDRS_04 version 19"

                                                       - once with a previous MOIS version -> becoming BFCPN_TDRS_04 V8
                                                       - the second time with Mois v5.3.16SP3 -> BFCPN_TDRS_04 V9

                                                       1 - The result is not the same. There is a difference in the LabelTime
                                                       column.
                                                       "Execution: ET -00.01.00" becoming "Execution: P_AT_RATE_DATE -
                                                       00.01.00"

                                                       2 - Modification after a Cancel action : In the BFCPN_TDRS_04_V8
                                                       proc.body, if we're opening the telecommand properties and closing by
                                                       using cancel button then the label/time items for this TC is changing to the
                                                       newer version


                                                       3 - If we're comparing BFCPN_TDRS_04_V8 with BFCPN_TDRS_04_V9
                                                       then the comparison log file shows difference between the two
                                                       procedures. However the procedure have not been upgraded.

                                                       Description of files enclosed :
                                                       In the BCPN_TDRS_04.zip you will find the two version of the procedure
          Differences in the label/time column after   BFCPN_TDRS_04, V8 and V9
    83796 two import of the same procedure                                                                                            Other - Other               Ma - Major                   RHEA
                                                       When inserting the procedure BFCPC_MVM_30 as an activity into
                                                       BFCPC_189, the inserted procedure is not linked to the mother
          The inserted activity is not linked to the   procedure.
    83844 mother procedure                                                                                                            Test - Test                 Ma - Major                   RHEA
                                                                                        14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                                TTFEE 248000

                                                                                                                                           Context                   Configurati    Entity in
Reference                  Title                                             Description                                       Phase      reference    Criticality    on Item        charge                  Comments
                                              the non conformances raised during TTFEE security acceptance shall be
                                              corrected (documentation modification, ¿). These non conformances are                                                                             # Affected Product : ATV-CC(OPS-
                                              described in OPS-NT-248000-50344-CNES, section 4. Only the non                                                                                    200000)
              NON CONFORMANCES - SECURITY     conformances which are tagged ABSp (or CNES ABSp) in the                                                                                          # Observations : will be treated in the
        10139 ACCEPTANCE                      "Responsabilité" column shall be managed by ABSp.                                                       mi - minor                   ABSp         framework of RfC ATV-CC 249
                                                                                                                                                                                                # Affected Product : ATV-CC/(OPS-
                                                                                                                                                                                                248000) TTFEE# Observations :
             REMOTE TTFEE APPLICATION QUITS   When two mains are connected on the same remote and one of them                            TTFEE V2.2                                             10/07/2006: TTFEE v3.0 acceptance:
             EVEN IF ONE CLIENT IS STILL      closes its gui then the connection with the other main is also closed                      ACCEPTAN                                               anomaly linked to the security
10161        CONNECTED                        (because the remote application is instructed to QUIT and exit).            Test - Test    CE TEST    mi - minor                     ABSp         acceptance
                                                                                                                                                                                                # Affected Product : ATV-CC/(OPS-
                                                                                                                                                                                                248000) TTFEE
                                                                                                                                                                                                # Observations : 10/07/2006: pb of
                                                                                                                                                                                                sockets diffusion overflow: CNES
                                                                                                                                                                                                proposed to postpone this
                                                                                                                                                                                                investigation, and perhaps to fix this
                                                                                                                                                                                                anomaly through the next TTFEE
                                                                                                                                                                                                delivery
                                                                                                                                                                                                # Remarks : A short network link
                                                                                                                                                                                                interruption occurs between the Main
                                                                                                                                                                                                TTFEE and the Remote TTFEE is
                                                                                                                                                                                                handled gracefully and the
                                                                                                                                                                                                communication is successfully re-
                                                                                                                                                                                                established when the network is
                                                                                                                                                                                                active again. When the interruption is
                                                                                                                                                                                                a little longer (let's say: about 25mn),
                                                                                                                                                                                                every module boxes turn to red.
                                                                                                                                                                                                When the network is active again, the
                                                                                                                                                                                                Remote TTFEE boxes turn green
                                                                                                                                                                                                again but those of the main TTFEE
                                                                                                                                                                                                stay red. We have to manually kill the
                                                                                                                                                                                                TMTC process on the remote TTFEE
                                                                                                                                                                                                to make the TTFEE working properly
                                                                                                                                                                                                again. The messages that appear on
                                                                                                                                                                                                the MMI are (with associated time
                                                                                                                                                                                                stamp): - 08:30:27 - global moncon
                                                                                                                                                                                                connection main remote TTFEE lost -
                                                                                                                                                                                                08:38:48 - global moncon error
                                              Any short network link interruption between the Main TTFEE and the                                                                                reading sock 7 : connection timed out
                                              Remote TTFEE is handled gracefully and the communication is                                IT 10                                                  while executing \n "get $sock" -
             STABILITY PROBLEM DUE TO         successfully re-established when the network is active again. However a                    REDUNDAN                                               08:38:52 - problem writing to sock7:
             NETWORK INTERRUPTION BETWEEN     longer interruption results in an inconsistent state where we have to                      CY                                                     error writing 'sock 7': broken pipe -
10233        THE MAIN AND THE REMOTE TTFEE    manually kill the TMTC process on the remote TTFEE. See comments.           Test - Test    TESTING  mi - minor                       ABSp         08:38:52 - global moncon: connection
                                                                                                                                                                                                # Affected Product : ATV-CC/(OPS-
                                                                                                                                         TTFEE V2.4                                             248000) TTFEE# Observations :
                                              In certain circumstances, applying a new meta-configuration file does not                  ACCEPTAN                                               10/07/2006: AR to be fixed through
10261        WRONG PROCESS ACTIVATION         update the "green/grey" process status as expected.                         Test - Test    CE TEST    mi - minor                     ABSp         the next TTFEE delivery
                                                                                                                                                                                                # Affected Product : ATV-CC/(OPS-
                                                                                                                                                                                                248000) TTFEE
                                              The TTFEE configuration is: telemetry and telecommand processes                                                                                   # Observations : 10/07/2006: still
                                              deactivated. An error message "underflow of the uplink fifo" is displayed in                                                                      opened, 2 main hardware problems
             NO ALARM ASSOCIATED TO THE       the message box but no alarm is raised (acknowledge button is "grey" and                   TTFEE V2.4                                             observed with TTFEE v3.0
             UNDERFLOW OF THE UPLINK FIFO     the Hardware Interface button stays green). The underflow error was                        ACCEPTAN                                               acceptance (see CRE TTFEE V3.0
10263        ERROR MESSAGE                    probably raised due to backup processes (resource consuming)                 Test - Test   CE TEST    mi - minor                     ABSp         OPS-MIN-248000-50733-CNES)
                                                                                    14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                    MIM 249100

                                                                                                                                                Context                  Configurati    Entity in
Reference                     Title                                                  Description                                    Phase      reference   Criticality    on Item        charge     Comments
                                                     Si on ouvre un Image Display en binaire, avec un recalage de la plage
                                                     d‟adresses, lorsque l‟on clique sur « Compare Image » et que l‟on choisit
                                                     la même image pour comparer, le MIM plante. L‟outil plante
          Problème sur ouverture d'une image display systématiquement si on essaye de faire une comparaison d‟images en                        FUNCT-
    84066 en binaire                                 mode binaires où on a eu un recalage d‟adresses.                            Accep - Accep DISP-N-071 Ma - Major                   THALES       By HK
                                                                                    14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                       MCI 249200

                                                                                                                                                   Context                  Configurati    Entity in
Reference                     Title                                                  Description                                       Phase      reference   Criticality    on Item        charge     Comments

                                                      Si on entre des valeurs aberrantes (type „aaaa‟ pour la masse), aucun
                                                      message d‟erreur n‟apparaît. La valeur n‟est pas prise en compte, mais
                                                      aucun message n‟est affiché. De plus, si on entre une expression dans un
                                                      des champs éditables (par exemple 12-6, possible erreur avec le point), la
                                                      valeur est bien prise en compte par troncature : le MCI prend 12 dans
                                                      l‟exemple. Le contrôle sur les valeurs négatives est correct. => appliquer
                                                      le même fonctionnement que pour la fenêtre de prédiction.
                                                      Nice To Have : Dans le contrôle, prévoir d‟autoriser la virgule et le point
                                                      comme séparateur de décimale.                                                               FUNCT-
    84068 controle sur les valeurs de masse saisies                                                                                 Accep - Accep MMGT-D-01 mi - minor                    THALES
                                                      Mettre a jour le fichier vdi_prop_mapping.properties pour les VDI portant
                                                      sur les tanks RefOx1 et RefOx2. Le RefOx1 doit pointer sur BO2 et
          mise à jour du fichier                      RefOx2 sur BO1                                                                              FUNCT-TCO
    84069 vdi_prop_mapping.properties                                                                                               Accep - Accep -N-02     Ma - Major                    THALES
                                                      Les nouveaux libelles « PASSED » et « NOT PASSED » n‟ont pas été pris
                                                      en compte dans les sorties de type report. Les libellés « BEFORE » et «
                                                      AFTER » sont toujours présents. Ces nouveaux libellés ont bien été pris
          Prise en compte des libelles PASSED et      en compte dans l‟IHM                                                                        FUNCT-PDC
    84070 NOT PASSED                                                                                                                Accep - Accep -N-03     Ma - Major                    THALES
                                                                                       14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                       GMS 249300

                                                                                                                                                          Context                   Configurati   Entity in
Reference                      Title                                               Description                                             Phase         reference    Criticality    on Item       charge     Comments
                                                         TST_FCT_CF_0080 : indiquer dans le manuel la configuration vidéo
                                                         nécessaire.

                                                         TST_INS_GM_0010 : Compléter l‟IEG pour décrire comment installer
                                                         Java3D (description du type M&C avec identification du user à utiliser).
                                                         L‟installation a été faite en utilisant le user atv_inst.

                                                         TST_LCH_GM_0010 : Concernant les droits sur les fichiers GMS, les
                                                         fichiers ne sont qu‟en lecture, mais pas en écriture il faut définir les droits
                                                         à allouer sur chaque répertoire de GMS. Il faut que la procédure
    83293 Modifications de l'IEG GMS                     PostInstall.bat prenne en compte ces droits.                                    Accep - Accep               Ma - Major

                                                         TST_FCT_RD_0060 : expliquer dans l‟UM comment est détecté un trou
                                                         TM.

                                                         TST_FCT_RD_0010 : Ajouter un paragraphe dans le user manual
                                                         expliquant le fonctionnement du Warning delay (est ce que les calculs
    83295 Modifications du User Manual GMS               sont faits avec les anciennes valeurs, ou est ce qu‟ils ne sont pas fait ?). Accep - Accep                  mi - minor

                                                         Step 5 : Le tooltip associé au zoom (out et in) mentionne que le scale
                                                         factor est défini dans le fichier de configuration, ce qui n‟est pas le cas.
          Revoir les labels associes au zoom dans        Voir aussi le ToolTip pour le bouton Zoom 1:1                                                TST_FCT_R                                               Corrigée par
    83296 les tool tips.                                                                                                                Accep - Accep D_0060    mi - minor                                    patch V1.1
                                                         Des incohérences sont apparues pour le zoom maximum dans le cas de
                                                         l‟enchaînement suivant :
                                                         - sélection d‟une zone autour du pattern théorique
                                                         - zoom in jusqu'à atteindre le max en zoom in
                                                         - à nouveau sélection d‟une zone => on avance encore => le zoom in
                                                         aurait du fonctionner encore
                                                         En fonction de la taille de la zone sélectionnée au départ, le zoom limit                    TST_FCT_R                                               Corrigée par
    83297   Problème sur le "zoom limit"                 autorisé n‟est pas le meme.                                                    Accep - Accep D_0060    Ma - Major                                    patch V1.2
                                                         il faudrait que lorsque l‟on demande a maximiser les fenêtres, les
                                                         fenêtres recouvrent la place restante en dessous du bandeau du M&C.
                                                         Cette maximisation semble se caler sur la position « coin en haut à
                                                         gauche » de la fenêtre en cours. De plus, lorsque l‟on agrandit/diminue
                                                         les fenêtres, on observe des comportements assez curieux si la fenêtre a
                                                         été déplacée ou non (si on maximise la fenêtre, puis qu‟on la re-diminue
                                                         avec le bouton « Restaurer », on ne retrouve pas la taille initiale de la                    TST_FCT_R
    83298   Maximisation des fenêtres                    fenêtre)                                                                       Accep - Accep D_0180    Ma - Major
                                                         Lors du lancement du fichier de télémesure TST_FCT_TM_0060-1, les
                                                         mesures des senseurs sont rassemblées au milieu de l‟écran, et sont
                                                         affichées avec un carré. Il semble que ce soit un problème d‟initialisation                  TST_FCT_T                                               Corrigée par
    83299   Problème d'affichage dans le Rtarget         de la fenêtre.                                                                 Accep - Accep P_0050    Ma - Major                                    patch V1.2
                                                         Si on se centre sur les axes du Rtarget et si on bouge la scroll bar
                                                         verticale seulement, l‟affichage se recale en horizontal aussi, alors qu‟il
                                                         ne devrait pas.
                                                         Les propriétés de la scroll bar sont mal définies. Les valeurs de "small
            Problème sur les scroll bar pour l‟affichage step" et "large step" doivent être redéfinies en fonction de la "page"                       TST_FCT_T
    83300   Rtarget                                      affichée et donc dépendre du zoom appliqué.                                    Accep - Accep P_0050    Ma - Major
                                                                                14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                     GMS 249300

                                                                                                                                                 Context                   Configurati   Entity in
Reference                     Title                                                   Description                                 Phase         reference    Criticality    on Item       charge     Comments
                                                    Le passage en freezing mode sur les fenêtres ouvertes n‟est pas
                                                    possible. Un message dit qu‟il n‟y a pas d‟intervalle de données
                                                    disponibles. Pourtant le fichier de simulation tournait depuis
                                                    suffisamment longtemps pour avoir alimenter le buffer de freezing mode
                                                    (d‟autant plus que les valeurs numériques étaient bien mises a jour en                      TST_PER_                                             Corrigée par
    83301 Anomalie sur le Freezing mode             temps réel)                                                                Accep - Accep    GM_0030  Ma - Major                                  patch V1.1
                                                    Lors de l‟exécution du .jar, un message d‟erreur est apparu disant que le
                                                    fichier « options.properties » existe déjà sur le disque. Ceci semble dû à
                                                    une erreur dans l‟environnement de génération du plugin. Supprimer le                       TST_INS_G                                            Corrigée par
    83302 Problème lors de l'installation GMS       fichier en double.                                                         Accep - Accep    M_0010    mi - minor                                 patch V1.1
                                                    Il faudrait voir le terminator sur la vue SA (cf spec :                                     TST_FCT_S
    83304 Visualisation du terminator               GMS_SA_COMP_ATV_050.)                                                      Accep - Accep    A_0020    Ma - Major
                                                    Point 1:
                                                    Lors de l'installation d'une nouvelle version, la procédure propose de
                                                    créer une sauvegarde de l'ancienne installation. A quoi correspond le
                                                    nom donné à cette copie ?
                                                    Exemple : gms_16_01_30_17_58 on aurait pu supposer qu'il y avait la
                                                    date, mais elle n'est pas reconnaissable.

                                                    Point 2:
                                                    Quand on ouvre le M&C, deux applications GMS sont présentées dans le
                                                    menu Applications!
                                                    La version antérieure semble encore accessible, mais comme il n'y a pas
                                                    de numéro de version dans le libellé de l'option du menu, on ne sait
                                                    quelle version est lancée.                                                                                                                       Corrigée par
    83305 Installation d'une nouvelle version       Il ne faut pas que l'ancienne version soit accessible.                    Test - Test                   mi - minor                               patch V1.1
                                                    La configuration du port d'écoute de la TM n‟est pas admissible : Le port
                                                    de réception de la TM est fixe pour GMS, tandis qu‟au niveau du M&C, le
                                                    numéro de port est géré de façon centrale par le composant SC. Ceci
                                                    implique qu‟il va falloir configurer chaque poste MCW et que l‟on ne peut
                                                    pas savoir lors du lancement si l‟on se connecte au flot temps réel ou au
                                                    flot rejeu central.

                                                    De plus, lors de l‟ouverture d‟un flot sur le M&C, il semble que ce soit le
                                                    port udp1 ou udp2 qui soit choisi de façon aléatoire par le composant SC.
                                                    Si c‟est bien le cas, le GMS NE pourra PAS fonctionner avec un port
                                                    défini dans le fichier de configuration.

                                                    Pour pouvoir lancer l‟outil GMS en parallèle des autres applications du
                                                    M&C et sans avoir à repositionner le port à chaque lancement, il faut que
                                                    GMS soit lui aussi client de TMProc, comme VisuTM.                                                                                               Corrigée par
    83306 Configuration du port d'écoute de la TM                                                                                 Test - Test               C - Critical                             patch V1.2

                                                    Lors du lancement du GMS, l‟outil crée ou utilise un fichier Descripteur
                                                    de contexte qui est sauvegardé dans le répertoire
                                                    configuration/operationalContextDescriptor. Ce fichier doit être supprimé
                                                    à chaque changement de contexte de façon à être régénéré par l‟outil.

                                                    Cette implémentation n‟est pas admissible par rapport au fonctionnement
                                                    opérationnel du M&C : avec le M&C, il est possible de choisir le contexte
                                                    sur lequel on se connecte. Ceci implique qu‟avec le mode de
                                                    fonctionnement actuel de GMS, il faut penser à supprimer le fichier
                                                    cache avant de le lancer avec le M&C, sinon le plugin GMS ne pointera                                                                            Corrigée par
    83307 Gestion du contexte                       pas sur le bon contexte !                                                 Test - Test                   C - Critical                             patch V1.1
                                                                         14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                     GMS 249300

                                                                                                                                          Context                   Configurati   Entity in
Reference                     Title                                        Description                                         Phase     reference    Criticality    on Item       charge     Comments
                                           Dans le fichier de configuration generalConfiguration.properties, il
                                           faudrait supprimer (ou mettre en commentaire) les lignes qui pointent sur
                                           les contextes utilisés pour la validation. (ligne
                                           operational.context.version=1_5_context et operational.context.root =
                                           D\:\\GmsContextOp\2_2)

                                           En effet ceci prête à confusion et on ne sait pas si ces lignes sont                                                                               Corrigée par
    83308 Fichier de configuration         utilisées.                                                               Test - Test                      mi - minor                               patch V1.1
                                           La même icône que l‟onglet « System » est utilisée pour le plugin GMS.
    83309 Icône liée à l'application GMS   Pour éviter toute confusion, il faudrait mettre une autre icône.         Test - Test                      mi - minor
                                           Le trouTM est affiché en permanence, alors que l‟on reçoit bien de la TM
                                           ATV. Les paramètres ISS sont en effet manquants, mais, dans la mesure
                                           où on reçoit une partie des données, il ne faut pas allumer l'indicateur
                                           trouTM.
                                           Le trouTM devrait s‟allumer uniquement lorsque AUCUN paramètre n‟est
                                           reçu, ce qui est cohérent avec l‟affichage « TM loss » de VisuTM ou
                                           mettre un indicateur pour chaque type de TM.                                                                                                       Corrigée par
    83310 Trou de Télémesure                                                                                        Test - Test                      Ma - Major                               patch V1.1


                                           Lors du lancement de la fenêtre SA, rien ne se passe. Les labels
                                           Moon/Sun et Earth sont centrés sur l‟affichage, les calculs ne semblent
                                           pas s‟être déclenchés et le warning HoleTM est allumé.
                                           Pourtant, les données de position ATV et attitude ATV sont disponibles
                                           (car visualisées sur les quickpages VisuTM). L‟affichage du SA aurait
                                           donc dû se déclencher, même sans TM ISS et afficher les positions de la
                                           Terre/Lune et Soleil dans Tatv. Le fait d‟avoir ou non la position de l‟ISS
                                           ne doit pas être un facteur de déclenchement du calcul, dans la mesure
                                           où on peut afficher la quasi totalité des éléments sans cette donnée.

                                           Du fait que la TM ISS n‟est pas reçue, le déclenchement du calcul ne se
                                           fait pas, or ce calcul ne nécessite pas les données ISS, donc on devrait
                                           l‟afficher.

                                           Au passage en S0, la valeur 0 s‟est affichée. Ce comportement n‟est pas
                                           cohérent. La TM ISS n‟a pas plus été envoyée que lors du premier test. Il
                                           n‟aurait pas fallu afficher le 0, d‟autant plus que le 0 n‟a plus rien a voir
                                           avec la valeur courante du RGPS qui est environ 12km !                                                                                             Corrigée par
    83311 Déclenchement des calculs                                                                                        Test - Test               C - Critical                             patch V1.1
                                           Le Task manager de Windows montre qu'entre 30% et 50% du CPU sont
                                           prises par le lancement de la fenêtre SA, même si rien ne se passe sur
                                           elle !
                                           Le temps de réponse sur le M&C s'en trouve très affecté.

                                           Le test de stabilité joué pendant la recette serait à réécrire en situation
                                           opérationnelle. En mode Dummy, on ne pouvait pas tester l‟impact de
                                           l‟outil sur les autres process du M&C.
    83312 Stabilité et performance                                                                                         Test - Test               C - Critical
                                                                                    14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                       GMS 249300

                                                                                                                                                       Context                   Configurati   Entity in
Reference                    Title                                                      Description                                         Phase     reference    Criticality    on Item       charge     Comments
                                                      Les valeurs affectées aux plages alphanumériques ATV de la zone ATV-
                                                      ISS velocity ne sont pas correctes.
                                                      L‟outil affiche les vitesses de l‟ATV (paramètres
                                                      GPS1_NAVSOL_VELX_ECEF_DATA,
                                                      GPS1_NAVSOL_VELY_ECEF_DATA et
                                                      GPS1_NAVSOL_VELZ_ECEF_DATA).
                                                      Alors qu'il était demandé d‟afficher les vitesses "relatives" ATV-ISS telle
    83313 Fenêtre SA : champ vitesse ATV-ISS          que données par le VDM (CLO_RVDM et FAR RVDM)                                     Test - Test               Ma - Major
                                                      La taille de certaines cellules ne permet pas de lire la valeur affichée, les
                                                      chiffres étant tronquées par la cellule. Même un agrandissement de la
                                                      fenêtre n'influe pas sur la taille de la cellule. Donc soit agrandir la taille ou
                                                      la rendre dépendante de la taille de la fenêtre.

                                                      Le même problème est apparu pour les libellés qui sont tronqués s'ils
                                                      sont plus longs que la taille de la cellule.

          Format d'affichage des petites ou grandes   Concernant le format d'affichage, si la valeur de la cellule est très petite
    83315 valeurs et taille des cellules              ou très grande, il faudrait basculer en affichage scientifique.                  Test - Test                Ma - Major

                                                      il est impossible de détecter qu‟une valeur n‟a pas été recalculée.
                                                      Elle se fige sur la dernière valeur prise et n‟est pas rafraîchie.
                                                      L‟utilisateur n‟a aucun moyen de faire la distinction entre une cellule
                                                      rafraîchie avec la même valeur et une cellule qui n‟a pas été recalculée.

                                                      Il faudrait que le contenu de la cellule d‟une variable soit grisée (avec
    83316 Affichage des données non recalculées       l‟ancienne valeur) si elle n‟a pas été recalculé.                                Test - Test                Ma - Major
                                                      Le GMS a été lancé avec un scénario AGCS de Rendez-vous, lors
                                                      duquel les données senseurs TGM et VDM étaient descendues.

                                                      Sur GMS, les champs Health Status, Active Sensor et Sensor Current
                                                      State ne sont récupérés dans aucune des fenêtres (SA, synthese, RDV
                                                      VDM1 ou RDV TGM1), pourtant ils sont bien redescendus par la TM
                                                      (vérification VisuTM).
                                                      Voir les copies d‟écran sur le TGM1 monitoring, VDM1 monitoring,
                                                      synthèse et SA, fournies dans Capture_ecran.zip
                                                      Conséquence : Etant donne que la valeur du HealthStatus n‟est pas
                                                      renseignée, les calculs ne sont pas déclenchés et on ne peut rien voir
                                                      sur les display.

                                                      Le fichier descripteur créé par le GMS estégalement fournis. Le context
          Non affichage des données Health Status,    opérationnel global sera fourni via FTP.                                                                                                             Corrigée par
    83322 Active Sensor et Current State                                                                                               Test - Test                C - Critical                             patch V1.1

                                                      1- Qd on active le freezing mode, il faudrait recopier le buffer courant
                                                      2 - Lorsqu'on bouge la "scrolling bar", il faudrait que l'affichage soit mis à
                                                      jour avec l'affichage correspondant à la date de la "scrolling bar".
                                                      Si on fait OK, l'outil doit rejouer les données de à partir de la date                       Recette                                                 Corrigée par
    83328 Freezing Mode                               sélectionnée et jusqu'à la fin du buffer enregistré.                           Accep - Accep usine          Ma - Major                               patch V1.2
                                                                                                                                                   Recette
    83329 Fuite mémoire                               Memory leak                                                                    Accep - Accep usine          Ma - Major
                                                                                        14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                      GMS 249300

                                                                                                                                                          Context                   Configurati   Entity in
Reference                      Title                                                      Description                                        Phase       reference    Criticality    on Item       charge     Comments

                                                          Les TMs emisent sont pris en comptes seulement si au moins une
                                                          fenêtre est ouverte en mode Temps réel.

                                                          Explication technique :
                                                          Actuellement, le "Channel" temps réel n'est pas créé à l'ouverture de
                                                          GMS. (Seul l'acquisition du flow temps réél tourne.).
                                                          Ce "Channel" est créé seulement à l'ouverture d'une fenêtre GMS(Sa ou
                                                          RDV).
                                                          Ce qui se traduit par un non calcul immédiat des TMs à l'ouverture d'une
                                                          fenêtre (SA ou RDV) alors que cela aurait pu avaoir lieu si le channel
                                                          temps réél avait été lancé plus tot! (cela est vrai au début. Si on recoit de
                                                          nouvelles données avec des dates différentes les calculs sont lancés.)

                                                          Les TMs émisent sont prises en comptes seulement si on appelle
                                                          tmReady(). Si on n'appelle pas tmReady(), cela se traduit par la non
                                                          mémorisation des données au niveau du ChannelManager (old, new,
                                                          previous).

                                                          Pour corriger cette FA, il faut créer un "Channel" Temps Réel à
                                                          l'initialisation de GMS (dans ChannelManager) et ne pas fermer ce                             Recette
    83330 Creation de Channel temps réel                  channel sauf lorsqu'on quitte l'application GMS                                 Accep - Accep usine        Ma - Major
                                                          La fenêtre de rejeu (dans laquelle on choisit la date de rejeu)peut etre
                                                          créée plusieurs fois.
                                                          Si l'utilisateur appuie n fois sur le bouton "Switch to Freezing Mode", la
                                                          fenetre pour la selection de la date de rejeu s'ouvre n fois!

                                                          Faire le nécessaire pour que cette fenêtre ne puisse être ouverte qu'une                      Recette                                               Corrigée par
    83331 Fenêtre de rejeu                                seule fois (grisé le bouton par exemple).                                       Accep - Accep usine        Ma - Major                               patch V1.1
                                                          Dans le fichier de configuration Appearance.xml, le label associé au
                                                          STR1 est : "Toto" ! Pourtant, dans l'écran SA, le label pour le STR1 est
                                                          bien STR1.

                                                          A quoi correspond alors ce Label ?

                                                            Si l'attribut "Label" du fichier de configuration permet bien de définir les
                                                            libellés des boutons pour les senseurs, ceci laisse à penser qu'il n'est
          Utilisation de l'attribut "Label" dans le fichier pas pris en compte dans le fichier de configuration, mais codé en dur
    83349 de configuration appearance.xml                   dans le code.                                                                Test - Test                 mi - minor
                                                            Dans les affichages alphanumériques des différents écrans GMS,
                                                            certains labels sont affichés en minuscule et d'autre en majuscule. Dans
                                                            VisuTM, les paramètres de type Enumérés sont tous affichés en
                                                            Majuscule. (voir copie d'écran Labels_majuscule-minuscule.jpg)
          Problème de casse pour l'affichage des
    83362 paramètres Enumérés                               Il faudrait uniformiser les affichages et tout afficher en Majuscule.        Test - Test                 mi - minor
                                                                                    14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                    GMS 249300

                                                                                                                                                    Context                   Configurati   Entity in
Reference                     Title                                                    Description                                       Phase     reference    Criticality    on Item       charge     Comments
                                                       Sur la fenêtre SA, même si la configuration est réglée sur un affichage
                                                       maximal de la fenêtre (180°; 90°), les labels en bordure de la fenêtre sont
                                                       coupés. Le problème arrive notamment pour le champ "Sunrise" pour
                                                       lequel les secondes sont difficiles à lire.

                                                       Lorsque le soleil et la lune se trouvent en bordure de la fenêtre, le label
                                                       est également coupé.

                                                     Il faudrait faire en sorte que les labels ne soient pas coupés en bordure
          Problème d'ergonomie pour la fonction SA : de fenêtre.
          labels Sunrise et Moon coupés en bordure
    83405 de fenêtre                                 Voir copie d'écran SA_labels_coupes.jpg                                         Test - Test               mi - minor


                                                       Lors du test effectué, auncune TM ISS n'était reçue.

                                                       Le problème suivant est apparu :
                                                       - Au début du test, les paramètres GNC_RGPS_POS_EST_LVLH_1,2,3
                                                       sont reçus avec pour valeurs 0. Sur l'écran RDV Synthesis, la valeur
                                                       RGPS distance apparaît avec la valeur 0. Etant donné que l'attitude ISS
                                                       n'est pas reçue (et n'a jamais été reçue), le calcul du RGPS distance ne
                                                       devrait pas se déclencher et la cellule devrait rester grisée.

                                                       - Plus tard dans le test, les paramètres
                                                       GNC_RGPS_POS_EST_LVLH_1,2,3 sont reçus avec des valeurs
                                                       cohérentes (voir écran AR_RGPS.jpg), le premier paramètre étant de
                                                       l'ordre de 36km. Sur l'écran RDV Synthesis, la valeur RGPS distance est
                                                       toujours à 0. La valeur n'est donc plus cohérente avec les données
                                                       reçues.

                                                       Pour le calcul de cette donnée :
                                                       - soit aucune donnée ISS n'est nécessaire et alors le calcul doit se faire
                                                       systématiquement avec les valeurs GNC_RGPS_POS_EST_LVLH...
                                                       reçues
          Problème pour le calcul de la RGPS           - soit l'attitude ISS est nécessaire et dans ce cas, si l'attitude ISS n'a
    83406 distance                                     jamais été reçue, le calcul ne doit pas être déclenché, même au début.        Test - Test               mi - minor
                                                                                      14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                  GMS 249300

                                                                                                                                                    Context                   Configurati   Entity in
Reference                      Title                                                    Description                                      Phase     reference    Criticality    on Item       charge     Comments
                                                         Les valeurs des champs "Validity Status" des fenêtres RDV VDMi et RDV
                                                         TGMi ne sont pas identiques à celles visualisées dans VisuTM. Elles
                                                         restent figées à "Valid" pour VDM et "Unvalid" pour TGM quelle que soit
                                                         la valeur du paramètre mentionné dans le tool tip.

                                                         Voir les copies d'écran fournies :

                                                         - AR_validity_flags_TGM :
                                                         Dans GMS, le champ "Meas. validity status" est "Unvalid" et pointe sur le
                                                         paramètre TGM_MEAS_IS_OK.
                                                         Dans VisuTM, le paramètre TGM_MEAS_IS_OK est
                                                         "ENUM_BOOLEAN_FALSE"

                                                         - AR_validity_flags_VDM :
                                                         Dans GMS, le champ "Meas. validity status" est "Valid" et pointe sur le
                                                         paramètre VDM_RANGE_LOS_MEAS_IS_OK.
                                                         Dans VisuTM, le paramètre VDM_RANGE_LOS_MEAS_IS_OK est
                                                         "ENUM_BOOLEAN_FALSE"

                                                         - AR_validity_flags_true:
                                                         Dans GMS RDV TGM1, le champ "Meas. validity status" est "Unvalid" et
                                                         dans VisuTM, le paramètre TGM_MEAS_IS_OK est
                                                         "ENUM_BOOLEAN_TRUE"
                                                         Dans GMS RDV VDM1, le champ "Meas. validity status" est "Valid" et
                                                         dans VisuTM, le paramètre VDM_RANGE_LOS_MEAS_IS_OK est
                                                         "ENUM_BOOLEAN_TRUE"

          Affichage incorrect des valeurs des validity La valeur du champ "Meas. validity status" doit être lue telle qu'elle arrive
          status pour les fenêtres VDM RDV et TGM dans le flux TM.                                                                                                                                      Corrigée par
    83407 RDV                                                                                                                        Test - Test               Ma - Major                               patch V1.1
                                                       Il est difficile d'accéder aux boutons "OK" et "Cancel" de la fenêtre
                                                       "Configuration/General", car lorsque l'on positionne la souris sur ces
                                                       boutons, les tool tip associés se superposent au bouton et on n'a plus la
                                                       possibilité de cliquer dessus.

                                                    Il faudrait agrandir un peu la fenêtre de façon à ce que les tool tips qui
          Ergonomie pour la fermeture de fenêtre de s'affichent ne se superposent pas sur les boutons et ne bloquent pas                                                                                Corrigée par
    83408 "Configuration/General"                   l'accès à ceux-ci.                                                               Test - Test               mi - minor                               patch V1.2
                                                    Avant ouverture de la fenêtre "Configuration/General", les senseurs
                                                    VDM1, VDM2, TGM1 et TGM2 sont désactivés sur l'affichage SA. Seuls
                                                    STR1 et STR2 sont activés.

                                                         Si on ouvre la fenêtre "Configuration/General" et que l'on modifie ou non
                                                         des paramètres de configuration, lorsque l'on ferme la fenêtre, tous les
                                                         senseurs sont à nouveau réactivés sur la fenêtre SA.

          Impact de l'ouverture/fermeture de la          Dans la mesure où cette fenêtre n'intervient pas dans la sélection ou non
          fenêtre "Configuration/General" sur la         des senseurs, il ne faut pas que son ouverture/fermeture modifie                                                                               Corrigée par
    83409 sélection des senseurs pour l'affichage SA     l'affichage en cours.                                                     Test - Test                 mi - minor                               patch V1.1
                                                                                    14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                               GMS 249300

                                                                                                                                               Context                   Configurati   Entity in
Reference                      Title                                                   Description                                  Phase     reference    Criticality    on Item       charge     Comments
                                                       Le label ISS est systématiquement affiché sur l'affichage SA, même si
                                                       aucune données ISS n'a été reçue. Le label se situe alors en bordure de
                                                       fenêtre, tantôt en bas, tantôt sur le côté. Cet affichage peut être source
                                                       d'erreur pour un utilisateur.
          Affichage du label ISS sur le display SA
          même si les données ISS ne sont pas        Lorsque la position de l'ISS n'a jamais été reçue par GMS, il ne faut pas
    83410 reçues                                     afficher le label ISS sur le display SA.                                   Test - Test               Ma - Major
                                                     Lors du tests RDV du 20/02 où des TM ISS et ATV étaient correctement
                                                     reçues par GMS, la distance RGPS calculée est restée à 0 tout au long
                                                     du test, même lorsque les données TM RGPS avaient des valeurs
          La valeur de la distance RGPS calculée est cohérentes (voir copie d'écran) et que tous les paramètres de position                                                                        Corrigée par
    83567 toujours à 0                               ATV et ISS étaient reçus.
                                                     Le passage en freezing mode sur les fenêtres SA et RDV se comporte         Test - Test               Ma - Major                               patch V1.2
                                                     de façon bizarre :
                                                     - pour le SA, si la période accessible par freezing mode est, par exemple,
                                                     23:30:52 à 00:22:11 et que l'on choisit de remonter à 00:00:00, alors la
                                                     date du freezing mode commence à 23:30:52 et essaye de rattraper
                                                     rapidement la date de 00:00:00 (en augmentant la date de 1 min toutes
                                                     les secondes environ). Dès que la date atteint 00:00:00, le défilement
                                                     des données reprend une fréquence conforme au temps réel.

                                                       - pour les fonctions RDV, le passage en freezing mode se positionne bien
                                                       à la date demandée, mais on observe des oscillements de la date de
                                                       freezing mode avec des retours dans le passé.
                                                       Ex : Il est 05:09. On donne une date de freezing mode à 04:36. Dans le
                                                       freezing mode, on remonte bien à 04:36 puis le temps défile à la
                                                       fréquence du temps réel, mais on a des retours en arrière très courts à
                                                       03:30, puis on revient à une date correcte de freezing mode, puis on
                                                       repart à nouveau en arrière à 04:30. L'oscillation arrête lorsque l'on a
                                                       suffisamment fait de freezing mode pour que la date dans le passé
                                                       dépasse la date que l'on a spécifié comme début de freezing mode                                                                            Corrigée par
    83568 Mauvais fonctionnement du freezing mode      (04:32 pour l'exemple).                                                  Test - Test               Ma - Major                               patch V1.2


                                                       Dans le bandeau GMS, la fonction SA est noté : "Situational Awarness";
                                                       Dans le titre de la fenêtre, la fonction est notée "Situational Awareness"
                                                                                                                                                                                                   Corrigée par
    83569 Erreur sur le libellé de la fonction SA      Le libellé correct est : "Situational Awareness"                         Test - Test               mi - minor                               patch V1.2
                                                       Dans les fenêtres RDV (notamment TGM et VDM), si on agrandit la taille
                                                       de la fenêtre alors qu'un zoom a été fait sur les graphiques, on perd le
                                                       zoom et le zoom initial est ré-appliquer.

          Perte du zoom lors du redimensionnement      Il faudrait garder les paramètres de zoom lorsque l'on redimensionne une
    83570 d'une fenêtre                                fenêtre.                                                                 Test - Test               mi - minor
                                                                                      14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                        GMS 249300

                                                                                                                                                        Context                     Configurati   Entity in
Reference                     Title                                                  Description                                            Phase      reference      Criticality    on Item       charge     Comments
                                                        Le bouton "ISS Hole" a un comportement incohérent.

                                                        Lors de l'utilisation de l'outil pour l'essai JIS EtE, plusieurs
                                                        comportements ont été observés :
                                                        - au début, les paramètres de TM ISS n'étaient pas tous reçus (les
                                                        paramètres PosX, PosY et VelX étaient reçus tandis que les PosZ et
                                                        VelY et VelZ n'étaient pas reçus). Le Warning "ISS Hole" clignotait (tantôt
                                                        allumé, tantôt éteint)
                                                        - ensuite, les paramètres ISS nécessaires au GMS n'étaient plus du tout
                                                        reçus et le voyant continuer de clignoter, alors qu'il aurait dû rester
                                                        allumer en permanence. (voir AR_pas_donnees_ISS.jpg) Dans ce cas, la
                                                        valeur du retard entre TM ATV et TM ISS était toujours du même ordre
                                                        de grandeur.

                                                        Ce comportement n'est pas cohérent avec la présence ou non de TM
                                                        ISS nécessaire au GMS.

                                                        De façon à être clair sur le fonctionnement de l'outil, il faut expliquer la                  JIS ETE
    83654 Clignotement du Warning "ISS Hole"            méthode de détection d'un trou TM ISS dans le Manuel utilisateur.               Test - Test   11/04/2007     Ma - Major
                                                        Un bouton permet de passer des fenêtres VDM1 ou VDM2 monitoring à
                                                        la fenêtre VDM Roll Calibration.

                                                        Si la fenêtre VDM Roll Calibration n'est pas encore ouverte, le bouton
                                                        permet effectivement l'ouverture de la fenêtre.

                                                      Par contre, si la fenêtre VDM roll Calibration est déjà ouverte et à été
                                                      réduite, le fait d'appuyer sur le bouton dans la fenêtre VDM1 (ou VDM2)
          Passage d'une fenêtre VDM Monitoring à      Monitoring ne fait rien. Cette action devrait agrandir la fenêtre VDM Roll                      JIS ETE                                                 Corrigée par
    83655 celle VDM Roll Calibration                  Calibration déjà ouverte.                                                         Test - Test   11/04/2007     Ma - Major                               patch V1.2
                                                      Lorsque la courbe atteint la fin de l'échelle de temps, la courbe repart
                                                      complètement à gauche. Il avait été demandé dans la fiche de dialogue
          Scroll Automatique sur les affichages de la 31 que les mêmes mécanisme que VisuTM soit implémentés, avec un                                 JIS ETE
    83656 fenêtre VDM Roll Calibration                décalage d'1/2 durée vers la gauche par défaut.                                   Test - Test   11/04/2007     Ma - Major
                                                      Le bulletinB IERS devra être mis à jour régulièrement.
                                                      Chaque bulletin à une nomenclature différente.

                                                        Si dans le répertoire configuration/resources/orekit, plusieurs bulletinB
                                                        sont fournis (même portant des noms différents), l'ouverture de GMS
                                                        provoque une erreur fatale (voir copie d'écran). Cette erreur demande de
                                                        fermer l'outil. Cependant, le bouton Exit de l'outil est sans effet: on ne
                                                        peut ni fermer l'application GMS, ni fermer le M&C. Il faut faire un arrêt
                                                        de l'application M&C sur le gestionnaire des tâches pour pouvoir tout
                                                        débloquer !

                                                        Il faut que l'erreur rende la main sur la fermeture de l'outil et encore plus
                                                        sur celle du M&C !

                                                        De plus, il faudrait préciser dans la Manuel d'Installation qu'un seul fichier SysVal -
          Plantage de l'outil et du M&C si deux         bulletinB doit être présent dans le répertoire orekit.                         System         Installation
    83657 bulletinB IERS sont présents                                                                                                 Validation     v1.1           Ma - Major
                                                        Le bouton "OK" de la fenêtre "Configuration/General" ne marche pas.
                                                        Que l'on ait fait ou non des mofifications sur les apparences des              SysVal -
          Le bouton "OK" de la fenêtre                  senseurs, le bouton est sans effet. Il faut faire "Cancel" pour réussir à      System         Installation                                            Corrigée par
    83658 Configuration/General est sans effet          sortir de la fenêtre.                                                          Validation     v1.1           Ma - Major                               patch V1.2
                                                                                    14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                     GMS 249300

                                                                                                                                                   Context                     Configurati   Entity in
Reference                    Title                                                  Description                                        Phase      reference      Criticality    on Item       charge     Comments
                                                      Si on change la couleur associée aux VDM par l'interface
                                                      "Configuration/General/Appearance", la modification n'est pas pris en
                                                      compte dans la fenêtre "VDM Roll Calibration".
                                                      Les courbes blanc sur gris sont illisibles.
          Le changement des couleurs du VDM n'est                                                                                  SysVal -
          pas pris en compte dans la fenêtre "VDM Si la couleur est modifiée directement dans le fichier Appearances.xml, la       System        Installation                                            Corrigée par
    83659 Roll Calibration"                       modification est bien prise en compte.                                           Validation    v1.1           Ma - Major                               patch V1.2
                                                  Toute modification des apparences senseurs par la fonction
                                                  "Configuration/General/Appearance" vide le fichier Appearance.xml (0 ko
                                                  après la modification!)! Si on ferme le GMS et qu'on le rouvre, tous les         SysVal -
                                                  senseurs sont en bleus et les labels pour le soleil, la lune et la terre,        System        Installation                                            Corrigée par
    83660 RAZ du fichier Appearance.xml           inexistants.                                                                     Validation    v1.1           C - Critical                             patch V1.2
                                                  Sur la partie Appearance, si on change par exemple la couleur du VDM
                                                  (en cyan) et que l'on fait "Apply", la nouvelle couleur est tout de suite
                                                  prise en compte sur la fenêtre en arrière-plan. Si on ferme la fenêtre
                                                  Configuration, la couleur est bien active. Si on rouvre la fenêtre
                                                  Configuration/General, la couleur cyan est bien présente dans l'onglet
                                                  Appearance.

                                                      Si par contre, on change les données du SA Angle, en remplaçant 180
                                                      par 100, que l'on fait Apply, puis fermeture de la fenêtre de Configuration,
                                                      puis qu'on la rouvre, alors la modification n'a pas été sauvegardée. Le
          Comportement incohérent du bouton           180 est remis par défaut.                                                    SysVal -
          "Apply" de la fonction                                                                                                   System        Installation                                            Corrigée par
    83661 "Configuration/General"                     Idem pour le SAA (les modifications ne sont pas prises en compte)            Validation    v1.1           Ma - Major                               patch V1.2
                                                      L'affichage du retard entre la TM ATV et la TM ISS est curieux.

                                                      Il faut préciser dans le Manuel Utilisateur la manière dont est calculé ce
                                                      retard (sur quel(s) paramètre(s) se base-t-il ?).
                                                      En effet, lors du test JIS EtE, les paramètres ISS de positions de l'ISS
                                                      étaient reçus avec une date erronée.
                                                      Les paramètres ATV étaient datés au 01/05/2007, tandis que les
                                                      paramètres ISS l'étaient au 11/04/2007. Les heures, elles étaient
                                                      cohérentes. La valeur du retard ATV-ISS affiché était de l'ordre de
                                                      quelques secondes (3-4 ou 5s). Ce retard prenait également parfois la
                                                      valeur 1,72 E6, ce qui correspond à la différence de 20 jours entre les
                                                      deux dates. Mais en règle général, le retard était de quelques secondes.
                                                      Comment sont calculées ces quelques secondes d'écart ?

                                                      De plus, après la date du 01/05/2007 05:48:00, les TM ISS sur les
          Calcul du retard entre la TM ATV et la TM   positions ne sont plus reçues par le M&C. Le retard affiché est pourtant                   JIS EtE                                                 Corrigée par
    83666 ISS                                         de -6s...                                                                    Test - Test   11/04/2007     Ma - Major                               patch V1.2
                                                      La variable delay.atv.iss du fichier de configuration
                                                      generalconfiguration.properties est positionnée à 3000ms.

                                                      Lors du test JIS EtE, si le retard affiché était de 4s, le warning ne
                                                      s'allumait pas. Pour des valeurs à 1,7E6, il s'allumait.

                                                      De plus, si le retard entre la TM ATV et la TM ISS était de -6s, le
                                                      Warning ne s'est pas allumé pas non plus. (voir copie d'écran
          Cohérence entre l'activation du Delay       AR_pas_donnees_ISS.jpg) Le delta paramétrable doit être appliqué sur                       JIS EtE                                                 Corrigée par
    83667 Warning et la valeur du retard ATV-ISS      la valeur absolue du retard et non sur sa valeur.                            Test - Test   11/04/2007     Ma - Major                               patch V1.2
                                                                                    14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                       GMS 249300

                                                                                                                                                      Context                    Configurati   Entity in
Reference                    Title                                                     Description                                         Phase     reference     Criticality    on Item       charge     Comments
                                                      Dans le menu RendezVous, si on sélectionne une fenêtre déjà ouverte,
                                                      mais réduite, rien ne se passe.
                                                      Pour les deux onglets de la fenêtre "VDM Roll Calibration", les libellés                       JIS EtE                                               Corrigée par
    83668 Activation des fonctions RDV                des graphiques fenêtre soit activée et agrandie.
                                                      Il faudrait que lane correspondent pas au paramètre TM qu'ils                    Test - Test   11/04/2007   mi - minor                               patch V1.2
                                                      représentent. Le titre des graphiques doit être le nom du paramètre de
                                                      TM tel qu'il arrive par la MDB ou tel qu'il est défini dans l'algorithme de
                                                      calibration, car ces libellés sont plus parlants pour l'utilisateur.

                                                      Pour la courbe qui trace la différence entre le Rollout et le Rollin, le titre
                                                      doit être : "Nom du paramètre VDMi RollOut - Nom du paramètre VDMi
                                                      RollIn)

                                                      Avec le contexte du JIS EtE, on aurait dû avoir :
                                                      Pour le premier onglet :
                                                      graphe 1 : VDM_ROLL_CALIBRATION_DER
                                                      graphe 2 : VDM_WHICH_IS_ACTIVE
                                                      graphe 3 : VDM_ATTITUDE_MEAS_IS_OK

                                                      Pour le second onglet :
                                                      graphe 1 : VDM1_VALIDITY_FLAG & VDM2_VALIDITY_FLAG
                                                      graphe 2 : VDM1_TTRA_REFT_MEAS & VDM2_TTRA_REFT_MEAS
                                                      graphe 3 : VDM1_TTRA_SYNTDEF_AVAILROLLOUT &
                                                      VDM2_TTRA_SYNTDEF_AVAILROLLOUT
                                                      graphe 4 : VDM1_TTRA_SYNTDEF_AVAIL_ROLLIN &
                                                      VDM2_TTRA_SYNTDEF_AVAIL_ROLLIN
                                                      graphe 5 : (VDM1_TTRA_ROLLOUT_MEAS –
                                                      VDM1_TTRA_ROLLIN_MEAS) & (VDM2_TTRA_ROLLOUT_MEAS –
                                                      VDM2_TTRA_ROLLIN_MEAS)
                                                      graphe 6 : VDM1_TTRA_ROLLOUT_MEAS &
                                                      VDM2_TTRA_ROLLOUT_MEAS
                                                      graphe 7 : VDM1_TTRA_ROLLIN_MEAS &
                                                      VDM2_TTRA_ROLLIN_MEAS

                                                                                                                                                     JIS EtE
    83671 Libellés des courbes VDM Roll Calibration                                                                                    Test - Test   11/04/2007   mi - minor
                                                                                     14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                     GMS 249300

                                                                                                                                                     Context                    Configurati   Entity in
Reference                     Title                                                    Description                                        Phase     reference     Criticality    on Item       charge     Comments

                                                        Deux GMS ont été lancés sur deux machines MCW différentes,
                                                        connectées au même flux de TM.
                                                        Les deux GMS ont été lancés au moment du passage en S3, donc bien
                                                        avant le déclenchement de l'algorithme.

                                                        Un des GMS a été lancé avec l'option Trace et l'autre sans Trace.

                                                        Les résultats obtenus surles deux MCW sont différents, alors qu'ils sont
                                                        censés recevoir les même paramètres de TM. Le nombre de points sur le
                                                        GMS "avec trace" est de 150, alors que le GMS "sans trace" obtient 160
                                                        points.

                                                        Le contexte utilisé, ainsi que les traces obtenues sur le GMS avec trace
                                                        seront fournies avec l'anomalie.

                                                        Une extraction sur le Data Handling a également été réalisée afin de
                                                        vérifier les paramètres reçus et stockés par le M&C. La comparaison de
                                                        ces extractions avec les traces GMS a montré que certains paramètres
                                                        ne sont pas stockés dans les traces alors qu'ils sont présents sur le M&C
                                                        (paramètre VDM1_TTRA_ROLLIN_MEAS par exemple).

                                                        L'analyse des paramètres du DH montre que 198 points auraient dû être
                                                        obtenu à l'issue de l'algorithme.
          Résultats de l'algorithme de calibration en                                                                                               QO RDV
    83894 roulis différents entre deux MCW                                                                                            Test - Test   25/05/2007   C - Critical
                                                        Si on lance une impression d'une des fenêtre de GMS, en gardant les
                                                        paramètres définis par défaut sur l'imprimante, une erreur sur
                                                        l'imprimante se produit (voir AR_print.jpg). L'erreur se produit quelle que
                                                        soit la fenêtre utilisée pour l'impression.

                                                        Si dans les paramétrages de l'imprimante, dans l'onglet Layout, on coche
                                                        "Zoom Options", alors l'impression fonctionne sans problème. (voir
                                                        Param_print.jpg)

                                                        Cette erreur n'apparaît pas pour les autres plug-in du M&C (notamment
          Erreur lors du lancement de la fonction       les quick pages VisuTM qui pointent pourtant sur le même paramétrage                        QO RDV
    83895 Print                                         d'imprimante)                                                            Test - Test        25/05/2007   Ma - Major
                                                        L'ordre des icônes permettant l'accès aux différents plug-ins du M&C est
                                                        différent entre les MCW où le GMS est installé et ceux où il n'est pas
                                                        installé.

                                                        Ceci peut être génant pour des utilisateurs qui ont l'habitude d'un ordre
                                                        donné. Il faut que l'icône du GMS soit située après l'ensemble des icones
                                                        existantes, de façon à ne pas modifier l'ordre.
          Ré-ordonnement des icônes du MCW lors                                                                                                     QO RDV
    83896 de l'installation de l'outil GMS              Voir copies d'écran fournies en pièces attachées.                             Test - Test   25/05/2007   mi - minor
                                                                                   14b7ba51-e8a7-49cb-bf34-3ca4c4df472b.xls                                                                   GMS 249300

                                                                                                                                                  Context                   Configurati   Entity in
Reference                     Title                                                   Description                                      Phase     reference    Criticality    on Item       charge     Comments
                                                      Lors du lancement de l'application GMS, une fenêtre demande de choisir
                                                      le port UDP sur lequel on veut se connecter.
                                                      Si on clique sur "Cancel" pour annuler le lancement de l'application, un
                                                      message d'erreur s'affiche disant qu'aucun port n'a été sélectionné (voir
                                                      copie d'écran). Il n'y a aucun moyen pour fermer la fenêtre si ce n'est de
                                                      se connecter à un des ports, donc attendre que l'outil charge le contexte,
                                                      puis de le fermer par la fonction "Exit".
                                                                                                                                   SysVal -
          Impossibilité d'annuler la connexion à un   Le bouton "Cancel" devrait permettre d'abandonner le lancement de            System
    83989 port UDP                                    l'application et fermer le plug-in GMS.                                      Validation                mi - minor

                                                      En Freezing mode, le retard entre les paramètres ATV et les paramètres
                                                      ISS n'est pas calculé. Le warning "Delay" ne s'affiche pas non plus.
                                                                                                                                   SysVal -
          Non calcul du retard ATV-ISS et de la       Le paramètre "delay" se fige à la valeur qu'il avait au moment où le         System
    84096 gestion du Warning en freezing mode         freezing mode a été lancé.                                                   Validation                mi - minor
                                                      The "Threshold" and "NbMeasMin" parameters of the VDM Roll
                                                      Calibration algorithm are not available in the configuration file. They have
                                                      been hard coded.

                                                      However, it was detailed in the RfC 82312 that their values were TBC.
          Adjustment of the Threshold and                                                                                          SysVal -
          NbMeasMin parameters of the VDM Roll        It is necessary to have access to these data if the values have to be        System
    84100 Calibration Algorithm                       adjusted.                                                                    Validation                mi - minor
                                                      When the snapshot function is activated in GMS tool, the user is able to
                                                      choose the name of the snapshot and the extension (bmp, png, jpg...).
                                                      The default extension is .bmp.

                                                      If the user enters a name and then changes the extension, the previously
                                                      given name is lost. The choose of the extension should not erase the
          Ergonomy : Definition of the name of a      name entered by the user.
    84102 snapshot file                                                                                                            Test - Test               mi - minor

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:152
posted:7/3/2011
language:English
pages:109