GUI Buttons

This file gives a brief description of all the buttons found on the ISAP GUI. The descriptions are grouped roughly in the same order as the layout of the GUI. The buttons are grouped in different categories according to their functions. The button names terminating with .. indicate that the button is a pull down menu.

For an alphabetical listing of GUI Buttons Click Here


These buttons are located at the right hand top of ISAP window.


These buttons reads AAR FITS file and displays information on AAR for user selection (part or all of data).  They are located in the upper half of ISAP window.


These buttons are hard coded  widgets and contain the basic information on AAR once it is read.They are located at the top of ISAP window and are not user controlled.
  • AOT
  • OBJ

     These buttons are used  to plot  and  study  the data.


    This allows you to alter the primary data  set by doing various operations given below.

    For Bad Data see SWS/LWS BAD DATA


     If you select either a portion or all of the plotted data by click-and-drag using the right mouse button the applications widget will pop-up. You will have a choice of following options which you can apply to the selected data. Caution.


    This allows you to alter /store the output data  set  from your application by doing various operations given below.


    The name of your working AAR. The text widget is editable so you can type in a new name.
    The AOT type e.g. L02 is an LWS line mode observation.
    The astronomical name of the source.
    The name of your reference data set (see MAKE REFERENCE )
    This is a pop-up text widget listing what is new in ISAP.
    This is a pull-down menu with 2 options
    Points you to these WWW help pages
    Mail us your comments and suggestions
    Register user's addresses and emails so that they can receive future ISAP software releases, news, and bug reports.
    This allows two plots to be overplotted and compared. The plots may be placed on the same scale based on user input or by auto-scaling to each other.
    Displays the FITS header in a pop-up window. When you have finished reading click on the QUIT button at the top of the display window.
    Displays the history associated with the AAR in a pop-up widget. To continue processing your AAR in the GUI you must exit this widget by clicking on the CANCEL button. Note that very few Version 1 ISAP routines update the history file!
    This is an EXTREMELY IMPORTANT button. It can be found on the sub-menu from Special Functions labeled `STORE PRIME' as well as at the top of the GUI labeled `STORE'. The GUI does not automatically save your working data set i.e. your PRIME AAR. If you reach a stage where you wish to export the data or try two different approaches to the analysis then you should STORE the PRIME AAR.
    This is a pull down menu that allows you to store your reference data set under the STORED DATA SETS... or display your reference data in a pop-up widget for inspection. See MAKE REFERENCE for more information.

    The GUI interrogates the AAR to find out which TAGS are present. If the GUI finds the SCAN, DET, LINE or SDIR tags it will make a button for each unique value of those tags. In addition if it is an SWS AAR it will make a BAND tag based on the DET tag.

    If none of these tags are present in your AAR no buttons are made, you can simply click on plot and all of your data will be plotted.

    If only a single unique value is found for a given tag then the default is that a single button is created and it is automatically switched on. Users should be aware that this means that if only one BAND is present in an SWS data set that the band button will automatically switch on all 12 detectors - you may want to switch the band button off!

    If some or all of the above TAGs are present you have to switch-on some or ALL of the buttons in each category. For example you could select SCAN 0, ALL DETRS, LINE 1, SCAN DIRECTION ALL and then click on PLOT. The ALL button toggles all the buttons on' in a given category. If you click on the ALL button a second time it will switch all the buttons off' in that category. For full details of the data TAGS and the corresponding fields in the FITS files see SWS and LWS AAR .

    Data Selection Categories:

    For LWS each scan of the grating either forwards or backwards is given a unique scan number. For SWS01?? a scan number is assigned to each pair of forward/backwards scans. For SWS02 ?? and SWS06 up and down scans are distinct and given a separate scan number. For SWS07 there are only up scans.
    The GUI makes a button for each detector present in the AAR e.g. detectors 0:9 correspond to detectors SW1,SW2,SW3,SW4,SW5,LW1,LW2,LW3,LW4,LW5 for a LWS AAR and detectors 1-52 for a SWS AAR.
    The line tag is used for LWS AOT's L02 and L04. Each LINE TAG corresponds to an observation of a single line. A LWS AAR can contain up to 10 lines, numbered 0:9. For SWS S01 observations processed with pipeline version 6 or later the line tag corresponds to an AOT band. Due to a known bug in version 6 it is still recommended to use CONVERT LINE. For SWS02/06/07 the line tag corresponds to scans of the same wavelength regions (i.e. lines).
       The grating can be scanned in either the forward/up or back/down direction. Foward/up  corresponds to increasing mechanism position and decreasing wavelength. Due to memory effects  the shape of continuum and line profiles may be dependent on scan direction and you may wish to select the data based on scan direction.
    SWS data can be selected on the ISAP GUI according to groups of detectors known as bands. Note this is groups of detectors not an AOT band. If you have read in an SWS AOT1 observation you can use the convert line -> AOT band(SWS AOT 1) option.
    This is a  pop up window which allows to include bad data in the AAR . By default  the bad data is ignored while reading  the  FITS file. The option to include data which are out of the nominal detector band limits is available for LWS. The default is to not include this data.
    This is a pull down menu with two options to load data files into the GUI. The data file is read from disk into an IDL structure called an AAR.The data file that is selected is AUTOMATICALLY made PRIME which means that you must explicitly STORE your PRIME AAR before loading a new data file. When multiple data sets are loaded from either a Raster or PHOT-S observation no data set is made prime. A single data set can be selected from the stored data sets menu.When an SWS07 observation is loaded, which has a merged SWS06 part, this SWS06 part is stored as a separate spectrum under stored data sets. The SWS07 part is made prime automatically.

    The pull-down menu for loading data has four options:

  • FITS    This option will read the auto analysis products generated by the LWS, SWS( and PHOT-S pipelines. LSAN.FITS, LSNR.FITS, SWAA.FITS and SWSP.FITS ,  RSRF  for LWS  (from  .../data/cal_lws/aal/lcgr.fits) , RSRF for SWS  (from  .../data/cal_sws/cal25).  Click on the FITS button and yet another pop-up window will appear This is an IDL widget called PICKFILE and it allows you to select your FITS data file. Select a FITS file by highlighting the file name with a click from the mouse then click on the button marked OK. The data set will be loaded into the GUI and made PRIME . If the data set is an LWS RASTER or a PHOT-S observation an additional pop-up menu will appear allowing you to chose either all the data sets or a sub-set or just one position. Each data set is loaded as a separate AAR and stored under STORED DATA SETS . As more than one AAR has been created you will need to select an AAR from the DATA SETs and make it prime.
  • SAP-XDR The same procedure above can be used to load an ISAP-XDR save set. ISAP can only restore data sets saved in a specific structure called memstor. memstor={data_flag:data_flag,aar:aar,name:name} where DATA_FLAG INT 1 AAR STRUCT ->  Array(1) i.e. your AAR in standard ISAP IDL format. NAME STRING 'AAA' name of the data set
  • ASCII This option will read in data given as an ascii file with at least two but no more than fifteen columns. The ascii files are converted to YAAAR structures upon readin. Columns must be separated by one or more blanks. There are three types of ASCII files that ISAP can read. For examples and a more detailed explanation of these, click on ASCII READ.
  • SURVEY PRODUCT This option will read in the Survey Products which are ASCII FITS files that were generated by the ISO Browse software in the ISO Archive.

    The Data Sets button has a "pull down menu" listing all the AARs that you have stored in the GUI. Each AAR has a "pull down menu" with 12 options
    MAKE PRIME - make this data your new working data set.
    DELETE - delete this data set i.e. free up some memory in IDL.
    Write is a "pull-down menu" with 3 options
               Writes a standard FITS file.
  • All - writes the header and then all the data tags in multi-column format
  • Minimum - writes the header and then the wave flux stdev and flag tags in multi-column format
    Writes out a structure containing the AAR (your data) as an IDL save set.
    This will merge the AAR with the PRIME AAR. The header is taken from the PRIME AAR. In order to merge an SWS AAR with an LWS AAR you should change the flux units.
    Makes the whole AAR the REFERENCE AAR, see MAKE REFERENCE.
    Pop-up widget that allows the user to change the units of wavelength and flux. Please see CHANGE UNITS under Special Functions.
    Allows you to change the name of the AAR. A pop-up editable text widget will appear. If you do not want to change the name click on cancel, otherwise enter a new title and click on OK.
    Displays the AAR header in a pop-up widget. To continue processing your AAR in the GUI you must exit this widget by clicking on the CANCEL button.
    Give information on the AAR structure e.g. wavelength ranges detectors present etc..
    Plots the AAR in a separate pop-up widget. You do not have to cancel this pop-up widget in order to continue processing your PRIME AAR.
    Displays the history associated with the AAR in a pop-up widget. To continue processing your AAR in the GUI you must exit this widget by clicking on the CANCEL button. Note that very few Version 1 ISAP routines update the history file!

    This group of buttons enables you to freeze the x- and y- ranges. Upon zooming the new ranges of the data are displayed in the limits windows (Xmin, Xmax, Ymin, Ymax), these ranges can be edited. To freeze/unfreeze the ranges simply click on/off the freeze ranges button.
    If you have zoomed in on the data using the left mouse button this button will re-size your plot to the original limits (or frozen limits - see below).
    If you zoom in on your data a -> b -> c, this button will resize the plot to scale b.
    Plots your data in exactly the plot range of the previous plot. For instance, if you zoom in on the data in the "before" window of average, and then click on "copied range" in the "after" window the averaged data in this "after" window will be plotted in exactly the same range as in the "before" window.
    A Pop-up widget gives you the option of writing either a color or black and white postscript file to disk. The default is black and white (B/W). The filename can be edited, the default is "". The title for a hardcopy plot can be edited. The default is the object name. Click on OK to make the postscript file or click on CANCEL to quit without generating a postscript file.
    Plots your data based on your selection of the data tag buttons using your chosen plotstyle .
    This allows you to change the plot style. It is a pop-up menu with 6 options. You need to make a selection from each.
    This is a pull down menu with 16 options that operate on the WHOLE PRIME AAR
    Logical combinations can be chosen from

                             Wavelength: m, cm,microns (um), Angstrom (A), Hz, cm^-1
                              Flux: Jy, MJy, W/cm^2/um, W/m^2/um, erg/s/cm^2/um, erg/s/m^2/um
    This widget will allow you to add a new data tag (DET, RPID, SCNT) and assign a value to that tag for a given YAAAR. This routine is useful if a data tag such as raster position ID has been lost after AVERAGE. In this case, you can add the RPID tag to data from each raster position, making each raster position an independent YAAAR. Then use MERGE to combine the AARs. Now the individual raster positions are combined into one AAR, and you may take a global AVERAGE across all raster positions.
    This widget will allow you to increment or decrement the value of one of the tags for your entire prime dataset.  The routine will  show you what tags are present,   the range of values for those tags that are present and will allow you to enter a negative or positive integer  to increment the selected tag values.  One use of this routine is to allow AVERAGE  to effectively average across  different lines in an AAR. This may be done as follows: Break the AAR into one AAR for each line.  Use INCREMENT DATA TAG to change the line tags in each AAR to a common value, then use  MERGE  to combine the AARs. The lines now all have the same tag number and AVERAGE will average across them.
    Fix SWS07:
    For SWS07 only. Sets scan directions that have been misidentified as -1 by the pipeline to +1
    Displays the AAR in a separate widget. You must click on the QUIT button to dismiss this window.
    Deletes data based on the LWS STATUS word. This button will be unavailable (i.e. grayed out) if your PRIME AAR is not LWS data.
    Deletes data based on the SWS FLAG word. This button will be unavailable (i.e. grayed out) if your PRIME AAR is not SWS data.
    Deletes data based on the SWS FLAG word flagged as NODATA only. This button will be unavailable (i.e. grayed out) if your PRIME AAR is not SWS data.
    Deletes data based on the SWS FLAG word flagged as GLITCHED only. This button will be unavailable (i.e. grayed out) if your PRIME AAR is not SWS data.
    Deletes data based on the SWS FLAG word flagged as partially OUT OF LIMIT only. This button will be unavailable (i.e. grayed out) if your PRIME AAR is not SWS data.
    Deletes data based on the SWS FLAG word flagged as totally OUT OF LIMIT only. This button will be unavailable (i.e. grayed out) if your PRIME AAR is not SWS data.
    A simple pop-up widget lists the active detectors and corresponding line numbers for a L02 or L04 observation i.e. where to look   your  expected lines.
     Each spectral point in the spectrum gets divided by the LWS beam solid angle; the final units will then be flux/sr. The beam solid angle adopted is the size of the equivalent cylinder which contains the observed flux; radii (one per detector) of this cylinder are read from the calibration file fl2bright.dat in the directory data/cal_lws in your ISAP distribution tree. The LWS beam sizes are still tentative; investigations are still under way and these numbers could change.
       This button changes the flux units in a LWS Fabrey Perot AAR from w/cm^2  to w/cm^2/um  by dividing the flux by wavelength.
    This button applies a gain correction which takes into account the fact that the absolute, as well as relative, calibration of the LWS was derived using a point-source; in essence, it makes the LWS calibration valid for extended sources also. It is then clear that this button should not be used if the spectrum is from a point source. The correction factor applied to each spectral point is obtained by linear interpolation from a set of factors derived from optical modelling of the LWS instrument; these numbers are contained in the calibration file ps2escorr.dat in the directory data/cal_lws in your ISAP distribution tree. The LWS extended source correction factors are still tentative; investigations are still under way and these numbers could change.
    Author: Chris Lloyd, RAL. (Algorithm is based upon one developed for the detection of periods in spectroscopic binaries.)

    Introduction - Origin of the LWS Fringes:
    Sinusoidal fringes are observed in the LWS spectra of extended sources and off-axis point sources. They arise due to the interference between two beams propagating in the instrument with a time delay between them. The two beams arise from the normal reflection from the field mirror M2 and from the substrate holding M2 which is ~1.45mm behind the front surface of M2.

    Providing the algorithm with data: The algorithm is invoked on the AOT using the "Special Functions" button.
    LWS01 data must be presented to this algorithm. Furthermore, it must have its scans averaged, but the detectors must
    still be present. Finally, this data does not take advantage (which is to say it does not ignore) ISAP "masked data." Therefore the user should eliminate (zap) "masked" data from an AOT spectrum before going to defringe. (Change plot style to see masked data.) An important caveat: the defringe algorithm has it own internal data masking capability. Using the right button within the routine, one can mask data inside the routine. For example, if one has a strong CII 158 micron line in detector 8, one does not wish this data to be included in the fit to the fringe, so one masks this data out with the right mouse
    button before pressing the defringe button.

    Also note: the action of defringing is hardly noticeable in general on the short wavelength LWS detectors: detectors 0-4, because the constant fringe waveform (constant in wavenumber) has a high frequency, is undersampled and nearly impossible to remove. Its removal possible and evident in the log wavelength detectors, detectors 5-9.

    The algorithm:
     The routine solves for the period, phase and wavenumber dependent amplitude of a sine wave fitted to the data from a single detector.   Select a detector, remove any lines or spikes using the right mouse button. Identify your source as either a point source or an extended source. An extended source is defined to be of diameter > 20 arcsecs. Defringe the data. Repeat these steps for each detector.

    The algorithm handles the two cases, extended and point source like this:

    Extended source [and Off-axis point source] case:
    The algorithm assumes that the fringing is due to an extended continuum and line source in the beam (or alternatively an off-axis point source with no significant extended continuum) The algorithms divides out the fringe:

    Spectrum_new = Spectrum+old * (FITTED CONTINUUM)/(FITTED CONTINUUM + FRINGE)
    (The second term here is called FR2.)

    [Centered] Point source Case; The algorithm assumes you have a point source emitting spectral line embedded in an extended  continuum region  (where the extended continuum is causing the fringes). In this case the algorithm subtracts the fringe..

    Spectrum_new = Spectrum - FRINGE
    (The second term here is called FR1.)
    Note:  As yet, no algorithm has been developed for a source with properties in between these states!
    When you exit the routine, i.e. save the defringed data, the routine will return with 3 data sets. The prime data set will be your defringed data (aar). Two other `aars' will be stored under `DATASETS', the fringe (FR1) and the normalized fringe (FR2). This means you can examine the fringes and see what the difference is between assuming your object is a point source/extended i.e. set up  either  FR1 or FR2 as the reference data set and then use ARITHM2(REF) to correct your original data.
    Defringe (SWS ALGORITHM)
    see Defringe SWS
    This routine was written to enable you to easily select the various AOT bands in an SWS AOT1. The line tag is mapped to reflect the AOT band where
    BAND LINE tag
    1A  911
    1B  912
    1D  914
    1E  915
    2A  921
    2B  922
    2C  923
    3A  931
    3C  933
    3D  934
    3E  935
    5A  951
    5B  952
    5C  953
    5D  954
    N.B. Pipeline 6 AARs (SWS01) the line tag does correspond to a single aot band (continuous counting from 1 to 16), which is, however not yet reliable. Pipeline 7 will have the remaining bugs removed, and the conversion in ISAP will not be necessary for those AARs.
    This is an EXTREMELY IMPORTANT button. It can be found on the sub-menuf rom Special Functions labeled `STORE PRIME' as well  as at the top of theGUI  labeled `STORE'. The GUI does not automatically save your working dataset i.e. your PRIME AAR. If you reach a stage where you wish to export the data or try two different approaches to the analysis then you shouldSTORE the PRIME AAR
    The undo button can be found on the sub-menu from Special Functions as well as at the top of the GUI. It will undo the last operation you made on your PRIME AAR. It will only undo 1 previous operation. For example if you have done 3 operations i.e. data set A-> B-> C if you click on undo you will get data set B if you click on undo again you will re-create data set C, click again and you get data set B etc.


    The overplot bad data button can be found under the Special Functions submenu. It will overplot LWS or SWS data that has been flagged as bad by the pipeline. The bad data are plotted as 'X'.
    The split apart aar button can be found under the Special Functions submenu. It is a popup which will ask how the user wishes to split an AAR. After splitting an AAR by the tags the user selects, these individual datasets are then stored under Stored Datasets from which they can now select.
    This button allows user to combine data  for common tags in a  group of AARS  selected from stored data sets.  The header of the output combined AAR  is copied from the header of the  first  AAR in the group.
    This ends your GUI Session - YOU MUST SAVE YOUR DATA BEFORE QUITTING! For example, if you wish to save your PRIMEAAR, you must first STORE  it then WRITE  it either as an IDL saveset, a FITS file or in ASCII format If you do not want to exit, click the mouse button outside of the GUI window to cancel the selection.

    With the exception of CANCEL and MAKE-AAR the new data returned from your selected application will be merged with the remaining portion of your PRIME AAR. This may result in the loss of some data tags e.g. in average you will lose most of the tags. The averaged/merged data will have the WAVE, FLUX, STDEV, DET and FLAG tags (if you average across the detectors the DET tag will also be lost). If you select the whole AAR (i.e. plot the whole AAR and draw a box that encompasses all the data points) the new data returned after the application will be the new PRIME AAR. 
    Please see GUI Photometry
    This can speed up the operations as it reduces the size of your working data set. The new (sub) PRIME AAR can be STORED and Written to disk. If you STORE it to the DATA-SETs menu you have the option of merging it with another portion/different AAR.   See MERGE WITH PRIMARY .
    A copy of the selected data becomes the REFERENCE AAR. Any AAR can be made reference. When you make an AAR the reference it replaces any previous reference data set. You should store reference data sets to the DATA-SETs menu and use the make reference option from the DATA-SETs menu prior to use. A reference data set  can be used as an option in both REBIN TO REF and NORMALIZE TO REF.
    This gives you basic information about the selected portion of your PRIME AAR. For example the TAGS present, their ranges   and mean, a translation of either the LWS status word or the SWS flag tag, etc.
    Quits the selected application without changing the PRIME AAR.

    ISAP Home Page 
    Last update:  May 1, 2000