Instrument Status
• On/Off Cycle: 26
• Hours On: ~47000 hours
– Continuously on since 1/15/2005 (probe relay)
• HDAC Filament Modulation:
– Filament 1: 97.28 hours (including T9)
– Filament 2: 12.22 hours
UVIS TEAM MEETING 1/2006
1
FSW Status
• ISA Z70771
– Fixed by FSW patch in C24
– Fixed by FSW V1.3 starting C31
• ISA Z86939 (bad EUV data in S11 icylon)
–
–
–
–
Probably FSW problem
Affects all icylon in S11 and the first icylon in S12
Workaround by updating the instrument setup
No progress since last team meeting
UVIS TEAM MEETING 1/2006
2
GSW Issues
• No new ground software problem
– Still need to re-ingest in DAPS data affected by
report # 38 (EUV and HDAC records are
coalesced in DAPS)
UVIS TEAM MEETING 1/2006
3
Operational Issues
• No new operational issues
• Data is partially zeroed
– Not enough time left between end of last
integration and next trigger
– We have developed a program to identify and
minimize trigger/integration timing issues
UVIS TEAM MEETING 1/2006
4
Planning/Sequencing Issues
• No new Planning/Sequencing issues.
• When a setup is not defined we re-use an
old setup from a similar type of activity.
UVIS TEAM MEETING 1/2006
5
New Products - HSP timing file
• HSP timing file
– Provides HSP timing to the resolution of the HSP integration
time
– File automatically generated when HSP data is archived
– Files are posted on the UVIS team site at
http://lasp.colorado.edu/cassini/team-site/operations_planning/hsp_data/
- It is a comma-delimited file
- The format is described a top of each.file There is also a
readme.txt file in the directory
- Josh has developed S/W to process it
UVIS TEAM MEETING 1/2006
6
HSP Timing file
First measurement after
first RTI0 since creation
of the packet
First measurement in a
packet (i.e in a record)
Time of the packet is xxxxxx.ddd
(where xxxxxxx is the integer
part of the SCLCK)
UVIS TEAM MEETING 1/2006
Time is xxxxxx + 1 0/+ HSP integration
time
7
HSP timing file
• The HSP timing file provides the time at the start
of each packet (xxxxxx.yyy) and the position
within the packet of the first measurement after
xxxxxx + 1 (xxxxxx is the integer part of the
SCLK)
• You can derive the time of each measurements in
the packet knowing the integration time.
• One packet = one DAPS record in DAPS file.
accessing: HSP2005_349_20_06_55_UVIS_019IC_IMPACT004_PRIME
% Loaded DLM: NCDF.
Data stored in array "data":
Record size:
945
Number of records: 2314
UVIS TEAM MEETING 1/2006
8
Notes on DAPS IDL routines
• The accuracy of the SCLK to SCET conversion
depends on which version of convert_sclk.pro is
used.
• Currently you should be running version 1.12
(which follows the latest version of the spacecraft
clock conversion file - SCLKSCET.00095)
• The convert_sclk.pro version number is at the top
of the file
;
;$Header: /cassini2/uvis_fm/daps_tools/RCS/convert_sclk.pro,
v 1.12 2005/12/30 03:34:16 uvis_fm Exp $
;
UVIS TEAM MEETING 1/2006
9
Notes on DAPS IDL routines
• Josh has developed a new version of
convert_sclk.pro that relies on the ICY DLM
library and directly access your current spacecraft
clock kernel (cas00095.tsc)
• Under this solution you are responsible for
updating the spacecraft clock kernel.
• ICY DLM needs to be installed on your
workstation or laptop.
UVIS TEAM MEETING 1/2006
10