01/05/10UVIS TEAM MEETING OPERATIONS UPDATE UVIS TEAM MEETING OPERATIONS UPDATE

01/05/10UVIS TEAM MEETING OPERATIONS UPDATE Instrument Status On/Off Cycle: 27 –No change since last meeting Hours On: ~81,750 hours –Continuous operations since 9/11/2007 –Current longest continuous operations is from 1/15/2005 (probe relay) to 9/11/2007 (S/C safing) HDAC Filament Modulation: –Filament 1: hours –Filament 2: hours –Last: 2006/255 –Next: H filament only 1/28/2010 (T66)

01/05/10UVIS TEAM MEETING OPERATIONS UPDATE Significant Issues S52UVIS_116RI_BETPER001_ISS deleted from the sequence by SP. Recovered via mini-sequence but data volume taken from UVIS_116ST_URALPVIR002_PRIME ISA Z93945 – Need to verify sequence prior to implementation. S55UVIS_123SA_MOS122APO009_PRIMELost due to weather. S55UVIS_122SA_MOS122APO003_PRIME UVIS_123SA_MOS122APO008_PRIME Lot of drops. Data ingested around the major data drop periods. S55UVIS_123SA_MOS122APO007_PRIME UVIS_123IC_ALPVIR001_PRIME Lot of drops spread all over. Be careful when using these datasets.

Significant Issues In S54 we refused to approve a waiver of FR84B2 (UVIS boresight to sun flight rule) without an analysis of the occultation timing by the Nav team –Seems to have raised the issue of margin in Solar occultation to a higher level –For this particular case the VIMS design was modified to add 7 minutes of padding 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE

01/05/10UVIS TEAM MEETING OPERATIONS UPDATE First Time Events S54: First use of the UVIS_SOL_OFF boresight for solar occultation –T62 ( ) UVIS_119SU_USUNOCC001/2_PRIME S60: First off-axis star occultation using the FUV occultation slit –T70 ( ) UVIS_133ST_ALPVIRTI001_PRIME –Set up tested in S54 (off by 1 pixel) and in S59

Rbot Issues The AACS team solves the Rbot issues by adding a rotation around the primary pointing axis –AACS used to give only an offset around Y –UVIS has always requested an RA/DEC equivalent for the secondary (mosaic) It took a while for AACS and UVIS to understand each other We seem to be Ok now –Which method to use depends on the request as the results are different 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE

Rbot: Titan Mosaic Example 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE Original design. AACS requested a 20 deg rotation. RA/DEC equivalentSimple rotationRotation with Z offset compensation

Rbot: System Scan Example 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE Original Design AACS requested a 20 deg rotation RA/DEC equivalent Simple rotation Note: Timing change if rotation is large

Rbot: Workload Impact The impact of Rbot on the ops team workload is highly variable: –S55: 1 request out of 18 had to be modified –S56: 4 requests out of 11 –S57: 1 request out of 14 –S58: 9 requests out of 20 8 of the 9 requests used an “rbot-friendly” secondary –S59: 1 request out of 7 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE

Data Distribution Issue Licensing issue with Sybase –Lab wide issue –May have to switch DB provider – Timeliness of data availability may be affected for a while –See Dave Judd presentation… 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE

XXM Process (SIP) 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE XMXXMChange Execution5W10W+5W Total Development93d78d-15d Pointing Designs (port 1)~21d13d-8d Pointing Designs (port 2)10d9d-1d Rbot analysis22d29d+7d Sequence Dev43d30d-13d Prime/rider coordination and other science driven pointing must be complete at the end of port 1 The staffing profile and SIP probably cannot support XM intensity science

Templates? What are the characteristics of a template? –#1 Same duration (or a multiple of… ) Constant allocation for turn time –#2 Pointing design independent of the viewing geometry –#3 Same SSR allocation #1 & #2: Re-use of a PDT template # 3: Re-use of an IEB Currently the nearest thing to a template we use is the instrument calibration 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE

By The Way…. The calibration template is 3 hours long and is used about once every 5 weeks –You would expect that nobody would dare temper with this template! In S55 it was changed to a 2 hours segment and a 1 hour segment –2 + 1 is not equal to 3 This is useless. If you cannot leave a calibration request alone remove it! 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE

What Can Help Our Workload We have not shown that we cannot develop XXM sequences Pseudo templates do not help –But guidelines that would take into account the duration and geometry variations are helpful Clean CIMS requests –No rider request overlapping multiple prime requests 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE

What Can Help Our Workload Clean CIMS requests (con’t) –Matching start time & duration between the prime & the rider request –Correct SSR allocation Make sure that what you are requesting is feasible or has a chance to give usable data –FR84B2 violation –Dust crossing period Don’t overreach 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE

Data Volume Reduction Spectral windowing –See ISA Z86939 Increase integration time (prime request) Spatial windowing (remove pixels outside the target - for prime request only?) Remove HDAC (except for IPH survey) Targeted trigger (rider request) 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE

Sequence Utilization Ratios: Prime Mission vs. Equinox Mission to Date SEQCAPSCDACIRSINMSISSMAGMIMIRADARRPWSUVISVIMS S S S S S Last 5 Seq. Avg SEQCAPSCDACIRSINMSISSMAGMIMIRADARRPWSUVISVIMS S N/A S N/A S S S S S S S XM Average

IEB Generation Process Assign IEB number TOL/ CIMS Edit IEB generation script Generate IEB load Load cmd De-assemble load cmd Verify Inst. Set-up Three types of IEB: Pre-loaded: Commonly used instrument setup: already in the IEB generation script Tour Library: Less commonly used instrument setup: IEB script-ready & requires edition of the IEB generation script Specific to a sequence: New or rarely used instrument setup: requires the development of an instrument setup script & edition of the IEB generation script & validation manual automated

Trigger Generation Process Extract pointing code Run PDT on each prime Merge short form files Generate trigger file Clean up trigger file Generate UVIS PEF Generate products Inst. timing SSR loading Trigger file Merged sequence Check products manual automated The utilization of pointing templates does not help the generation of the trigger commands

01/05/10UVIS TEAM MEETING OPERATIONS UPDATE Notes and Reminders Use UVIS_SOLAR_OFF to Sun in CIMS for all solar occultation instead of ISS_NAC to Sun (-20.0, 0.0, deg) offset. Before requesting sponge bits let us know what you want as we may have a good understanding of instrument SSR loading. The list of ring occultations that contain an atmospheric occultation is on the team web site at The list of all the tour calibrations is on the team web site at The UVIS PEFs are on the team web site at

01/05/10UVIS TEAM MEETING OPERATIONS UPDATE Concerns Is the HSP usage policy put in place after last meeting working Ok? –No more HSP HVPS ON at -03:00 –HSP HVPS ON only where useful. What do we have to do in order to have usable FUV and EUV up to 2017?

ISA Z86939 Summary From The 7/2005 Team Meeting 01/05/10UVIS TEAM MEETING OPERATIONS UPDATE

UVIS TEAM MEETING 7/ 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 S12 IEB patched for Enceladus encounter S13 and S14 IEB updated –Identification of the problem EUV.WIN1=14, 48, 1, 560, 1023, 2 16-pixel repeat pattern

UVIS TEAM MEETING 7/ ISA Z86939

UVIS TEAM MEETING 7/ ISA Z86939

UVIS TEAM MEETING 7/ ISA Z86939 (EM test) Compare the EUV and FUV indirection tables –They are identical Test using a Hg lamp (FUV channel) –Could not reproduce

UVIS TEAM MEETING 7/ ISA Z86939 (Hg lamp test) Extracted from 14, 48, 1, 512, 1023, 2 Extracted from 0, 63, 1, 0, 1023, 1 14, 48, 1, 560, 1023, 2

UVIS TEAM MEETING 7/ ISA Z86939 (Hg lamp test) 0, 63, 1, 0, 1023, 1 14, 48, 1, 560, 1023, 2 14, 48, 1, 512, 1023, 2