• EVENTS Widget

The EVENTS widget allows the user to run EVENTS (which must be installed on the computer), or to load a previously saved EVENTS output file.  The details of events are displayed in the center of the widget under the heading "Event Times."  An event may be selected (by clicking with the mouse) from the list of Event Times and its details are copied into the Data Entry panel of the Session Data Entry Widget.

• Information Area

1. Events File: Name of the currently loaded file
2. Events Version: Version number of Events that produced the file
3. Spacecraft: Spacecraft that the Events file was generated for
4. Central Body: Central body that was used by Events
5. Time Format: The type of time that Events was asked to produce. NOTE: For CASPER use, this should be UTC.
6. Tour Kernel: Name of the tour kernel that was used by Events. NOTE: Although Events can produce listings for a number of tours per file, at present CASPER just read the FIRST tour listing in a file, as CASPER can only utilize one tour at a time.
• Filters
1. Event Type Filter: Filter the events list by selecting the name of the type of event that you're interested in.
2. Target Filter: Filter the events list by selecting the name of the target body that you're interested in.

• Control Buttons

1. Run Events: This creates the Run Events window that allows the user to run the Events program and generate their own list of events for the loaded tour.
2. Load: This allows the user to select and load the output from a previous Events run. This will usually be the case for an Events run that calculated a large number of different event types, or calculated CPU intensive event types such as stellar occultations, that would be too time consuming to run within a CASPER session.
3. CEF Load: Loads a previously saved CASPER-decoded Events list.
4. CEF Save: When reading a standard Events output file, CASPER decodes the information into a form it can use internally. This option allows the user to save a decoded version of the Events file that will be faster to load next time. This is useful for large Events files. These files have the extension CEF (for CASPER EVENTS FILE)
5. Cancel: Closes this window.

 
•  Run Events Widget

This window allows the user to setup and run the Events program, with the resultant output being automatically read into the Events window ready for use (see above).

• Output File: The name of the file that will be produced. If you are just making a temporary listing, then this does not need to be changed as CASPER will just create a temporary file. However, if you are running Events to produce an output file for later use, then you can use the Select button to select a new output file for the Events results.
• Central Body: Select the central body to use for this Events run. For Cassini, this will nearly always be the default Saturn.
• Spacecraft: Specify the spacecraft to use. This will always be the default Cassini for CASPER, but to generalize the Events interface for use by other tools, additional options are available.
• Start UTC: Enter the start time of the time range that should be examined by Events in standard UTC format. The Ephemeris Start button when selected will override the Start UTC options by forcing Events to use the Start of the tour file. It also makes the text widget inactive to indicate this.
• End UTC: As Start UTC above, but specifies the end time of the time range to search.
• Maximum CPU Time: The maximum amount of CPU time that Events will spend looking for the selected event type within the tour.
• Event Type:Select the type of event to search for. The type of event chosen will affect what is displayed in the target and subtype droplists.
• Target: Select the Target to be used by the event if one is required.
• Subtype: Select the subtype for the event if one is required.
• Event Buffer List: Displays the current list of events that you wish to use for Events. NOTE: If no events are in this list, then running Events will use the event information displayed on the droplist widgets instead. This is a quick shortcut for running on just one event type.
• Run: Run Events on the current events buffer list (or on the displayed droplist event if no list is available). CASPER waits until the Events run has finished and then displays the results in the Events widget. The Run Events widget is closed.
• Run/Nowait: Some events require considerable computing time. This function will set Events running like Run but CASPER will not wait for or display the results, although you can load them manually once Events has finished. NOTE: You can cause problems if you try and run two Events sessions at the same time as the data files used will be overwritten by the second session.
• Cancel: Closes the window without running Events
• Status : Displays information messages

Not all Events types are supported by the CASPER interface. However, any Events output file can be read by CASPER.