Filling Out CIMS Fields for Tour
Jerod Gross
May 10, 2001
CIMS Fields
Overview
•
In order to create an APGEN file for use by Science Planning, teams are
required to fill out CIMS requests, and not just observations. Furthermore, the
requests need to have APGEN fields added to them.
•
This package attempts to document everything teams/subsystems need to
know about filling out their CIMS requests and adding APGEN fields as of
CIMS version 1.2.
–
•
A new version of CIMS will be delivered in June/July 2001, which will have some new
fields to be filled out (ex. Priority). Instructions on filling out the new fields will be
circulated after the CIMS delivery.
There are also team-specific sections to assist in the addition of APGEN fields
to the requests.
J. Gross
2
05/10/01
CIMS Fields
Overview (cont.)
•
Each team should input their desired activities for all Tour sequences starting
with Sequence 1. Sequence 1 begins May 15, 2004 (2004-136T00:00:00).
–
Exception: The TOST and (the targeted icy satellite) SOST periods will be delivered
on a different schedule than the rest of the Tour.
•
The Science Planning will soon be adding Tour epochs to CIMS. Epochs will
be added for apoapses, periapses, Titan and icy satellite flybys, ring plane
crossings, etc.
•
If there are any other events you would like to have defined as their own
epochs, please let the Science Planning team know ASAP.
–
J. Gross
Keep in mind, however, that epochs are available from a single drop-down list. We
don’t want to overwhelm the user with thousands of epochs, so request your epochs
somewhat judiciously!
3
05/10/01
CIMS Fields
Required CIMS Inputs
See following pages for detailed information in filling out required fields
CIMS Request Fields
•
•
Request Header
CIMS APGEN Fields
•
CAPS: Activity types CAPS_<rate>, Parameter RateMultiplier
CDA: Activity type CDA_524, Parameter RateMultiplier
–
Title
–
ID
•
•
–
–
Start Time
•
INMS: Activity type INMS_1498, Parameter RateMultiplier
Projected Duration
•
ISS: Activity type ISS_<target>_”X”_by_”Y”, Parameters
–
Change
MAG: Activity type MAG_1976, Parameter RateMultiplier
–
Visibility
•
•
•
RADAR: Activity type RADAR_364800, Parameter
Request Description
–
Description
–
–
Pointing
–
Rate & RateMultiplier or Frames &
BitsPerFrame
Estimated Data Volume
CIRS: Activity type CIRS_4000, Parameter RateMultiplier
NumberFrames and BitsPerFrame
MIMI: Activity type MIMI_<rate>, Parameter RateMultiplier
RateMultiplier
•
RPWS: Activity type RPWS_<rate>, Parameter RateMultiplier
•
•
RSS: Activity type RSS_Activity, no Parameters
•
VIMS: Activity type VIMS_<rate>, Parameter RateMultiplier
UVIS: Activity type UVIS_<rate>, Parameter RateMultiplier
Activity type VIMS, Parameters NumberFrames and
BitsPerFrame
•
J. Gross
4
ENGR: Activity type MILESTONE, no Parameters
05/10/01
CIMS Fields
Filling Out a Request
•
•
Log into CIMS (https://cassini.jpl.nasa.gov/cims/index.jsp)
From the “Request” tab, select “Add”.
–
Certain fields which are required by CIMS are marked with an asterisk. Additional fields required by
Science Planning are indicated below:
–
Required “Request Header” Fields
•
Title: Title of the activity. This can be anything which describes what you are doing. (CIMS req’t)
•
ID: The official Cassini request name, which follows the Cassini naming convention
– Select the appropriate period from the Period menu
– Select the appropriate target body from the Target menu
– Type a name for the activity which describes it (9-character max.) in the Name area
– Type an number for this activity in the Instance area (ex. 001 for first instance in a given period)
– Select “Prime” from the Prime menu if you are the prime instrument; if you’re a rider, select the appropriate
prime instrument
•
Start Time: Must be epoch-relative or absolute (i.e, SCET).
– Do *NOT* use the “Text” option, as APGEN activities cannot be created from activities with the times defined
as text. If you do not know the exact Start Time of your activity, put in a dummy epoch-relative or absolute
time and make a note in the Description area of the timing requirements (e.g., over a DSN pass)
– Let Science Planning know if you need to create new epochs for your activities.
J. Gross
•
Projected Duration: Duration of the activity
•
Change: a short description of the edits made to the request (CIMS req’t)
•
Visibility: Must be marked “Public” by the time Science Planning is ready to create the APGEN file. All “Hidden”
requests are ignored when CIMS creates the APGEN file
5
05/10/01
CIMS Fields
Filling Out a Request (cont.)
–
–
J. Gross
Required “Request Description” Fields
•
Description: a brief description of the activity
•
Pointing: the primary and secondary axis pointing
•
Estimated Data Volume: for science instruments only
•
Rate/Rate Multiplier/Frames/BitsPerFrame will be discussed on in the team-specific sections
•
You can ignore Sequence Type, OpMode, Telemetry Mode, Power, Estimated CDS Words, Team
Consumables
There are no required fields in the “Support and Other Descriptive Information” or “SASF
Fields” areas. You may provide support information, if you so desire.
6
05/10/01
CIMS Fields
Adding APGEN Fields to a Request
•
From the “Request” --> “View” page, select the request which needs to appear on the APGEN timeline
•
Under the “Request Description” header you will find the “APGEN Fields (Beta Module)” area. Click
on “Add”.
•
You will be presented with a pulldown menu called “APGEN Activity Types”. Select the appropriate
APGEN activity type for your request. Each should see only activity types that apply to their own
instruments
–
•
The following pages provide details of which activity type each team should use
You will have presented with a number of fields to fill out for that particular activity type. Details of how
each team should fill out the fields is on the following pages.
–
Legend is the APGEN legend on which the activity will appear
–
Duration is defaulted to the duration specified in your request (No changes to the Duration should
be required if the Request Header is filled out properly)
–
Color and Pattern are the color and pattern for your APGEN activity
–
Description is defaulted to the description from the request (No changes to the Description should
be required if the Request Header is filled out properly)
–
Parameters depend on the specific activity type.
J. Gross
7
05/10/01
CIMS Fields
Adding APGEN Fields to a Request (cont.)
•
CAPS APGEN Activities
–
Activity Types: Either CAPS_2000 or CAPS_16000. The numbers indicate the bits-per-second at which APGEN will
model your data volume.
–
Parameters:
–
•
•
Rate Multiplier: If your actual data rate is less than the rate specified in the name of the activity type, use the
RateMultiplier. For example, if CAPS is collecting data at 500 bps, the RateMultiplier for a CAPS_2000 activity
should be 0.25; for a CAPS_16000, it would be 0.03125.
•
Ignore CDS Words and Power
Expected Requests With APGEN Fields:
•
One request that spans the entire sequence at the CAPS background data rate
•
Additional requests for special CAPS activities that require different data rates (I.e, Solar Wind experiments)
CDA APGEN Activities
–
–
–
J. Gross
Activity Types: CDA_524. This means that APGEN models CDA activities at 524 bits-per-second.
Parameters:
•
Rate Multiplier: If your actual data rate is less than the rate specified in the name of the activity type, use the
RateMultiplier. For example, if CDA is collecting data at 50 bps, the RateMultiplier for a CDA_524 activity should
be 0.09542 (= 50/524).
•
Ignore CDS Words and Power
Expected Requests With APGEN Fields:
•
One request that spans the entire sequence at the CDA background data rate
•
Additional requests for special CDA activities that require different data rates
8
05/10/01
CIMS Fields
Adding APGEN Fields to a Request (cont.)
•
CIRS APGEN Activities
–
Activity Types: CIRS_4000. This means that APGEN models CIRS activities at 4000 bits-per-second.
–
Parameters:
–
•
Rate Multiplier: If your actual data rate is less than the rate specified in the name of the activity type, use the
RateMultiplier. For example, if CIRS is collecting data at 2000 bps, the RateMultiplier for a CIRS_4000 activity
should be 0.5
•
Ignore CDS Words and Power
Expected Requests With APGEN Fields:
•
•
One request for each desired observation in the sequence.
INMS APGEN Activities
–
–
–
J. Gross
Activity Types: INMS_1498. This means that APGEN models INMS activities at 1498 bits-per-second.
Parameters:
•
Rate Multiplier: If your actual data rate is less than the rate specified in the name of the activity type, use the
RateMultiplier. For example, if INMS is collecting data at 50 bps, the RateMultiplier for a INMS_1498 activity
should be 0.033378 (= 50/1498).
•
Ignore CDS Words and Power
Expected Requests With APGEN Fields:
•
One request that spans the entire sequence at the INMS background data rate
•
Additional requests for special INMS activities that require different data rates
9
05/10/01
CIMS Fields
Adding APGEN Fields to a Request (cont.)
•
ISS APGEN Activities
–
Activity Types: There are *numerous* ISS activity types, which fall into two classes. One class is ISS_<rate>, and the
other class is ISS_<target>_”X”_by_”Y”. Examples: ISS_60928 and ISS_Phot_1_by_1. ISS should ONLY activities
of the type ISS_<target>_”X”_by_”Y”. It makes no difference which of those type activities are used.
–
–
Legend: Change to ISS.
Parameters:
•
NumberFrames: Regardless of actual number of frames, please specify 1.
•
BitsPerFrame: Regardless of actual bits-per-frame, please specify data volume for entire observation.
– Example: a 9-frame 100Mbit observation should be listed as 1 frame, 100000000 bits-per-frame. That makes
it easy for Science Planning to look at the parameters and see the total data volume requested, instead of
having to do the calculation of NumberFrames*BitsPerFrame
•
–
Expected Requests With APGEN Fields:
•
•
Ignore CDS Words and Power
One request for each desired observation in the sequence.
MAG APGEN Activities
–
–
–
J. Gross
Activity Types: MAG_1976. This means that APGEN models MAG activities at 1976 bits-per-second.
Parameters:
•
Rate Multiplier: If your actual data rate is less than the rate specified in the name of the activity type, use the
RateMultiplier. For example, if MAG is collecting data at 62 bps, the RateMultiplier for a MAG_1976 activity
should be 0.031377 (= 62/1976).
•
Ignore CDS Words and Power
Expected Requests With APGEN Fields:
•
One request that spans the entire sequence at the MAG background data rate
•
Additional requests for special MAG activities that require different data rates
10
05/10/01
CIMS Fields
Adding APGEN Fields to a Request (cont.)
•
MIMI APGEN Activities
–
Activity Types: MIMI_2000 or MIMI_8000. This means that APGEN models MIMI activities at 2000 or 8000 bits-persecond, respectively.
–
Parameters:
–
•
•
Rate Multiplier: If your actual data rate is less than the rate specified in the name of the activity type, use the
RateMultiplier. For example, if MIMI is collecting data at 200 bps, the RateMultiplier for a MAG_2000 activity
should be 0.1.
•
Ignore CDS Words and Power
Expected Requests With APGEN Fields:
•
One request that spans the entire sequence at the MIMI background data rate
•
Additional requests for special MIMI activities that require different data rates
RADAR APGEN Activities
–
–
–
Activity Types: RADAR_364800. This means that APGEN models RADAR activities at 364800 bits-per-second.
Parameters:
•
Rate Multiplier: If your actual data rate is less than the rate specified in the name of the activity type, use the
RateMultiplier. For example, if RADAR is collecting data at 1500 bps, the RateMultiplier for a RADAR_364800
activity should be 0.00411 (=1500/364800). If RADAR is collecting a total number of bits in the specified duration,
the RateMultiplier = Total bits / 364800 bits-per-second/duration.
•
Ignore CDS Words and Power
Expected Requests With APGEN Fields:
•
J. Gross
One request for each desired observation in the sequence.
11
05/10/01
CIMS Fields
Adding APGEN Fields to a Request (cont.)
•
RPWS APGEN Activities
–
Activity Types: RPWS_30464, RPWS_60928, RPWS_182784, or RPWS_365568.. This means that APGEN models
RPWS activities at 30464, 60928, 182784, or 365568 bits-per-second, respectively.
–
Parameters:
–
•
•
Rate Multiplier: If your actual data rate is less than the rate specified in the name of the activity type, use the
RateMultiplier. For example, if RPWS is collecting data at 200 bps, the RateMultiplier for a RPWS_30464 activity
should be 0.006565 (=200/30464).
•
Ignore CDS Words and Power
Expected Requests With APGEN Fields:
•
One request that spans the entire sequence at the RPWS background data rate
•
Additional requests for special RPWS activities that require different data rates, Exception: RPWS high-rate
activities which use up available downlink. Science Planning will be responsible for adding those activities into the
APGEN file when the time comes.
RSS APGEN Activities
–
–
Activity Types: RSS_Activity.
–
Expected Requests With APGEN Fields
Parameters: none
•
J. Gross
One for each desired observation in the sequence
12
05/10/01
CIMS Fields
Adding APGEN Fields to a Request (cont.)
•
UVIS APGEN Activities
–
Activity Types: UVIS_5032 or UVIS_32096. This means that APGEN models UVIS activities at 5032 or 32096 bitsper-second, respectively.
–
Parameters:
–
•
•
Rate Multiplier: If your actual data rate is less than the rate specified in the name of the activity type, use the
RateMultiplier. For example, if UVIS is collecting data at 74 bps, the RateMultiplier for a UVIS_5032 activity
should be 0.014706 (=74/5032). If UVIS is collecting a total number of bits in the specified duration, the
RateMultiplier = Total bits / 5032 or 32096 bits-per-second/duration.
•
Ignore CDS Words and Power
Expected Requests With APGEN Fields:
•
One request that spans the entire sequence at the UVIS background data rate
•
One additional request for each desired pointing observation in the sequence.
VIMS APGEN Activities
–
Data-rate Activity Types: VIMS_18432 or VIMS_94208. This means that APGEN models VIMS activities at 18432 or
94208 bits-per-second, respectively. Data-volume Activity Type: VIMS. This means that APGEN models VIMS
activities at a specified data-volume, regardless of duration.
–
Parameters:
–
•
Rate Multiplier (for VIMS_18432 and VIMS_94208 only): If your actual data rate is less than the rate specified in
the name of the activity type, use the RateMultiplier. For example, if VIMS is collecting data at 300 bps, the
RateMultiplier for a VIMS_18432 activity should be 0.016276 (=300/18432). If VIMS is collecting a total number
of bits in the specified duration, the RateMultiplier = Total bits / 18432 or 94208 bits-per-second/duration.
•
NumberFrames and BitsPerFrame (for VIMS only): Set NumberFrames = 1 and BitsPerFrame = total bits for
observation
•
Ignore CDS Words and Power
Expected Requests With APGEN Fields:
•
J. Gross
One request for each desired observation in the sequence.
13
05/10/01
CIMS Fields
Adding APGEN Fields to a Request (cont.)
•
•
ENGR APGEN Activities
–
Activity Types: MILESTONE.
–
–
Parameters: none
Expected Requests With APGEN Fields
•
One request for each engineering activity in the sequence. For example, if there are 5 RWA Unloads in the
sequence, there should be 5 engineering requests, each with a MILESTONE APGEN activity added to them.
•
If you do not know the exact time of the engineering activity, select a dummy start time, and indicate the actual
timing requirements in the description.
If any team is dissatisfied the choice of APGEN activity types available to them, please let Science
Planning know. It is possible to add new APGEN activity types via a Class D ECR. We are still working
out all of the details with ULO, but they are responsive to our need for having a very quick turnaround for
creating new activity types.
J. Gross
14
05/10/01
CIMS Fields
Verifying APGEN Fields
•
As a final step in adding APGEN fields to a request, each team is required to make sure that all of the
APGEN fields have been filled out properly. APGEN fields that are improperly filled out are not saved by
CIMS into the APGEN .apf files used by Science Planning. If your APGEN fields are not filled out
correctly, that activity will not make it into the sequence!
•
Select “Transfer” tab from main menu.
–
Select the appropriate period from the “Period” pulldown menu
–
Select “Just the selected teams” button from the “Make file for” menu
–
–
Highlight your team in the window with all of the team names
Push the “Prepare File for Export” button
•
It may take about a minute for the system to prepare the file.
•
After the file is prepared, you will see a report
–
Criteria lists the period and the team(s) for which the file was prepared
–
Status lists the following
–
•
•
Number of public requests for the team(s) in the selected period (remember, only public requests can be saved
into the APGEN file)
•
Number of public requests with APGEN fields added to them
•
Number of public requests with APGEN fields that have ERRORs
•
Number of public requests with APGEN fields that have no ERRORs and will be exported to the APGEN .apf file
For each request that has an ERROR in the APGEN fields, there will be a short description of the
problem, and a link to the offending request.
It is the responsibility of each team to make sure that their APGEN fields have been added
correctly
J. Gross
05/10/01
15