[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fwd: GOES-10 Sacnline Modification]]



SSEC has been notified of the following:

This is a 'heads up' to try and let concerned parties know of an
upcoming GVAR test at the CDA/Wallops soon which will be perfomed to
verify a good bug fix for their GOES Sensor Processing System (SPS)
software.  The bug fix deals with correcting errors in the GOES-8 &
GOES-10 scanline startup values in the SPS displays.  CDA/Wallops will
apply this code fix (which is believed to be transparent to GVAR users)
at the 15:50 Z Housekeeping period on Tuesday, March 14th.  They'd like
to have users monitor the ingest to ensure that this upgrade truly is
transparent at the user end.

Please see the email below for further information.



---------------------- Forwarded by Barbara C Hickman/PRC/ssd/US on
03/09/2000 04:11 PM ---------------------------


"William Speidel" <address@hidden> on 03/09/2000 03:58:13 PM

To:   Barbara C Hickman/PRC/ssd/US
cc:
Subject:  GOES-10 Sacnline Modification

                       SPS Scan Line Modification

The subject scan line problem was first noticed during SPS 4.2 S/W
testing (See SPS Monitor Console/r.status display/scan line/near bottom
left).  It seems that when an SPS is initialized, "iofnsi" is computed
based upon the S/C configured at startup.  The current SPS S/W version
does not recompute "iofnsi" when a CONFIG or RECOVER command is
executed.  So if a RECOVER command is used to change the configured
S/C, "iofnsi" would be incorrect (this bug only effects GOES-10;
Yaw-Flip mode only).  This has not created a problem in the past
because it only effects the scan line displayed in the SPS.  GVAR is
not effected (based our tests results).  To prove this, two SPS's were
set up, one with the correct "iofnsi" and the other with the incorrect
value.  GVAR from both SPS's was ingested by two parallel PM's.  The
top scan line (empty space NW and NE of the earth) of an IR and a
visible image was compared on both PM's.  They each had the same line
number.  Also, using the same SPS/PM configuration, the following GVAR
parameters were compared:

   RISCT =  Relative output scan sequence count since start of frame
   AISCT =  Absolute number of the current output scan
   INSLN =  Number of the northern-most visible detector scan line in
            the current scan
   INFLN =  Number of the northern-most visible detector scan line in
            the current frame
   ISFLN =  Number of the southern-most visible detector scan line in
            the current frame
   IMDLN =  Number of the scan line corresponding to an instrument
            elevation of 0 degrees
   IMDCT =  Number of the output scan corresponding to an instrument
            elevation of 0 degrees
   IGVLM =  Number of the visible detector scan line which intersects
            the sub-satellite point

No differences were found in GVAR.  The difference seen at the SPS is
approximately 371.



------
SSEC Data Center            Email:  address@hidden
UW Madison                  Web:    http://www.ssec.wisc.edu/datacenter
1225 W. Dayton              Phone:  (608) 262-0502
Madison, Wisconsin 53706    Fax:    (608) 263-6738