1 / 40

RBSP EFW SOC (in support of INT) and ConOps

RBSP EFW SOC (in support of INT) and ConOps. Science Operations Center (In Support of INT) and Concept of Operations (SOC and ConOps ) John Bonnell Will Rachelson Matt Born Space Sciences Laboratory University of California, Berkeley. EFW SOC and ConOps Outline (EDIT THIS).

helen
Télécharger la présentation

RBSP EFW SOC (in support of INT) and ConOps

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. RBSP EFWSOC (in support of INT) and ConOps Science Operations Center (In Support of INT) and Concept of Operations (SOC and ConOps) John Bonnell Will Rachelson Matt Born Space Sciences Laboratory University of California, Berkeley EFW INST+SOC PDR

  2. EFW SOC and ConOpsOutline (EDIT THIS) • Science Operations Center (SOC) • Requirements • Organization • Description: • Data Products • Data Processing Flow • Development: • Schedule and Milestones • Test Plan • Status • EFW Concept of Operations (ConOps) • Instrument Commissioning: • Turn-On and Check Out • Boom Deploys • Nominal Operations: • Conditions for Nominal Operations • State-of-Health Monitoring and Trending • Commanding and Day-to-Day Operations EFW INST+SOC PDR

  3. EFW SOCRequirements • The EFW SOC allows the EFW SOC and Science teams to: • Process and distribute EFW science data in a timely, accurate, and configuration-controlled fashion. • Efficiently command and control the EFW instrument, both during ground testing and on-orbit operations. • Governing documents: • RBSP Mission Requirements Document (DOC-REF). • RBSP-EFW UCB Performance Assurance Matrix (GSE and SOC tabs). • RBSP EFW SOC Requirements Document (DOC-REF). • RBSP EFW SOC Software Development Plan (DOC-REF). • Contributing Documents: • RBSP Science Data Management Plan (DOC-REF). EFW INST+SOC PDR

  4. EFW SOCOrganization • The EFW SOC will be: • Developed at UCB. • Hosted from UCB. • UCB has played a similar role on previous missions: • CRRES, Polar, FAST, THEMIS. • EFW Instrument I&T occurs at UCB, and SOC development builds on the GSE required to support that effort: • GSE→Test SOC→FLT SOC. EFW INST+SOC PDR

  5. EFW SOCTop-Level Data Processing Diagram EMFISIS SOC MAG data OTHER RBSP and GEOPHYSICAL DATA Sources RBSP MOC CTG-CTG SOC-NRT SOC-PDP SDC-MDP SDC-MAG SDC-ODP SDC-BSEL EFW Supporting DATA ARCHIVES: EMF-MAG STATE MOC OGPD SOC-logs EFW Instrument DATA ARCHIVES: SOH L0+, L1, L2, QL, CAL, L3+ SDC-DVAL SDC-CAL SDC-SDA RBSP EFW SOC Command-Telemetry-Ground Support (CTG) and Science Data Center (SDC) elements. I-CDR SOC-CDR EFW INST+SOC PDR

  6. EFW SOCData Processing Organization • SOC is divided into two parts: • Command, Telemetry, and Ground Support (CTG). • Science Data Center (SDC) • CTG consists of a single CSCI, CTG. • SDC consists of 9 CSCIs, 1 of which is directly relevant to INT efforts: • NRT – Near-real Time data processing and display. • METUTC -- MET↔UTC Time Conversion • PDP – Processed Data Production. • DVAL – Data Validation • BSEL – Burst Data Selection • MDP – MOC Data Products Processing. • MAG – MOC and EMFISIS Data Products Processing. • ODP – Other RBSP and Geophysical Data Products Processing. • SDA – Science Data Analysis. • CAL – EFW Calibration Parameter Production. EFW INST+SOC PDR

  7. EFW SOCData Products (make sure agree with SDMP) EFW INST+SOC PDR

  8. EFW SOCCTG Block Diagram GSE EFW INST+SOC PDR

  9. EFW SOCNRT Block Diagram RBSP MOC EFW SOC CTG Near-Real Time Data Acquisition, Processing, and Display (Science and SOH) MOC L0 to SOC L0+ processing EFW L0+ Archive L0+ to L1 Processing EFW L1 Archive NRT Data Analysis And Display Autonomous Operation SOC and SCI team input required External Process or Resource EFW INST+SOC PDR

  10. EFW SOCDevelopment Plan: Schedule and Milestones EFW INST+SOC PDR

  11. EFWGSE • Rachelson presentation here. RBSP-EFW CDR 2009-09-30 469

  12. EFWScience Data Center • Products Under Development • SDC-NRT data analysis tool, EFW Plot • Planned Products • SDC-BSEL burst selection tool • SDC-DVAL data validation and release tool • SDC-MDP L0 retrieval and archiving service • SDC-MAG ancillary magnetic data retrieval, integration, and archiving service • SDC-ODP ancillary data retrieval and archiving service • SDC-PDP L0->...->L4 conversion and archiving service • SDC-SDA scientific data service • CAL calibration data service RBSP-EFW CDR 2009-09-30 470

  13. EFWScience Data Center • SDC-NRT Analysis Tool • Requirements • Acquire instrument data • Scriptable operation allows tie-in to the EFW CTGfor data during I&T, etc. • Network interface will allow tie-in to forthcoming SOC-MDP during flight. • Process instrument data • Decompression of DeltaMod-2 • Decommutation of data packets as defined in the CTM • Display instrument data • View, save, and print customizable plots of data • View statistics about data • Value-added features • User interface requires little to no training • Import from and export to legacy tools, including tplot • Unit testing and use-case testing maintains quality • Generic back-end design allows for reuse in SDC-BSEL, SDC-DVAL, and SDC-SDA products. RBSP-EFW CDR 2009-09-30 471

  14. EFWScience Data Center RBSP-EFW CDR 2009-09-30 472

  15. EFWScience Data Center RBSP-EFW CDR 2009-09-30 473

  16. EFWScience Data Center RBSP-EFW CDR 2009-09-30 474

  17. EFWScience Data Center RBSP-EFW CDR 2009-09-30 475

  18. EFWScience Data Center RBSP-EFW CDR 2009-09-30 476

  19. EFWScience Data Center RBSP-EFW CDR 2009-09-30 477

  20. EFWScience Data Center RBSP-EFW CDR 2009-09-30 478

  21. EFWScience Data Center RBSP-EFW CDR 2009-09-30 479

  22. EFWScience Data Center • Present state of support for I&T • Communication • L0 files written to disk by GSEOS are located and read without issues. • Decommutation • APIDs 0x241 – 0x259 are fully implemented • APIDs 0x100 and 0x260 – 0x26a are not yet implemented. (ETA <2 weeks) • Decompression • Delta Mod-2 decompression is implemented and tested. • No other compression algorithms are currently used by flight software. • Output • Plots are sufficiently configurable to allow inspection of data to the level required for verification of operation. RBSP-EFW CDR 2009-09-30 480

  23. EFWScience Data Center • Security Processes for SDC Software Product Development • Confidentiality • Unintentional disclosure of information is prevented by access control. [LDAP] • Unintentional disclosure of credentials is prevented by secure channels. [HTTPS] • Integrity • Source changes are restricted by access control. [LDAP] • Source changes are reversible through version control. [SVN] • Inadvertent failures are detectable by automated testing. [Python] • Catastrophic information loss is prevented through data backup. [rsync] RBSP-EFW CDR 2009-09-30 483

  24. RBSP EFWSOC (in support of INT) and ConOps Concept of Operations (ConOps) EFW INST+SOC PDR

  25. EFW ConOpsInstrument Commissioning • EFW Commissioning consists of two phases: • Initial instrument turn on and check out. • Radial and axial boom deploys. • May occur at RBSP MOC (using Test SOC) or at EFW SOC (using Flight SOC). • Turn-On and Checkout consists of stowed functional tests (duplicates of SC-level I&T procs and data). EFW INST+SOC PDR

  26. EFW ConOpsInstrument Commissioning: Radial Booms Deploy • Initial EFW boom deploy plan already developed: RBSP_EFW_TN_003C_EFW_BoomDeploySequence.doc. • Boom deploy power controlled by MOC (SC service). • Boom deploy commanding through EFW SOC (test or flight). • Spin rate changes during staged, pairwise boom deploy illustrated below. • Spin rate vs. boom stroke and time during deploy used to monitor state of deploy and abort, if required. • Baseline NNN-day parallel deploy schedule between both observatories incorporated into current Mission Timeline (DOC-REF). Fine wire unfurling EFW INST+SOC PDR

  27. EFW ConOpsInstrument Commissioning: Axial Booms Deploy • Axial boom deploy occurs after radial boom deploy is complete, and observatory mass properties and dynamics confirmed (typically no significant delay required). • Axial booms deployed singly, in stages using motor deploy system to ≈5-m stroke (≈10-m tip-to-tip). • Final deploy lengths trimmed in roughly 10-cm increments using Survey axial E-field and SC potential estimates to reduce common-mode signal (expected duration of trim phase is N weeks, and occurs in parallel with other instrument commissioning activities). EFW INST+SOC PDR

  28. EFW ConOpsValidity Conditions for Nominal Operations • Sensors Illuminated -- All EFW sensors illuminated (goal for aft axial sensor). • Attitude Known -- Post-processed Observatory attitude (spin axis pointing and spin phase) known to accuracy better than 3 deg. • Ephemerides Known -- Post-processed Observatory position and velocity known to accuracy better than (10 km, 30 m/s, 0.1 deg; 3-sigma). • Booms Settled -- EFW radial booms within 0.5 deg of nominal position. • DC B-Field Known – Post-Processed DC B-field known to accuracy better than 1%. • EFW-MAG-SCM Relative Orientation Known – Post-processed relative orientation of EFW, MAG, and SCM sensor axes known to better than 2 degrees. EFW INST+SOC PDR

  29. EFW ConOpsInstrument Health and Status Monitoring • Instrument State-of-Health (SOH) monitored through near-real-time or playback engineering data via the SOC-CTG. • SOH compared against red/yellow limit database. • Off-Nominal conditions leads to: • Notification of EFW SOC personnel (page, e-mail). • Issuance of scripted commands, for certain, well-known off-nominal conditions (example: CRRES DDD-false commanding and resets). • Long-term trending and storage of SOH data: • New solution in GSEOS as part of CTG efforts or… • Incorporation into existing UCB MOC BTAPS database (decision: part of Phase III development, 2010 time frame). EFW INST+SOC PDR

  30. EFW ConOpsNormal On-Orbit Operations (1) • Commanding • Complete instrument state (sensor biasing and data collection) set by ~50 commands. • Instrument configuration changes infrequently (~1/few weeks, after initial commissioning phase). • ~daily commanding to support ground selection of burst segments as needed. • ~monthly Sensor Diagnostic Tests (bias sweeps) to confirm and optimize instrument biasing. • Data Management • 12 kbps daily average: • ~ 5 kbps continuous Survey data (32 S/s E and V; auto- and cross-spectral data products). • ~ 7 kbps Burst1 and Burst2 data (0.5 and 16 kS/s E, V, and SCM data). EFW INST+SOC PDR

  31. EFW ConOpsNormal On-Orbit Operations (2) • Burst Management • Higher-rate waveform data (E, V, and SCM) collected continuously and banked into SDRAM and FLASH in seconds to minutes long segments (many days of B1 storage; many hours of B2 storage). • Each segment tagged with “Burst Quality” computed on-board from DC or AC fields data cues (DOC-REF; Filter Bank AC E or B, cues from other instruments). • B1 playback is through ground selection based on Survey data and other data sources (geophysical indices, etc.); on-board with Burst Quality allows for autonomous selection and playback, as needed (vacations, illness, ennui, etc.). • B2 survival and playback selection on-board is based on Burst Quality; playback selection includes option for ground selection based on Survey data and other data sources (geophysical indices, etc.). • B1 and B2 support for time-tagged campaign modes available as well (e.g. BARREL support). • Inter-Instrument Burst Data • EFW message includes axial sensor status (illuminated/eclipsed), sensor sweep status (static/sweeping), and current burst-valuation algorithm ID and value. EFW INST+SOC PDR

  32. EFW ConOpsCommand Generation • EFW-SOC shall generate commands by reference to UTC, as well as MOC data products (predicted ephemerides, etc.) and other data assets (e.g.. Geomagnetic indices). • EFW commands shall be validated as needed by running command load on EFW TestBed (ETU) and verifying appropriate change of state, data production, and instrument configuration. • Command validation shall occur prior to transmission of command load from EFW-SOC to RBSP-MOC. • Verification of current MET↔UTC SCLK Kernel shall occur prior to translation of EFW commands from UTC to MET. • Command receipt will be verified after transmission using standard MOC data products. EFW INST+SOC PDR

  33. This page intentionally almost blank EFW INST+SOC PDR

  34. BACKUP SLIDES EFW INST+SOC PDR

  35. EFW SOCPDP and DVAL Block Diagram EFW EMF-MAG Archive MOC L0 to SOC L0+ processing L1 to L2 Processing L0+ to L1 Processing RBSP MOC STATE (EPHEM/ATT) Archive EFW L0+ Archive EFW L1 Archive EFW L2 Archive (internal) CAL Archive EFW QL Archive (internal) EFW L2 and QL Archive (ext. access) L2 and QL transfer to external access L2 and QL Validation QL Data and Plot Production. Processed Data Products (PDP and DVAL): Acquisition, Production, Validation, and Delivery. Autonomous Operation SOC and SCI team input required External Process or Resource C T G EFW INST+SOC PDR

  36. EFW SOCBSEL Block Diagram EFW EMF-MAG Archive EFW Burst (B1 and B2) Ground Selection RBSP MOC EFW SOC CTG MET↔UTC Conversion STATE (EPHEM/ATT) Archive EFW Command Archive OTHER Data Acq. EFW QL Archive (internal) EFW L2 Archive (internal) OTHER Data Sources Burst Selection ( BSEL): Generation, Validation, Delivery, and Archiving. Autonomous Operation SOC and SCI team input required External Process or Resource EFW INST+SOC PDR

  37. EFW SOCMDP and MAG Block Diagrams RBSP MOC RBSP MOC QuickLookMAG data EMFISIS SOC MAG data MOC Data Products Retrieval (non-Data, non-SOH) MOC Data Products Archive EMF-MAG Data Acq ATT/EPHEM to STATE Processing Other MOC Data Products (OMDP) Processing SCLK Kernel Processing EFW EMF-MAG Archive SOH Archive EFW OMDP Archive EFW STATE Archive EFW SCLK Archive SCLK (MET↔UTC), MOC Data Products and MAG Data Processing: Retrieval, Validation, Processing, and Archiving. Autonomous Operation SOC and SCI team input required External Process or Resource EFW INST+SOC PDR

  38. EFW SOCSDA and CAL Block Diagrams EFW EMF-MAG Archive STATE (EPHEM/ATT) Archive CAL Archive STATE (EPHEM/ATT) Archive EFW EMF-MAG Archive Plasma Data (eg. ECT-HOPE Vion) L2 to L3+ Processing (TDAS or SDT) L1 to L2 Processing (TDAS or SDT) CAL Archive CAL Archive CAL Production EFW L1 Archive EFW L2 Archive (internal or external) EFW SOH/HSK Archive EFW L1 Archive External Users (ISTP CDF End Users) EFW L2 Archive Science Data Analysis (Internal and External) CAL Parameter Estimation and Production Autonomous Operation SOC and SCI team input required External Process or Resource EFW INST+SOC PDR

  39. EFW SOCTest Plan • Detailed GSE-SOC test plan under development (due Q2 or Q3, 2009; supports SDP Phase II). • CSCI elements will be tested in isolation to establish basic functionality (test cases; error cases and signaling). • Example: phased introduction of DCB functions and testing using GSE. • Elements are brought together into full modules and fed instrument data from known sensor excitations to verify module-level functionality and requirements fulfillment. • Example: basic instrument functional tests during I&T. • End-to-end testing at each stage of integration to weed out problems early. • Example: testing of complete PDP chain as early as possible during Phase D using data from SC I&T and environmental tests. EFW INST+SOC PDR

  40. This page intentionally almost blank EFW INST+SOC PDR

More Related