NRAO Home  >  Green Bank  |  Wiki Topic:    GB > Data > ConfigGui
   Changes | Index | Contents | Search | Statistics | Jump to Topic

Configgui (F. Ghigo)

Getting Started

The source code is located in /home/astro-util/src/glish/gfuncs/. The GUI can be launched by typing CONFIGGUI. A related glish script, gbtsetup.g, implements a command-line interface to the setup functionality.

Pros & Cons

Pros:

Cons:

Capabilities and problems with CONFIGGUI

F. Ghigo, NRAO-Green Bank August 5, 2003

Introduction


CONFIGGUI is a utility GUI written in glish which allows users to set up their desired GBT configuration. This note lists the capabilities of this tool, and also its deficiencies.

Capabilities


- Handles all receivers that have been used on the GBT so far: Prime focus 1 and 2, L-band, S-band, C-band, X-band, Ku-band, K-band, and Q-band.

- Handles all back ends: BCPM, Spectral Processor, ACS, DCR, radar, and VLBI.

- Handles 1, 2, or 4 IFs, and multiple beam receivers.

- Velocity and reference frame can be specified.

- Switching modes and types can be specified.

- Has test mode and debugging mode.

- The configuration is organized in terms of the primary and secondary keywords described in the memo by Ghigo and Maddalena (April 2003).

- The CONFIGGUI tool is separate from the code that does the configuration. CONFIGGUI calls a separate glish function ("gbtsetup.g") to actually configure the M&C system.

- Consults a "badfibers.dat" file to patch around signal paths if one or more fiber drivers or receivers are out of service.

Deficiencies


- Does not consult the cabling file. No flexible searching of possible signal paths.

- There has not been extensive testing of all possible setups.

- No save/restore of configuration; GUI does not remember how it was set up in a previous session.

- No integration with GO: GO does not know what CONFIGGUI did, and vice versa.

- "DCR_AF" option is not implemented.

- Does not know about the receivers whose IFs are split to go to both converter racks A and B, hence doesn't know how to handle

  1. IFs.

- probably does not handle multi-beam and multi-IF cases correctly needs more testing in this area.

Usage of gbtsetup.g

#/====================================================================
#/==  gbtsetup : command-line function to set up the whole system.
#/====================================================================
#/==  Usage:
#/==   gbtsetup( , , , , , 
#/==            , , , , , 
#/==            ,   )
#/==
#/==     : Rcvr_342,  Rcvr_450,  Rcvr_600,  Rcvr_800, Rcvr_1070
#/==                    Rcvr1_2,   Rcvr2_3,   Rcvr4_6,   Rcvr8_10,
#/==                    Rcvr12_18, Rcvr18_22, Rcvr22_26, Rcvr40_52, Holography
#/==    
#/==     : cont, spec, pul, radar, vlbi 
#/==
#/==       : dcr, sp, acs, spect, vlbi, radar, bcpm
#/==                    dcr_af, dcr_if, bcpm/sp, bcpm/acs
#/==
#/==     : frequency (in MHz) to be tracked by LO1.
#/==            If more than one spectral window, this is an array of size Nwin.
#/==
#/==     : the bandwidth in MHz per backend channel.
#/==
#/==     : backend integration time in seconds.
#/==
#/==     : a glish record specifying the switching:
#/==          [ , , , [freq1, freq2] ]
#/==             sw=[mode='tp', type='none', swper=1, df=[0.0, 0.0] ]
#/==
#/==       : a glish record with additional receiver parameters:
#/==          [ , ,  ]
#/==          For Example:  rcv=[cal='lo', pol='circ', beams='B12']
#/==
#/==     : a list of frequency offsets.
#/==          df=[ DF1, DF2, ...] ]  ( frequencies in MHz)
#/==
#/==     : a glish record specifying velocity tracking info:
#/==          vel=[ v=[v1,v2], vdef=, frame= ]
#/==          (veloc in km/sec)
#/==
#/==     : this glish record depends on the backend.
#/==                     : For the Spectrometer, this is: 
#/==                       [ ,  ]
#/==                     :  is 3 or 9;
#/==                     :  'low', 'med', or 'hi'
#/==                     : example:   [levels=3, nchan='low' ]
#/==                     : For the SpectProc: [ multmode= 'Square'|'SqrCross']
#/==
#/==     : this is a list of the fiber paths to be avoided:
#/==           For example:  [2, 7]
#/==            If bad_fibers='auto' the bad fiber list is found from a file.
#/===========================================================================


-- Main.NicoleRadziwill - 12 Sep 2003

Topic ConfigGui . { Edit | Attach | Ref-By | Printable | Diffs | r1.1 | More }
Revision r1.1 - 12 Sep 2003 - 18:02 GMT - NicoleRadziwill Content copyright © 1999-2007 by the contributing authors.
All material on this collaboration platform is the property of the contributing authors.