JIVE Wiki

User Tools

Site Tools

Trace:
supportsci:tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
supportsci:tools [2018/08/23 07:12] – benitosupportsci:tools [2019/04/08 11:58] (current) – [EEE(2)] benito
Line 1: Line 1:
 ====== Support Tools ====== ====== Support Tools ======
 +
 +=====Personal Computers=====
 +**schedgaps.py** checks the 'early' times in a sum file to make sure gap length is > 11 s every 15 min.
 +<code>
 +usage: schedgaps.py [-h] [-e EARLY] sum_file
 +
 +List gaps for each telescope in a SCHED keyin file. Note, stations with
 +continuous cal will be reported but have an asterix in front of them
 +
 +positional arguments:
 +  sum_file              the .sum file to read. Must have early as a 'bottom'
 +                        sumitem or by itself (last)
 +
 +optional arguments:
 +  -h, --help            show this help message and exit
 +  -e EARLY, --early EARLY
 +                        seconds antenna must be on source before scan start to
 +                        count as sufficient for tsys. Defaults to 11
 +</code>
  
 =====CCSBETA===== =====CCSBETA=====
Line 22: Line 41:
                         this case the default is: <experiment>-{key}.lis.                         this case the default is: <experiment>-{key}.lis.
 </code> </code>
 +
 +**schedule_fringe_test** - script to schedule an automatic fringe test.
 +
 +Inside the experiment name (/ccs/expr/<expname>).
 +<code>
 +log2vex.pl
 +    - tapelog evlbi
 +    - EOP
 +    - Sched from Skdfile
 +    - Clock
 +    - Compile vexfile
 +
 +
 +vex2db <exp>.vexfile
 +
 +schedule_fringe_test [-h] -e EXPERIMENT -s STATIONS -m EMAIL [-n SCANNAME] [-t STARTTIME] [-d DURATION]
 +
 +Either specify a scan or startime plus duration.
 +
 +Arguments:
 +    -h              Show the help
 +    -e EXPERIMENT   Experiment name
 +    -s STATIONS     List with all stations (e.g. EfJbO8)
 +    -m EMAIL        Email where the results will be submitted
 +    -n SCANNAME     Name of the scan to obtain (e.g. No0040)
 +    -t STARTTIME    Starttime of the fringe test (e.g. 2017y290d12h42m00s)
 +    -d DURATION     Duration of the fringe test in seconds (default 4 s)
 +</code>
 +
 +
 +**recorrelate_fringe_test** - to correlate again a fringe test scheduled with schedule_fringe_test.
 +
 +<code>
 +recorrelate_fringe_test -e EXPERIMENT -n SCANNAME
 +</code>
 +
 +
 +
 +
  
 =====EEE(2)===== =====EEE(2)=====
Line 40: Line 98:
   --version      show program's version number and exit   --version      show program's version number and exit
   -v, --verbose  Only checks the visibilities to flag (do not flag the data).   -v, --verbose  Only checks the visibilities to flag (do not flag the data).
 +</code>
 +
 +**fringeSelect.py** - script to help find you a fringe finder. Queries astrogeo rfc:
 +<code>
 +usage  fringeSelect.py [-h] [-b BAND] [-e MIN_EL] [-f MIN_FLUX]
 +                       timeStart duration stations [stations ...]
 +
 +Provide some options for sources to use as fringe finders. Based on RfC
 +catalogue.
 +
 +positional arguments:
 +  timeStart             The start date/time of your experiment. Format
 +                        ='DD/MM/YYYY HH:MM'
 +  duration              The duration of your experiment (in hours)
 +  stations              Space delimited list of stations
 +
 +optional arguments:
 +  -h, --help            show this help message and exit
 +  -b BAND, --band BAND  The band you are searching for, one of l, s, c, m, x,
 +                        u, k, q. If not specified will default to using C-band
 +                        fluxes as priority.
 +  -e MIN_EL, --min-el MIN_EL
 +                        The minimum elevation to consider a source being 'up'.
 +                        Defaults to 20.
 +  -f MIN_FLUX, --min-flux MIN_FLUX
 +                        The mimimum flux density of sources to consider.
 +                        Defaults to 1.0 Jy
 </code> </code>
  
Line 119: Line 204:
 </code> </code>
  
 +
 +**pipelet.py** - Parses the pipe letter (exp.pipelet) to be sent to the PI after pipelining the data.
 +<code>
 +usage: pipelet.py [-h] [-v] [-o OUTPUT] [-c CREDENTIALS] [-u USERNAME] [-p PASSWORD]
 +                   experiment jss
 +
 +Creates a .pipelet file in the current directory. This letter is the content that must
 +be sent to the PI after pipelining an experiment. It contains information about the
 +pipeline output and the credentials to access the data.
 +It takes the credentials from the username_password.auth file that should be placed in
 +the current directory (otherwise specify its file, or the username and password as parameters).
 +The user must provide the following information:
 +- The experiment name (case insensitive).
 +- Who are you (the Support Scientist). Type your surname.
 +
 +positional arguments:
 +  experiment            Experiment name.
 +  jss                   JIVE Support Scientist doing the post-processing (your surname).
 +
 +optional arguments:
 +  -h, --help            show this help message and exit
 +  -v, --version         show program's version number and exit
 +  -o OUTPUT, --output OUTPUT
 +                        Output directory where the file {experiment}.pipelet will be store
 +                        (by default the current directory)
 +  -c CREDENTIALS, --credentials CREDENTIALS
 +                        Auth file containing the username and password in its name (required
 +                        if *.auth is not in current directory).
 +  -u USERNAME, --username USERNAME
 +                        Username to access the data (required if no credential file exists)
 +  -p PASSWORD, --password PASSWORD
 +                        Password to access the data (required if no credential file exists)
 +
 +</code>
  
 =====Pipe (jop83)===== =====Pipe (jop83)=====
Line 221: Line 340:
  
 **uvflgall.csh** - makes a uvflgfs file from any .log files in the current directory. Also changes flagr line to make uvflg.pl happier. **uvflgall.csh** - makes a uvflgfs file from any .log files in the current directory. Also changes flagr line to make uvflg.pl happier.
 +
 +**comment_tasav_file.py** - tool to create the comment file to be located in the pipeline output before running the feedback.pl script (and after having run the pipeline):
 +
 +<code>
 +usage: comment_tasav_file.py [-h] [-v] [-oc OUTPUT_COMMENT] [-ot OUTPUT_TASAV]
 +                       experiment
 +
 +Creates a .comment file (in $OUT/exp directory) and a .tasav.txt file (in
 +$IN/exp). Given the default templates, it customizes them to include the basic
 +data from the given experiment. The script takes the information from
 +different locations (ccsbeta, pipe $IN and $OUT directories). The EVN Pipeline
 +must have been run before calling this script.
 +
 +positional arguments:
 +  experiment            Experiment name. Note: in case of multiple passes
 +                        write {exp}_number (e.g. ev100_1
 +
 +optional arguments:
 +  -h, --help            show this help message and exit
 +  -v, --version         show program's version number and exit
 +  -oc OUTPUT_COMMENT, --output_comment OUTPUT_COMMENT
 +                        Output directory where the file {experiment}.comment
 +                        will be saved (by default in $OUT/{experiment})
 +  -ot OUTPUT_TASAV, --output_tasav OUTPUT_TASAV
 +                        Output directory where the file {experiment}.tasav.txt
 +                        will be saved (by default in $IN/{experiment})
 +
 +</code>
 +All additional data are taken from different files: the script access ccsbeta to get the epoch of the observation (from the MASTER_PROJECT.LIS file), and it also reads the pipeline input file and the pipeline output .SCAN and .DTSUM files. The default output will be in $OUT/{exp}/{exp}.comment, unless other location is indicated by the -o option.
 +
 +
 +
supportsci/tools.1535008362.txt.gz · Last modified: 2018/08/23 07:12 by benito