General idea is to use the (presently) unused timeline tag "tl.science_component.obs_id" as an indicator of which offsets to apply. Up until now this tag hasn't been used, so is zero for all TL entries. In the future, it will be possible to simply set this to a non-zero value when adding a new study to the TL. Get EIS/AIA offset using John Mariska's routine "eis_aia_offsets.pro" (see "notes/eis_iris/eis_aia_offsets.txt". This requires an input time. The hard-wired EIS/SOT offset (0,50) is NOT time-dependent. This offset was introduced shortly after launch, and has remained constant since then. So, somehow we have to transmit the time-dependent EIS/AIA offsets into the (lower-level) routine "eis_get_mirror_position". Q. How are we gonna do that? Eh? A. I dunno, mate. I'm off for coffee. See you later. A. OK, maybe need to transmit both the obs_id and EIS/AIS offsets. Perhaps as a structure {obs_id:obs_id,eis_aia:DOUBLE(2)} as an optional input. Alternatively, pass the obs_id and time; {obs_id:obs_id,time:0.D} and use JTM's routine later to retrieve the offsets. Hmmm, I think I prefer the latter. It's slightly simpler ;-) Or use bunnies? (\___/)(\___/)(\___/)(\___/)(\___/)(\___/)(\___/)(\___/)(\___/)(\___/) (=’.'=)(=’.'=)(=’.'=)(=’.'=)(=’.'=)(=’.'=)(=’.'=)(=’.'=)(=’.'=)(=’.'=) (“)_(“)(“)_(“)(“)_(“)(“)_(“)(“)_(“)(“)_(“)(“)_(“)(“)_(“)(“)_(“)(“)_(“) OK, obs_id and time it is! Inputs to "eis_get_mirror_position" are delx, dely, and ra_id. So we have required info available at this stage. ___________________________________________________________________________ Which routines/methods call "eis_pointing_offset"? eis_cpt_gui ::oplot_pointing Unused* eis_mk_plan_gui ::populate_point_stc Done ::oplot_pointing Done eis_get_mirror_position (delx,dely,ra_id) Done eis_get_xy_point (sc_x,sc_y,mip,yip,ra_id) Done eis_get_raster_pointing (start_time,stop_time, Unused* num_days=num_days) *NOTE*: the "eis_cpt_gui::oplot_pointing" method is actually unused. Also, the offsets are NOT applied in "eis_get_raster_pointing". So, no change required. ___________________________________________________________________________ Which routines/methods call "eis_get_mirror_position"? eis_structure_container ::initialise_raster_pointing Done ::update_raster_pointing Done ::offset_pointing_coords Done eis_mk_plan_gui ::pointing_inherit_all Done ::update_pointing Done ::update_x_point Done ::update_y_point (x2) Done eis_xrt_flare_gui ::get_new_mip_and_yip Done ___________________________________________________________________________ Which routines/methods call "eis_get_xy_point"? eis_structure_container ::relative_raster_pointing Done ::offset_pointing_mechan Done eis_mk_plan_gui ::pointing_inherit_all Done ::get_new_response_structure Done ::update_mip Done ::update_yip Done eis_xrt_flare_gui ::get_new_solar_coords Done ___________________________________________________________________________ Which routines/methods call "eis_get_raster_pointing"? This routine looks for appropriate J-Side pointing files and returns the contents. eis_structure_container ::relative_raster_pointing Unchanged ::initialise_raster_pointing Unchanged eis_timeline_plot_gui ::get_pointing Unchanged *NOTE*: the "eis_pointing_offset" call here is unnecessary!!!! The returned offsets aren't applied here. So no changes are required. ___________________________________________________________________________ ; +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ ; JAR 1-Apr-2014. Add "obs_id" and "aia_time" inputs to routine ; "eis_pointing_offset" obs_id = s.science_component.obs_id aia_time = sra.ra_start_time ; +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Notes: 1. "eis_mk_plan_gui::pointing_inherit_all" calls both routines "eis_get_mirror_position" and "eis_get_xy_point". This is to do with the optional button on the Pointing GUI, present for multi-raster studies.