+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
XRTF Trigger scheme - Moving the Hunter Study on the timeline
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

When moving an XRTF trigger study (which must already have been saved in
order to generate a non-zero seq_id) the response entry has already been
created and saved, also. When created, the response DB entry inherits the
hunter study pointing info (x/ycen, sc_x/y and mip and yip). So, when the
hunter study is moved to a different time (its new pointing has already
been calculated), the response DB entry pointing must also be updated.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
1 "Verify in EIS FOV" is enabled (the default case).

In this case we need to update the response pointing: solar coords
and s/c pointing of hunter. The mip and yip will be unchanged. This is 
done in;
   eis_mk_plan_gui::move_study_to_cp
   eis_structure_container::relative_raster_pointing

Essentially, the response DB entry re-inherits the hunter pointing info.
It is crucial that the mip and yip values are retained.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
2 "Verify in EIS FOV" is disabled (EIT Wave).

Not implemented yet!


+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Test Case

Hunter Study (study_id = 1):
time	= 09:00 10-Oct-2013
seq_id  = 36774
x/y		= 440.29,54.83
sc_x/y	= 440.29,54.83
mip/yip	= 1040,306

Response Study (study_id = 2):
resp_id = 365
x/y		= 440.29,54.83
sc_x/y	= 440.29,54.83
mip/yip	= 1200,306
(mip/yip checked by inserting this study on the TL)

Move to 16:00 10-Oct-2013

Hunter Study (study_id = 1):
time	= 16:00 10-Oct-2013
seq_id  = 36774
x/y		= -15.18,-939.96
sc_x/y	= -15.18,-939.96
mip/yip	= 1040,306

Response Study (study_id = 2):
resp_id = 365
x/y		= -15.18,-939.96
sc_x/y	= -15.18,-939.96
mip/yip	= 1200,306

Notes:

N1. In this case the big difference in pointing before and after the move
    was because of moving from one tracking curve to another.

Q1. Summary tool needed had to be updated manually? Why didn't it update
    automatically? Also, seen when moving a non-trigger study.
A1. Call "Self.eis_timeline_container->reorganise_container" inside method
    "eis_mk_plan_gui::move_study_to_cp" to make sure it does. Lovely!