+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
XRT Flare Trigger Notes
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

This file outlines the notes for the XRTF trigger work. These are for my
own benefit. ;-)

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
xrtf_mechanism.txt: General description of initialisation and use.

General description of how the basic method works. This is how a timeline
study is enabled as a trigger study and the process of creating a
corresponding response DB entry. Also, how the TL and response DB entries
are related. Further discussion of the processes involved when moving and
copying XRTF trigger studies are described below. This also includes
changing the hunter study pointing after the response has been created

Status: Finished

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
xrtf_moving.txt: Moving the Hunter Study (single entry)

Description of process when a hunter study is moved on the timeline (the
new pointing for this study is re-calculated according to the new time).
However, the response (DB entry) study pointing needs to be updated as well. 
In effect, this is achieved by re-inheriting the new hunter study pointing.
Essentially, mip and yip are retained.

Status: finished for case where "Verify FOV" is enabled.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
xrtf_copying.txt: Copying (and pasting) an XRTF trigger study

When an existing XRTF trigger study is copied and pasted to a new time,
the pointing must be re-calculated. This is already in operation for the
hunter study. However, a new response entry must be initialised whose
pointing is inherited from the hunter study.

Status: Finished

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
xrtf_repointing.txt: Repointing the hunter study after it is created
                    
Status: 





The routine "eis_xrt_flare_props_same.pro" checks that all XRTF tables are
the same. It compares;
+ response_st_id		Response Study ID
+ filler_st_id			Filler Study ID
+ adjust_x			
+ adjust_y
+ raster_identifier		Repoint Raster Index
+ locate_x				X0
+ locate_y				Y0
+ ra1_mip				mip
+ ra1_yip				yip

This table is uploaded to the s/c.