Changes between Version 7 and Version 8 of Development/cabb-upgrade/PGFLAG


Ignore:
Timestamp:
10/01/09 11:53:45 (15 years ago)
Author:
JamieStevens
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • Development/cabb-upgrade/PGFLAG

    v7 v8  
    66
    77We want a simple PGPLOT-based utility to
    8  * display UV data from a single baseline, in the format
     8 * display UV data from a single baseline, in the format (achieved in version 1)
    99   * channel number on X axis
    1010   * time on Y axis
    1111   * amplitude or phase shown as "greyscale"
    1212 * display a cursor with 'live' readback of the amplitude/phase, channel number, frequency and timestamp
     13   * PGPLOT has no callback routines on cursor movement, so unable to implement live readback
     14   * instead have made it possible to 'measure' the point under the cursor via keypress
    1315 * it would be helpful to display the source name as well, either as a live readback, or as an annotation on the display window (perhaps at the scan boundaries)
     16   * not implemented in version 1
    1417
    1518We want to use this to select subsets of the displayed data and apply flagging commands to the subset.
    1619
    1720 === Display characteristics ===
    18  * display one baseline at a time
    19  * we want to be able to jump to a different baseline number (forward and back thro' the sequence)
    20  * don't average time steps by default (make the averaging a command parameter)
     21 * display one baseline at a time (version 1)
     22 * we want to be able to jump to a different baseline number (forward and back thro' the sequence) (version 1)
     23 * don't average time steps by default (make the averaging a command parameter) (version 1)
    2124 * do sum the channels such that the entire bandpass fits in the PGPLOT display window (allow turning this off via command line params)
    22  * if the uvdata array extends beyond the edges of the display window, allow scrolling (vertically or horizontally)
     25   * PGPLOT routine PGGRAY does this automatically (version 1)
     26 * if the uvdata array extends beyond the edges of the display window, allow scrolling (vertically or horizontally) (version 1)
    2327 * when it is possible to scroll, show an arrow (outside the display grid) pointing in the direction one can scroll. Arrow keys are the most obvious shortcut key!
     28   * PGPLOT uses the cursor keys in interactive mode as another way to move the mouse
     29   * instead version 1 uses the vi movement keys h,j,k,l for scrolling
    2430 * the cursor would ideally be an 'open plus' shape - lines extending to the edge of the display grid but with a small open area at the intersection (so you can see what is directly under the cursor).
     31   * unable to change PGPLOT interactive cursor shape
    2532 * zooming - allow zooming up to 1:1 display. May be useful to have higher zooms than this?
    26  * must support SELECT and LINE keywords
     33   * PGPLOT routine PGGRAY allows for easy zooming with automatic scaling (version 1)
     34 * must support SELECT and LINE keywords (version 1)
    2735
    2836 === Flagging ===
    2937 * when user selects a piece of data, and says 'flag it'
    30    * update the display to show the data flagged away
    31    * allow 'undo' of the last flagging command.
     38   * update the display to show the data flagged away (version 1)
     39   * allow 'undo' of the last flagging command. (version 1)
    3240 * selection:
    33    * by area (PGPLOT boxing)
     41   * by area (PGPLOT boxing) (version 1)
    3442   * this will do single rows and columns as well.
    3543   * however one does want to be able to flag an entire row while still zoomed in (ie data extends beyond display borders)
     44     * version 1 can extend the selection to the entire row/column, but only on viewed region
     45     * it is a simple matter to add this function
    3646 * should be able to abort a flagging session, ie throw all flags for the current baseline and/or all baselines flagged so far.
     47   * version 1 can abort completely, not start again without reloading
     48   * small amount of effort required for implementation
    3749 * probably want to use temporary flagging files that only replace the flag file for the dataset at the end of the task
     50   * version 1 uses in-memory flagging, and applies only at the end
    3851 * probably want to allow logging of the flagging commands so they can be played back/edited with UVFLAG
    39 
     52   * version 1 logs all flags to the history, and can make BLFLAG selgen-like files, but of course the 'select' keyword cannot be used to constrain channel ranges
    4053
    4154