Events are the heart of Sequence Generator Pro. They define what type of frames you are after and many other attributes to fit your needs (explained below).
Common Event Attributes
Adding a New Event
Event Icons and Actions
Tip: Double-clicking an event header will copy the value of event 1 into all of the other events.
Copying Event Data
Using the context menu above, you can perform a variety of event copy operations:
Every event has a set of associated options that can modify sequence behavior both before and after the event is started or completed.
Park Telescope: If this option is checked, the telescope will be parked when the event starts (pre) or ends (post).
Pause Sequence: If this option is checked, the sequence will be paused when the event starts (pre) or ends (post). When paused, a dialog containing the "Message" text will be displayed.
Run Script: This will allow you to run a user created VBS or EXE script when the event starts (pre) or ends (post). Keep in mind that the sequence will not continue until the script complete. SGPro uses the Windows "cscript" VB engine. This means that you cannot use wscript interface elements (i.e. windows and dialogs). Everything in your script must be designed to run on the command line. Please see Windows cscript documentation here. If your script hangs or never completes (closes), the sequence will hang with it...
Reset Event: This will reset the progress of the event (not its options or settings)
This section is used to convey critical information about the capture of frames in this sequence. The example above shows a "lit" exclamation point indicating there is at least one event notification. Clicking the exclamation icon open the event display window. This example shows that there was an frame restart at 22:29 due to a guiding error. Other general notifications may appear here as well.
Adjusting Capture History
It's unavoidable that you will capture some bad frames from time to time. In these cases, you may wish that the captured fraction no longer reflect the bad capture. This will help you to understand how much "good" data you have captured. To do this manually, simply double click the "fraction" or "progress bar" for the event you wish to alter:
From here, you can alter the number of frames you have actually captured for this event.
Light events are used to capture normal data representing your actual target.
Dark events are used to capture dark calibration frames. They don't require use of a filter, but need to be taken in an environment that does not allow light to hit the CCD (if you have light leaks, you can use foil to wrap around the nose). Furthermore, most dark frames are taken at the same exposure length and temperature as the corresponding light frames (some image processing applications can scale darks to any exposure length). It is acceptable to take these frames and build a library (such that you don't need to take them every imaging session.
Bias events are used to capture bias calibration frames. They don't require use of a filter, but need to be taken in an environment that does not allow light to hit the CCD (if you have light leaks, you can use foil to wrap around the nose). Furthermore, most bias frames are taken with the minimum allowable exposure time (set exposure time at 0). Some cameras (like the QHY8L) will require longer bias frame times. It is acceptable to take these frames and build a library (such that you don't need to take them every imaging session.
Flat events are used to capture flat calibration frames. These frames should be taken during every imaging session because they depend on the alignment of the entire imaging train. Flat frames normally target a mean ADU of 22,000 to 25,000, but this will depend on camera and user preference. If your flats data is defined (per filter), selecting a flats event will automatically populate the saved exposure time (for the selected binning).