Herschel Ground Segment ICC: HCSS

1
Herschel Ground SegmentICC HCSS SPIRE IDT
ICCs
SPIRE ICC Definition Team
MOC
HSC
HCSS
2
ICC Mission Statement

• The primary role of the ICC is to make possible
  the processing of the instrument data into
  scientifically useful products. It does this by
  providing the necessary software and expertise to
  allow the definition of astronomical observations
  and engineering tests and the processing of data
  taken from their measurement into usable products
• The ICC is also responsible for the monitoring
  and maintenance of the instrument scientific
  performance throughout the mission  

Draft ICDT meeting 25th April 2001
3
Object Oriented (OO) Design Approach
The ICC definition team have decided to design
the ICC using the OO approach

• Efficiency, adaptability, re-useability
• Proven concept e.g. ORAC DR
• Approach being used by other ICCs, HSC
• Used by Herschel Common Science System
• Databases will be OO so software should be OO
• What the programmers will want

4
Object Orientated Design

• Process of defining a system as a collection of
  interacting classes.
• Three major phases
• URDs
• Use Cases
• Class Diagrams

5
From a SIRD to a SIP
Use Cases
SIP
URDs
SIRD
543
ICCF-205
Work- Package
Summary Level usecase
ICCF-205
3.1.2
3.1.2
3.1.2
3.1.3
Work- Package
ICCF-85
ICCF-85
544
Summary Level usecase
Work- Package

ICCA-50
ICCA-50
557
6
URDSSPIRE-ICS-PRJ-000XXX

• 543 AIV requirements (ILT, IST etc) Ken
• 544 Calibration requirements Seb
• 545 Photometer processing Walter/Seb
• 546 FTS processing Jean-Paul
• 548 Instrument engineering Gillian
• 549 ICC as a whole system Neal (Steve)
• 550 FSC Neal (Steve)
• 551 Common Uplink System Sunil
• 552 Astronomical Observation Prep. Marc
• 553 On board software Sunil
• 554 Instrument operation Gillian
• 554 SPIRE consortium Seb
• 555 MOC Sunil
• 556 Other ICCs Marc
• 557 Public Seb

1st Versions Completed
7
Extract from FTS URD
8
Use Cases

• Use cases describe actors' carrying out tasks in
  the system under design'. Various staff and
  subsystems in the HSC and ICCs can take on the
  role of the actors for a usecase
• By producing a complete set of usecases the
  domain model can be defined and together they
  serve as the basis for implementing the ground
  segment.

9
Summary Level Use-Cases

• UC-AIV010 Generate command sequences
• UC-AIV020 Update OBS
• UC-AIV030 Access data storage
• UC-AIV040 Test script validation
• UC-AIV050 Instrument database validation
• UC-CAL010 Produce calibration plan
• UC-CAL020 Generate calibration report
• UC-ENG010 Simulate instrument performance
• UC-ENG020 Investigate external SC/instrument
  effect on SPIRE instrument
• UC-ENG030 Store analysis data

Half Written
10
Summary Level Use-Cases

• UC-ICC010 Create or update a software
  artefact(s) (within the ICC)
• UC-ICC020 Create or update a document
• UC-ICC030 ICC and DAPSAS database access
• UC-ICC040 ICC and DAPSAS computing interface
• UC-ICC050 Maintain computing environment
• UC-ICC060 Maintain ICC web page
• UC-ICC070 Out of hours call out
• UC-ICC080 Store an artefact locally in ICC/DAPSAS

Half Written
11
Summary Level Use-Cases

• UC-FSC010 Training in software tools
• UC-FSC020 Support HSC query
• UC-CUS010 Prepare MIB for ingestion
• UC-CUS020 Test and validate observing modes
• UC-CUS030 View schedules of the CUS
• UC-AOP010 Run time estimator
• UC-OBS010 Instrument OBS groups information
  interface
• UC-OBS020 Test and validate OBS
• UC-OBS030 Report an OBS problem
• UC-CON010 Consortium expert knowledge capture
• UC-CON020 Evaluate/integrate ICC-external
  algorithm
• UC-CON030 Disseminate knowledge
• UC-CON040 Supply ICC information to consortium
• UC-OTH010 Interface for joint-ICC areas of
  commonality

Half Written
12
UC-CAL010 Update Instrument Calibration

• Level summary
• Scope SPIRE ICC
• Version 0.2
• Status draft
• Brief description
• This use case describes the high level steps in
  the long-term calibration of the instrument. This
  includes the preparatory laboratory measurements
  of the instrument, calibration observations
  performed on other instruments, calibration
  during testing and calibration during the
  operations phase.

13
UC-CAL010 Update Instrument Calibration

• Main Success Scenario
• 1. CS Implement the (Herschel) calibration plan
  for the next X days (UCF-741)
• 2. CS Analyse the latest SPIRE calibration data
  (UC-CAL012, c.f. UCF-007, UCF-746)
• 3. CS Maintain database of calibration sources
  (UC-CAL013)
• 3.1. CS Interface for joint-ICC areas of
  commonality (UC-OTH010)
• 3.2. CS Obtain (non-Herschel) observations of
  calibration sources (UC-CAL0132)
• 4. CS Produce calibration models (UC-CAL014,
  c.f. UCF-745)
• 5. CS Update Calibration plan for the
  subsequent X days
• (UC-CAL015)

14
Time Table

• Delivery of SIP 31st May
• ESA Review of SIP 26th June (TBC)
• Internal review of ICC TBD

15
Herschel Visibility Cirrus Constraints
Presentation Promise of FIRST
B100 Contours at 1 and 2 MJy/sr
b45 contours
IRAS 100mm Cirrus map from Schlegel et al. 1998