CIMS UPDATE AND FAQ's
30 July 2001
The CIMS due date is rapidly approaching. This memo collects all the new instructions I
have received from Brian in the last two weeks and forwards them to you, in case you are
not on his distribution list. In addition, I am answering the 'frequently asked questions' I
have received from team members. If you do not have time to incorporate this new
information, please follow the May memo from me (available on the UVIS webpage:
click on 'observation planning' section, then on 'planning tools'). Alain and I will be
meeting on Thursday morning to check and promote all the UVIS CIMS requests.
UPDATES
Instrument setup. For this information, please use the 'Team Internal' field from now on,
not "Notes'. Use the syntax in the May instructions.
Titan inputs. After T3: Titan requests outside +/1 one day. T11-T22: Titan requests
outside +/- 30 minutes are due 31 August. T3, T5, T6: Titan observations inside +/- 1
day.
CIMS APGEN legends. Select from one of the following UVIS_Atmospheres,
UVIS_Surfaces, UVIS_Rings, or UVIS (for all others). Please spell these exactly as
indicated.
Priority—please color code your requests as described. I quote Brian below.
Hi All,
A meeting was held during the PSG week in Oxford to discuss the standardization of the
APGEN-related fields in CIMS for the Tour requests. The reason for this was to provide
a consistent APGEN display for all TWT allocated segments in the Tour. The convention
attempts to convey additional information about priority and nature of the request using
both the APGEN pattern and color. Please use the following convention when inputting
your Tour CIMS requests:
Priority 1 Requests*:
APGEN Pattern in CIMS=íSolid Colorí
APGEN Color in CIMS=íHot Pinkí
Priority 2 Requests*:
APGEN Pattern in CIMS=íSolid Colorí
APGEN Color in CIMS=íDodger Blueí
Priority 3 Requests*:
APGEN Pattern in CIMS=íSolid Colorí
APGEN Color in CIMS=íPlumí
Requests where you need only M of N:
APGEN Pattern in CIMS=íFull Color Wide Right Diagsí
APGEN Color in CIMS=use the appropriate Priority color from above
Alternate or Backup Requests:
APGEN Pattern in CIMS=íFull Color Wide Left Diagsí
APGEN Color in CIMS=use the appropriate Priority color from above
(*Note: in the CIMS v1.2 release that occurred on July 7-8, the CIMS priorities were
'Must have', 'Should have', and 'Nice to have'. This was changed to priority 1, 2, and 3 as
of today. For those planning to use XML, please update your priority use to 1,2 and 3.)
Once the TWTs integrate the request into the plan the APGEN Color will be changed to
'Green'. In addition, requests that are pending deletion will have the CIMS-APGEN
pattern of 'Wide Diagonal Cross-Hatch'.
To change the Pattern and Color fields in a CIMS request click the ëEdití link in the
ëAPGEN Fields (Beta Mode)ë box in the Request.
Team Leaders and PIs please foreword this e-mail to anyone on you Team that's making
Tour CIMS inputs that I don't have on my distribution list.
Brian
Brian has also supplied two corrections to this memo, as follows:
Hi All,
One more CIMS-APGEN convention item. In order to reduce the clutter on the APGEN
displays, the ORS Teams should use different Legend names depending on which
discipline the request is associated with. This is how the APGEN displays were
configured during Jupiter.
The ORS instruments (CIRS, ISS, VIMS, UVIS) should use the following convention for
the APGEN Legends field in CIMS: InstrumentName_Atmospheres, or
InstrumentName_Surfaces, or InstrumentName_Rings.
For example, CIRS_Atmospheres, CIRS_Surfaces, or CIRS_Rings.
It is important that you spell these exactly as indicated (capitalization and all) otherwise
additional new legends will be created when we import this into APGEN. This will cause
significant grief later on.
UVIS should use the Legend='UVIS' for magnetosphere-related observations.
Brian
And:
Hi All,
Based on a few recommendations to minimize the possible confusion between the
patterns for the observations in the two categories below please use the CIMS pattern
called ' Large Pinwheels' for the 'M of N' requests. I realize this change is rather late
with respect to the July 31st delivery, but please try your best to accommodate this
change.
Brian
FREQUENTLY ASKED QUESTIONS
1. What fields may we leave blank?
According to the science guidelines, you can ignore the following fields:
Sequence type, Opmode, Telemetry Mode, Power, Estimated CDS Words and
Team Consumables.
Alain
2. Is the rate multiplier called for in several locations the same?
Yes, use the same value everywhere. See my May memo for how to use Alain's
rate computation spreadsheet.
3. Larry, can you tell us if we are now required to use the color coding in CIMS
entry as outlined in Brian P's memo?
Yes, if your DWG has assigned a priority. See above.
4. Also, there is a new Team Internal field for observations which might be a better
place to put the instrument setup rather than Notes. Should we move instrument
setup information there?
Yes, for future inputs. Alain will move your setup info that is now in your
existing requests.
5. When we select the APGEN type (5032 or 32096), is there some reason we
choose one over the other? Are these related to data rates in such a way that if the
data rate is greater than 5032 we must use 32096, or does the existence of the
"multiplier" mean that it doesn't matter?
This is important if we are in a telemetry mode where UVIS packet pick-up rate is
lower, but APGEN doesn't care. I use 32096 for occultations and 5032 for
spectroscopy.
6. Also, after we've checked a request, should we click on "Export File" or is that
something Alain will do later?
Alain will do it later.