N 84- •»<> 435

STARLAB

GROUND SYSTEM GUIDELINES

DOCUMENT

FINAL

JANUARY 1984

IWNSA 60DDARD SPACE FLIGHT CENTER

National Aeronautics and GDCCUDC1 T HADVI 11111

Space Administration allCCNDCLI, mAnlLAIltl
This document was prepared by:

Dr. Frederick J. Hawkins

and the

Data and Operations Sub-committee (DOS)
EXECUTIVE SUMMARY

In accordance with a letter of intent among Australia, Canada and the

United States, the United States will supply a Starlab Ground System to

support required mission planning, pre-launch, launch, normal, and contingency operations phases and post-flight data preprocessing and processing,

and data archival. This Starlab Ground System will support at least two

six months missions on a Space Platform/Station. The Starlab Ground System

augmented with Experimenter Ground Support Equipment (EG3E) will provide

required capability for investigators from the three participating

countries and possibly guest observers for these missions. A Data Analysis

Facility (DAF) is planned and will be sized to provide science data processing capability for U.S. investigators and guest observers. It is also

anticipated that Australia and/or Canada will develop similar capability

using appropriate commonality to support their national investigators and

guest investigators. The -Starlab Ground System will provide the necessary

interfaces and data products to support the DAF and other national

facilities.

The Starlab Ground System will provide all data streams required for

quicklook analysis of high rate science data to the Payload Operations

Control Center (POCC) and EGSE. These streams will be configured to enable

data systems communications transparency, wherever possible. Off-line

analysis capability will be provided by the DAF. The image analysis

capability provided by the EGSE will be required to bridge the gap between

realtime (same orbit) response and that which can be reasonably expected

from an off-line facility. The data preprocessing and processing functions

will provide science data, appropriately calibrated, appended with

necessary ancillary data, and with required instrument signature removal to
support science data processing functions. Various data types and products

produced by the preprocessing and processing functions will be archived by

the Starlab Ground System. This archive will provide a complete storage of

necessary Starlab derived data and data products. Access requirements will

be sized to support the science data analysis needs of U.S. investigators

and guest observers and the retrieval needs of Australian and Canadian

investigators.

It is important that serious consideration be given to the development of

preliminary requirements and to the conceptualization of the required

Starlab Ground System at this stage to avoid some of the problems that have

been experienced in the development of other ground systems. This document

provides a compilation of preliminary requirements and guidelines for a

ground system to meet currently identified Starlab needs. Section 6

summarizes these requirements and will provide the nucleus for the

subsequent requirements document. Both Shuttle sortie and Space

Platform/Station type missions have been addressed. At the time this

document was prepared the initial Starlab flight(s) were to be in the

Shuttle sortie mode. However, at the November 1983, tripartite meeting

the decision was made to delete the sortie mode and to use as a baseline, a

six month mission on the Space Platform/Station.

Several sources of information have been utilized in the preparation of

this document, but in particular the support of the Starlab Data and Operations Sub-committee (DOS) is appreciated.

ii
TABLE OF CONTENTS

Section Page

Executive Summary i

Table of Contents iii

List of Figures v

List of Tables vi

List of Abreviations and Acronyms vii

vu.woooi.jr IX

1.0 Introduction 1-1

1.1 Purpose 1-1

1.2 Scope 1-2

1.3 Applicable Documents 1-4

2.0 Overview of the Starlab Science Objectives 2-1

2.1 Science Objectives 2-1

2.2 Ground System Considerations 2-3

3.0 Overview of the Starlab Space Segment 3-1

3.1 Facility Definition 3-1

3.2 Facility Operations 3-4

3.3 Space Segment Configuration 3-8

3.3.1 Shuttle Sortie 3-8

3.3.2 Space Platform/Station 3-13

3.4 Space Segment Operations 3-15

3.4.1 Shuttle Sortie 3-15

3.4.2 Space Platform/Station 3-18

3.5 Ground System Considerations 3-19

4.0 Overview of the Mission Operations Concept 4-1

4.1 Mission Planning Phase 4-1

4.2 Integration and Test Concept 4-2

4.3 Normal Operations Concept 4-5

4.3.1 Shuttle Sortie 4-5

4.3.2 Space Platform/Station 4-9

5.0 Overview of the Ground System 5-1

5.1 Ground System Objectives 5-1

5.2 System Overview 5-3

5.3 Potential Remote Facility Functions 5-8

iii
TABLE OF CONTENTS (concluded)

6.0 System Functional Guidelines 6-1

6.1 Observing Proposal Management 6-1

6.2 Planning and Scheduling 6-7

6.3 Guide Star Selection System 6-10

6.4 Space Segment Control Operations 6-14

6.5 Science Control Operations 6-14

6.6 Support Requirements 6-18

6.7 Ground System Data Management 6-21

6.7.1 Direct Imager (DI) Image Reduction 6-28

6.7.2 Spectrograph Data Reduction 6-29

6.7.3 Grism Images 6-31

6.7.4 Image Catalog 6-32

6.7.5 Current NASA Capabilities 6-33

6.7.6 Data Archival 6-33

6.7.7 Computer Resource Estimate 6-37

6.8 Science Data Analysis 6-37

6.8.1 Analysis Functions 6-39

6.8.2 Data Products 6-41

6.8.3 Delivery Times 6-42

6.8.4 Relationship with the Data Processing Function 6-43

6.8.5 Number of Users 6-44

6.8.6 DAF Data Access 6-44

6.8.7 Computer System Estimate 6-47

6.8.8 Hardcopy Functions 6-47

7.0 Interfaces 7-1

7.1 Starlab/NASCOM/TDRSS Interfaces 7-1

7.2 Starlab/Institutional Facilities 7-1

iv
LIST OF FIGURES

Figure

3-1 Spacelab Data System (Overview)

3-2 Overview of Starlab Facility Showing RAU and HRM

Interfaces

3-3 Potential Leasecraft C&DH Subsystem Overview

4-1 Mission Operations Support Phases

4-2 Starlab Requirements - Science Operations

4-3 Overview of Mission Operations

5-1 Starlab Ground System Overview

5-2 JSC POCC - Standard Services (Overview)

5-3 Starlab Ground System Overview

6-1 SLDPF Functional Diagram
LIST OF TABLES

Table

2-1 Ground System Considerations Derived from the Science

Objectives 2-4

3-1 Onboard Data Acquisition and Control Functions (Preliminary) 3-5

3-2 Potential Onboard Functions 3-6

3-3 Data Availability Requirements for Shuttle Sortie

Configuration 3-11

3-4 Ground System Considerations Derived from the Space Segment

Requirements 3-20

6-1 Sample Starlab Missions 6-2

6-2 Potential Data Contained Within Each Proposal 6-5

6-3 Preliminary List of User Aids 6-9

6-4 Timeline Factors Requiring Consideration 6-11

6-5 Factors Affecting Target Availability 6-12

6-6 Typical Constraints 6-13

6-7 Engineering Data Analysis Functions 6-16

6-8 Typical EGSE Functions 6-17

6-9 Required Support Capabilities 6-19

6-10 SPIF Capabilities for Supporting Missions

Utilizing the STS 6-20

6-11 Distinct Data Levels 6-22

6-12 Data Preprocessing and Processing Functions 6-25

6-13 Data Preprocessing and Processing Characteristics 6-26

6-14 Data Processing Data Base Size Estimates 6-27

6-15 Potential Archive Considerations 6-35

6-16 Preliminary Starlab Image Archive Requirements 6-36

6-17 Analysis Tools and Resources Needed for Image, and

Spectrograph and Grism Data Analysis 6-40

6-18 Temporary On-line Storage 6-46

6-19 DAF Access Requirements 6-48

6-20 Starlab Hardcopy Output Products Available from the DAF 6-49

7-1 TDRSS Ku-Band Downlink for Spacelab 7-2

VI
LIST OF ABREVIATIONS AND ACRONYMS

Term Explanation

AFD Aft Flight Deck

AM Accumulating Memory

BCH Bose-Chaudhuri-Hocquenguem (Cyclic Codes)

ECU Bus Coupler Unit

C&DH Command & Data Handling

CAPS Crew Activity Planning System

CCT Computer Compatible Tape

CCTV Closed Circuit Television

CDMS Command & Data Management System

CU Central Unit

CVZ Constant Viewing Zone

DAC Direct Access Channel

DAF Data Analysis Facility

DEC Declination

DEP Dedicated Experiment Processor

DI Direct Imager

DOS Data & Operations Sub-committee

DST Department of Science and Technology

DQM Data Quality Monitoring

EC Experiment Computer

ECAS Experiment Computer Applications Software

ECIO Experiment Computer Input/Output

ECOS Experiment Computer Operating System

EER Engineering & Economics Research, Inc.

EGSE Experimenter Ground Support Equipment

ESA European Space Agency

EU Electronic Unit

FDF Flight Dynamics Facility

FFT Fast Fourier Transform

FGS • Fine Guidance System

GSFC Goddard Space Flight Center

GSSS Guide Star Selection System

HDRR High Data Rate Recorder

HRDM High Rate Demultiplexer

HRM High Rate Multiplexor

1C Instrument Computer

ID Identification

IPS Instrument Pointing System

IUE . International Ultraviolet Explorer

JSC Johnson Space Center

JSWG Joint Science Working Group

KSC Kennedy Space Center

MA Multiple Access

MCC Mission Control Center

MDB Multiplex Data Bus

MDM Multiplexor-Demultiplexer

MIPS Mission Planning Computer System

MMS Multi-mission Modular Spacecraft

vii
LIST OF ABREVIATIONS AND ACRONYMS (concluded)

Term

MMU

MOU

MSOCC

NASA

NASCOM

NCC

NRCC

NSSDC

OBC

OCF

OD

PA

PCM

PDI

PIP

PMP

POCC

RA

RAL

RAU

RCS

RIU

ROM

SA

SAA

SC

SCIO

SDPF

SLC

SLDPF

SMM

SPIF

SPSS

ST

STACC

STDN

STINT

STS

SWG

TAGS

TC

TDRSS

UV

ZOE

Explanation

Mass Memory Unit

Memorandum of Understanding

Multi-Satellite Operations Control Center

National Aeronautics & Space Administration

NASA Communications

Network Control Center

National Research Council of Canada

National Space Science Data Center

Onboard Computer

Orbit Computing Facility

Operational Downlink

Position Angle

Pulse Code Modulated

Payload Data Interleaver

Payload Integration Plan

Pre-Modulation Processor

Payload Operations Control Center

Right Ascension

Rutherford Appleton Laboratory

Remote Acquisition Unit

Reaction Control System

Remote Interface Unit

Rough Order of Magnitude

Single Access

South Atlantic Anomaly

Subsystem Computer

Subsystem Computer Input/Output

Sensor Data Processing Facility

Starlab Computer

Spacelab Data Processing Facility

Solar Maximum Mission

Shuttle/POCC Interface Facility

Science Planning & Scheduling System

Space Telescope

Standard Telemetry and Command Components

Space Tracking & Data Network

Standard Interface for Computer

Space Transportation System

Science Working Group

Text and Graphics System

Telescope Computer

Tracking and Data Relay Satellite System

Ultraviolet

Zone of Exclusion

viii
GLOSSARY

The following definitions are used in this document. This list is intended

to clarify those terms which might be confusing to the reader and is not

meant to be a complete set of definitions.

Ancillary Data - Additional, non-Starlab data which are required to

facilitate the analysis and reduction of science data and/or Starlab

instrument engineering data. These data include: time data, programmatic

data, attitude data, empheris data, and non-Starlab instrument engineering

data obtained on special request.

Data Ana-lysis Facility - A host facility providing off-line science data

analysis capability for the support of U.S. investigators and possibly

guest observers. The primary DAF function is to provide tha capability for

the extraction of scientific knowledge from Starlab images and associated

data. It also provides information necessary for feedback to the planning

of subsequent observations and for developing and improving calibration

procedures. The DAF provides processing customized according to the

specification of individual users, where these comprise two basic classes.

The first class includes observers and archival researchers who process

Starlab images and spectrograms for scientific purposes; the second process

Starlab images and spectrograms to help understand the Starlab instrument,

to monitor its performance, and to update its calibration functions and

tables.

Data Preprocessing - The function providing Starlab data capture and

recording, demultiplexing and synchronization, data quality monitoring and

data accounting. Following data preprocessing the resultant data are

delivered to the data processing function and/or data archives.

Data Processing - The data processing function performs a number of

processing steps on buffered pre-processed data received from the data

preprocessing function in order to produce various data products including

level 2 data. These steps include an assessment of image data quality,

archival of raw images (level 0), calibration parameter determination,

creation and archival of level 2 calibrated images, and maintenance of a

Starlab image catalog complete with the associated calibration history.

Experimenter Ground Support Equipment (EGSE). - EGSE provide support at

various phases of the ground flow and/or operations. These include

instrument development and calibration, facility development and

calibration, payload integration and test and Payload Operations Control

Center (POCC) operations. The EGSE are investigator provided, and support

various quicklook processing functions at the POCC including selected

processing of the engineering data stream and data processing of high rate

science data. In general, POCC facilities are not designed to handle data

streams in excess of approximately 2 Mbps.

Science Data' Analysis - This function provides primarily extraction of

scientific knowledge from the Starlab images and associated data. It also

provides the capability necessary for a feedback of information to support

ix
planning of subsequent observations and for developing and improving

calibration procedures.

Starlab Ground System - The Starlab Ground System provides the required

capability to support mission planning, pre-launch, launch, normal, and

contingency operations phases and post-flight data preprocessing and

processing, and data archival. The Starlab Ground System requires

augmentation by investigator provided EGSE to provide necessary quicklook

analysis functions. A DAF sized to provide science data analysis

capability for U.S. investigators and observers is planned as a part of the

Starlab Ground System. Australia and Canada are proposing to develop

similar capability to the DAF to support their national investigators. The

Starlab Ground System will provide the necessary interfaces to support

these remote facilities.
1.0 INTRODUCTION

1.1 PURPOSE

The purpose of this document is to identify preliminary requirements and

guidelines to be considered in the definition of detailed requirements for

the Starlab Ground System. The Starlab Ground System will be supplied by

the United States in accordance with the letter of intent signed by the

three national agencies under a tripartite agreement reprasenting

Australia, Canada, and the United States. These agencies are the Australian Department of Science and Technology (DST), the National Research

Council of Canada (NRCC), and the National Aeronautics and Space

Administration (NASA) respectively.

The letter of intent covered the first two long duration missions to be

performed utilizing the Starlab facility carried upon a space platform,

which would be supplied by the United States. Subsequent to this

agreement, it has been proposed to perform up to two missions in an

attached Shuttle sortie configuration. It is therefore necessary to

consider the additional guidelines necessary to support these missions.

This document will be used as input on the Starlab Ground System necessary

for the preparation of the Memorandum of Understanding (MOU) to be executed

between the three participating countries. In addition, the document will

provide inputs to be used in the preparation of a detailed Starlab Ground

System Requirements Document. This latter document will represent the

statement of ground system requirements as approved by the NASA Starlab

Project at the Goddard Space Flight Center (GSFC).

1-1
1.2 SCOPE

The Starlab Ground System will provide necessary capabilities required to

support mission planning, pre-launch, launch, normal, and contingency operations phases and post-flight data preprocessing, processing, and

archival. These capabilities will include mission planning, science operations control, space segment operations control (as required), data management and appropriate support requirements. In this document, consideration

will be given to the overall ground system for Starlab including potential

facilities within Australia and Canada, however the emphasis will be on the

definition of preliminary requirements and guidelines for the NASA provided

Starlab Ground System. The Starlab Ground System will provide appropriate

data products and the necessary interfaces to support science data processing activities within the U.S., Australia and Canada. Science data

processing capability to support U.S. investigators and possibly guest

observers will be provided via a Data Analysis Facility (DAF). It is

likely that similar capability will be developed by Australia and Canada to

support their national investigators. Commonality of systems and/or subsystems will be an important consideration in the development of these

science data processing facilities.

Current NASA plans are for the development of a Space Station, which is

likely to provide for both manned and unmanned elements. The unmanned

element of the Space Station is therefore a possible candidate to provide

the Starlab space platform capability. An alternate candidate is a

Leasecraft type system and at the present time this is the preferred

candidate. In each case, the platform will be in low Earth orbit and

tended periodically by the Orbiter. The capabilities required for space

segment operations control are dependent on the flight configuration and it

1-2
is therefore necessary to consider both the attached Shuttle sortie

configuration proposed for the initial up to two missions and the

subsequent space platform configuration in the guidelines definition.

For both configurations, ground systems capability for space segment

support will exist or will be developed to support all missions to be

carried on the space segment. It is therefore necessary to consider the

development of a Starlab Ground System in the context of available and

planned capability.

In the case of the attached payload configuration, the command of the

Orbiter flight with control of all resources and safety aspects is under

the direct control of the Johnson Space Center (JSC) Mission Control Center

(MCC). In addition, Spacelab elements such as the European Space Agency

(ESA) supplied Instrument Pointing System (IPS) are under MCC control. The

JSC Payload Operations Control Center (POCC) can support attached payloads

in this operational environment, where the broad range of capability and

services provided by this facility can be augmented by Experimenter Ground

Support Equipment (EGSE), as required. Further, data preprocessing services for Spacelab payloads for providing data products for post-flight

analysis are provided by the GSFC Spacelab Data Processing Facility

(SLDPF). For the Leasecraft system, a Multi-Satellite Operations Control

Center (MSOCC) type capability and the Sensor Data Processing Facility

(SDPF) can support similar functions.

In this document, the guidelines for a Starlab Ground System will be

developed within this overall framework for providing required capability.

Guidelines for the various functional requirements and interfaces will

therefore be developed. One important aspect in the definition of the

1-3
guidelines will be the development of a concept to provide continuity

between configurations, wherever possible.

In general, the Starlab Ground System will provide for data capture,

signature removal, quality checks, and quicklook analysis for realtime

control for U.S., Australian, and Canadian investigators, and possibly

guest observers. Facilities for detailed' analysis and data archival will

be developed by each country while the DAF will host U.S. based

investigators.

1.3 Applicable Documents

The following documentation has been used as input in the preparation of

the Starlab Ground System guidelines defined in this document:

1. Starlab, An Australia-Canada-U.S.A. Orbi-ting Telescope, Project

Concept and Scientific Goals, A Report of the Starlab Joint Science

Working Group (JSWG), University of Virginia, Charlottesville, VA

22903, September 1982.

2. Study of Starlab Ground Segment, Issue 1, Rutherford Appleton

Laboratory (RAL), Chilton, Didcot, Oxfordshire, England, August 1982.

3. Ground System Considerations for Projects, POB-30SD/0181, NASA/Goddard

Space Flight Center, January 1981.

4. Payload Operations Control Centers User's Services Guide, MOD-1

PUG/0180, NASA/Goddard Space Flight Center, April 1981.

1-4
5. Spacelab Payload Accommodation Handbook, SLP/2104, Issue 1, Revision

No. 5, January 31, 1981.

6. POCC Capabilities Document, Volume 1, JSC Attached POCC Capabilities

Description, JSC-14433, Revision A, February 20, 1981.

7. POCC Capabilities Document, Volume 2, MCC/Remote POCC Interface

Capabilities Description, JSC-14433. Revision A. March 1, 1980=

8. "Starlab Mission Profile Analysis, Mount Stromlo and Siding Spring

Observatories, Australian National University, January 1983.

9. Starlab Reference Specifications, JSWG, November 1983.

10. Starlab Memory Usage, A report prepared by the Data and Operations

Sub-committee, March 1983.

11. Real-Time Interaction with Starlab, A discussion paper prepared by the

Data and Operations Sub-committee, March 1983.

12. Summary Response to EER Priority Issues, Starlab Data and Operations

Sub-committee report, September 1, 1983.

13. Starlab Shuttle Mission Profile Study, Data and Operations Subcommittee, October 1983 [Issue 1].

14. Starlab Mission Profile Analysis: 1983 Canadian Survey [J. Hesser],

March 24, 1983.

1-5
15. Starlab Command and Data System Requirements Document, Code 600,

NASA/GSFC, Preliminary copy, October 1983.

16. Starlab-Level 1 Scientific Requirement Document (SRD), JSWG, Draft,

December 1, 1983.

1-6
2.0 OVERVIEW OF THE STARLAB SCIENCE OBJECTIVES

2.1 SCIENCE OBJECTIVES

The planned Starlab facility will consist of a one-meter space telescope

having unique.capabilities which will enable the pursuit of a wide variety

of frontier astrophysical problems in the optical and ultraviolet spectral

regions. The initial one or two flights of the facility will be in an

attached mode on the Orbiter utilizing the IPS and Spacelab. Flight times

of two weeks are anticipated. Subsequent flights will utilize a space

platform to provide a series of missions lasting a minimum of six months

each.

Starlab will provide a definitive contribution in two areas:

o Very high spatial resolution, large bandwidth imagery over a large

field of view, and

o High efficiency, high spatial resolution spectroscopy of extended

or point sources in applications where large spectral or spatial

multiplex gains are required.

Starlab will provide an ideal complement to the powerful capabilities of

the Space Telescope (ST) having the potential to survey significant areas

of the sky for fundamentally new astrophysical phenomena near ST's

threshold. Starlab operates in the same spectral range as ST, has a

spatial resolution and spectral coverage in the same class, but will have

an imagery field one hundred times larger. Its imagery field is therefore

2-1
perfectly matched to the scale of many important targets, including

globular star clusters, nearby galaxies, and distant clusters of galaxies.

The current Starlab design includes two each of two instrument types:

Direct Imagers (DI) mounted radially and echelle spectrographs axially

mounted. Among the many imagery problems to which Starlab would make

definitive contributions are the following: the early evolution of

galaxies, clusters of galaxies, superclusters, and quasars viewed at large

look-back times; calibration of "standard candles" used in determining

cosmic distances and use of new distance indicators, especially Type I

supernovae to extend determination of the cosmic deceleration parameter to

the largest possible distances; investigation of the "missing mass" by

using globular cluster tidal radii to map the gravitational field in the

halos of galaxies and by searching for the signature of decaying massive

neutrinos in clusters of galaxies; stellar physics in other galaxies,

including the study of very short-lived evolutionary phases, the initial

mass function, and star formation in spiral arms; the spatial structure of

supernova remnant shock waves; and analysis of the important ultraviolet

radiation from gas and dust near stellar birthsites in . our and other

galaxies.

The unique power of Starlab's multimode spectrograph instruments derives

from the capability for high spectral resolution coupled with superb

spatial resolution over a long slit (up to 8 arc-min). The resulting

multiplex gains give Starlab distinct advantages in many applications over

the ST and other spectroscopic facilities in both the ultraviolet and

optical regions. Important scientific problems for which these unique

capabilities are essential include the following: study of the physical

properties (chemical abundances, temperatures, densities, flow velocities)

2-2
of extended structures in the interstellar medium such as supernova

remnants, H II regions, and planetary nebulae; dynamics of stars and gas in

the vicinity of galactic nuclei; physical conditions in the extended

ionized gas often encountered in strong extragalactic radio sources and

galaxies which appear to be accreting hot material from circumgalactic

space; studies of individual stars in crowded fields (e.g., globular

clusters and nearby galaxies) or variable stars; analysis of the recentlydiscovered hot halo'gas of our own and nearby galaxies; and study of atomic

and molecular emission from comets and planets.

2.2 GROUND SYSTEM CONSIDERATIONS

It is important to identify science objectives which have an impact on

ground system design. Several areas requiring consideration have already

been identified. These are the following:

a) The need for realtime interaction versus preprogrammed operation has

been considered by the Starlab Data and Operations Sub-committee (DOS).

Their recommendations are summarized for both space segment configurations in Table 2-1.

b) The capability for providing small offsets corresponding to a small

fraction of the minimum width of the telescope's point-spread function

is required. A 0.1 arc-sec offset with 0.016 arc-sec resolution is

typical. These offsets could be necessary to eliminate the aliasing

caused by the coarse sample interval of the DI detector. The recording

in sequence, of a number of exposures with very small differences in

the guidance null positions, corresponding to the fine sub-pixel offsets needed to give critical sampling is a technique under

2-3
CO

cu

4J

y

cu

•n

XI

O

CU

y

c

01

•H

CU

e

o

hi

u-i

•a

cu

CO

c

o

cd

hi

cu

CO

e

§

4J

CO

>>

eo

TJ

3

O

hi

O

I

CM

»— *

4-1

X

CU

a

CU

J=

4-1

C

•H

oo

c

•H

hi

CU XI

c

c

o

•H

4J

y

cu

CO

i

XI

3

CO

o

4-1

IH

CU

UH

CU

hi

CO

hi

CU

a

CU

4J

M

»TM*

C

c

4.

CO

IH

-

01

•ri

UH

C

cj

c

o

iH.

4J

cd

hi

cu

13

•H

CO

C

o

o

e

o

4.1

CO

S

cu

y

cd

CX

CO

CU

•H

4-1

hi

o

CO

CU

iH

4J

4J

3

CO

cu

€

a

eo

o

hi

ex

cu

Cu

•o

cu

g

cd

00

o

hi

CX

cu

1,4

PM

CO

3 CU

CO T3

hi O

CU C S

> 0

•H 00

e 4J c

o as — i

4J cu co

y ex hi

cd o cu

hi CX

cu -o o

4J CU

CM a r— i

•H a co

cd ex

41 hi iH

a oo o

•HO C

4J U -H

r-l CX IH

» 4) IX.

O) hi

(2 cx o

,H

0

U"^

c

0

•H

4J

y

co

CO CU

C 4J

0 C

•H i-t

jj

cd cu

> a

<U 4J

CO r-l

ft CO

O CU

hi

UH

O 00

c

4J -H

C hi

CU i-l -

y 3 hi cr

01 Ol

A- hi

*Q

4J CO

hi C

•rH O

x: -H 4J 4J

CO

CO >. >

C rH 1-1

O CU 01

iH 4J CO

co a o

> 1-1

hi X rH

CU O rH

(0 M cQ

xi cx

o ex UH

CO O

y

•H hi 4J

ex o c

O UH CO

y y

en 4j IH

o e cu

IH 3 CX

4J 0

<J (J s-*

01 y o

CX cfl f>

4^J

•H

rH

y

cd

UH

UH

O

00

C

•H

C

o

•H

CO

CO

•H

a

a

8

c

o

1-1

4J

y

cdU

cu

4J

C

•H

S

•H

4J

1-1

cd

01

C

>» o

hi -H

CO 4J

a o

•H C

hi 3

K UH

O

2-4

1 C C

•H O O 4J

CO iH "H CU

•H 0) 4-1 U 00

3 x; co co hi

cr 4J N hi co

CJ iH 3 4J

ed C B 00

00 iH iH CU

Ol rH CX C Cd

oo to o o c

IH y hi

ed >. « 01

0) -H C rH

•O 4J rH O) CO

01 co co a

4J hi 3 C

m 3 x: hi co

•H y cx 4J /-N

co y cd co o oo

co cd hi e 4J c

Cd OO-H iH

o o s x:

•a 4J IH 01 cu y

c 4j x: rH e

3 C o 4-1 co 03

O O CU hi

iH TJ CX UH hi XI

O 4J CO O O ^-'

r*

4-1 Ol

00 1 -H rH

4J 1 4J 0 hi 3 CX hi

CXI 3 iH CUOI4JN^ac U

0) O O O U-l XI 4J hi 1-I4J

•H M 1 3O4JCOCCOr H

lyC X ^i 0) T3 i-ICX O iH

cu -H *yxtcuco o a. -H 13 u-i

hlUHUHCOO l hi -rt C 01 3 4-1 C

CXUHOOIX!r H cdi-iacOiHcdC U

Ol 4JyrH*OOhl-r 4 CO 4J

CU CO3 -HC U 34J>,-rt/-\c d

4-1 o m -H c IH C o! C cr C hi

rH O 6 CO ^ 4J iH • 0) O O 11 4)

00 rH C C 3<Ut H 0! E 4-1

c co ao>4H c i-t cu o o >. oirH

•H CdOOrHXIrHC i • i-l 4J > CO

•UOi H iH 4JrHOICUrHCUr H

•H4JrOCO4JC U O-HCOCOOOOC O

h i OICOaUHUHhlCOahl>C d

|H CU "XJ rH 5> iH O Ol X- hi Cd C

CU y d CO iH 4J 9^ CX CX O 4J iH X*

>CCOCJ4JrH»4O X C U

O 0 » coycOOCNoir H y3 3

3COICOCU1/ 1 cdTJ-HCUC O

hlCTO e I- 1 XrHCrHCXh l

CD 4J 4-1 xi <u xie-Ho y cc

00 cfl 4JX:-O-HO4J3co>,O O

C-ON C 4JCUCO-HC O OrH-H- H

1-ICUlHlHOO lHC04J>etHX>4J4 J

4-ie a coiiHOcohiO4JiHcd y

CO C- iH X iH CO 3 CX VJ CU *H y CO ^H CU

T3 03 4J B In CB CT Ol CO 4-1 0) CO Ol rH

3"exo'rH(S>&22 o"o co co'cxo'c o

Ol

a

•H

4J

i-H.

cd

01

hi

X^I

•o

01

I .

o

UH

hi

01

cx e

o

CO -H

c U

o o

•H cd

4J hi

y 01

3 C

0
0

1caocj CO01u01 o0>c01 •H

co1 Ol sopTJOl COco4J

cfl p01 T) iHCOes0) COcopoCN.0g

1—^

4-1XOl

4-1

01c•H00ciHpOl A3edo•H

4-1O01CO1fl3COop0)

<4H01pCOp01 1eOl uH

l__l

co•Hp3ai

Ul c8co•H4JCOp01 •0•HCOeoCJ

Spo

Ul 4J rHP*01oCOo

.

CO0) • •H

4-1poCOOl

iH

4-1

4-13CO

•o01p

•O iH

CU 3

rH 0"

3 01

•0 p 01

,£ 41

U Xt

CO

rH

01 rH

.£ iH

4J 3

Ul 01

o c•H 00 rH e oi •H e c -S C 4J (0a, oi Ol C P C P rH o ft

M-) Ol

_CO Pa

COOl i0

01G

•> 4J

00e oi •H rH e u o x iH O COCO 00 •H a e 1-1 e e o e (J COrH X 0. U 01 •H P rH•H C CJ O CO iH UH COCO 4J iH P S 0Cu CO

ft3 0

)

CO P01 O A 4J 3

1eOl CO0)p(XO) p•oOl p01 •o

•rtCOcouCOCOPor?CN^HUHO

01 CO S H

•H CO

01 4J

J3 rH Ul CO O

•O Ol

IH p e 3 0 O P -< 3 oi 4J U CO oo co ua C rH P iH 3 C 0) 4-1

C MP

CO 1H 01

rH S O.

ft -rH

Ol C -O

P -H C S CO

CO

•H o d •

J= 4J O M

H -H e

•O 4J O

• CU O iH

Ol C CO 4J

> 00 P cfl

iH iH 01 P

4J en 4-i oj

cfl oi C Cu

4-1 73 -r*. O

en

rH

iHCOCJ

•rtCu

4-^101poA CN

Ul oS3e•Hc•HsCN4J •HStPO

CO P C (1) 0 0

.

•H4J P CO Ol > .O P S Si J30 0 o

Ol s

iH4JPOl O > m o Io oi •* CO

cfl 01PCJe•HSi 4J -HS0en

Oen i

n

1 CN

mes

1pcuCO

.£1 rH 4-1

0 cfl U

4J O>

X 0 O P

Cfl TH 4-1 -H

•O ft T3 0 f P cj « -a oi co -H e a. o » co P P 4-1 -O X oi o oi a* £> O) P O § 0. co u CO ft CO e e o UH O P 0) O O *J 00 CJ CO 4J CO Ol X P c e ft P oi oi o co oi > 0 -H SO <! p 4.) P CO cu co o e O OH > UH -H •o

om m 1 f^ 0x^rHCOU

1-1

ft

4-^1 in i

n

CN en

1OCN

NM/ Omen

C0•H

4-1

COP /-

N

3 CO

•0 <U /-v

4J CO

X 3 0)

4J C 4J

•H IH 3

rH 8 C

•H •*-* iH

ja e <e <u *^ rH TJ •H iH 01 ca cfl -a > 4J iH CO iH VJ CO J2 iH 4J P rH ^ 01 O C P oo 3 m P p CO O co ai H ft O O UH

P01oo •H^^O3aX

,_4r\ iHCOCO

I

^3cCO 000^H^P /-

N

O N UH >CJ p N-^ 01 £ CO 00 01 •H C

Cs]

AU 0

0

3 C S -r43 X 0) rH -H ^a > •HCO CO CO 3 0 0

ft 3C T5 -H e 4-1 CO C o a O 1 0 C •H O >N C 01N•HCO014JCOe•H0^p

CO ft 3 ft 41 « •^en 0 —

O1men0en1mCN

COc04JCOp01CO ^o

><l

aT3p01

ftp01e01ooCOpD

. ^O

2-5
•o

cu

c

e

o

y

oo

0)

u

y

cu

cu

y

cu

I

hi

•o

cu

CO

c

O

cd

hi

cu

T3

•H

CO

O

CJ

<U

iJ

CO

T3

O

hi

O

I

CM

.Q

&

•—I

4J

X

01

4J

CU

si

C

•H

CO

e

•H

hi

cu

J3

e

c

o

•H

y

cu

00

I

jo

3

09

O

4J

hi

cu

U-l

CU

hi

CO

hi

1

c

e

cu

JJ

rH

^^

C

c

4.

\

c

u.

c

O

U

C

o

•H

4-1

<d

hi

cu

•0

1-1

CO

e

o

u

S

hi

o

UH

4J

cd

r-l

cu

y

cd

a.

CA

0)

•H

4-1

hi

&

<a

i-l

4-1

4-1

3

C

C/5

O

1

^

o

^

X

1^

ON

O

^H

X

m•

PO

CU

4-1 4J

Cd -H

hi J3

hi

cd o

cd hi

•rt <y

CX

CU

00 CO

C3 4J

hi iH

cu ca

3 0

T-f

0

«—*

0

^H

X -»

o ^^ cd

TJ

CO

CU

4J

3

C

•H

B

a

00

H

O

en

1

o

rH

X

•H

0 3

0 >,

-* cd

T3

X en

hi

in cu

CX

ca

cu

e

•H

4J

i-H.

cd

hi

CU

>

CU

cn

00

CX

JO

2C

2

4J

cd

CO

•r^ ^^

CO 4J

CO -H 00

>» IH .a e

CO B hi •*

•a oo o -a

hi CO CO- o CU

CU hi CU -H i-l

ex 4J 4J 4_i u-i

3 ed

4J 4.) —I .C Cd

•H CO S *H i— (

PQ C3 SMS f— ^ fT|

o o o o

jj

CU

,£

4-1

•a

e

cd

Q

cu

r?

4J £

CX

o cd

4J hi

oo

CO O

CU hi

•H tJ

r-i y

ex cu

p. ex

< CO

o

CO

cu

•H •

r-l A

a. Q.

ex cd

< u

30

0

• ^|

CU 4-1

hi y

3 cu

CO CX

o ca

CX

x cu

CU JS

4J

hi

cu -a

CX C

03

00

CU r-l

u a

3

c cu

•H ff.

0,

CO

CU

S

•H

*J

cd

cu

hi

A

"3

cu

y

U-l

0

e

0

•H

4-1

cd

eg

•H

r-l

•H

4-1

•

cu

i— i

J3

•H

CO

00

o

CX

CU

hi

cu

i

4_)

CO

cd

cu

4-1

cd

e

o

•H

^j

cd

3

•O

CO

CU

4-1

3

C

•H

S

m

I

o

rH

rH

O

U-4

4-1

CO

cd

CU

I-l

u

cd

c

o

•H

U

cd

hi

3

•o

CO

CU

4J

3

C

•H

e

m

CX

r-l

y

hi

<

o

CO

cu

oo

e

cd

.c

y

c

o

4_|

<d

hi

3

60

•H

U

C

O

y

ao

c

•H

»

O

^,_f

U-l

cu

4J

U-l

O

CO

cu

00

c

cd

si

y

c

o

•H

U

<d

hi

3

00

•H

U-l

C

O

y

oo

c

rf

a.

ed

hi

oo

o

4_»

y

cu

CX

ca

cu

Si

4-1

U-l

O

r*

CX

cd

hi

00

0

hi

4J

y

cu

a.

00

*o

cu

hi

•H

3

cr

cu

u

CO

e

o

•H

4J O

cd -^

>

u

cu

CO

0

T3

cu

4-1

«

cu

CX

S

•o

cu

hi

1^4

3

cr

cu

hi

CO

c

o

•H O

4J CN

 -

cd

hi

cu

00

o

•o

cu

4-1

cd

CU

c.

S

y co

CO -H C

hi hi 0 1

03 4J — I ,-1

4-1 CU 4-1 CU rH

co S *^ cd S cd

O C hi -HO

•^ 4J Cd JO 4-1 i— 1

hi O 1-1 hi CO

•O CX r-l cd O UJ -H

c o y ca — ( s

Cd 13 JS 4J r-l O

•uccuyc x co 03 c

cocd^i-ic d U4J O

4-1 hi hi J3 O hi

Hj O AJ 00 «rH W tJ

O -H U-l CU O r-l CO

hi o B hi cd X. cd

C- CU CJ 4-1 y i »M r*

OSOOC U CU3C O

4-1 U 4-1 Q. CD Cd*O 4J

>cohihic u Chio >

i-i 03 ja 4-1 j; cucd-Hh i

ajhir^a j hiBedc o

O<*-lcJCO O Ony^ O

0 0

2-6
•o

cu

d

iH

4J

o

y

09

0)

>

•H

4J

y

01

•r-)

<§

d

cu

iH

y

en

cu

4-1

e

o

I-l

>4H

•O

01

>

•H

U

S

CO

d

o

•*4

4J

COw

CU

13

•^

CO

d

o

u

cu

4J

CO

>,

en

TJ

3

O

U

OTabl

e 2-

4-1

x

CU

4-1

01

f

J_l

c

1-1

eo

d

•H

Vl

CU

.0

a

d

d

o

•r4

4J

y

Ol

CO

I

.O

3

00

o

u

J_l

0)

14-1

cu

V4

CO

1-1

01

&

d

S

0)

u

rH

i__i

d

o

•H

4J

<?

h

3

01

V4-I

d

<S

r«

^

cfl

M

Ol

•o

•r"

Q(

g

C

o

s

o

U-l

(0

r-l

PL<

Ol

y

(0

o.

in

cu

•H

4-1

}-]

C?

0)

±J

Jj

s

1

cu 1 co II co

C 1-tVj *J > cd T3>

O <U CU " -H fcl > Ol Vl

co j-i u .£ ,0 <u i-1 >> do

oidcuoiyi-icDcucu d -H co

M-H-o6do,acoe < Sj a

C(J 4J CO 3 O »Q ""H 00 w O "O

CU O ^J Cfl rH O 4"^ d CU 0)

CO CU 4-1 CO rH Cfl <U • ,H .U rH -H

4-1 S O. 3.drH<4Hd>0>C0 3

C O "O 00*J4Jr-IOO>-iT33T 3

01 y cu I-H d y ea i-icu 4jc u

a Q cu<4-ii-i4J3 oi^oco^^co y o

ca CQ uoi — i-HOcudOi-ii-i o oo »

H H i-l •HJS'Hjr-H'J-l-i-'a 4-ICU H

3co4JvirH4j g y M-J co j= co

CT4J3O O M>>dOIO34-iO I

cu o) ^ V4 01 y 3 .d s 5

M CO 00 *O O *•* d *4^ 4^ d 00 *^ *

4-ICU CUO I ^i-^^-j 1

•HoJOItH^i H y 34->y4JT30 0

4J>»J-O3O>M- I 00 1-t -H r-4 13

C 0) *H CO OIO)OQ3£yCUCOL l

CUC03CUiHQQ* H dO'HiHCOd O

•H C7*d 1-|£OOO)-I4J14-| O O

yoj cu-r-i4J.d y di-*J3 OUM-I >ITH y

CO O(^ScO*JCOlH4-l4JOQ J ^O 4J CO

• so

d d « ** o *^ ^*

c o s «

•H -H >H

*J » > 5s

cd 0) (0 CO

C d co Q. d

•H 3 O

r-l >4-l O >> -H

oo y o 3 n "

u d d co y

co -H OO-H -a in

m ~3- d -u C t-i

rS T3 -H d O 4J

CN CO CO v CU Ol

0) Q, T3 1

•ad <u <u

3 - cfl S »

4J 00 ^ -HO

•rn c ai tsi u a.

4J i-l rH > Q- e

4j co oo u 1-1

CO cfl d >— ' -O

j= CO co 4J

^ Cu CD ^H O

•H CO CU ••• d

O CO -2 N W "O

,^

X 01

4J i-l 1

•H J3 CO

r-l Cfl )-l

(U -H rH Cfl

rH J3 iH O.

3 iH 10 rH

T3 X > rH CO

4J 0) Ol cfl CO d

00 £ O rH 4-1 O

rH CO S -O •>->

«04JiH^. ( w M g

t

"'' 0

( 4 H l

rH2 0, a ">«

4J S 0) CO d O *

«d t*\ S CU O ^*

i-H CO y *H 3 iH V4 ^%

y-OCUOIcO<4H d O

•rH (1) <^o QJ V^ N Q)

S M £• ^3 *^ ^5 *^ *^

dO.4J>S-HOI- H i H

OOIdOlH4J4-IU H M

lj(jQt| 1 ja,CU'* H O

u Prf O cu >«x o a <u **^

•2 o o £

e d* o

2-7

"O

0)

I-l

iH

3

CT

<U

O

2S

i— 1

CO

S

d

"e

0

"^ W3

^3 tTM^

(U C/3

c

iH O

00

cu d

T3 o

>

*-^ iH

CO CO

3 "£

O 3

.d 4J

CN Ol

— i O.

1

CO

J^

CU CU

Ou rH

o y

01 y

>

« d d x-x

ij cu d co

4J CU rH 00

/^*

"*2 S ^5

OO o" y

•5 »H O )*

c •* o

rH d -H E

O. O S >~x

eS H o

a
T

3CU3CCOyCOOJ ycu

•*-)

.oocuycuCUoId•ocuCOcoCOLi 41 •O•H00 I414JCO CO3OIdOI41

1— TM»

4JX414J41

4-1d•Hood•HId41 JOdCo

1-1

4-1y

-

41

CO13CDO

4-1Ll CU

<4d41Li COId41 •gCs41

4-1

hd

*~^ i IMC1 0dcC5 LI 4) •c00cu

sIdo

<4d 4JCO

ll CM4) ya

.

CO

41

il

4-1Ll OCO41

rd.

4-1

4->3CO

41

COd c

o

O 41

O* 4J

co 3 41 d Id id 1 S 4J •H 0 ja CM Ido • 00 0 d Ll •H 0. S o. O CO •H

iH 14-1

O 0

14-1

41

L. s O -H 6u 4J CO414J3C•Hem••*.XoIda. a.

cfl COcu00dCO 4=ycu iH id

.

41 4-1

id 41

4-1 00

Ll 0 o a

.

d CD iH 41 S Id 0

«coy4) CO o£SCO *^cOy41CO oCMV/ 1Li 4) 4J 4

1

d CO

•H e0 41 Q" e co

•H 4)

4-1 Id

rd.

a) >%

41 4-1

Id iH

l-d.

Id -H

CO .0

41 CO

C Q.

^ CO

4) y

•H d 4J 0

i-d. iH 4)

co 4J e

4) y -H

a! co 4j

o

CO

4JdoeMo

<4dCO^\ cd

d

i-» o•H

4-1 4-1

oo cd

CO >

CU LI

rd. 41

CO

CO O

r* ,_^ 4J CO -H y 3 T-S CO O x d

cfl O

•O Id

4-1

sr co

-d CO

do•H

4-1Ll3T3d r

d

0 3)

id 4-1

CO O

co H

•HS 0 o4

1

CO

cdy

4-1

COido3CO

O~ v 41 m

a 9 H V^ §

4-1L^l CU4141O

C -0

o d

•H Cfl

4-1

Cfl rd.

y co

•H d c Ud Id o •H CU -H Ll 10 4-1 4J 4> -H d CO > CO iH I

d

>v *^s CO

00 rd Q. 41

d co d cu d o

•r4 d- o u o

Id CS -H Qu Z

41 4-1

41 41 CO X

dUb LI

•H d Ja u

oo cd IH c

c e rd cu

41 Id CO (U i o y /-<• M CO I4d r-( >> LI 1 cd 1 cd cu d •o o, >> u x cd CU CO • d x

COd0•H

4-1

CO

jj4100

4d 0

iH *O d 41 rd

. 00

CO 3 4-1 03 C

<U 4J 03 6 -H

•H Ll 0. L, J-

*-• O il O CJ

•H a, y d d

> Q,-rl Cfl

•H O 4J I4d Id

" d o ja

CJ <4d CO

co o 4j cu

u e 4-1 Id 00 41 41 cd 41 4J J3 y d A 41 S Ll Id o £?^ S 2 0 £ 0 0 < CO 4-1

2-8

yc

.

oy9)oId4Jy4) Q

.

CO00

•o d 41 *H Vl 41 •H J3 3cr 4J 41 CO

eat oe • f- ^j

id.30V

f-d^^4) •H 0

rd.

COCo•H

cfl ^J41COr>OCOLj O

dO '

i i

•rt o 4dCO 4J N d "H CU

rd. y

•H Li

4-1 0)

=> CU

0 0
cu

•O

t-H

U

O

u

CO

cu

cS

cu

y

C

cu

•H

CU

s

o

Ll

•o

cu

CO

o

CO

Ll

cu

•a

•H

CO

c

e

cu

4J

CO

>,

CO

T3

3

o

Li

I

cu

»^^

u

X

cu

cu

j:

c

T-l

60

e

^H

Ll

CU

C

e

a

•H

4J

y

cu

CO

1

,0

3

CO

o

Li

CU

U-l

CU

CO

Ll

CU

e

cu

M

C

o

•H

tJ

3

60

U-l

C

Cj

C

o

•H

4_)

CO

Li

CU

•H

CO

c

o

QJ

g0

ij

CO

i-l

CU

y

(0

a.

CO

CU

•H

4J

Ll

O

CO

cu

iH

1 }

3

CO

• cu

u -a

•rt -r-l U

(— ( 3 •— (

co O 3

y

p« • ^^

a. T3 «-<

CO CU «-i

60 CO TS

0 -^

Li CO C

4-1 CD -H

y (0

CU 1 C

fS- «^ Q

CO tf «H

S w

IW O iH

O P CO

60 -H

c ^ cr

cu I-H y •

B ^ co co

e -H -o

60 0) Li i— 1

•H CO CO CU

r-j O 4J -H

<; o. CD u-i

l>

•^

CO

JC

Q.

cfl

60

O

4-1

y

cu

a.

CO

o

^.j

c

cu

60

•H

^

CO —''

4-1

e

cue

cu

•H

3 13

cr cu

CU 4J

M M

O

60 a

C CX

•H ?

c

•H CO

O C

a. o

•H

r-t *J

co y

•H e

y s

CU t*«

a.

co o

>

CO CO

cu cu o

>» >. e

x

CO CO i-H

cu cu cu

X X ^i

•H

^

e

o

•H

4J

CO

Ll -H

CU 3 &o u cr

e 3 y -o

•o -H a, a cu

cu 4-1 a 1-1

4J C O T3 CO

Ll -H y CU -H

O O — I CO

CX CX *T3 ^ Cfi

CU Ll O CO

3 T3 CO Li

co C o *J 3

•H .a c 0)

U -4 C O Li

a» ja o y y

•a

O i l 1 S I I i

o

CO

cu

X

•-^i

A

CO

0

Ll

PH

•0

cu

4J

CO

•H

CO

CO

CO

T3

e

3

o

60

1

1

2-9
consideration to support this requirement. With a photon counting

detector as proposed on Starlab the sample mesh can possibly be made

arbitrarily smaller without degradation in overall picture quality;

the penalty is the increased demand on data transmission and processing

for a single field. However, technical limitations limit the mesh size

adopted. Utilization of this technique would increase operational complexity, but is only proposed for the space platform configuration

missions.

c) Most observations, particularly direct imaging, are expected to have a

duration of approximately twenty (20) minutes or longer. Table 2-1

presents the number of observations per orbit and the average number of

observations performed per day for both configurations.

d) The proportion of direct imaging observations relative to spectroscopic

is a function of observational requirements. The percent of

spectroscopic observations anticipated is presented in Table 2-1.

Utilization of dark time for direct imaging with spectroscopic

observations conducted on the sunlit side of the orbit is likely to be

common.

e) Observations of variable or transient phenomena will frequently be

necessary, and will result in the need for repetitive observations of

the same field.

f) A significant fraction of scheduled observations will require multiple

exposures at the same position and with the same instrument

configuration to achieve a single long exposure. This results from the

duration of target availability for a single orbit (refer to Table 2-1

2-10
for typical dark and sunlit side observation durations). It will be

desirable to return to the same guide star and Position Angle (PA)

to facilitate the addition and registration of the images (both imaging

and spectroscopic) for these exposures.

g) Observations with high time resolution will be required for the study

of objects displaying periodic or aperodic variability of short duration. The capability to store data from a small area (or sub-image) in

successive areas of the Accumulating Memory (AM) will be required. The

ground system will need the capability to extract data collected in

this operational mode for the analysis of observed variability. An

absolute time accuracy of 1 msec is required.

h) Based on the need to schedule two (2) to three (3) observations per

orbit as a direct consequence of the need to avoid target occultation

by the Earth, a significant number of large maneuvers will be required.

Table 2-1 presents the approximate maneuver size and average number of

maneuvers required per day.

i) Based on the mission profile analysis for the Shuttle sortie and space

platform configurations (references 13 and 8 respectively) and the

assumption that an individual exposure produces 1.3 x 10' bits per AM

memory dump (9000 x 9000 pixels x 16 bits), the average data rate

requirements presented in Table 2-1 were derived. The NASA tape

recorder of capacity 3.8 x 10 ^ bits can store approximately 29 Starlab

images of this size. However, it is recognized that several factors

could increase these values including:

o Utilization of shorter than average exposure times.

2-11
o Inclusion of engineering data of approximately an additional ten

(10) percent.

o Increased detector resolution requiring significantly increased data

per exposure. For instance, an increase of a factor of two in

resolution would require a fourfold increase in memory size.

o The requirement to sub-step the telescope to overcome the image

sampling problem as described in item b) above would require an

increased number of shorter exposures. This could increase the

quantity of data required to be dumped for some observations

(approximately 30% TBD) by as much as a factor of 4.

o The need to transmit additional data in a non-destructive mode during

an exposure for ground monitoring purposes.

It was therefore suggested that based on these factors the derived values

should be increased by a contingency factor of ten (10) for planning

purposes.

j) Orientation of the Position Angle (PA) will be significant for certain

observations. These include:

o For imaging, when multiple exposures of the same field are required

(e.g. in different filters, or to achieve a long exposure), utilization of a "constant" roll angle will facilitate image analysis.

o For spectroscopy, the roll angle may need to be defined to align the

spectrograph slit at a desired PA.

2-12
o When required due Co a thermal constraint,

o To support guide star selection.

k) There is a requirement for scheduling regular calibrations of the

instruments. These calibrations include measurements for flat fielding

of the detectors and filters, astrometric and photometric calibrations

on star fields, focussing and alignment checks, wavelength calibration

of the spectrographs^ spectrophctometric calibration of Che

spectrographs on standard stars, and determination of the intensity

transfer function. The frequency of calibration measurements will be

determined primarily by the repeatibility and stability of the

instruments in orbit. These characteristics are not known, but the

information presented in Table 2-1 is assumed to be fairly typical. In

addition, the following calibration requirements are likely:

o Focussing sequences may be required for verification purposes.

o Astrometric and photometric calibration of the DIs will require

collection of data from selected fields for TBD minutes per day.

o Occasional exposures on standard stars will be required for

photometric calibration of the spectrographs.

1) The ability to track solar system objects with predetermined orbits is

required.

m) The astronomical targets to be observed will be selected by some form

of tri-national peer review procedure. The timeframe for the selection

2-13
of these targets is shown in Table 2-1. In addition, it is expected

that the targets selected will require a longer period of observing

time to complete than the time available since this will provide for

flexibility in the construction of an efficient mission timeline. The

factor defining the ratio of selected observing requirements to available observing time is also shown.

n) Optimization of the orbital parameters can provide a significant

improvement in the amount of observing time and also the ratio of night

side to sunlit side observing time available. This results from

phasing passages through the South Atlantic Anomaly (SAA) entirely

outside orbital darkness, selecting the mission timeframe to coincide

with the new moon to reduce background light levels, selection of the

sun beta angle to maximize the amount of time spent in the Earth's

shadow and the selection of the location of the CVZ to coincide to

desired target areas. In addition, orbit altitude and inclination

affect the plasma glow intensity (reduces with increasing altitude) and

the size and intensity of the SAA (both increase with altitude). Table

2-1 summarizes this requirement.

o) The payload complement selected should allow Starlab the principal role

in the selection of requirements such as optimization of orbital

parameters (reference item n. above), and should avoid secondary

payloads imposing restrictions on achievement of Starlab science and

operational objectives (Table 2-1 summarizes this requirement).

p) The capability to perform specific replanning and interactive

operations is required. This requirement is presented in Table 2-1.

2-14
q) The mission duration needs to be selected to enable adequate

performance of Starlab astronomical observations. Again, Table 2-1

provides specific details.

r) Serendipity observations with the DIs should be conducted during al-1

spectroscopic observations. In this mode, imagery of the outer field

segment is obtained during the acquisition of spectroscopic data from

the inner segment. This is the only approved parallel instrument

operation and will most likely involve the use of the grism (for survey

purposes). Utilization of this mode will involve the separation of the

direct imager component and the spectrograph component from the data by

the ground system.

s) A requirement to observe targets of opportunity, such as comets,

supernovae, and errupting variables will be relatively infrequent. An

average case would be once per two weeks, and would probably not arise

during a Shuttle sortie mission. A target of opportunity would

frequently require more than one observation; e.g., a supernova would

be observed perhaps 15 times over the course of weeks or months.

Overall however, targets of opportunity should account for less than

five (5) percent of observations. Observation of targets of

opportunity should be performed by replacement of a planned target in a

timescale of a few orbits. Reference 16 specifies a maximum response

time of 12 hours, with a goal of a 3 hour response time. This

capability should use standard procedures for the updating of

preplanned timelines. Table 2-1 summarizes this requirement.

t) The capability to plan and execute alternate branches within the

preplanned timeline is required for the space platform configuration.

2-15
Utilization of this capability for the Shuttle sortie case is considered unlikely, since it is not proposed to request significant

changes to the timeline at short notice (i.e., a new target) in this

mode. The frequency of branching operations will be commensurate with

the amount of realtime astronomy conducted and in practice should be

less than 10% of the operational load for normal operations. This

restriction is important since utilization of branching provides additional complexity requiring constaint checking, maneuver and acquisition computations, and verification of end-state for all paths. In

general, branching operations will be used for spectroscopic observations.

The primary function of branching sequences will be to provide

flexibility in observing poorly understood or unpredictably variable

objects (e.g., cataclysmic variables). Preparation of a branching

sequence will require considerable additional planning, which will need

to be justified. Utilization of this capability is not considered

likely for early termination of an observation because adequate signal

to noise has been achieved. In this situation, the start of the

following observation would not normally be able to be initiated

earlier than planned. Table 2-1 summarizes this requirement.

u) Realtime, or near realtime, data processing and analysis will be

required to support routine monitoring of instrument performance and

data quality, diagnostics and instrument optimization, and also interactive observing sessions. For an interactive observing session (probably spectroscopic) facilities will need to be provided for groundassisted target acquisition and also for the display of astronomical

data in a form suitable for decision-making by the astronomer. This

2-16
area needs further study, but it can be assumed that the facilities

would be similar to those used currently with ground-based photoncounting detectors. Specifically, the spectroscopic image (or subimage) would need to be displayed in a 2-D grey-scale format to allow

quick assessment of the overall data. Via cursor control and/or keyboard command, it should be possible to extract from the display, a sky

subtracted spectrum of counts versus wavelength from the object of

interest. This processing is likely to be performed on the raw image

i.e., prior to flat fielding, distortion removal, etc. It will be

essential to have hardcopy facilities to record raw images and processed data. The response time for these type of activities is covered in

item p.

v) Special pointing requirements will be required for alignment of the

spectrograph slit. No decisions have been made with regard to

potential spectrograph acquisition modes, but three modes are likely:

namely; blind pointing, onboard computer controlled acquisition, and

ground assisted (or crew assisted?) target acquisition. Performance of

the latter mode would need transmission of an image obtained via the

direct imaging mode of the spectrograph (an image size of 256 x 256

pixels is possible). The centroid position of a reference object in

the image would need to be determined by a cursor and/or by function

fitting, with offsets automatically calculated and uplinked to place

the target object in the slit. A second direct image may need to be

transmitted for verification purposes before beginning the

spectroscopic observations. Note that precise centering will only be

required in one dimension (i.e. perpendicular to the slit), unless a

coronagraphic-type aperature is used.

2-17
On the space platform it is possible that ground-assisted acquisition

of a guide star (rather than a target) may be required in difficult

fields. This may require transmission of the pointing system sensor

star-field data, or starfield data from the Fine Guidance System (FGS).

Table 2-1 summarizes this requirement.

2-18
3.0 OVERVIEW OF THE STARLAB SPACE SEGMENT

The Starlab facility will be carried in an attached payload configuration

on up to two Shuttle sortie missions in order to provide a sufficiently

early launch date for the facility. These early flights of approximately

two weeks duration each will be followed by a series of flights on a space

platform such as Leasecraft or the Space Station. Utilization of these

different space segment configurations provides complications especially in

the Starlab facility interface, since the avionics and capabilities provided by each configuration are dissimilar. In the Shuttle sortie configuration utilization of the Spacelab is required since the IPS is an integral

part of this system. For the Space Station the configuration and

capabilities are largely undefined at this time, whereas Leasecraft

primarily utilizes a Multi-mission Modular Spacecraft (MMS) system. The

solution of this interface problem is outside the scope of this document,

but the impact of the utilization of the different configurations from a

ground system standpoint must be considered.

3.1 FACILITY DEFINITION

The facility consists of a 1-meter f/15 modified Ritchey-Chretien

telescope, and instrument bay, and data acquisition and control systems.

It will be approximately 5 meters long and 2 meters in diameter and will

weigh approximately 1800 kg., including instruments. The nominal telescope

optical coating for general applications will be aluminum overcoated with

magnesium fluoride, usable from 1150A to the near infrared. The telescope

will provide a fully baffled field. A reflective corrector will direct the

telescope beam to the DI instruments, mounted radially, and enable the

entire 30 arc-min diameter field of an instrument to be recorded with very

3-1
little degradation of image quality. An annulus of outer diameter 0.8

degrees and inner diameter 0.5 degrees surrounding a Dl field will provide

a guidance field for a Fine Guidance System (FGS). An uncorrected data

field in the axial position will carry the multimode echelle spectrographs

designed to accommodate slits up to 8 arc-min long. It is intended that

simultaneous operation of a spectrograph and a DI over a significant frac-

• tion of the DI data field will be possible (serendipity mode).

In the attached payload configuration the IPS will be used to provide crude

guidance via star tracker inputs. In the space platform configuration

similar pointing capability will need to be provided. Fine guidance will

be accomplished by the FGS. The fine guidance sensors will be mounted in

both radial and axial fields, where there will be TBD FGS sensors: TBD for

the DIs and TBD for the spectrographs. It is proposed that the spectrograph FGS sensors be capable of acting as backup for the DI and vice versa,

where in the latter case there would be a sacrifice in the ability to

orientate the spectrograph slit. A Guide Star Selection System (GSSS) will

be needed to support utilization of the FGS. Access to the ST GSSS data

base and/or utilization of ST developed systems and/or expertise should be

explored to support this requirement.

The FGS will provide an image stability of 0.016 arc-sec rms and a minimum

probability of acquiring a suitable guide star of 95 percent without target

decentering at the galactic poles. This fine guidance will be accomplished

via articulation of the telescope secondary mirror.

Bright objects must be avoided during telescope pointing. The avoidance

angle for the Earth will depend on whether the limb is dark or bright.

However, the dark and bright Earth avoidance angles are not fixed

3-2
quantities, but will be dependent on the position of the terminator,

instrument used, wavelength range, target brightness, etc. Faint objects

will require the darkest possible sky and observations in the far ultraviolet (UV) may require higher angles to minimize atmospheric absorption.

In addition, it is anticipated that less stringent conditions will apply to

the FGS, depending on the magnitude of the guide star. Typical requirements are presented in Table 6-6 in Section 6-2. However, reference should

be made to Starlab requirements specifications for precise values. In

addition, consideration will have to be given to moon avoidance, bright

star avoidance, zodiacal light background, and avoidance of the bright or

dark Orbiter surface. The sensitivity of Starlab to the ram effect is TBD

at present. A cover with automatic closure within TBD degrees of the sun

will be fitted, but this is a contingency safety device and should never be

exercised under normal operations.

The sensitivity of the two instruments and the FGS to the South Atlantic

Anomaly (SAA) may be different and the capability of modelling more than

one constraint is therefore required. In addition, the model should be

adaptive allowing modification when necessary. It must be possible to

switch the FGS into a standby mode during passages through the SAA. Observations of bright targets or calibration exposures may be performed during

outer SAA regions.

Roll pointing precision is required to be 0.25 x narrowest spectrograph

slit width or 15 arc-sec rms. This precision would be provided by the IPS

in the attached payload configuration.

Two instrument types will be carried in the instrument bay. Two DIs

mounted radially and two spectrographs mounted axially. The DI will have a

3-3
30 arc-minute field of view and utilize two detectors to provide coverage

of the ultraviolet and visible/near infrared spectral regions. A total of

24 and 24 filters are proposed for the ultraviolet and visible/near

infrared detectors respectively. Two grisms (one per detector) provide

spectral resolution across the entire 30 arc minute field of view for both

spectral regions.

The detectors will be of the photon counting type with a diameter of 90 or

130 mm. These detectors provide 2-dimensional image registration over up

to 10,000 x 10,000 pixels. The filter accommodation and detector size for

the spectrographs are TBD.

Data acquisition and control functions will be provided by various onboard

computers. These include the Starlab Computer (SLC), the Telescope

Computer (TC), and Instrument Computer (1C). In general several baseline

and non-baseline functions are likely to be provided. Table 3-1 presents a

preliminary breakdown of likely functions for the various computer systems.

Table 3-2 provides several additional functions which may be considered for

potential inclusion.

3.2 FACILITY OPERATIONS

/

The multi-mode spectrographs have been designed for on-orbit operational

autonomy. There are three modes of operation.

o Low dispersion: three mirror surfaces, four interchangeable fixed angle

gratings used in first order. Ultraviolet cutout filters can be used in

long wavelength bands. The maximum resolution is 5000, and maximum slit

length 8 arc-min throughout the 1100-8000A range.

3-4
Table 3-1: Onboard Data Acquisition and Control Functions (Preliminary)

System Function

SLC Facility control including:

— Power distribution and management

— RAU interface management of TC and 1C interfaces.

— Starlab CDMS Management (SLC/TC/IC buses, etc) including:

redundancy management

— Performance of facility level functions including

o command buffering, preliminary decoding, routing, etc.

o telemetry buffering

0 DEP load buffering

o Formatting and buffering DEP dumps.

TC Telescope control including:

— Command handling (decoding, execution, verification, etc.)

— Telemetry acquisition and dispatch (and monitoring functions)

— Management of TC CDMS

— Housekeeping - control of mechanisms, power supplies, thermal

control, etc.

— FGS control

— Test and diagnostics

1C Instrument package control including:

— Commands

— Telemetry (including monitoring)

— Management

— Housekeeping

— Test

— Control of Accumulating Memory (AM) [dump, etc]

3-5
Table 3-2: Potential Onboard Functions

a) A high time resolution mode to satisfy requirements

detailed in item 2.2 g)

b) Full-field image compression

c) Selectable readout of memory (selected area of pixels and

selected bit depth)

d) Realtime monitoring of image buildup

e) Onboard algorithms including possibly an automatic

acquisition mode for the spectrograph, sub-stepping

control, and spacecraft ephemeris generation (for

spectrograph doppler corrections)

3-6
o High dispersion: two mirror surfaces, four interchangeable, fixed angle

cross disperser gratings used in first order and two interchangeable

echelles optimized for long and short wavelengths. Ultraviolet cutout

filters can be used in long wavelength bands. The maximum resolution is

10 . Maximum slit length is 30 arc-sec without order overlap throughout

the 1100-8000A wavelength range.

o Direct imaging: four mirror surfaces. This mode will be used for

acquisition of very faint objects. The maximum field size is 8 x 0.5

arc-min over the wavelength range 11QQ-8QQQA..

Incorporation of two charged particle monitors is proposed to enable

automatic reduction of instrument detector high voltages upon recognition

of event rates above a predetermined threshold. This situation could occur

during passages through the SAA. In general mechanisms including

assemblies for filter wheel rotation are being designed for • simultaneous

operation, when desirable. Movement times of less than ninety seconds are

planned.

Present engineering studies indicate that due to thermal dissipation, it

will not be possible for both DIs to be fully powered up simultaneously.

Furthermore, the warmup time may be as long as 12 hours before normal

observations can commence. During this warm-up period neither DI will be

available for astronomical observations or serendipity observations, and

therefore the spectrographs must be scheduled at these times. The actual

instrument warm-up characteristics and constraints will be defined during

Phase B.

3-7
There is a requirement that both spectrographs can be operational at any

one time, at least in low resolution mode, and preferably in all modes.

This is essential to allow successive ultraviolet and visible spectroscopy

of time-variable objects. It is also assumed that switching between spectrographs does not require a warm-up period. Serendipity observations are

possible with either DI while either spectrograph is gathering data.

At present, the immunity of the DI detector to bright sources with the

possibility of permanent damage is TBD.

3.3 SPACE SEGMENT CONFIGURATION

3.3.1 Shuttle Sortie

A three-pallet train to mount the Starlab facility carried on the IPS is

planned. An overview of the Spacelab data system for supporting an attached

payload in the Shuttle sortie configuration is shown in Figure 3-1. The

Starlab will be interfaced with this system via Experiment Remote

Acquisition Unit(s) (RAU) and a direct link(s) into the High Rate

Multiplexor (HRM) for downlink of high rate science data. (An alternate

approach using a Direct Access Channel (DAC) is available for the latter,

but its use is considered unlikely). The RAUs are connected to the

Experiment Computer (EC) via the Experiment I/O Unit. The RAUs provide for

transfer of commands between the ground and/or the Aft Flight Deck (AFD)

under control of the EC. Engineering data from the Starlab would normally

be included in the Experiment Computer Input/Output (ECIO) data stream for

downlink via the HRM and for transfer to the AFD for onboard monitoring by

the crew. Alternately the engineering data could be multiplexed with the

high rate science data and input into the HRM experiment channel. However

3-8
L

UOUJ H- 00<CQa.

C/5

r uj:

25i

•TM a* t

? i '

Ss = UJU^^ ^ tf UO '

~

_ <- £

u

 t-« _«a

te U -1 * -JZ

* UJUJ UJUJ

l-iss * « ^ «s I £»_ zi U3SO £ .-MU —«J— 0. X

00

siS

LU

cc: §

Ht:aua9U UUJa. asUJ t— J

K

:£S3.2< a uuH"] 3*•Zh—30U

i

a^£o^_JI^it _j§xA* \1-tacbLtLrkr.Lp^2f-uV, / •CO:i 1 _J! <l 3«

,

Jh»3^9a^ 5nnulc1.

cau5C

P

C

E H • <1 r* uA3<«JIsit h

-

j 3

en-iUJzuvuVJ

hT» 1 h- K

QUJCJ

S<O

OKU

S S

fk.

cs

«-JSO

</1 a. *•CMPO^\

y|

•y^swi ixaS•»iin

CVJ O^

C/1 aac ic\V. zcUi UJaHw^az. S<31. 3-

)tu

nUJXin.or^aS

# £f

E C 5C• a>a

Pf

uK'J:iji

"TTTTT

KUJXUJa. i .

r

oc

> tj3:j =

lo

3-9
without inclusion in the ECIO stream the data would be unavailable at the

AFD. The ECIO stream containing multiplexed data from all instruments

using this capability has a data rate of 51.2 kbps and is transferred via

the Ku-band signal processor on channel 2.

High rate science data with a data rate of 16 Mbps will be transferred from

Starlab to the HRM. This data may be downlinked directly via channel 3 or

stored on the HDRR for later playback. The HDRR is played back through the

HRM at 32 Mbps again for downlink via channel 3. The process of storing

data on the HDRR following HRM processing with subsequent playback via the

HRM produces data, which is multiplexed twice. Demultiplexing twice on the

ground using a High Rate Demultiplexer (HRDM) is therefore required. Full

details of the capabilities provided by these various Spacelab elements may

be found in reference 5.

The data streams required for support of the Starlab during operations

(realtime and near realtime analysis), offline analysis and scientific

analysis are shown in Table 3-3. This table has been prepared using the

assumption that engineering data will be included in the ECIO. The need

for each data type is included. It is evident that a considerable number

of data streams must be correlated in order to perform certain types of

analysis. This requirement may be reduced by multiplexing specific data

streams onboard as required.

An overview of the Starlab facility showing the interface with the RAU and

the HRM as presented in Figure 3-1 is shown in Figure 3-2. Again, this

shows the inclusion of engineering data into the ECIO. In the case where

the engineering data is multiplexed into the high rate science stream, it

3-10
OCOhi 300oo

4-1hi oCO3COhi oCO

4-1C0)e0) hi cr01 aiCO —I

i-tCOCO

4-1

fl

fl

CO H

u

•H

Ul •H4JCOl

1-1oCOOl c

1-11

Ul

14-1 oCOc0

1-14JCO01

.0.

ocoFunctl J//I//II//1

•oOl hi 3cr Ol hi Ol Q. >^ 4JCO

4-1

CO

"OeoCOOl CO

1-1COX

cfl 3en

1-1COXr— ( CO 3

•o / Oi / u I hi /

§•/

§7

CO / 7//////// <UO* >* HcO4J

Cfl Q

C

X O

1— 1

C 0) rl

O J«! CO

•H il C C

4-1 rH 00 O

0) C il -H

a 3 co 4-i hi CO O - 0 C

ui Q Ol il

C b T3 -O

> O

X 01 O

hi .e u-, u

CO 4J O

rl CO

rl B C C •H O O O U hi iH A i-l C U-l 03 CO 4J •< 3 r-l CO 3 r-l tl hi

Cyj d> w CD (U

H -rl C 4-1 Q.

CO > il CO O

co

CO

•K

co Oi ><

rl aCM

H hi

O 01

^ cfl

^ 01

C rl •H hi rH 0» §

4-1c

«§ ^

rl 4-1

2 s o•H T3 4J Cfl CO O O 0

)

hi -H 01 U

01 X -O -H

&, Cfl -rl O

co o a* > >

HCO

e

rlc3o•a

cfl

cfl •o4)ucOl

1-10CO0)oj c2r;00 •H*

^(•

M r^

HBO

H >>

+O

H CO

hi oX01 -^ rH U 5- 3 <w) ^^ rH3 rH S oi e Ol B — 1

4-1 Cfl ID

ca js c

06 u eCO

J= CO ,=

00 CO CJ

•H 0)

"~ CJ C

1 < 01e

.O 4J -H

m o hi rH 01 01 oi ^s hi a

.

0 S -H X

03 2S Q S3

a, -g

CO >->

Cfl rHhi CO

4-1

COs0hi UHCO 4JCO T300c•H

• hi V01e•H00cwCOcoCO3o. BrHhi Ol

4-13o

.

oo

4-1e0)s•HhJ0)B

.

XEd

o" MCJM4J3Q.

4-13o

CO3

4-)

cfl 4J COCOOHrHCOV3CO

4-13cueMhi 014J30.1s014JCO^CO ^3CO

CO01a

.

4J

cfl

4-1

cfl T3rHrHCO UH0eo•H4J

cfl rH01hi tl0o01eiHH^><

r^1

o

1

h- 1 CO4J3Q

.

4J3 H 0 So

ifl

4J

cfl 131•^0) ^Jo4JCO

Ul 0^jd•HHQ^^4^4e?shi 01 T3hi oo0) 040>4J£CO 4J

(rt u_goO-H•^

/*xai OHhi Ol 13hi oCJ <s*^COo

" p*l

eO

XI—I 0)c301hi 0) •o•HCOcooCO —I H

flLl CO

N

>. 1-1

•o01hi

1-13cr 01 ai

4-1

0) CO J33CO1CO

4-1sOl sOl hi •H3cr 0) as

rl CO •H4JC01

4-1 CO

O- 01

P- >•

\ i 0- >•

cj COO) CJ uShi 01ucrHUuoSu ^^Ol

rl U

4-)3J=COCO •H>0) rH^

fl i— i •HCO <1*

4J0c

I—

1 ec•ar*CJ

4-1C01s•Hhi 01a

.

X11

Ul

*r4•o0) hi •H3o* 01hi >^

rlCo1

-1-

3-11
ENGINEERING DATA

COMMANDS

ECIO

SLC

STARLAB

COMPUTER

1C

TELESCOPE

COMPUTER

INSTRUMENT

COMPUTER

TELESCOPE

ELECTRONICS

INSTRUMENT PACKAGE

ELECTRONICS

INCLUDING ACCUMULATING

MEMORY

Figure 3-2. Overview of Starlab Facility Showing RAU and HRM Interfaces.

3-12
would still be necessary to provide duplicate status into the ECIO to

support AFD operations.

3.3.2 Space Platform/Station

A potential Leasecraft Command and Data Handling (C&DH) subsystem overview

is shown in Figure 3-3. This C&DH subsystem is based on the Multi-mission

Modular Spacecraft (MMS) subsystem which has been configured to support

the Solar Maximum Mission (SMM) and Landsat, The Pre-Modulation Processor

(PMP) provides the necessary signal conditioning and processing. Up to two

separate data channels can be transmitted simultaneously, where data

channel selection is by command control with candidate channels derived

from the Central Unit (CU) (return, link telemetry), Tape Recorder (Tape

playback), Standard Interface for Computer (STINT) (computer memory

contents), plus possibly a number of externally supplied relatively high

data rate channels.

The forward link command and data signals are detected in the transponder

receiver/detecter and delivered to the NASA Standard Telemetry and Command

Components (STACC) CU as digital signals for distribution both within and

external to the C&DH module. The forward link signals provide realtime

commands, delayed commands (for storage in the Onboard Computer (OBC)

memories), and OBC programs (also for memory storage).

The STACC system (CU, Remote Interface Unit (RIU), Electronic Unit (EU),

Bus Coupler Unit (BCU), and STINT) utilizes the Multiplex Data Bus (MDB)

supervisory and supply lines for the distribution and control of telemetry

and command functions both within the C&DH subsystem and to all other

Leasecraft functions.

3-13
o

3

01

•H

l-i

0)

O

a

01

to

3

w

3

u

JJ

<4-l

O

0)

CO

ca

V

,-1

(0

•H

J_>

c

til

4-1

O

•

7

f*7

<u

u

3

00

•H

Cb

s

2

H—

oa

Co

oo

1

I

ni

o

PN.

SO

<:

0

X

UJ

-u

a.

— j 3

i

_j

UJ

00

a

z

c

<j

a

<

1

t/>

a

>u

c

c.

—

^

^—

—

I

1—

—

Z

o:

O

u

LU

UJ

<=

a±

o

(^

X

'

i

a

_i

u

3

' ' 4

«

, , *

C

»-*•

>-*

^•M

1

O

z

Q

O

E S

IS

3 —

. - * "2

u ~ri as o

• °° -*•

 z

: —

UJ —

- *sll

as o o

or K— O QS ?

uj ;? ^- •— u.

0 S < Z cs

O s as O LU

U S L*J O HS £ Z L«

 2

0

 S-

<' f uy^

2

§ 2

' 5

—

u_

rf

^0

So

5#«

Q.

LO

1 '

O

UJ

O£

a.

»

• >— »— : as — > o S

• °~

 x

-

— — —

= as o ,_

l|i

LU

SI !

>—

LO

1

,, 1

-U LU

Hae. < oo

O OS LU

on y O

J2 * S5

s °«

°

i

- <

 ^^

 ?

_ S1 Q

}*;

2

Of.

uu

Q. Of

< 0

*- 0

LU

X

0

1

J

G

= 0

|2

°l

3

|

cj

00

oo

2

^u

O

X

O

o

- z

^§

a 2

2_ S; , uo

25

X Z

o

3-14
The CU serves as the central distribution for both telemetry and command.

A BCU is interposed between the RIUs and MDB for fault protection. Telemetry channel capacity increase is available by addition of an EU, which

functions in conjunction with the associated RIU. The OBC provides auxiliary control of telemetry and command functions. Communication with the

various subsystems is accomplished via the CU and MDB. All signals to and

from the OBC are routed through the STINT. The OBC can provide control of

the downlink telemetry format (otherwise derived from the CU), issue stored

commandsj and request telemetry data for internal use. The Lsasecraft

downlink telemetry data rate characteristics and onboard tape recorder

storage capacity are TBD at present.

No details exist on the Space Station system at this stage.

3.4 SPACE SEGMENT OPERATIONS

3.4.1 Shuttle Sortie

Command of the Starlab may be performed from the ground or the AFD. In

each case the EC provides command handling functions. The Mass Memory Unit

(MMU) may be used to store command sequences and sets of commands for

execution under timeline control. The IPS is controlled by the Subsystems

Computer (SC).

Generation and initiation of the following command categories is provided

from the ground.

a. Commands to initiate EC Operating System (EGOS)/EC Applications

Software (EGAS) functions (e.g. Dedicated Experiment Processor

(DEP) load, timeline maintenance)

3-15
b. Commands to make data inputs to ECOS/ECAS (e.g. constants, timeline inputs)

c. Experiment RAU Discrete Outputs (on/off)

d. Experiment RAU Serial Outputs

e. IPS pointing commands through the SC.

Commands to Spacelab and for payload functions when utilizing Spacelab are

transmitted in blocks of 32 words, where each word is 16-bits. The maximum

rate for transmitting these commands through the MCC/Orbiter system is

approximately 1 block per second or 512 bps. In general, commands may be:

a. Single stage - Approximate 1 second execution rate per block with

command rate of 512 bps.

b. Two stage - Rate of approximately 1 block every 10 to 30 seconds

or 18-52 bps.

In^addition, a modification to send commands single stage, but with a check

on the block zero word count has been incorporated within the MCC. This

utilizes the fact that BCH encoding provides a confidence of approximately

1 in 10^ that commands with no error detected have been received correctly. This technique allows the use of single stage commanding with high

confidence. A maximum throughput of nearly 1 block per second or 512 bps

is possible. Current requirements indicate that a command rate of 512 bps

is needed for Starlab.

3-16
Note, that an MMU data set is 512 words and takes approximately 6-10

seconds to transmit from the ground. Also, a master timeline data set is

512 words and subordinate timeline data set 100 words.

Control of the IPS is currently planned under normal circumstances to be an

Orbiter crew function. Both digital input (i.e., input Right Ascension

(RA) and Declination (DEC)) and analog inputs (i.e., joystick) are provided

onboard. Ground capability through the MCC currently only has the digital

input capability. In addition, at the present time utilization of the

ground for IPS commanding is not recommended. Software to verify that

planned IPS pointing movements do not create a safety hazard (i.e., impact

the payload doors, other payloads) are run pre-mission. No software

capability exists at present to perform this verification in realtime.

During crew control of the IPS, the system is in constant view from the

AFD. If ground control is allowed the following two constraints are likely

with the current capability.

a) Crew members will have to be awake and on duty to monitor IPS

movement for safety compliance.

b) Only small movements (i.e., fine pointing) will be allowed and no

changes to the target observed are likely.

Starlab has a requirement to provide continuity of the ground systems

capability and operations concept between the Shuttle sortie and space

platform configurations whenever possible. The capability to operate the

IPS from the ground is therefore required, although utilization of crew

involvement to support this function is not precluded. The latter

constraint above is therefore not consistent with this requirement.

3-17
Further, inclusioa of analog capability at the ground would be a

requirement. Expansion of the ground capability is likely to require

inclusion of necessary safety compliance software within the MCC.

Starlab telemetry will include engineering data output through the RAU into

the ECIO data stream and transmitted via channel 2 and high rate science

data. The ECIO data stream has a data rate of 64 kbps and is available

both in realtime and from HDRR playback. Ground processing is required to

extract the Starlab engineering data subset from the ECIO stream and to

perform processing of the resultant data. The telemetry rate for the high

rate science data downlinked in realtime on channel 3 will be 16 Mbps.

When this data is stored onboard on the HDRR, playback will be at 32 Mbps.

The maximum Starlab science data output rate in the Shuttle sortie

configuration can therefore be 48 Mbps (16 + 32), when both realtime and

playback data are downlinked.

3.4.2 Space Platform/Station

Operation of the Leasecraft from the MSOCC facility is currently proposed

for the first two Leasecraft missions. This facility provides a range of

general-purpose hardware/software systems to support a multi-satellite

environment. The facilities are fully operational and undergo planned

enhancement/development in order to provide up-to-date support for approved

missions. Following the first two missions, consideration is being given

to the development of a MSOCC type facility at the Fairchild Space Company

facilities in Germantown, Maryland. If a facility of this type is

developed, it is highly likely that it would be utilized to support

Starlab, since the projected initial Starlab launch date in 1990 would use

a Leasecraft mission in the mature operational phase. In this eventuality,

3-18
consideration would have to be given to the distribution of functions and

the interfaces between the Gennantown MSOCC type facility, any GSFC

institutional facilities utilized, and the DAF.

No details exist for the Space station configuration.

3.5 GROUND SYSTEM CONSIDERATIONS

The following preliminary ground system considerations have been

identified. Table 3-4 provides a summary of these requirements.

a. In the Shuttle sortie mode the MCC has ultimate command of the Orbiter

flight and control of all resources and safety aspects including the

Spacelab elements. Control of the space segment to support required

experimentation must therefore be performed through and coordinated

with the MCC. In particular, the scheduling and utilization of all

crew support must be coordinated with the JSC Crew Activity Planning

System (CAPS). In addition, the JSC POCC can provide a range of standard capabilities and services to Starlab as an attached payload. If

the JSC POCC is not utilized similar capability needs to be provided by

a remote POCC. For the space platform, the situation is either

different or presently undefined. A Leasecraft type platform could be

supported from a POCC sucn as the GSFC Multi-Satellite Operations

Control Center (MSOCC). This capability supports the space segment for

a free-flyer of this type and in addition provides various capability

for supporting payload health and safety. For the Space Station, the

ground elements are presently undefined.

3-19
C

O

4Jccue0)3craocu cocuocoa. co0)

4-1§M•acuCOco•H4J(0

I-l cu •a•HCOCau

4-1

CO5s encohOI en

,«— ,

4-1XCUucu

4-1c

1-100 •H

Il CU JO3CcoiH

4-1

CJ CUCO X)3COo4J

I-l CU UdCU

1-1COtlcu J3CaL^

Cc4JCO1^301

Ul CcSdo•H

4-1

CO

(-.

cu

T3

•HCOCOCJ

E

liOUdUCO rH&4CUCJ COo. COcu •H

4-1

iJ0?cu iH

4-1U3

,dCO

oCJocn 4J »w CO >, -o A CUd *O *H CU UH 4J CU

il -O

0 d Q. 3 O. 3 1 CO •>. c 1 *J O

1-1 -H

^J r*ii 4J

Ud iH CO

CO O 4-1 •

Id Cfl CO 4J

0 UH C

CU CU CU

CO CU CJ CO

CO O, CO CU

CU >> 0. fci

rJ 4J en a.

• • CU £

4-1 00

4-1 •

4-1 CJ CO

O 0) 4-1

rH O. e

^3 rH CO (U

C co co 6

CO CU

a u-i i— i

O 4-1

CJ iH 0) JO

O Ud CO

0) M Cfl rH

4-1 4-1 CO CU

(0 d O a o -o co

•H y d Q.

4-1 CO CO

rH T3 3 e c

o oo

CO V C

CO CJ -H

CO 4J Id T3

J= J= 3 3 00 O rH

CJ -H CO CJ

CJ rH CU C

*ecuaoocu COCUuCOo. COcu

CT.

4-1

UHorH0Id

4-1doCJCO

Tj Id

Id o CU

CO Ud CJ

T3 0) CO

C C x: O.

co O u CO

4J -H

CO 4J >> CU

CJ rH Si

CO C Xi 4J

3 CO

CO Ud XI UH

•H O O CO Id

1-1 C O. 4-1

O 0 C Id -H T3 01 u u c a C CO CO 0) O Id rH CJ CU 4-1 CU 00 O CO "O • C hi CU C •H T3 CJ d O 4J e <y d -H C 3 co co u •H o co a co O M CU C 4-1 cu oo i-J 3 cn • 1•HT3o *o a c 4

J

CO C

CO t3 CU

Q* ^3 QJ ^ 3

M CU CU U CU

4-1 d CO 5>

0) -H 3 M

4-1 iH 4-1 4-1 >

rH O d

*UH rS CO iH

O XiH

rH 01 CJ CO

^H Vj «^ CJ C2

O -H -H 2: O

Id CO rH iH

jj y^ t^ • ^j d co o co co O >.-H CU Id 0 rH d V. C

U

4-1 cu o 3 a. d oi co 4-1 cu 3 M M CO CJ 3 O l-i 00 O O 01 Id 3 Q. T-l 1-1 Id * * *

iHou

4-1doCJaCU

4-1

CO>

,

cn00d•Hud•H,2

J3*

Jj

CUo

iH?S TJ rH d

iH CO cO4J CU d rH CO 4J

4-1 4J

to 3 3 cn CO c 1 CO f.

Ul CO r*Y Id U CJ iH CU Id CO O CO -H rH 0, •d0iHCOCO (^eCU

4-1

4J3x: cndoT3cu . CO >

,

CO 4J

•o o 0 -H o vu O O< *>14J iHrH^H^(0rHiHCO>CO ^eTd

iHcn•o

COcuCJ3oCOCU00d

iH)dCO C

O

^ t3

co coQ

U rH

0 >>

<i-t coo<

4-1

CU 0) a .£• 0) 4-1 IH 0 •H3 £ cy u CU -H W 3

»ty^

•

co co

CO UH

4-i 0) O

0 0o ^ >• co 0)

4-1 J2

•H ^ £ I-H d = •H iH d j3 rH CO CU & < (A o cn hi M CO Qd Id i-H Q 1 UH CO d ^t Ud O 4-1 O •H iH

cfl O O

4-1 iH C

CO Id -C

O. -H

(U iH O J2 CU CO 00 .M O< -H -H cn £ j • •

•

CO

cuM30CO

1 CU

IdcuCO "50

4-1

CO

•oCOo

iH>

,

COo

.

4Jo— ) 0a. XICO^4ed CO M0 x: o

.

4-> O.

•H 3 3 co S rH CO CU cu c 4-1 do <; co cn id < cu z o

.

4-1

CJ cu

•f)0Q. ocOrHIdCO

4-1

cn 4-i (d £ O 4J f>

.

•H O<

3 3CO aCO rH cu cu 4J d

<:§

CO CO

<: n Z cuo

.

d0

1-1

4-1

COucu >\ d 4J (U iH 00 rH>^ja 0) iH d CO •H C -

-rH O-

cu c.

a to

S 2 QJ

"OOJ 13

T-(>•0&aIdoUdCO rHo. cuy

cfl o

.

CO, • IdoUdcu ^3 crj 0) M T3•H 3 > cu O i-H Id CO o. •o cn d p 1 Q rH CJcu "O CO d

Cfl U01 Id O

. Id

01 01

4-1 O 4J

•H U"l -H

XI CM j3

Id • Id

O 0 O * * rHoid

4-1dou00 0

0

d u

•H iH

4J U C 00

•rH -H

O hi O. 41

-

4-1

cu u

"Cfl cB

Id Id

cfl co

cSS UH

CO01

•0 3 d d

c o*

0) tO

4J — <

•HJj O o 00 id d O IH Ud rH4J CU 4-> a cu •H M Jj oo 3 d CU iH rH -O CO 3rH 0) O oo d

Cfl iH

cu cn

> ftl < M*
>*^

•o

•a

3

r*4

y

B

o

y

09

4J

B41

a

u

3

er

«!

^J

e

01

a

00

41

CO

41

U

CO

0,

4J

a

o

u

<4-4

•^J

41

JS

U,

0

CO

C

O

CO

41

•O

•H

CO

C

ow

a

00

CO

•g

e

3

o

u

0

^1

^S

4)

.a

CO

H

*^*

X

41

41

,J3

U

e

f4

00

•H

U

41

^Q

a

B

e

o

^y

41

00

s

09

O

u

hi

41

4)

U

09

1)

A

I

a

41

M

C

o

u

ta

3

ao

'•fc*

e

CJ

e

0

u

CO

u

41

•o

•H

00

c

a

o

H

CO

41

y

a.

41

•rt

U

O

ta

41

Jj

3

£

en

en

CJ

u

"S

^

e

41

CO

CO

Q

U

^

^

^4

3

0]

Q.

3

O

O

• 41

CO 3

X 41 -O

r-1 U

e 3 >o

OB <s

v4 41

en a ^

ou hi

M CO 41

b **rf Q

O O

vw 41

oo ao

(US iW

a -( co

4J W

U M

3 4) O

u co «*

— 1 CO 90 — 1

B CO

11 -H -H

90-0 «

CO 3 S

1- — 1 41

41 O u

0 0

*^

O

U

B

O

y

ao

B

W

B

•H

O

a.

D

CO

u

«

3

CO

^

4>

s

u

•3

er

41

U

^CO

Q

2

u

11

o.

o

CO

41

y oo B ao

S B -H • 1 B

so O u « i* .• •*

»fl *p4 >% *H M f^ *rt» C

W ^ ^^ ^ 41 ^ M *H

§

l« dM 1 t . « . . W ^

41

» -^ •* a

u u a. e ^ 60 01 U o .C ^ -O .*

**4 O O* 41 U 3 00 *v4

U <J ^ CB j. ffl ^

3 cn 11 3 -o aj ^ £ •oa-ae-ooorju a

O ^ **^ v4 CO * 'i j * O

M 4J 8 B . B ^

B C O0""> a " rii "3

•^ 4t B ^ b % M B

a -H 1 e w "T o a) co

S) U b -2 S X S

C3 CU 41 41 ^ O ^* ^ ^ 4)

*»4 CD 00 <J ^ O (0 *^4 S

iW 41 <A C 3 *^ M 4)

£3°2'o'«§s l'3- H

cow u c -H u a, 3

CO 4JQD4>4jO^^ 8 7

eao.SwM'uNftiy u

0 0

09

y

•H

00

u

41

y

CO

U

00

"y

a it

4) 41 >

O oo a. ^ u it e x 3 u

u u CO iO CD 09 41

O U B S •-*

a o -o o on

11 O **^ B U **4 00

U W 4J 3 U

<o o oo ta x

3 41 41 CJ >O O 11

*^ 4J Q> £& *4 ^

°* " a) O 41 u

a a^-HinMu y

§

{Q

W

00 03 « « -« 4> 4)

co w co o <9 e

41 O jj *H

-O CO J-» £ £ O CO •

C 4J 3 w w ^ ^ O Q

O*Q O -H 4) Q

U - 4J 3 4J 0) >%-O

C5 CO ^rf ® T3 O ^H *J

C O ^" ^ C 9 ^ *H ^3

"cO^^^B^uS^ S

'ua'yaS^u^J'eo' s

CO CJ «H * B B b 4) CX O"

tn — i o* -^ o J o.flu y io o o o

^*~J

S.

-2T*

•^

fiTM

o

u

w

J3

TM

^H

w

CO

TM

CO

u

<d

"3N

•rt

^

CO

4J

e

3

o

~

u

<w

o

a.

fii

3

CO

^4

CO

B

O

u

(0

U

u

5-

•H

3-21
b. As already described ground control of Che IPS in the attached mode is

currently fairly limited. In the space platform configuration ground

control of the pointing system will be a requirement. For a Leasecraft

type system this control could be supported from an MSOCC type facility

directly. In the case of the Space Station the situation is not

defined at present. An upgrade to available capability in the attached

mode will therefore be required in order to provide continuity between

Starlab configurations.

c. Limited command uplink rate is available with the attached Shuttle

configuration (refer to Section 3.4.1). This is currently a concern to

Starlab. It is possible that much higher capability will be made

available with the space platform allowing support for more extensive

operations from the ground system. Insufficient details are available

at the present on potential Leasecraft and/or Space Station

capabilities.

d. Telemetry rates for the DI in the attached configuration are 16 Mbps

for realtime transmission of imagery and 32 Mbps for HDRR playback. In

addition, a lower output mode with a rate of less than 50 Kbps will be

available. The higher rates require the Single Access (SA) mode on the

Tracking and Data Relay Satellite System (TDRSS), whereas the lower

rate may be transmitted Multiple Access (MA). Use of the MA link

enables virtually continuous coverage (with the exception of the Zone

of Exclusion (ZOE), etc.) for monitoring purposes, but with substantially increased downlink times for normal image data.

In the attached mode, the required access to the SA link is likely to

be available, based on the priority of the Shuttle as a manned mission.

3-22
A requirement for approximately 4 minutes SA link availability per

orbit was determined for the space platform configuration based on a

mission profile analysis (reference 8). However, it was stated that

this value should be increased by a factor of 10 based on a number of

considerations (reference item 2.2 i)). Assuming utilization of the

HDRR this would correspond to a requirement for approximately 20

minutes SA link availability.

In general, scheduling of this SA link time say be made either using

generic or specific scheduling. Generic scheduling is likely to

provide increased link availability and reduced conflicts, especially

under conditions of heavy TDRSS usage. However, use of this mode can

require careful consideration in the development of planning and

scheduling concepts and/or systems. The DOS currently considers that

it would be exceedingly difficult (or impossible) to construct an

observational schedule that took advantage of generic scheduling unless

constant use is made of the HDRR or another suitable tape recorder.

This conclusion was reached since exposure timing must be determined by

astronomical/orbital requirements and cannot be subject to change at

short notice because of sudden changes in TDRSS availability for direct

data transmission. Further, even if generic scheduling could be used

via utilization of short-timescale flexibility (minutes) in the timing

of tape recorder playback, there would always be a need for specific

scheduling to support for instance ground-assisted target acquisition.

In the case of the attached Shuttle configuration the mission priority

is likely to provide sufficient link availability. The availability of

SA link time for the space platform configuration is somewhat more in

question, based on current program status and the possibility of sup3-23
port requirements for large numbers of payloads. For a Leasecraft type

platform, it is likely that the platform will have substantially lower

priority than for the Shuttle sortie case. The time available will

also possibly need to be shared amongst a number of users. The Space

Station is likely to have a far higher priority, but may carry substantially more payloads on the unmanned element than for Leasecraft.

e. For the Shuttle sortie configuration timeline generation will be

performed by a NASA team with Starlab project personnel support. A

corresponding operation is proposed for the space platform.

f. Coarse pointing will be performed by the Orbiter and IPS for the

Shuttle sortie missions. On the space platform the platform itself

will provide pointing capability.

g. Additional time is required for acquisition to provide precise

alignment of the spectrograph slit. A time of 5 minutes is currently

assumed for this procedure.

h. There is concern with regard to the operational characteristics of the

Orbiter Reaction Control System (RCS). There is a possibility that as

many as 450 RCS firings per orbit could be required. The resulting

disturbances are outside the present specifications of the IPS which

would require approximately 10 seconds to return to a quiescent state

(not to mention any additional time required by the Starlab FGS to

recover fine acquisition). This would require an overhead of approximately 75 minutes per orbit which is clearly intolerable. The RCS

firing rate may be reduced to approximately 50 per orbit by optimizing

the Orbiter attitude to minimize atmospheric torques. This introduces

3-24
a further constraint, which will conflict at times with Starlab pointing requirements. In any event at least 8.5 minutes per orbit would

still be unusable. This area obviously needs investigating since this

latter number could easily be exceeded based on inclusion of all constraints.

Utilization of a "free drift mode" whereby the Orbiter is allowed to

drift for approximately 10 minutes while the IPS tracks the guide star

is a possible solution. At the end of this interval, the RCS system

would return the Orbiter to the nominal attitude. This mode would

replace unpredictable thruster firings by single bursts at presumably

predictable times. This mode would permit Starlab pointing requirements to be met but would incur two penalties. First, observing time

would be lost during the Orbiter/IPS/FGS attitude recovery. Second,

long exposures (i.e. > 10 minutes) would not be possible. This would

make the timeline scheduling more complex, and result in an increase in

downlink data rates.

i. Operational support requirements differ for the two configurations.

Refer to Table 3-4.

3-25
4.0 OVERVIEW OF THE MISSION OPERATIONS CONCEPT

The Starlab mission, operations concept is required to provide coordination

of all mission operations functions including crew operations. In the

attached Shuttle sortie configuration, the crew are an integral part of the

operations having involvement in many realtime operations functions

including control of the IPS. In the space platform configuration, the

operations are completely supported from the ground.

4.1 MISSION PLANNING PHASE

For all configurations, mission analysis and planning functions are

required for the definition of appropriate requirements, capability and

resources necessary for successful operations. The definition of the

requirements for supporting data preprocessing and processing, and data

analysis functions must be defined in these analyses. As stated in Section

2.2 a) the majority of Starlab observations will be preprogrammed.

The mission planning phase provides performance of the following functions:

o Definition of orbit requirements (An inclination of 28.5° as a

standard STS orbit has been selected for the performance of mission

profile analyses, although a lower inclination is preferred)

o Selection of candidate targets

o Definition of Starlab instrument observation constraints

o Definition of target observation requirements

4-1
o Starlab - space segment compatibility assessment. For the attached

Shuttle sortie configuration this includes compatibility with the

Space Transportation System (STS) and the Spacelab including IPS.

o Identification of special hardware, software, and support services

requirements

o Identification of potential problems from a resource and/or operational standpoint

o Evaluation of satisfaction of overall program objectives.

An overview of the functions required for mission operations support is

shown in Figure 4-1. This figure refers specifically to the attached

Shuttle sortie configuration, but is generic enough to represent many

aspects of the space platform case (note: no crew are available in this

mode).

4.2 INTEGRATION AND TEST CONCEPT

Integration and test of the Starlab facility with the space segment will be

a function of the configuration based on the significant differences

between the ground flows and interfaces^for the STS/Spacelab and the space

platform. Full details of this activity are outside the scope of this

document. However, the elements effecting the mission operations concept

need to be considered.

The availability of EGSE will be required to support various phases of the

ground flow and/or operations. These include:

4-2
V

4 C

<D O

rH CO

& 5•o CO hi 4J O t

uui1_jddA^^CQSi

«•

cu3

rHCJ MCOeo

4-1Ua3Cu

0)3crc3ico•HCOCO 5§uCO

C/3 •aa3ouoJOCO rHCO co*

JJ^JoO

.

a.

3COeoiHCO •HrHCO W) eoiH4JCO300 •H

Ul a8

<u

4-1Oe<S

(-* 4j •H3eoiHCO iHrHCO ^^COeoCOCJ -e43g<3*

COcu -4•HrHiH^COa. jjhi Oa. a. ca

^00c•Hc

1-1COhi HS<uCO ca*oe3oo•oaCO3<uhi u*

COo4JCO 1— 1 3a—4 CO

00

iH

Ul

Ul CO4J co8cuuCOXcoT>§ohi u*

COCUu•H^

*^44JCJ •*COco•HCOhi cua

.

O44oao•HCOe•wocS*

XCO rHa. CO —a4 <#00c•HCOCOcuuo

PL, CO4JQ) £3oorH1CJ iH

<§.

*

rHOhi

4-1C3vBCO0Ou•^COOfH

00 CO

e o-

•Hhi -

0

O CO

4J i— 1

T4 hi

e ca

X co*

*JOo

.

cu3CO00ciHrH3cuoCOco

1-1COCO :g*

CO01COCOOC

.

a.

3

— cyj I<• en u c

GtS -H

CJ

0)C

.

O05CO

00

*H24^flu00«409aJQ

,.hi OCxCO4Jccushi •H3er (2

Ul Oeo

4-1

•He

Ul CU

scu4JCO co•ocooACO rHCOuCO

CO3o

.

rHcuCDCO caCO 4JQ

«4JCOiH4JCOhi 300 IMccS•

^faCOCO CO

Ul Oe? iHhi O•HCO Hao•H4JCJ CU r- 1 cu CO*

•oa3o£4 orHCOUi^hi ^CJ CU

i-4H•aCU3cr •H£

COcu e CJ 0 •H iH > CO hi CO CU -H co S*

•oCUN

«p4 rH•HU3CUhi cu i•4JcCUso. •H3W* 4j hi Oa. a. CO

.c

uCJ CO UHhi cu4JeMhi cuCO•

CU3creao

iHCOCO jj

00C 3

il CU

-S 5 CO14H •

rHcueoCOhi cu 0MacucoXco•os3Ohi O•

cue^ahi CU uQO4J90eiHa•HrHcuaT4HaoiHCOCO

**H*

CO

rH3oCJ -4UJ•HC(U•HCJ CO

Ul o4JeCU>cu ^4!*

*4COeCO rH04

^•4COO•H

4-1

CO>hi <uCO c§4Jecu iHCJ iHUd04w*

COo•Hhi COcuCJ CO

COcuCJu3oCOcu PB^cCUcu cocuoCOa. CO•

^•HrH

•r4jQ•H4JCOa

.

aoCJ

rH01coen<ugcu

4.)

CO

en

*ocohi o

fcJJJ 30)uCJ*

encCO rH04

4-^1

•rt>

CO iH

•O 4J CO CJ O •< rH^ 3 hi cu O hi 3 0*

4-3
a) Instrument development and calibration in Australia and facility

development and calibration at the developer site in Canada. Utilization of EGSE for this function is a developer decision, but availability of the same EGSE or EGSE of similar type to that needed to

support operations will facilitate both crew and/or ground systems

operations personnel training. In the STS arena, the conduct of

operations personnel training at the development site has been shown

to be cost effective based on reduced requirements for simulations

capability.

b) Payload integration and test ground flow support. For the STS, ground

flow processing with the Spacelab and Orbiter will be conducted at the

Kennedy Space Center (KSC). Again, utilization of available time

during this flow for operations personnel training has been shown to

be advantageous, and utilization of the same or same type of EGSE as

utilized for operations support will facilitate this activity.

c) Operations support at the POCC. The JSC POCC provides a range of

standard capabilities and services to an attached payload. These

include various standard data processing services for payload

engineering and/or science data, where these services include functions such as demultiplexing, data stream or data subset extraction,

performance of arithmetic and simple processing functions, and data

monitoring and display. In the case of payload engineering and

science data, the JSC POCC processing capability is limited to data

streams of 2 Mbps or less. For streams of higher rate, the data may

be made available to EGSE. The availability of EGSE to perform

required processing functions is therefore required for Starlab based

4-4
on identified data rates. Coordination of the functions performed by

this EGSE by the three participating countries is required.

Utilization of a remote POCC capability may be considered for Starlab.

In this event, EGSE is still likely to be a requirement. For the

space platform case, the same applies. The MSOCC facility or a

facility of similar type which could be utilized to support a Leasecraft type platform can provide similar data processing services to

the JSC POCC for data streams with maximum rates of approximately 256

kbps. The MSOCC is continually being upgraded to meet future mission

^

requirements and current plans are to install substantially increased

processing capability in the form of 3 Mips machines. However, this

capability would still be insufficient to meet Starlab requirements

and therefore special purpose EGSE would still be needed. For the

Space Station, the situation is undefined.

4.3 NORMAL OPERATIONS CONCEPT

4.3.1 Shuttle Sortie

The requirements for supporting Starlab science operations for the Shuttle

sortie configuration are shown diagrammatically in Figure 4-2. The

functions to be performed by the Starlab Ground System are presently

planned for support out of the JSC POCC, where the EGSE will be resident

within one of the seven user rooms. The possibility of developing

alternate remote POCC capability is currently under review. If a remote

POCC capability is developed, this facility would provide similar

capability and be interfaced with the MCC in accordance with the requirements detailed in reference 7. The mission planning function supports both

4-5
a:

UJ

a.

O

LU

O

<J

V)

CO

LU

IT

c

UJ

0*

-J

Q£

CO

CN

LU

cr

crt

Z

c

^<-

e

UJ

a.

o

a

<

C

2

a

<

K

<

VJ

O

Z

VI V)

ZVt _l

OUJ O

— <j ac

N- O M

52 §

Ul U a.ac/1

oujzo

«525

Q U h* ^

zS^Z

Z B Z ^

UJ UJ 3 O

MQUh^

• • •

o <z o

:>- i- -lui — _iui a,— N-

^•«o o u < ataas z zin > — o «

z — u. ui

_ <no «

o. u. _i«

OU.O cnui — •-

Q ^££Z

§

Z Z ^ HI ^ ^ UJ M ^m f o^

ZOui^az zaeuaii^via.

— O*~£ UI4JUJ<<^ U

^•••^UJZ ^>

 >l>*ZQ.^<aaZ

• ••••OEO^ujuujvjtf uj

zuz —— <— —o-^o, X I>-

^UJ^3V> ^Z U.V>C/1£UJUJV1

U.^U.OV1UJUU. fc_QO£K>

4-6
operations from the crew and the Starlab Ground System. Close coordination

of these operations activities must be provided. Voice, downlink video,

and Text and Graphics System (TAGS) uplink capabilities are available to

support this coordination, in addition to the command and telemetry functions. The TAGS system provides an uplink facsimile service.

Data product generation for the Shuttle sortie case will be provided by the

SLDPF as a standard service for Spacelab payloads. Any required coupling

between this data processing function and the Starlab Ground System must be

identified.

Support from other observatories and facilities for providing target of

opportunity reporting, supporting data and information, and correlative

observations is shown. The need for and form of this support requires

definition.

Figure 4-3 provides a mission operations overview for the attached Shuttle

sortie configuration. The MCC has responsibility for the command of the

flight and all flight safety aspects. The JSC POCC is interfaced with the

MCC and provides required functional capability for the Starlab Ground

System. The MCC provides verification of safety compliance for all JSC

POCC payload commands. In addition, the MCC provides STS and payload

planning information, STS ancillary and orbit information, payload command

verification and Orbiter Air/Ground voice. Channel 2 and 3 data are

received directly both at JSC and GSFC. At JSC the Channel 2 and 3 data

containing the ECIO and high rate science data, and Spacelab voice are

demultiplexed, and selectively distributed and processed by the JSC POCC.

4-7
FIGURE 4-3

Overview of Mission Operations

(ATTACHED SHUTTLE SORTIE CONFIGURATION)

• SENSOR DATA COLLECTION

• OEDIC.AIEU PROCESSING

FUNCTIONS

t POINTING CONTROL

• CSDH SUPPORT

• SELECTED PROCESSING

FUNCTIONS

• CREM I PAYLOAO SPECIALIST

ACTIVITIES

* ClDH SUPPORT

t PROVIDE ANCILLARY DATA

ORB I TEH

t COMMAND OF FLIGHT

AND FLIGHT SAFETY

• ORBITER/PAYLOAD

RESOURCES M6MT.

t COMMAND MGMT.

• ORBITER/PAYLOAO

CONTINGENCY

ANALYSIS

t ANCILLARY DATA

PROCESSING

JSC MCC

DATA CAPTURE t RECORDING

DEMULTIPLEXING t

SYNCHRONIZATION

DOM

DATA ACCOUNTING

I/O CHANNEL DECOMMUTATION

SL ANCILLARY COMPUTATIONS

DATA PRODUCT GENERATION

PRODUCT DELIVERY

* DATA REDUCTION

* DATA ANALYSIS

t SCIENTIFIC

INTERPRETATION

* PUBLICATIONS

GSFC SLOW INVCSTISATO* INSTITUTIONS

• INVESTIGATOR OPERATIONS ACTIVITIES

( OPERATIONS COORDINATION

• 8UICK-UJOK DATA PROCESSING

• DATA nOMITOHIM * DISPLAY

t PAYLOAO COMMAND J CONTROL

• ESSE INTERFACE ! UTILIZATION

• MISSION PLANNING SYSTEM INTERFACE

t UTILIZATION

STARLAS GROUND SYSTEM

4-8
The GSFC .SLDPF provides data preprocessing functions for Channel 2 and 3

data as a standard service for Spacelab payloads. During mission support

the SLDPF provides information on Channel 2 and 3 data quality to the JSC

POCC. Post mission data products are distributed to the investigator

institutions for data reduction and analysis and publication preparation.

For Starlab, additional and higher capability data processing functions

will be required however in order to provide calibrated data with appropriate signature removal. The investigators may be located within the

U.S., Australia and/or Canada and conceivably from other nations, when

participating as guest observers on the Starlab program. Distribution of

data products is currently normally via Computer Compatible Tape (CCT).

However, utilization of a state-of-the-art media such as optical disk

should be planned for Starlab.

In the event that a remote facility is utilized to provide the Starlab

Ground System capability instead of the JSC POCC, the facility would be

interfaced directly to the MCC. In the case of a facility at GSFC, it is

likely that high rate science and ECIO data would be extracted by the SLDPF

and provided to the ground system.

4.3.2 Space Platform/Station

Current indications are that Starlab will be carried on a Leasecraft type

platform which will be controlled from a MSOCC type facility located at

Germantown, Maryland. The capabilities of this facility, if built, and the

utilization and interface of institutional capability and a DAF at the GSFC

are not defined at present. The development of a normal operations concept

is therefore premature at the present time.

4-9
5.0 OVERVIEW OF THE GROUND SYSTEM

5.1 GROUND SYSTEM OBJECTIVES

The objectives of the Starlab Ground System are:

a) To provide mission planning, mission operations and data processing

support services to the Starlab community, where this community will

include investigators from the participating countries: namely;

Australia, Canada and the United States, and potentially guest

observers selected from the science community at large. For the

support of the initial up to two attached Shuttle sortie missions, the

Starlab Ground System will host investigators from all three

countries. For subsequent long duration missions on the space platform, Australia and Canada may provide remote facilities interfaced

with the Starlab Ground System to provide selected support services

for utilization by their respective communities and other guest

observers, as required.

b) To provide management of observing requests as input to the planning

and scheduling function.

c) To provide planning and scheduling capability necessary for the

generation of detailed timelines and command schedules for Starlab

operations. Based on identified science requirements approximately

fifty (50) percent of observations will be preprogrammed in the

attached Shuttle sortie mode and eighty-five (85) percent preplanned

in the space platform configuration. The higher requirement for the

Shuttle mode is based on the facility commissioning needs. For real5-1
time observations, planning will still be required in order to allocate observing periods and resources, identify and/or schedule targets

on regions of particular efficiency or suitability, and to develop

plans for interactive commanding.

d) To provide management of all realtime and preprogrammed command

processing functions, and to provide appropriate command performance

and history processing capability.

e) To provide necessary data processing support to maintain payload

health and safety and for operations support. This can include data

receipt and recording, data demultiplexing and/or synchronization,

data decommutation and preprocessing and arithmetic and simple

processing functions. It is anticipated that EGSE interfaced with the

Starlab Ground System will support Starlab engineering and quick-look

analysis functions. EGSE is required for the processing of streams of

data rate greater than 2 Mbps.

f) To provide appropriate data product generation for dissemination to

host investigators and/or for delivery or transmission to remote

investigators and facilities.

g) To provide appropriate on-line storage of engineering and science

data, overview data and/or command history information as required to

support operations activities.

h) To provide for the transfer of appropriate data to an archive such as

the National Space Science Data Center (NSSDC) and/or alternatively to

5-2
provide suitable archive capability as an integral function of the

Starlab Ground System.

i) To provide necessary STS or space platform and other ancillary data

and information in a form suitable for mission operations support.

j) To provide all required operations, EGSE, user, and support areas and

rooms necessary for the conduct of operations. These facilities will

be equipped with consoles, terminals, monitors and displays as

required. EGSE will be supplied by the investigators.

5.2 SYSTEM OVERVIEW

The Starlab Ground System needs to provide an overall capability for the

support of mission planning, mission operations and data processing support

services. In addition, a DAF will provide off-line data analysis

capability for the support of U.S. investigators and possibly guest

observers. In developing a system concept to support these activities

there are three major considerations.

a) The ground system must be capable of supporting or be developed to

allow for efficient modification or phaseover to support both the

initial attached payload and the space platform configurations.

b) Utilization of existing facilities such as the JSC POCC and the SLDPF

should be considered for providing cost effective support, and • be

incorporated into the concept in a manner consistent with item a)

above.

5-3
c) The ground system needs to be able to support remote facilities in

Australia and Canada if and when these facilities are developed to

support missions carried on the space platform.

An overview of the current system concept for supporting the initial

attached payload missions is shown in Figure 5-1. In this concept the JSC

POCC augmented by EGSE provides required payload operations support

activities. Figure 5-2 provides an overview of the JSC POCC. This

facility will provide Starlab support functions including:

a) A user support room for accommodation of EGSE equipped with three

intelligent terminals and overhead TV for display of relevant MCC and

POCC information.

b) Additional user accommodations including access to a POCC planning

room, conference room and office space.

c) Availability of standard arithmetic and simple processing functions on

the POCC applications processor, if required. However, it should be

noted that the maximum input data rate for utilization of this service

is 2 Mbps, and further the maximum subset of this data which can be

accepted for processing is 2000 16-bit parameters per sec. In

addition, this is the maximum processing capability which must be

shared with all other attached payloads utilizing this capability.

The incorporation of EGSE to support Starlab is therefore considered

essential.

5-4
L

U

s: a:

LU O h- W 00>• LU 00 -I <n i- O ws a:o aLU 03 Z <c u I— < (/) ^ at Q£

5-5
S"(OVERVI

E SERVICE

S

1JS > 1

H

CO

1

o

8 -7 eu §

01

W— «1

CS

in

01

oo

>• •

^••^i^^

§

• ••^

C

M

.

r*«

3

u ,

11

a

a

Ml

«

X

w

u« w

= - 3

= S 2S 3

i r as r 5 « s£ 5

2S

 11 5

. JL. '

t

!, > .

< >

*• 3 **

 — ^— ~r

«§j «* Ii

 ^ J« 25 !SSS as- ass «

<M C* IM »

• i i s i i ~ I

u < 3 §

2 I 2 i

•• Wl u*

V* * 22

ii

 a |i§

1

 i!

A I

i - j i y

<0-

-«S *" «I

?§P » 3^ a*«u*

'

.s

32

*« . .j

i

IM

UMAHS/lfll

> 10 »ln

>«•

Ii

i

i

i 3 >

v! ,1- '

J ZZ3 ,

w^~*

1

i

'

i '

; i

t-., _ii- ,

* i i ii, j

S- : ! ia* !

*l VI

2-5- 5 3 u jI'l §

r T *•

uinnia

5-6
d) Data monitoring display functions on the intelligent terminals and

overhead monitors. Displays include the output of the functions

described in item c) above.

e) Payload command and control via intelligent terminal standard

functions or by external system interface to the intelligent terminals

on a RS232 interface if required.

f) Accommodation of EGSE within the user room with access provided to the

Starlab high rate science data (i.e., the experiment channel input to

the HRM), Starlab EC10 subset, video downlink and HRM time reference.

In addition, these data may be relayed to remote locations, if

required, via user provided data lines.

g) Acceptance of EGSE defined command data via the intelligent terminal

interface described above, as required.

Two areas need further consideration in the definition of this concept.

a) The system used to provide mission planning and scheduling functions

and the interface of this system into the JSC POCC.

b) The extent of the functions provided by the DAF and the interface for

inputting required data into this system. Essentially three sources

are available for the input of data.

o Data delivery from the SLDPF. The current SLDPF commitment is to

provide these data 60 days following data acquisition. The receipt

of level 0 data at the DAF within 24 hours is required for Starlab.

5-7
o Data transfer from the EGSE to the DAF. This requires the

capability to record data on a suitable media on the EGSE.

o Direct data relay from the JSC POCC to the DAF. This requires

utilization of Domsat, since the data rate is 16, 32 or 48 Mbps

depending on mode.

For the space platform configuration, the JSC POCC would be replaced by

either a MSOCC type capability for the Leasecraft or a Space Station

support facility. In either case, EGSE is likely to be required and it is

therefore important to provide for similar interfaces for this equipment as

provided by the JSC POCC. Similarly, alternate capability to the SLDPF

would be utilized. Figure 5-3 provides an overview of a system concept for

supporting a Leasecraft type platform.

5.3 POTENTIAL REMOTE FACILITY FUNCTIONS

There are several functions which can be supported by remote facilities in

Australia and/or Canada, if developed. -Consideration needs to be given to

the functional requirements for these facilities in order to identify

requirements and interfaces for the Starlab Ground System. The following

are potential functions for these facilities:

a) Management of observing requests submitted by their respective

national users and processing of these requests to conform with

planning and scheduling input requirements for the Starlab Ground

System. In addition, an interface with planning and scheduling

activities especially long term planning could be maintained, if

required. This subject is considered in more detail in sub-section

5-8
U

J

LU Z > O ° H2 < ni ry h- =3

C/J O 00 U. Q O Z O O I- Qd 'i

CT3 <01

CO O < LU o: < < LU h- _J oo ^^ i inLUQL=5

5-9
6.1i however, it should be noted that the procedures for the selection

and prioritization of observing requests are outside the scope of this

document. It is only important that the Starlab Ground System

capability is configured to support the policies and procedures

adopted by the Starlab participating agencies.

b) Operations support activities including evaluation of quick-look

analysis data and off-line analysis including trend analysis. Several

options exist for the support of these functions including transmission of selected engineering and science data for local processing,

transmission of data subsets extracted by the Starlab Ground System

for final local processing or the transmission of parameters suitable

for direct display using similar display capability as provided at the

Starlab Ground System itself.

c) Data reduction and analysis of engineering and science data

transmitted from the Starlab Ground System for the support of

scientific analysis by national and/or guest observers. Again several

options exist for the data types to be transmitted from the Starlab

Ground System. These options are considered in more detail in subsection 6.7.

d) Archival of appropriate data types to support local users. The

techniques to be utilized for archival of Starlab and appropriate

ancillary and correlative data need resolution. Subsection 6.7.3 contains more detail on this subject.

5-10
6.0 SYSTEM FUNCTIONAL GUIDELINES

Guidelines for the Starlab Ground System have been subdivided into eight

subsections. These are Observing Proposal Management, Planning and

Scheduling, Guide Star Selection System, Space Segment Control Operations,

Science Control Operations, Support Requirements, Ground System Data

Management and Science Data Analysis. The ground system data management

includes post-flight data preprocessing, processing and archival. It

should be noted that there will be a strong interdependence between several

of these functions requiring good communications between the responsible

individuals. For example, astronomers performing science data analysis

will be continuously evaluating and updating calibration and batch processing software for support of the data processing function. It is therefore

advisable to have at least the science data analysis, data processing and

planning and scheduling functions located in close proximity.

For the purposes of determining ground system requirements in this section

we consider two missions as characterized in Table 6-1. References 13 and

8 provide details on the typical characteristics for each of these missions

respectively. The Starlab Ground System requires sufficient archival capacity to store data collected over a two year period. This requirement

would enable the archival of data from four flights of type II.

6.1 OBSERVING PROPOSAL MANAGEMENT

Observing time on the Starlab will be allocated between the three

participating countries responsible for the project, and could include time

allocated for guest observers from the science community at large. It is

likely that observing time will be allocated based on a review of observing

6-1
Table 6-1. Sample Starlab Missions

Mission

II

Mode

Shuttle sortie

Space platform

(Leasecraft)

Duration

10 days

180 days

# of Images

- 500

- 9000

6-2
proposals submitted in a manner agreed upon by the three participating

countries. The procedures adopted for the review of these proposals is

outside the scope of this document. From the standpoint of this document

it is assumed that the observing proposals go through some form of review

process during which a priority or category is assigned which qualifies the

acceptance of the proposal in the determination of the overall observing

plan. This is assumed regardless of whether one or more bodies are responsible for the review process, since it is assumed that the prioritization

or category assigned defines the coordinated outcome of this review.

The number of observing proposals is likely to increase substantially

between the initial attached Shuttle sortie missions of short duration and

the long duration flights on the space platform. It is therefore necessary

that the proposal management function be capable of expansion or augmentation to handle the long term requirements. The number of observing proposals this system needs to handle requires resolution and 'until detailed

requirements are available the form of this system cannot be specifically

defined. The information required includes:

a) Average number of proposals per day or other specified time period for

both the attached payload and space platform configurations.

Any required contingency in these values is also required.

b) The time span covered by the proposals for each configuration, where

this time is compatible with the planning and scheduling function.

c) Access requirements to the proposal Information to meet user and

planning and scheduling requirements. This will include processing

requirements with corresponding timeframes.

6-3
d) The concent of each proposal and if necessary the sub-division of each

proposal into individual observational requirements for specific targets.

Table 6-2 lists potential requirements for the content of each proposal.

This list needs to be reviewed for adequacy. It should be noted that

certain information is likely to be required 'multiple times for many

proposals, i.e., many proposals will include several or numerous targets

with accompanying requirements. An assessment of the requirements in this

area is needed.

The type of observing proposal information described will be needed to be

stored in an observing proposal file. The technique to be used to store

this information, whether manual or automated, will be a function of the

volume of proposals requiring storage and retrieval. The following type of

interfaces to the observing proposal management system will be required:

a) Input of observing proposals. Definition of standardized input

format(s) will be required to facilitate this activity. This can take

the form of a questionnaire(s) and/or a user friendly computer

interface.

b) Observing proposal prioritization or category.

c) Observing proposal status output from the system.

d) Request to the user for clarification and/or additional information.

e) Input of request clarification and/or additional information.

6-4
Table 6-2. Potential Data Contained Within Each Proposal

Ho. Item

1) Proposal number/Identification (ID)

2) Receipt date

3) Proposal title

4) Proposer(s) ID/address/phone/affiliation

5) Instrument(s) required

6) Target(s) ID, description, position

7) Observation time(s) requested, granted and planned

8) Special orbital conditions/requirements

9) Special data or sequence requirements

10) Detailed observing sequence requirements

11) Realtime interaction requirements

12) Special calibrations

13) Proposal status

14) Number of observations/sets

15) Target attributes (spectral type, magnitude, luminosity

class, etc)

16) Acquisition mode(s)/pointing mode(s)

17) Instrument mode(s) (Filters, spectrograph wavebands, slit

parameters [length], serendipity configuration)

18) DI image field(s)

19) Position Angle (PA)

20) Guide star information, coordinates, magnitudes, etc.

21) Realtime requirements, uplink, downlink (48 Mbps, 16 Mbps,

or low r.ate (MA link))

6-5
Table 6-2. Potential Data Contained Within Each Proposal

(concluded)

Ho. Item

22) Observing time requirements, total time, number of observations, time criticality (absolute, sequential, order,

uninterrupted duration)

23) Time resolution

24) Branching Requirements (overall requirements should not increase

Starlab Ground System operational load by more than 10 percent)

25) Proposal priority or category

26) Date/time scheduled

27) Background requirements, zodiacal light, South Atlantic

Anomaly (SAA)

28) Constraints and requirements, shadow, bright object avoidance

(Sun, moon, planets, etc.)

29) Data rate & volume requirements

30) Comments

6-6
f) System summary outputs showing number of observing proposals contained

within the system, proposal status, and number and type of processing

performed within the last accounting or processing period.

Again, specification of requirements in this area is required.

6.2 PLANNING AND SCHEDULING

A planning and scheduling function is required to support:

a) Long term planning during which the overall mission plan can be

analyzed to determine potential launch windows and orbit

characteristics, suitable candidate targets, and satisfaction of

science and program objectives based on candidate timelines.

b) Short term planning during which detailed timelines are generated in

order to:

o Show that the scientific objectives for selected observations may

be achieved, or in cases where they are not achieved, the extent to

which they are achieved.

o Obtain a high utilization of available time on orbit to increase

the scientific return, whenever possible.

o Demonstrate that the proposed observations may be conducted within

the available SIS, Spacelab and supporting facilities resources, or

similar resources for the space platform case as appropriate.

6-7
o Identify potential problems and conflicts from a resource and

operational standpoint.

c) Generation of command sequences, loads and allocation of realtime

operations sequences based on the prepared detailed timeline

requirements.

d) Changes to planned activities and timelines needed to respond to

targets of opportunity, contingency operations, etc.

The planning and scheduling system required for the performance of these

functions is likely to need or should have several attributes including:

a) A number of user aids may be required to facilitate the selection of

candidate targets and operational sequences in order to obtain

efficient timeline sequences without the need for excessive iteration.

Table 6-3 provides a preliminary list.

b) Interactive and/or automated modes for the generation of timelines may

be required. Full utilization of various functions such as user

prompting and menu generation will facilitate the timelining process.

c) The schedule- for the performance of the timelining function should be

matched to the schedule required by the Network Control Center (NCC)

for utilization of the TDRSS. This will aid efficient interfacing

with this system.

d) Careful consideration needs to be given in the selection of scheduling

technique for the TDRSS (Reference section 3.5.d)).

6-8
Table 6-3. Preliminary List of User Aids

a) Target Availability charts based on solar avoidance zone, power

constraint zones, etc.

b) Skymaps showing:

— boundary of the forbidden region around the sun

— sun's position

— moon's position

— position of the anti-sun

— continuous viewing zones

— position of ram avoidance

c) Solar System ephemerides listing the position of the planets over

a given timeframe.

6-9
Table 6-4 lists several factors which are likely to require consideration in

the analysis and determination of suitable timelines, where the factors

listed in Table 6-5 are relevant to target availability determination.

Table 6-6 presents typical constraints for a subset of these factors for the

DI, spectrograph and the FGS. In addition, other factors including environmental conditions such as incidence of thruster firings and waste dumps

could be significant. It should be noted that the factors listed are

specific to the attached Shuttle sortie configuration. However, many of the

factors are directly applicable to the space platform case. A review of

these various factors is required.

The implementation of the planning and scheduling function is likely to

utilize existing NASA capability, including possibly:

a) The Mission Planning Computer System (MIPS).

b) GSFC Institutional capability.

c) ST Science Planning and Scheduling System (SPSS).

Final implementation approaches will be based on identified requirements.

6.3 GUIDE STAR SELECTION SYSTEM

Reference 16 specifies a requirement that Starlab must be capable of

acquiring, and tracking, guide stars in at least 95 percent of randomly

selected fields at the galactic poles. The Guide Star Selection System

(GSSS) must have suitable capability to support this requirement. The

implications of this requirement on the GSSS are TBD.

6-10
Table 6-4. Tiaeline Factors Requiring Consideration

No. Factor

1) Orbit Parameters

2) Orbiter attitude profile

3) Launch window

4) Available support systems

5) Resource utilization including

a) Target availability

b-> Guide Star Availability

c) Power

d) Energy

e) TDRSS availability

f) Timesharing of support system including

i) HDRR

ii) Orbiter payload recorder

iii) Video

iv) Analog

Iv) Experiment Computer (EC)

g) Orbiter Reaction Control System (RCS)

h) Crew

i) Uplink capability

j) Thermal

6) Instrument operational constraints and characteristics

6-11
Table 6-5. Factors Affecting Target Availability

No» Factor

1) Earth occultation

2) SAA passages

3) Night/day orbital status

4) Minimum angular approach to sun, moon, planets

5) Minimum angular approach to bright Earth limb

6) Minimum angular approach to dark Earth limb

7) Minimum angular approach to bright Orbiter surface

8) Minimum angular approach to dark Orbiter surface

9) Bright object or star avoidance

10) Zodiacal light background

11) Ram effect

12) Aberration effect on plate-scale

6-12
Table 6-6. Typical Constraints

[Approximate Values for Guidance Only]

Constraint System

DI Spectrograph FGS

Sun 50° 50° TBD

Moon 20° 20° TBD

Bright Earth limb* 15° 15° TBD

Dark Earth limb* 5° 5° TBD

Bright Orbiter Surface TBD TBD TBD

Dark Orbiter Surface TBD TBD TBD

Ram Effect 30° 30° N/A

* Default Values, actual values condition dependent (see text)

6-13
6.4 SPACE SEGMENT CONTROL OPERATIONS

With the attached Shuttle sortie configuration the command of the Orbiter

and Spacelab are directly under the control of the MCC. The Starlab Ground

System therefore has no direct control over these systems. Utilization of

these systems must be requested through established channels and

coordinated with planned payload operations. Channels for requesting

Orbiter and/or Spacelab system support include:

a) Payload Integration plan (PIP) and associated annexes.

b) Crew activity Plan (CAP).

c) Interface with appropriate MCC personnel either directly or via voice

link.

d) Air to ground communications with onboard crew members, when

authorized by the MCC and using uplink voice capability configured by

MCC personnel.

The control of the space segment for the space platform is obviously

dependent on whether a Leasecraft type or Space Station system is utilized.

Leasecraft is likely to be operated with a MSOCC type facility. The system

to be utilized for the Space Station is currently undefined.

6.5 SCIENCE CONTROL OPERATIONS

Various data receipt and recording, data demultiplexing and/or synchronization, data decommutation and preprocessing and arithmetic and simple

6-14
processing functions are required to support the maintenance of payload

health and safety. Table 6-7 lists potential standard functions required

for engineering data analysis. These functions should be reviewed for

completeness. In addition, various quicklook processing functions of the

science data will be required for operations support. These functions can

include the following:

a) Selection of a segment of the accumulating memory for transmission to

the ground and display. This capability would be required to be

performed without interrupting the recording of an exposure in progress.

b) Image processing of the complete field at full spatial resolution to

enable rapid evaluation of the data.

Again, it is necessary to identify required quicklook processing functions

together with requisite frequency of usage, data rate and volume input

requirements, timeliness of processing, processing algorithms and/or

requirements, on-line storage requirements, output products or information,

and anticipated usage in operations support. Note, that it is anticipated

that EGSE will support many, if not all, identified functions. Table 6-8

identifies anticipated EGSE functions both to support I&T and operations.

Command capability to respond to observed features or events contained

within the engineering and/or science data will be required. The following

type of commands have been identified:

o Discrete (on/off)

o Serial

o Pointing system control commands (fine pointing control)

6-15
Table 6-7: Engineering Data Analysis Functions

No. Function

1) Conversion to engineering units

2) Conversion of analog data based on simple arithmetic

expressions and calibration, data

3) Limit checking using possibly red and yellow limits with

maintenance of a log of all violations.

4) Monitoring of status indicator values, and maintenance of

a log of mode changes and of deviations from the "normal"

value.

5) Tabulation of selected parameters for selected time periods.

6) Graphical display of parameter values as a function of some

other engineering parameter.

7) Histograms of values of selected parameters for selected

time intervals.

8) Basic statistical analyses on values of selected parameters,

such as means, variances, ranges, and correlation

coefficients.

6-16
Table 6-8. Typical EGSE Functions

I&T

o Facility and Instrument validation and calibration

o Electrical interface verification

o Flight software validation (SLC/TC/IC)

o Instruraent/RAU interfaces

o DEP load buffer and transfer

o Timeline verification via sample load execute

o Test procedure buffer

o Health and Safety analysis

o Safing groups availability

o Self test diagnostics

Operations

o Facility and instrument commissioning

o Flight software upgrade/maintenance

o DEF load buffer and transfer

a Starlab Ground System terminal/applications interface for

realtime command functions

o Test procedure buffer

o Health and Safety Analysis

o Safing Groups Availability

o Self Test Diagnostics

o Receipt and synchronization of engineering and high rate

science streams

o Quicklook analysis functions

6-17
o DEP loads

o Timeline updates.

In addition, air-to-ground full duplex voice will be required for

coordination with the crew and availability of TAGS capability would be

desirable for the Shuttle sortie configuration.

6.6 SUPPORT REQUIREMENTS

Various attitude determination and control system capabilities are needed

to support the Starlab Ground System. For the attached payload mode, JSC

provides these services to the JSC POCC and post-flight, as required. For

the space platform these capabilities could be provided at the GSFC via

institutional support facilities. The facilities include:

a) The Flight Dynamics Facility (FDF) which provides attitude

determination and control system, and mission analysis and orbit

maneuver system support.

b) The Orbit Computing Facility (OCF) which provides metric data

collection, and trajectory and orbit computation capability.

Support capabilities likely to be needed are shown in Table 6-9. Again,

review of these capabilities is required. In the event that a remote

facility is provided to support the attached mode, the GSFC Shuttle/POCC

Interface Facility (SPIF) could be utilized to provide required support.

This facility provides a range of capabilities to support missions

utilizing the STS as described in Table 6-10.

6-18
Table 6-9. Required Support Capabilities

No. Capability

1) Space Segment attitude determination

2) Space Segment attitude maneuver computations

3) Space Segment attitude dynamics evaluation

4} Attitude sensor performance analysis

5) Analysis of operations critical to the health and safety

of the space segment during attitude maneuvers

6) Orbit mission analysis

7) Launch window analysis

8) Orbit maneuver planning and evaluation

9) Realtime monitoring and correction of orbit maneuvers

10) Trajectory/orbit determination

11) Tracking system performance assessment

12) Mission maneuver suppport.

6-19
Table 6-10. SPIF Capabilities for Supporting

Missions Utilizing the STS

No. Capability

1) Planning and coordination functions for assistance in

mission planning and the integration of payloads into STS

operations.

2) Delivery of pre-flight planning data containing Orbiter

trajectory data.

3) CCTV display of Orbit tracking data (every 3 minutes under

timeline control or by request) and 2 hour projections

showing all planned Orbiter maneuvers.

A) CCTV display of Orbiter attitude data'(every 12 seconds

under timeline control or by request). Realtime and

projected data (next 48 hours) are available.

5) CCT transfer of Crew Activity Planning System (CAPS) information

from JSC with formatting for user display [planned capability].

6) Formatting of Operational Downlink (OD) data subsets provided

and building of displays for user CCTV

7) Imagery uplink to the Orbiter via the TAGS [planned capability]

6-20
6.7 GROUND SYSTEM DATA MANAGEMENT

This system provides the following functions:

a) Data preprocessing

b) Data processing

c) Data archival.

Table 6-11 defines a number of distinct data levels which are helpful in

describing the various processes presented in this and the following section. The calibrated images produced at level 2 are the images normally

used by the astronomer for detailed analysis as opposed to quicklook analysis. It must be recognized however that calibration will be an on-going

process; the instrument parameters will be better understood with time.

Therefore reprocessing of level 0 data will be needed (in timescales of

weeks to even years) using improved parameters from level 1. However this

process must obviously be used judiciously and within the available capacity of the system. The level sequence provides a partition for software

development and implementation responsibilities, and distinguishes

activities performed within the data preprocessing and processing functions

(through level 2) to those performed within the DAF (through level 4).

Table 6-12 presents the functions performed by data preprocessing and

processing. The level 0 through 2 data prepared by these functions are

archived. Table 6-13 provides an overview of the characteristics of the

data preprocessing and processing functions extracted from reference 15.

A calibration data base will be required to support the data processing

function. This data base will be developed based on pre-launch data and

procedures provided by the instrument and facility teams. Table 6-14

6-21
0

9

iH(U1a

^4JA£34JUa•Hat S••H^1vOVJ}4

au•H4J01 •HIHcu4JUcd

Iri cd

jQ°

IHCU

4-1

cd

ilCUcd

4->

cd T)IHcd •HOcd01cdcu •aaeCUc0cus0CJ cuCJ cu •HCJ COCOCU •a3i— 1 CJ MOCU •HJ2cd

4J31£cd4JS•ecu4J4•HOoQO 3

COcdcuCoccdcocu60cde•H3S

ader block accompanying the image, or 0) cdoc•HTJCU

4-1QIH0CO •Hcd

4-1*•

S*\

_*: CO

1-1

iHCJ •H

4-1CuO•CU••H^/«•HT3CUe

•

CU

•H•H

(4H

•ocucd -HCJOCOCOcdCcdCOcdij0

<4HXCo•oCU

4-10cu^4^4ou

•o

1-1CUcdIHIH0UH0) •— 1 JDcd

4-1

•H3CO4J14OUHCU00 •HCcdo4Je•HT3CUN"ecd00o4Jecuc0cusooCUCJ cCU •HoCAO•COIH0IHCUc • O

TlCOCO •HgCOccdIH

4-1

•eo•HUcd

i-H, 3Cu •HCBCcdxcd

iicuCO •HT3

ons, the serendipity field is separated •H

4-1

cdIHcuCO J30CJ •HCU0CJ CO0

4-1ocucuCOIHOo

.

CU00S•H

r-H.

cdIH4JCJ cuCUCOCU A

4-1BoIH

<4H

•oCU£•HC8 4J .OO

x~s

CO

iHCUX•H0

.

«»

«NO— HX-C*N0

fHOCM

ui >t CMi— 1 mcu •H^^CU00cde•H•aCUCOCOcuIHCUBoo<o

cd

4-1

cd

•acdIHcu

4-160

•HCOX0>, u§cusooo

iH.cr •ocd0cocuX4-1sIHUHIHCU si •HCU

•

COCU00cd •HCo•H

4-13•HOCOCUr*oo

1-1Si cu

4-1

COCU "ecdcuB0CJ CJ cd

.e. total counts, countrates) are output •HCOCJ •H

4-1

CO

1-(

4-1

cd

4-1

COXIH§|COcuoocdSi— i o

em and a subset are Included in the image

4-1

CO

CA4JecuBcu60cdcscd4J s

•

CU IH

si cu

4J 13cd

o cu

4-1 si c•H-o41>H0

"4-1

COCU60cde

i-»ioT>01COCucu

IH.

COcuoocdB•H

iHCd •HOcuCUCO

4-1

cdoUHcuUl 0

4-1

4-^1 •H

fH•Hs^cdCu <3O

ith timing appended) 3cu •o0ec0•H

4-13•HOCOCUucu

1-4

4-1

si

oo

c•Hecu

4-1

CO

CA

•oC0

(-1

CJcdIHcd4J0)

4-1

cdcu10cu

i-H.

cd

•Hcdca60c•HCOCOcuCJoIHCu 0

iHCU>$0

u

rH.

.O•HCOCOoQ

.

CO

cdcue•HiHcdcu*IHcducCOid

>.

4J

1-1cdcucdo>. CuOCJ T3cdcu60 •HO1— ( cu^3o

•a0cua

.

QcdIHO

<4HCUe•H1C0•acdCOeo•H4JcdCJo

rl CUOCUIHe0IH

<4Hcu -H•HCOCUuCJ cdcd io

cd

4-1

cd

•aocucu

1-11

UI COCU00cdS

Tteo•H

4-1

cd

IH

•H

1—4, cdCJ CO

4-10cdIHu£o•oCU>•HIHCUCO4J3COcuco•H

4-1

cd

.a•HiHCJ

es as appropriate and produces single fla ^13CO0cu0^1 •^

I-4CU •HUH

4-1

cd

UHCOCUe•HS3eoCOcuCJ scucr 4) COC0•H

4-1

cd

J3

•H

ilcdCJQOIHUH

•e0•HCO •H>•HT3^40UHCU

•-I

cdu•H3COCO *o

IH01

•

CO0•H

4-1

cd

li

jQ•Hi— 1 cdCJ cu •HCJ IHcdIH0UHCOIH0)

4-1§cdijcdCuC0•HCOCUa. ca •HT3COCU>•HIH(SO

•acd>

,

4-1

iHCOccu

4-1B

il siuo,0CO3COIHCU>>»

4-1

cdcu •H

iHCoccu60cde•HCOCUN•HIHCU

4.JCJ cd14cd 6o

XsicucdoooCuo

4-1

4-1

cuoocd4J

and distortion

standard star observations

CO

4J S CJ 0 CU (4

UI UH

cu

T3 CUCO

CU C oo o cd a. B co

•H CU

IH

COcu si N Q

.

1-1 cd

IH IH

CU 00

4J O CJ IH Cd 4J

fcl CJ cd cu 6 0

.

CA

O O

6-22
Is (continued)

c

s

CU iH

> *J

a ^Id.

cd 01

4J 4J

« 0

P *h

4J 5

CJ £

0 U

•H

4J

CO

•

^4

•4

1

V0

It

s for subsequent us

e wit

h associate

d

e medi

a

3 rH

CO -O

01 Cd

rJ CO

cd

C Id

O CU

•H

4-j a

« « o

Id 4-1

J2 cd 01

•H "O 00

rH Cd

Cd rH P

y cd o

y 4-1

CO -H CO

oo S

cd o 01

u c e

O -H

OJJ-li— l

S *J 1

•H CO C

H cd O

agement System.

c

S

cd

4J

S

o

4J

4J

3

cu

4J

3

O

X

14

cd

I

CO

libratio

n files.

cd

y

•O

rH

Ol

TH

U-l

4J

cd

rH

U-l

<4-l

O

>^

Cu

0

y

T3

u

S

t

c

o

•H

CO

•H

>

i-l

•o

•o

rH

CU

1-1

U-l

4J

cd

rH

Cu

orrectio

n (i.e., coincidenc

e corrections).

y

>»

4-1

•H

U

cd

0)

c

•H

rH

1

e

o

c

01

4-1

cdM

i

4J

§

O

u

•

•o

01

IJ

•rH

cd

CU

01

Id

CO

4J

y

01

Ud

O)

•o

y

iH

4J

CU

CO

cS

.

•o

0)

ISS

Ol

u

s

o

•H

4J

u

o

4-1

CO

•H

•0

rH

ed

y

•H

P

4-1

01

O

s

C-

•0

01

O

e

01

M

C

0

•H

»->

cd

4J

O

Id

•o

rH

01

iH

bial non-uniformity.

4-1

cd

Cu

CO

id

cu

4-1

rH

T-l

Ud

Id

O

«-(

e

o

•H

4-1

y

01

u

id

cS

s (if applicable).

01

00

cd

•H

•o

01

CU

p.

01

4-1

CO

1

J3

3

CO

CO

Ol

•H

•§

Iplie

d t

o spectrograp

h data.

Q.

cd

CO

c

o

•H

4-1

cd

b

.a

•H

rH

cd

y

.c

u

00

01

rH

01

>

5

•

•a

V

•a

01

01

CO

cd

CO

e

o

•H

4J

cd

iJ

J3

•H

rH

Cd

y

id

cu

4-1

0

e processin

g a

s note

d for Level 0.

00

cd

S

rH

cd

•H

y

Ol

Cu

CO

Wl

o

Ud.

c"

o

•H

CO

•H

S

Id

Oi

e

d header

s identical/similar i

n bot

h

4-1

cd

•H

y

o

CO

CO

cd

-o

c

cd

CO

0)

00

g

•H

U

3

Cu

4J

8

1 0 dat

a (includin

g corrected,

01

>

cu

rH

O

u

4J

cd

o

U-l

•a

c

cd

4-1

e

0)

4J

e

0

y

^

01

00

cd

e•H

•a

0)

CO

CO

01

b

Cu

0

y

vailabl

e for distributio

n

cd

0)

•a

g

TJ

C

cd

•o

01

>

•H

f

y

u

cd

CO

01

oo

a

eH

a wit

h periodi

c (milestone) archivin

g i

n

•H

T3

Ol

a

CU

rH

£>

ed

CO

«d

i-i

01

c

o

00

c

•H

>

•H

Si

y

3

O

U-l

4-1

e

01

c

cd

g

0)

cu

b Groun

d Syste

m an

d accessibl

e fro

m remot

e

cd

rH

IJ

cd

4J

CO

cu

j=

4J

4J

cd

Ol

C

1-1

rH

1

a

0

cd

4-1

,s

>x

u

•H

rH

•H

J3

cd

Cu

cd

y

CO >.

C Cu

O O

•H y

4-1 1

cd 13

y vi

rS S

o o o oooooooooo o o o

•O -H

01 >>

cd

4-1

cd

y cu^co

01 a, 01 3

lJ Cd rH Cd

M -H t

O

Ol

e js

y .o

-a o

e at -H

a) C

•rt

T5 cd IJ

01 4J J* r^ ^

4-1 JD -H —' O

Cd O rH

fcl Cd rH rH

ja 01 y 01 01

•H 00 > >

rH Cd 01 01 Ol

« e f rH rH

O -H 4J ^-/ v^

— c

o

u

6-23
u§u0) H41«d

4-1

4J

•H4JCO s

09U^H4J09 •HhCU 4JOCO(4Jj O

.

4-1CCUaOl yA£<u00

fl •He^ 4JO0eg

mul t i pi e image s . 60CiH>rHO>ciHCOCo•H

4-1

cdOl CUoy

iH4JOl aA

4-t

•H^

of interest from a larger field. COcO•H6001hi •0CU MH•HyCUeuCO MHOCo•H

4-1ycdhi

4-1 w

.

COO) 60cdS•H

iHcdhi 4JyOl a

.

CO

CU

4Jycdhi

4-1n3CO1CO

luding color/BW photographic yc•HCOC0

1-1

4-1a

.

oxa. oyhi cd J£MHo

4_^| 01 •Hhi §•

entations, contour plots, etc.

distribution and publication of

CO hi 0) O hi MH Q. 01 T3 hi CU•a 0) <U

iH 01

cd C yCO X 1 rH X C 01 O 6o0u 1oO CO 4-*

iH CO 4J 0 y E 3•O CO O 01 hi 60 a. to 2 rl

.

CO4J

iHCOCUhi yiHMHiH

4-1CCU •HyCO

o01

4-1

CO

C/3 •oCocd rHhi cd enOl

4-1

4-1

cd01c•HrH1CoOl rH

,40cd rH•Hcdcdai

4-

i1

Ml OCO COrHOl $

or science operations control. MHCO fHCOX

iHcdecd^oo

iHiH3cr cu4Jcd

4.)

•H

rH

•Hy<o MH

performed off-line at national DAFs

of supporting this level of image CU

60 rH

C X>

•H « CO O. co cd cu y yO CO hi C Q. 0iH

ff) 4J3

rH 4-1

01 -H

>

lt

*•»

m orj

iS CiH MH0 hi Ol X A

4-1 4J

•H O hi 0 T3

il C

.

xs60C•HCOCO01y0hi CU

requested parameters (i.e. fluxes, -C

4-1

•H9CO4Jycu •— i ^oCOhi 4JCO rHiHcd MH /-\ O COhi

4-1 O

CO' rH

•H 0

rJ CJ

CO

4Jycu X>0

ilcd3•9•HiH^C•Hhi 0MHcdhi

4-1y01a

.

CO

requested parameters (i.e. redshifts x:

4-1

•H3COcuc•HrH

iHcdhi

4-1ycuCO — 1 rHcd MHO

4-1

CO

•H

^^CO A•a3uaCU

•-Hcd •H3S"

Starlab Ground System to further cu A

4-1

4JcdcuC•HrH1CoCU§4-1 MH0CO

-a-

rHOl >

y for science operations control. 4J iH

iHiHX)cd0

.

cdy^oo

iH

"»* y3cr CU A4JcuycdeOl •oCO

iHCOC0•H4Jcd

4-1

COCU rH

Ul MH060c•HCOCOCUy • O CO SH d Q. O•H •* 4J3

1-1 4J

CU iH

CU CO

rH C— < MHO rHcd X 3

4-1 "O

•H iH

hi > O iH — 1 T3

o o o o o

o o

2S•s

3CD

COCU60cde

60 cy 0)

c o3 w

C CU

o -a

Cu O

<n e 01u a M O 0 iH y 4-i cd co > 01 hi 60 Ol cd co 43 fj

C CU

0)Ol O yC 60 O) C •H TH y co co co a S o o hi hi *W Q«

cd

•W COcu

01 60 y co c e CU iH •Hy c CO CO

y:S

•H

n_l I.

•H CU

y x:

01 4J C. CO CO hi

en

6-24
Table 6-12. Data Preprocessing and Processing Functions

Data Preprocessing

a. Data capture and recording

b. Demultiplexing and synchronization

c. Data Quality Monitoring (DQM)

d. Data accounting

e. Data delivery to data processing function, archives and/or data

archival

Data Processing

a. Receive buffered pre-processed data and format into images

b. Assess data quality (preview display of images)

c. Archive raw images (level 0)

d. Determine calibration parameters from images and laboratory data

e. Maintain all necessary calibration data on-line

f. Batch process raw images to create level 2 calibrated images

g. Archive level 2 images and spectra

h. Distribute level 2 images to all three national data analysis

facilities and requested level 0 images

i. Maintain a catalog of all Starlab images with a calibration

history

6-25
09

u

•H

4J

00

•H

hi

hi

3

S

00

00

o

1

9•Hocess

&

£

3

&

•

cu

1

Deliver Tim

e Recordin

g

io

n o Goal of delay of n

o o Ra

w telemetry rou- more tha

n 3

0 minute

s tinel

y recorde

d t

o

to befor

e buffere

d trans- allo

w retransmisu

•H

4-1

•H

hi

4-1

CO

S

y

UH

TH

CO

CO

cu

y

o

£

cd

u

a

0

r"

"y

4-1

3

I

2

a

•Hprocesse

d d

a

3)

O

c

o

•rt

4-1

y

3

tv

cd

4-1

Cnsmlssi

o

2

co -a

g! 2

•H CU

x: UH

y UH

J3c3

0 0

•O

*^ CU

CU 4J

4J Cd separ

a

associ

S *

cd cu

S 2P

* I

CU -H

"° O e u

cd c y -H

oo

c

CO

CO

CU

y

O

a.

cu

cu

hi

iH

cr

cu

hi

CO

cd

c

o

CO

cd

4-1

cd

TJ

cu

o

o

•H

CO

CO

•H

B

C

O

•H

4-1

1

UH

2

•H

CO

CO

cu

y

ed

4-1

CO

4-1

§

aineerin

g co

m

cu

processin

g functio

n o Dat

a kept onl

y a

s

lon

g a

s needed.

2 o Shuttle-complet

e set

AF, of level 2 dat

a prer pare

d withi

n 3 months

CO

ex

2

&

1

m

4-1

cd

rH

CU

I

rH

UH

O

CU'

CO

CU

4J

CU

rH

O.

0

&

cd

rHibrate

d Star

rH

0

cd

4J

o o

UH

O

4-1 Cd

•s!

J<3

hi

4-1 «

CO IH

•H rH

hi

« 4J

4-1 CO

2

4-1

o, cd

CO 4-1

1*

CO rH

CU CU

00 >

J

CU

rH

•*^

oo

c

iH

CO

CO

cu

o

o

4J

cd

4J

cu

0

rH

cd

iH

y

5

2v_x

co

4J

rH

COermediat

e r

e

4-1

O

ste

d - quickloo

k dat

a avail5J

cr

2

*0

0

•H

4-1

5iH

hi

4J

CO

O

|

cdcalibr

cu

i

CO

cu

oo

i

CO

CU 0)

4J -* CU

3 CN 00 X

C ffl rH

IH UH 6 rH

O >» i-H

<n CJ rH g

hi CU 4J Cd

cu 4J hi co c

4-1 ffl O X O

UH rH UH CO IH

Cd 4J

rH CO hi Cd

<U C8 hi CU hi

I-H 4J 3 4J y

xi o o 4-i 5.

cd 4J X! cd O

1

^ -* oo -o

y • CN hi c cu

1 • IH 4JO O • iH 4J

hi 003 COrH COhi y

cdc d -4-icrfsjao.H^gc u

UH *O 4J S <U O CO r-J . iH CO

o ea G a hi -H e o oo

eyo o IH • m c cd

<DO UHlHCU H 4J <]J 4J

4ji-iai4Jcnoo3t n /*\ cd

cd 4J oo ed co cdS co -a

TJCdCdrHlHCOShlCu-IC U

a hi e ex B cu C o o -a >~.

o)3Xli H C04JOT3U H 3h i

CU iH CUC-HUHC U XIrHc d

aoyrHTjycdc o cocu4Jy g

JIH cd e 5 hi c3 co (JOTS c § •dycd2.J-»i)iHcug-Hi H 3

o co u u e 3 ca

1H4JC U J«iO<BO'i-<T3c d

3uccohioe4-)axiC4-i- o

lj PJ hi XJ fa i— 1 hi CS O CO xi T3 03

0 0

CU CO CU •*

J3 iH CO CM 1

CO CO O rH

•O O >> CU -^ iH CU

r-j _£ rH hi X Id 4-1

33 cd Q. 00-* > "^ O

o eaccNcde g x

x: en cdo-rj o 03 a) u

Cflhl yg-HC U M -H

CU hi Cd >_/ O — X> >> rH

x-scoo-4-i y cdo -H

CU3UHCdCdCCOT3rH U X I

00 T3 4J TH CU rH O. Cd

cdo e cd so d co c a.

xiucuTSTSUJcao-H O cd

x:cu OBXJTJ- H y

CdCU4-IN ^ iHC O CO

4-1 rH -HOC O hlC O >-, T3

cdxicurHoexir—oi H Q.CU

T33)hlCdrH.OCd4JUH S O hi

rHiH-HJiiHi— Ict l ffiCOyiH

CiH3yycahiBcuecu'u 3

ocdcrcuiHhicdCf-Hed'Uhic r

iH>cua.3cU4Jox)hiiHcdc u

4->vdhlOOO'>COU-ICd4JC03h l

O 0

I •

CO CO

C T3

ed e

hi 0 4J y

cu

t*Q CQ

^ c

rH iH

CU -C

55CJ

cd -a

hi CU

CU 4-1

4-1 4-1

6-26
Table 6-14. Data Processing Data Base Size Estimates

[Data bases required on-line]

Item Approx. Size

Flat field correction for 48 filters 48*160 Mbytes

Linearity correction file < 160 Mbytes

Blemish files 100 Mbytes

Geometric distortion files < 100 Mbytes

Others < 10 Mbytes

Total ~ 8000 Mbytes

Note:

These data will change with time but only one set need be online

for a given calibration sequence. Different sets could be stored

on removable disk cartridges. These data could be stored on a read

only device such as an optical disk.

6-27
presents a preliminary analysis of the size of the data bases required to

support data processing. It should be noted that a high percentage of data

base information required by the data processing function will also be

required by the DAF. In general, the evaluation of the overall data base

requirements for the Starlab Ground System will need careful examination in

order to minimize duplication and provide an integrated capability.

Image reduction techniques are a function of image type. The following

subsections detail the type of processing required to provide calibrated

Starlab images.

6.7.1 Direct Imager (DI) Image Reduction

The calibration functions for data processing of DI images include:

a. linearity correction

b. flat field correction

c. background subtraction

d. removing known cosmetic defects

e. locating and cataloging bad and questionable pixels

f. removing geometric distortion

g. spectrophotometric calibration of the grisras and photometric cali-

"" bration of each filter.

h. correcting for filter spatial non-uniformity

i. Computation of input flux levels from the knowledge of instrument

gain including filter transmission values

The first two steps will use an algorithm which is both pixel and wavelength dependent. It might, for example, be a function or an interpolation

6-28
table assuming that the response curve is adequately determined. Tables of

coefficients for each filter will be online for this calibration. The

known cosmetic defects will include known bad areas of the detector and

memory. These may change slowly with time and must be monitored. Step e.

includes recognizing possible cosmic ray hits, telemetry errors, and other

asynchronous events and cataloging these with identifying codes. The

removal of geometric distortion will probably involve two steps. The first

will be a correction for discontinuities caused by shears in the pixel

array (either in the optical fiber bundle or the channel plate ) and the

second will correct for more gradual distortions. This second part will

probably be a control grid mapping with a weighting scheme that preserves

the total flux locally. The final result of these calibrations will be

pseudo counts/pixel and a global calibration coefficient to convert these

counts to physical units. The pseudo counts will represent the actual

counts on the average and, providing the flat field corrections are not

especially large, can be used to roughly determine statistical

significance.

When specified in the observing schedule, some DI images will require

•Piil»f-V» furtheo Tr» processin r»i-r»/*ae e-f ngo tlhir» whichh ma mavy -fn/^lii/lo include:*

a. removing field rotation (to align images)

b. combining several images to obtain longer exposures

c. combining sub-stepped images

6.7.2 Spectrograph Data Reduction

Spectrograph data calibration will be more complicated. Because the flat

field and linearity response of each pixel may be wavelength dependent, the

6-29
wavelength associated with each pixel must first be obtained. Using

calibration data, the position of each spectral order for a given mode can

be readily obtained although some provision for imprecise positioning of

the slit may be necessary. The wavelength dependence of each pixel will

probably be determined by linear interpolation from a table of coefficients

for each pixel. The pixels in each spectral order will be processed for

the appropriate response and geometric corrections. Note that in cases

where spectral orders overlap, a given pixel may be processed as a member

of more than one spectral array with orthogonal spatial and wavelength

dimensions. The pixel size of these new arrays will be as close as

possible to the original image pixels. Note that in cases with order

overlap, the data volume will be larger than the original level 0 image.

The next step is the deconvolution of order overlaps which depend on a good

calibration of the cross disperser's spectral dispersion function. With

slits short enough to minimize overlap, this can probably be quickly

accomplished interactively. For longer slits, the problem becomes more

difficult and may need to be deferred to the data analysis function. A

straightforward deconvolution (e.g., using Fast Fourier Transforms (FFT))

may also be possible but is likely to require high precision calculations

and increase the necessary computer resources considerably.

The quantity stored in each pixel will be a pseudo count which is defined

as the photons that would have been counted by a pixel with the average

response at that wavelength. Coefficients to convert the wavelength index

number into physical wavelength for each order will be contained in a

record header for that order. These calibration steps can be summarized as

follows:

6-30
a. spectral order boundaries will be determined

b. a wavelength calibration will be derived for each pixel

c. spacecraft doppler correction

d. linearity correction

e. flat field correction

f. removing known cosmetic defects

g. removing geometric distortion

h. each order will be "straightened" into a rectangular array with

orthogonal spatial and wavelength dimensions

i. deconvolve order overlaps

j. derive absolute calibration

These processed spectra files will then be archived as a separate file type

for each spectrograph mode with identifying information in the file

headers. Each file will need to be organized into records corresponding to

the spectral orders. A record header will contain order specific

information such as physical wavelength information.

6.7.3 Grism Images

The "grism" observing mode will also require additional processing. A

grating + prism combination ahead of the focal plane produces a small spectrum of objects in the DI's field of view. The desired data processing

product is the spectra of each object and its position in the sky.

Automating this process could be a challenging software task. It could be

simplified if a short exposure without the grism was available for the same

field of view. In this case, the program would simply process a parallelogram representing the potential spectra of each identifiable source. In

crowded fields, there may be considerable overlap of such areas which will

6-31
produce some confusing spectra and increase total processing time. Once

the spectral zone of each object is determined, the processing is similar

to the spectrograph processing procedure above. The data would be

organized as a grism file with a record for each spectra. Record headers

would contain information on the sky position of that object and wavelength

calibration coefficients.

6.7.4 Image Catalog

A comprehensive catalog of all Starlab images needs to be automatically

generated as part of the image processing. Each catalog entry will contain

information reduced from the actual image, associated engineering data, the

observing schedule (from the planning and scheduling system), and manually

entered comments. A calibration history will also need to be updated each

time the data is processed or re-processed.

This catalog will be the primary means of organizing the Starlab data base.

Both the data processing and analysis software systems will use it to

locate specific data sets. In addition, various search and survey programs

need to be available to users to allow data selection based on information

contained in the catalog. For example, it must be possible to ask a search

program for all images available that cover a specific point in the sky

taken in a particular observing mode. In general, the search program must

be able to select any logical combination or range of catalog values.

The size and exact contents of the catalog entries for each image and

spectrum file are TBD. However, we can roughly estimate that each file

would require about a 2000 byte record. For the two year data requirement,

this implies a total of 70 Mbytes of online storage for the catalog.

6-32
6.7.5 Current NASA Capabilities

The Sensor Data Processing Facility (SDPF) provides data preprocessing

functions for many NASA programs. In particular, the SLDPF provides a

range of standard data processing functions and products for Spacelab

payloads as shown in Figure 6-1. This facility provides these products to

the users nominally 60 days after the data are acquired. Data products are

normally in the form of CCT, but other media are available. Data

preprocessing functions are likely to be provided by the SDPF for payloads

on Leasecraft. No details on facilities to support the Space Station are

available.

6.7.6 Data Archival

Following the processing of the various types of data, an archive needs to

be established to support the requirements of U.S., Australian and Canadian

investigators and possibly guest observers. This archive will be contained

within the NSSDC and/or the Starlab Ground System. In the event that

remote facilities are developed in Australia and/or Canada, the archive

could be distributed, where each country retains a complete archive. Whatever distribution is determined for this archive it is important that the

overall management of the function be considered in order to ensure data

validity.

Table 6-15 contains a potential list of considerations which need to be

reviewed in the definition" of the archive requirements. In addition, it is

necessary to consider the flow and the responsibilities for input of data

into the archive. Table 6-16 summarizes preliminary data archive storage

requirements for level 0 and level 2 data for the sample Starlab missions

6-33
oa_i <ou_Q_QLUOS(sa.

Q

LLJ

6-34
Table 6-15. Potential Archive Considerations

1) Distribution of archive

2) Data types with levels

3) Archive capacity

4) Reference information required to identify archived data "

5) Data security and/or access protocols

6) Search criteria

7) Typical access scenarios with timeframe requirements

8) Archive file management requirements

9) Anticipated user access of the archive with representative requests for data type and volume, frequency,

timeliness and overall loading requirements

10) Need for simultaneous access of specific data

11) Timeframe for insertion of data into the archive

6-35
Table 6-16. Preliminary Starlab Image Archive Requirements

Mission I Mission II

# of images

per day 50 50

Image size before 80 Mbytes 160 Mbytes

compression

Image size after

compression 40 Mbytes 80 Mbytes

# of raw image

copies to store 2 2

# of intermediate

images to store TBD TBD

# of processed

copies to store 1 1

Storage/day 6 Gbytes 12 Gbytes

# of days 10 200

Total Storage 60 Gbytes 2400 Gbytes

Note: Total storage required for a two year data requirement is 730 days x

12 Gbytes = 8760 Gbytes.

6-36
and in order to satisfy the two year data requirement. Other data storage

requirements are minor in comparison. These estimates assume that the data

is stored in a compressed format which reduces the storage requirements for

an image by a factor of two without loss of information.

6.7.7 Computer Resource Estimate

A rough estimate of the computer power needed for the data processing can

be obtained as follows. Assuming that each image is 9600 by 9600 pixels

and that there are 50 images/day to process in a 16 hour shift, the system

must process 80,000 pixels/second. Current estimates are that approximately 50 to 100 operations per pixel may be required and perhaps 10 I/O

transfers. These figures would imply a system speed of about 8 MIPS (million instructions per second) and an I/O transfer rate capability of at

least 1.6 million bytes per second. (Each pixel is 2 bytes).

6.8 SCIENCE DATA ANALYSIS

A DAF is required to provide a host facility for the support of science

data analysis functions for U.S. investigators and possibly guest

observers. Implementation of this concept was found to be extremely

beneficial on the International Ultraviolet Explorer (IUE) program, and the

development of a similar capability for Starlab is therefore proposed. The

primary function of the DAF will be to extract scientific knowledge from

the Starlab images and associated data. It will also provide the feedback

necessary for planning subsequent observations and for developing and

improving calibration procedures. In very broad terms, some of the major

tasks of the DAF are:

6-37
a. Provide astronomers quick access to all archived Starlab images and

related data bases

b. Interactive image processing to obtain level 3 and level 4 data

c. Provide sufficient support to allow prompt organization of results into

a form suitable for publication and/or presentation

d. Continuing software development for calibration and analysis

e. Feedback of results to other Starlab system components

f. Analysis support for mission operations.

The DAF will provide the environment and the tools to permit the astronomer

to carry out detailed studies of his data. Similar facilities will

eventually be commissioned in Canada and Australia for the space platform

missions. It is essential that the computer and data management systems be

similar enough to allow the mutual exchange of analysis and data reduction

software.

In contrast to the data processing function, which handles Starlab data in

a systematic, uniform way, Che data analysis function performs processing

customized according to the specification of individual users. It is

expected that two basic classes of users will utilize the data analysis

capabilities. One type of user will be the observers and archival

researchers who will process Starlab images and spectrograms for scientific

purposes. Another type of user will be members of the observatory staff

who will process Starlab images and spectrograms to help understand the

6-38
Starlab instrument, to monitor its performance, and to update its calibration functions and tables. Both types of users require some form of interactive computing and may therefore be accommodated by the functions

provided.

Both classes of users will work with Starlab data in its various stages of

reduction. For scientific analysis, the reduced (level 2) form of data

will be used most of the time. For calibration analysis, the data will

need to be examined at several stages of reduction.

6.8.1 Analysis Functions

Anticipating all of the analysis tools that will be used to process the

large field survey imagery and spectrographic data from Starlab is probably

impossible. Also, many techniques will be data and/or astronomer specific

and only developed after experience. Table 6-17 presents some of the

spectrograph and grism data analysis tools.

Two general capabilities will be required. The first is the capability for

computer-assisted recognition, measurement and storage of the results of

measurement for features of interest within the Starlab data. The second

capability is computerized statistical analysis capability for processing

of tabular data extracted from Starlab images. For either capability

astronomer interaction should take a minor role (i.e. initiating the calculations and reviewing the results) with the actual processing performed

in possibly a batch-mode.

The DAF software system must serve users with a wide range of computer

expertise and needs. Easy to use software packages should be built for all

6-39
Table 6-17. Analysis Tools and Resources Needed for Image,

and Spectrograph and Grism Data Analysis

Image Data

o Image display

o Interactive image extraction and manipulation

o Contour mapping

o Temporal change analysis

o Point source and surface photometry

o Object classification

o Geometric analysis of objects

o Multi-color classification

o High and moderate quality hardcopies

Spectrograph and Grism Data

o Spectral display

o Spectral extractions and manipulations

o Spectral comparisons

o Spectral feature identification

o Velocity analysis

o Time series analysis

o Curve of growth

o Profile fitting

6-40
commonly used tasks but generalized software should also be available for

sophisticated users. Already there are many extensive software systems in

use or under development that address the needs of astronomical data

analysis. By the time that the Starlab project will be required to commit

to a detailed hardware and software design, there will be several mature,

active astronomical data analysis facilities around the world. A very

important aspect of the Starlab DAF will be its ability to make use of

these software systems and only embark on expensive software development

projects for Starlab specific requirements. This implies a degree of

computer compatibility that may determine the choice of the computer

system.

6.8.2 Data Products

A large percentage of DAF activities will involve the production of level 3

and 4 data from the level 2 data- processing output. The specific

operations required are science oriented. As defined in Table 6-11, level

3 data are in the form of images and spectra while level 4 data are final

extraction of physical parameters of specific objects. Examples of level

4 data include.

o Lists of stars/objects in a given field with extracted observables

(fluxes, colors, ...)

o Cepheid periods and fluxes in M31

o A list of spectral lines with requested parameters (wavelengths,

widths, redshifts, ...)

o Galactic rotation curves

6-41
Much of the level 4 data generated will be combined into a large

astronomical data base that will eventually be available to the scientific

community. Calibration results obtained from in-orbit calibration

sequences are another product. These results converted into calibration

data bases and procedures are used to convert raw images into level 2 data.

This will be a continuing product as the instruments change with time and

become better understood. Quality image hardcopies, graphics and other

intermediate and final result representations are required.

6.8.3 Delivery Times

Analysis of some aspects of Starlab data may continue for many years, but

it is essential that the major objectives are accomplished in a reasonable

amount of time. It will be necessary for both the data processing and

analysis functions to provide rapid quicklook analysis of the quality of

the calibration data as well as the level of scientific return being

achieved.

To meet these requirements, the DAF must have access to selected images

(perhaps 10% of the total) within 24 hours and it must have the capability

to evaluate these images within another 24 hours. Examples of such evaluations include simple quality checks such as:

o background uniformity

o signal to noise levels

o focus checks

o correctness of calibration.

Some of these tests may require only selected parts of the full images.

6-42
In addition to the requirement that the DAF be able to provide quick

feedback on selected data for the effective operation of Starlab, it must

also have a total throughput capability able to keep up with the

observations to prevent an ever increasing backlog. The DAF together with

corresponding facilities in Canada and Australia must be able to handle

data at the same rate that Starlab acquires data (about 50 images/day).

Because of overlaps in data analysis efforts, the GSFC DAF's share would be

about 25 images/day. For a given observing program, a user should expect

to be able to extract the primary scientific information within 3 months of

completion.

6.8.4 Relationship With the Data Processing Function

The size of the Starlab data processing and data analysis functions is such

that it would be impractical to have them operating in a single computer

facility. The data processing function will need to work full time in the

most efficient batch mode possible turning out the level 2 products. This

involves not only the actual computation effort but also the cataloging and

archiving effort. Very careful quality control will be needed to guarantee

that the most recent and correct-calibration is applied and that adequate

records are kept. The DAF will need to provide the data processing

function with sufficient response time to permit the calibration process to

be properly tracked and updated. It is important that the DAF be able to

run the standard data processing functions so that the testing of software

and calibration modifications can be made off line to the data processing

production activities.

6-43
6.8.5 Number of Users

It is required that up to 16 researchers be able to access data during any

given period of time at the DAF. Eight of these will be doing Direct

Imager work and eight will be doing Spectrograph work. These 16 users will

be divided into two shifts, so that there will be only 8 simultaneous major

users utilizing the system at any one time.

6.8.6 DAF Data Access

The.. DAF tasks require access to a number of large data bases and also

require sufficient on-line storage to support user activities. The major

data bases include:

o raw image archive

o processed data archive

o observation catalog

o calibration data

o observing plans

o stellar catalogs

The raw image and processed data archives will be too large to be entirely

on line. These data could be stored on optical disks which would allow

access to any given set with about 10 minutes. (The DAF access to this

data will be read only. The data is generated by the data processing

function). Expansion of the compressed form and higher subsequent I/O

rates are likely to be required for data analysis tasks. Hence transfer of

the data from an optical disk to an alternate media such as a disk is

likely.

6-44
The observation catalog needs to be entirely on-line to allow its effective

use for data searches. The other data bases listed need to be quickly

accessible but not necessarily on-line for the DAF. However, their volume

may be small enough in comparison to other on-line requirements to allow

complete on-line access.

The amount of on-line read/write storage required for analysis activities

will depend on the number of users that are actively using the system at a

given time. The system must be designed such that a natural growth of

active users can be allowed as the volume of acquired data increases. This

will permit-an orderly growth from a current research type of facility into

a facility that can also handle archival studies of the ever growing

collection of survey quality imagery.

A possible breakdown of temporary storage required for 16 simultaneous users

is listed in Table 6-18. Allowing for some extra data sets the total

estimate shown should be raised to about 100 Gbytes of data.

The DAF must also have access to non-Starlab data bases. One of the most

important aspects of survey type of research is the ability to crosscorrelate the current data to similar data obtained with other instruments

and apparently unrelated research done in other fields. For example, the

comparison of optical and X-ray imagery of the same region of the sky

searching for and comparing H-alpha emission objects with UV excess

objects. Therefore it is a requirement that the Starlab DAF have access to

the existing networks of astronomical data bases, for example the GSFC

NSSDC or the Catalogue of Stellar Identifications. This puts a requirement

on the DAF hardware and software that it be of such a nature to permit easy

access to local area networks as well as national and international packet

6-45
Table 6-18. Temporary On-line Storage

Type of user

Direct Imager

Extracted Spectra

Original Images

Number

original

images

Number

copies

Total

per

user

Total

for

system

10

20

20

6.4E9

80.0E6

7.2E9

60.0E9

1.6E9

14.4E9

Total = 76.0E9

6-46
switching networks. Table 6-19 summarizes the data access requirements for

the DAF.

6.8.7 Computer System Estimate

The computer resource estimate for the Starlab DAF includes capability for

the general purpose image display and analysis< image manipulation, and

feature extraction. It is assumed that there will be 4 image work stations

and 4 spectroscopic work stations on line at one time.

The number of instructions needed per image is difficult to quantify. It

is clear that both integer and floating point operations will be needed,

integer for speed and floating point for calibration accuracy. A typical

image operation will require a fetching of one or more input images, 5 to

20 instructions per image operation, and storing of a modified output

image. This implies 20 to 25 instructions per pixel and 2 I/O operations

per line of the image in a serial type computer system. If the image size

is 9000 by 9000 pixels and there are 4 active image manipulation tasks, and

if a reasonable response time for an image operation is 5 minutes, then the

computer system must have the equivalent computational speed of 27 million

instructions per second and an I/O transfer rate of 1.6 million bytes per

second.

6.8.8 Hardcopy Functions

Hardcopy output products are required to record Starlab imagery. This

requirement is summarized in Table 6-20 and provides information on the

hardcopy requirements as a function of user and/or workstation as

appropriate.

6-47
Table 6-19. DAF Access Requirements

Item

Raw Data Archive

Processed Data

Calibration Data

Observation Catalog

Temporary User Storage

System and User Software

Stellar Catalogs

Observing Plans

Type of Access

Read only

Read only

Read only

Read/write

Read/write

Read/write

Read

Read

On-line Requirement

~ 5 to 10 Gbytes

~ 5 to 10 Gbytes

-'5 to 10 Gbytes

70 Mbytes

100 Gbytes

~ 100 Mbytes

~ 100 Mbytes

6-48
C "

O

o 01

•H 4J 4J O 3 01

CO01o

ij -a e

o

M c

co o co

01 u

w> to

O)

.£ rH B

OOrH -H

il 3 Li LI

x ui a. 4->a

.

CO

18

cd

T5<ua

. aCOH

U b-.

<U <

.a Q3 C C -H a li SQ -H H 3

C 4-1

O O a)

O -H S

O u Si

- 30

O .-I 14-1

-HO U tn oo o

x 01 X rH

M oo o

o o O rH C o <u a .

c

- X *J

O -H C -H

—I CXH S

Q.

CO 4J M O eo .c o co u a

.

o cs

OH co

o u •U X O Ol CO O O

.

>, o

(0 £

rl 0)

ex ex

rn fl •H C O CO

c

M O (U -H O. 4JCO X u CO co IPS*

 O

H 3

•a 01 oi 3 1-1 y o

o c

^. rH -H CO O

00 to > S 1-1

O) 1H 4J

Li Li T3 CO

O O JS 4J

00 U CO

e co

•H Ol ~£t

a,

CO

o e 3"

COai rH -H C

« CO "O S -H

O rH

O O O 4J O

4J 3 O

Ll U CO rH O

o c a o —<

M CO u

a. S co

Ol ao

O Li o 01 O S

U CX 4-1 Ll 4-1 1-1

•oI

COO r

H >,

•H CO 4J

A C -H

O. ^ rl

CO 3 CO

o •-

°>£

o

—I co

<o u e -H

1-1 I-l 3 J= O 3

"-) PM

rH CO

co -a

h ca

3 >» 4J

O -U U3

O— (0 O

CO 3 U H ty a

.

M-l CO 0 cM Vj 3 01 O XI -o c

o

§

>> O CO

S u 1-1 01

C 01 il J3 U

4-1 rl O.TH

Q CO co (0 >

« >, 3 M 01

H CO CT 60T3

opaEH

ouhCO

(0

•a

CO O u o

•H rH f ^a o CO -H

oorH^ C

O

O 4->

•H O

co M e

rl O O 00 3 -H

4-1

O h co

pa oi •u

H Q. CD

•O 0 e -H CO SI C a o 0> efl -H 00 M 4J CO 00 CO

S ou

•H Ij CO

U Ol Li

CO CX O

W co 3

o=QH

41

rHA

•O W 4J

M CD 3

CO 4J O

•a 3 AJ

c ex c

to e TH

4J O VJ

co u ai

CO

CO

CO 00

4-1 C

1-1 1-1 o •>-> (X CO

CO

•oCO0100COa. aCQH

73 CO

Il M CO S Ol •a 01 u C 4J C CO W i-l 4J >, U CO CO O

.

CO0) -

O U

a jj a>

•H CO 4J U

rH T3 3 3 s o. a

.

CN CO S •U

•H CO

O 3 O O

eo

•ooLl 0-

O) ootoca

CO M

3-S. X C a. o O Ol 1H U U 4J T3 -rt Cfl u > u

COu

4-1 il O UH 3 i-l •a o O 01 b a

.

CM CO

6-49
7.0 INTERFACES

7.1 STARLAB/NASCOM/TDRSS INTERFACES

In the Shuttle sortie configuration the various STS, Spacelab and Starlab

data are transmitted over channels one, two and three under normal

operations. The contents and characteristics of channels one, two and

three data as downlinked by the TDRSS Ku-band are shown in Table 7-1. As

shown in Figure 5-1. channel 2 and 3 data are received directly at the

GSFC. Channel 1, 2 and 3 data are received at JSC and selected subsets of

channel 1 are extracted by the JSC MCC and forwarded to the GSFC SPIF.

Table 6-10 provides a summary of the capabilities performed by the SPIF for

supporting payloads utilizing the STS. With reference to Figure 5-1, the

channels 1, 2 and 3 data as appropriate, are forwarded from the TDRSS

Ground Station to the GSFC and JSC via the Domestic Satellite (Domsat).

In the Leasecraft space platform configuration, the Leasecraft communicates

with the GSFC again via TDRSS and Domsat. The JSC is not utilized in this

configuration (Reference Figure 5-3).

7.2 STARLAB/INSTITUTIONAL FACILITIES

The interfaces of the Starlab Ground System with the various GSFC

institutional facilities are not provided in this document for the Shuttle

sortie configuration, since current indications are that utilization of the

Shuttle sortie mode will not be made for Starlab. The corresponding

interfaces for the Leasecraft space platform mode are TBD at present. At

the present time consideration is being made on the development of a MSOCC

type facility at the Fairchild Space Company facility at Germanto'.M,

7-1
CO

a.

CO

o

U-l

d

3

o

a

05

ca

i

Cfl

I

r~

<1)

^

c8

_J

LU

Z

z

CJ

KO

CN

r-H

LU

a

o

S

CO

_J a.

< 03

i— si

o o

— LO

a i

eg

CO

a.

03

H- CNJ

0 CO

a o

o

"03

CO CO <

_i a. a. _i

< CO 03 LU

i-^i*: s u — o < OCN-=T cr a,

— <DUD U. CO

_*

r— 1 Q.

M

X

co 5£

a.

as un

< O^TLU

h-a- o z

— 1 CC _l £TZ

CS tO O < O <

— r-H Z X

Q ^"^ ^ > O

Ho o

CO

a.

03

_i s:

t— CVJ

3 U3

Q O

0

*^

CO CO <

-I 0.0. -1

< ca 03 LU

t-^::*: s: u — o <

OCN-^ Of Q-

— • G^CO U_ CO

'

^^ ^

CN LL

"^

a:

o

LU a

< < Q; O

cr 00

LU _l

x u o <

o z LU z

— LU Q <

CO

LU

Z < LU <

<crcj _J

Z LU LU

1

 O X LU CJ.U

— 0 — < —

o — o a. o

LU X CO CO >

a

z

^

o:

^

^j

_J LU

— CJ

CO CJ —

H- Z O

CO <>

Q

LU

K—

Ui^

c — < s

LU O CO

a. a. c i—

7-2
Maryland, to support Leasecraft. The location of the POCC facility is

likely to have implications on the internal interfaces required within the

Starlab Ground System.

7-3