User Tools

Site Tools


analysis:solve

This wiki is not maintained! Do not use this when setting up AuScope experiments!

This is an old revision of the document!


The full guide to using Calc/Solve is here. The following information describes the process used at Hobart and is aimed at routine processing of post-correlation data.

Prepare level 2/3 databases

Level 2 databases have an updated clock model applied (using calc11), replacing the model used by the correlator. To generate new databases, edit the up11.inputs file with the new database names (note the leading $):

$14FEB05XT
$14FEB05ST

and then run up11 up11.inputs AU. After completion, you should have 14FEB05XT_V002 and 14FEB05ST_V002 in /data/vlbi/mark3_dbh

Level 3 databases have cable cal and MET data added to provide an apriori atmosphere model. This is usually only applied to the X-band data. First, download the station log files with wget http://lupus.gsfc.nasa.gov/ivs/ivsdata/aux/2014/aust19/aust19hb.log, etc. Then run pwxcb aust19hb.log. You will be prompted to confirm some details of the experiment, and optionally edit the recorded MET data. When running pwxcb for the first log of an experiment, you will be prompted to give name of the database that this experiment is linked to - use the same syntax as in the up11 file (e.g $14FEB05XT). Repeat pwxcb for all stations in the experiment and then apply the calibrations by running dbcal /data/vlbi/wxcb/aust19.dbcal. After completion, you should now have a 14FEB05XT_V003 file in /data/vlbi/mark3_dbh

Start calc/solve & get a viable solution

First start Calc/Solve with the command enter AU. Once inside the Calc/Solve system, be extremely careful with your typing as almost any keypress can and will be quietly interpreted to change various settings. Also, default settings may not always be displayed, or displayed correctly on start-up. A last warning - Calc/Solve always starts up with the same data & settings loaded as when it was last run. To restart an analysis you should re-load the data, overwriting any previous databases in memory.

  • Load in the data, starting with X-band: Enter G to get some data through the SDBH program. Tap * to toggle the mode between between the append and replace modes. Use replace if starting afresh. Type K to enter the X-band database and version number ($14FEB05XT 03). Press enter to read the history file and a list of aprioris until you get back to the SDBH window. NB - you msy see some Warnings about Hart15 not being in the Flyby file - these are benign. Toggle the mode to append with*, and then use K to load in the S-band database. Again, review the information by pressing enter until you reach the SDBH window again & then return to the main window by pressing O
  • Set up appropriate calibrations by pressing +. Apply UT1Ortho, XpYpOrth, XpYpLib, UT1Libra, OPTLCont by entering 6, 7, 8, 9, #. Then press N to change to the S-band database and repeat. Return to the main menu with O
  • Set up initial solution (1^{st} order clock). Enter L. Press + and then 3 to use Group Delays only, and make sure that no EOPs are being estimated - you can move around the text menus with the arrow keys and toggle some variables by pressing the space bar. The screen should look like this:
Polar motion and UT1: Polynomial Parameterization         SETFL Ver. 2007.07.30
14/02/05 19:00 XWOB Coefficients   0 0 0 0
14/02/05 19:00 YWOB Coefficients   0 0 0 0
14/02/05 19:00 UT1  Coefficients   0 0 0 0
Select:(/)G.Rate & Segments (%)Only Segments (|)Sine Style (@)Reset Poly Epoch
Gamma, Precession rate             0 0    Nutation(.): Dpsi, Deps  0 0

Print residu(A)ls: OFF             Print corr. (M)atrix: OFF
Print (N)ormal Matrix: OFF         (Z)ero Normal Matrix: OFF

(^)Elev. cutoff: None              Pick parameters: (!)Sites OFF  (#)UT1/PM

Wea(K) Station Constraints: OFF    (R)Use rate: Yes

Use normally (W)eighted delays     Select: Baseline-(C)lock offsets

(:)Delay  Group  (;)Rates Off      Select: (B)aselines, (X)Data bases

Page: (E)Site       (S)ource       (O)ptions            (")Constraints
      (Q)Run least squares         (T)erminate SOLVE    (<)A priori clock
      (+)Change data type          Group delay only
      (')Change suppression method SUPMET__PRE98        (-) Singularity check

 Last page   Parms used / Max parms available:   20/ 2000
</code?

Then press ''E'' to set up the site parameters. For the initial solution, set the Clock Polynomials line to ''1 1 1 0 0 * * *'' for every station bar one (the reference station - choose the same one as was used for a reference in fourfit). You can change between the stations with the ''N'' and ''P'' button. Make sure that all other parameter estimations are set to zero for all stations & beware of errant keypresses. Once ready, you can geenerate a solution by pressing ''Q''.

The solution will be writtento the screen. Check that the Weighted RMS in delay is < 1 microsecond (if greater, suggests strong outliers or systematic problems). Also, check the second page where the clock solutions are listed:

<code>
  1. HART15M  CL 0 14/02/05 06:59                -7063.162 ns      1.95 ns
    2. HART15M  CL 1 14/02/05 06:59                   76.263 D-14    9.44 D-14
    3. HART15M  CL 2 14/02/05 06:59                    14.85-14/d    9.13-14/d
    4. HART15M  NG 14/02/05 06:59                  -44.17 mm         48.37 mm
    5. HART15M  EG 14/02/05 06:59                 -140.18 mm         41.28 mm
    6. HART15M  NG 14/02/06 06:59                  138.50 mm         46.24 mm
    7. HART15M  EG 14/02/06 06:59                 -151.57 mm         36.44 mm

If CL 0 is greater than 100000 ns (100 microsec) or CL 1 > 100000 D-14 in rate then you will need to apply an apriori clock model or, better yet, recorrelate the data. See the solve guide for instruction on applying a priori model. If the solution is ok, return to the main menu with O

  • Next, proceed to Ambiguity Resolution by pressing A. Change the minumum quality code to 5 by pressing Q and 5. Start the process by pressing A and check the printed results. You will sometimes encounter warnings like this:

<code> GAMB S-band: r.m.s. of whole solution is OK GAMB $b$ group ambiguities are resolved, but solution looks bad Are you sure, that you really need to save these results in scratch file ? <\code>

These are usually caused a few bad sources/observations - press S to save the results and return to the main window.

  • Now apply a per-baseline clock model. Press L and then C. Set the reference clock by entering the station number, and then press M. Generate a new solution by pressing Q. The weighted RMS of the solution should be in the range of 550-1500 ps and the magnitude of the baseline clocks should be < 1 ns. If now, refer to the guide on how to deal with permanmet ambiguities (this hasn't been necessary yet). Retun to the main page with O
  • Next inspect the residuals for any sign of clock breaks. NB - Don't try to run this on a machine with a display with < 1080 vertical pixels - the pgplot window is fixed at a very large size. Press P to start the plotting program. Press X in the pgplot window to return to the main window.

Prepare level 4 database & convert to NGS format

/home/www/auscope/opswiki/data/attic/analysis/solve.1407807990.txt.gz · Last modified: 2014/08/12 01:46 by Jamie McCallum