1 / 8

UVIS Ops Team

Review of UVIS instrument's status, significant issues, planning challenges, and action items discussed in the team meeting on June 23, 2008. Includes on/off cycle data, operational hours, lost data issues, planning problems, and AI from the previous meeting.

susanmoses
Download Presentation

UVIS Ops Team

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UVIS Ops Team UVIS TEAM MEETING 6/23/08

  2. Instrument Status • On/Off Cycle: 27 • No change since last meeting • Hours On: ~69,000 hours • Continuous operations since 9/11/2007 • Longest continuous operations was from 1/15/2005 (probe relay) to 9/11/2007 (S/C safing) • HDAC Filament Modulation: • Filament 1: 100.28 hours • Filament 2: 12.22 hours • Last: 2006/255 UVIS TEAM MEETING 6/23/08

  3. Significant Issues • S36: UVIS_055SA_NAURMOV001_PRIME • Partial lost - Rain in Spain • S37:UVIS_058ST_URBETLUP001_PRIME • Miss the star (wrong RA/DEC in CIMS, no double checking) • S38: UVIS_059ST_ETACMA002_PRIME • Incorrect dead band during RCS to RWA transition (?).Star in/out the FUV slit. ISA Z92247 • S39: None • S40: Lot of partial or total data looses due to DSN • Some riders and UVIS_067IC_ALPVIR001_PRIME (total), UVIS_065ST_URALPARA001_PRIME (partial), UVIS_069SA_NAURMOV002_PRIME (partial) • S41: None to this day UVIS TEAM MEETING 6/23/08

  4. Planning/Sequencing Issues • RBOT analysis • New process for the XM • More wheel biases, less science impact, less workforce impact • Needs to be concluded at SOP port 3 • No late pointing changes • S42 was very clean, S43 somewhat less UVIS TEAM MEETING 6/23/08

  5. Planning/Scheduling Issues • “Just-in-time” process • Significant problems with the quality of what is delivered by SP for implementation by the ops teams • Random secondary axis (cut & paste?) • If possible use the WP secondary • Significant time lost and frustration over this issue • Custom period not defined in CIMS • Bogus information in CIMS (cut & paste?) • Take the time to review your CIMS requests UVIS TEAM MEETING 6/23/08

  6. AI from last meeting • Atmospheric Occultation during Ring Occultation • We are switching to the AO set up from inside the D-ring to Saturn limb whenever possible. • List of the requests will be put on the team web site (updated after data is collected). • Provided in next slide UVIS TEAM MEETING 6/23/08

  7. UVIS TEAM MEETING 6/23/08

  8. AI from last meeting • HSP at 500µ sec • Nothing done yet. UVIS TEAM MEETING 6/23/08

More Related