AuScope VLBI Operations Wiki

User Tools

Site Tools

You are here: start » analysis » solve
Trace:
analysis:solve

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

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
analysis:solve [2014/08/12 01:46]
Jamie McCallum [Start calc/solve & get a viable solution] 		analysis:solve [2014/08/12 04:09] (current)
Jamie McCallum [Prepare level 4 database & convert to NGS format]
Line 48: Line 48:
  
  Last page   Parms used / Max parms available: ​  20/ 2000  Last page   Parms used / Max parms available: ​  20/ 2000
-</code?+</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''​. 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''​.
Line 72: Line 72:
  ​GAMB ​ $b$ group ambiguities are resolved, but solution looks bad   ​GAMB ​ $b$ group ambiguities are resolved, but solution looks bad 
 Are you sure, that you really need to save these results in scratch file ? Are you sure, that you really need to save these results in scratch file ?
-<\code>+</code>
  
 These are usually caused a few bad sources/​observations - press ''​S''​ to save the results and return to the main window. 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 [[lacerta.gsfc.nasa.gov/​mk5/​help/​solve_guide_01.html| the guide]] on how to deal with permanmet ambiguities (this hasn't been necessary yet). Retun to the main page with ''​O''​   * 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 [[lacerta.gsfc.nasa.gov/​mk5/​help/​solve_guide_01.html| 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.   * 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.
-  * +  * If you have to deal with clock breaks, you can do this by inserting a breakpoint in the clock solution. Press ''​L''​ and then ''​E''​ to get to the ''​Sites''​ menu. Use ''​N''​ to select the correct station and then press ''​*''​ to reveal and change the method until you get ''​Insert''​ (other options are ''​Reset'',​ ''​Delete''​ and ''​Automatic''​ which is the default). Then press ''​C'',​ and enter the time of the clock break. Press enter on an empty line when all the clock breaks have been inserted. You should now have additional entries for clock polynomials - use the arrow keys to highlight the first three zeroes and use the pace bar to toggle them to ones. The section below shows the set up for Katherine in aust19 which had two clock breaks at 035-133000 and 035-191200. 
 + 
 +<​code>​ 
 + Clock polynomials 
 + ​14/​02/​05 06:59                1 1 1 0 0 * * * 
 + ​14/​02/​05 13:30                1 1 1 0 0 * * * 
 + ​14/​02/​05 19:12                1 1 1 0 0 * * * 
 +</​code>​ 
 + 
 +  * Next, set up for an intermiary solution.  
 +    * Press ''​L'',​ ''​+''​ and ''​7''​ to set the solution type to ''​G-Gxs combination''​.  
 +    * Press '''''​ and ''​3''​ to change the suppression method to %%SUPMET__COMB1%%. 
 +    * Press ''​-'',​ ''​A'',​ ''​1'',​ ''​2''​ (press enter), ''​2'',​ ''​5''​ (press enter), ''​3''​ and ''​4''​ (press enter) to set up the singularity check with the recommended parameters. Press ''​S''​ to save & return. 
 +    * Enter the sites menu with ''​E''​ and toggle mode to Automatic with ''​*''​. Press ''​C''​ and set the time interval to 300 minutes (''​300''​ ), polynomial order to 2 (''​2''​),​ and use Batch mode (''​B''​). Set the reference station as before. 
 +    * Press ''​A''​ to estimate the atmosphere. Use an interval of 300 minutes and batch mode 
 +    * Return to the main menu with ''​O''​ and then go to the Weighting menu with ''​H''​. Press ''​C''​ to add a noise floor to the weights, then save areturn to the main menu with ''​O''​ 
 +    * Generate a solution with ''​Q''​. If the weighted RMS is < 150 ps, things are likely ok. You should be able to produxe a version 4 database and NGS file at this stage if you want to work on the data in VieVS/​OCCAM/​etc. This avoids calc/solve flagging ''​outliers''​ automatically. To proceed on to obtain a final solution, read on. 
 +  * Eliminate outliers with ''​\''​. Set recommended parameters with the following commands: ''​X'',​ ''​1000''​ (press enter), ''​U'',​ ''​400''​ (press enter), ''​C''​ (press enter). When ready, the screen should look like this: 
 + 
 +<​code>​ 
 +Automatic outliers elimination utility ​                   ELIM  Ver. 2007.08.01 
 +                   ​����������� 
 +$14FEB05XT <3> 
 +'​SUPMET__COMB1'​ 
 +Information about residuals is not available yet 
 + 
 +(X) Maximum uncertainty:​ 1000. psec        (A) Acceleration factor: 1 
 + 
 +(U) Upper threshold for outlier detection: 400. psec      (E) EQM speed-up: No 
 + 
 +(C) Cutoff limit for outlier detection: ​   not specified ​ (Y) Type: baseline 
 + 
 +(Q) Quality code limit: 5                  (D) Update residuals 
 + 
 +(-) Singularity check                      (') Change suppression method 
 + 
 +(V) Verbosity level: ​   1                  (N) Confirm each action: no 
 + 
 +(S) Return to Optin and save results ​      (O) Return to Optin without saving 
 + 
 +(P) Proceed for outliers elimination ​      (T) Toggle elimination/​restoration 
 + 
 +(W) Weights update ​                        (H) On-line help 
 +</​code>​ 
 + 
 +  * Press ''​P''​ to proceed with detection & elimination & press ''​S''​ to save the results & generate a new  solution. If the wrms is between 15 and 100 psec with the ''​used observations''​ precetage > 80%, then it's regarded as good. Significantly worse wrms/low acceptance suggests mishanded clock breaks, un- or mis-applied calibration,​ or maybe a bad station. 
 +  * Assuming that you have a good solution, or one with known and uncorrectable problems, you can then go on to generate a final solution. 
 +    * Press ''​L''​ to enter the estimation menu. Press ''​.''​ to esimate nutation and press ''#''​ to estimate EOPs. Use the arrow keys to change the UT1 coefficients line to ''​UT1 ​ Coefficients ​  0 1 0 0''​ 
 +    * Press ''​E''​ to enter the site menu. Toggle mode to Automatic with ''​*''​ and then set up both blocks (''​C''​) and atmosphere (''​A''​) using batch a 1 hour interval and batch mode. Set up gradient estimation with ''​G''​ and choose a 50 hour interval.  
 +    * Generate the solution ''​Q''​. Check the text listing makes sense and inspect the residuals (''​P''​) and estimated parameters (''/''​).  
 +    *   
 ====== Prepare level 4 database & convert to NGS format ====== ​ ====== Prepare level 4 database & convert to NGS format ====== ​
  
 +You can do this at any stage after running GAMB which handles the ambiguity resolution & ionospheric correction process. It's a two-tage process of creating an updated database & the running a DOS script to convert it to NGS format.
 +
 +  * Creating an updated database
 +    * From the main menu (''​O''​),​ press ''​U''​. Make sure that only the X-band database is selected and then press ''​N''​. ​
 +    * Press ''​G'',​ ''​5'',​ ''​6''​ and ''​7''​ to set the options as shown below. Press ''​N''​ to proceed.
 +
 +<​code>​
 +Database update ​                                          NEWDB Ver. 2007.06.05
 +-------------------------------------------------------------------------------
 +
 +
 +Database to be updated: $14FEB05XT
 +
 +        Reweighting:​ (G)roup (P)hase (B)oth (#)None
 +
 + (1) Clk & atm parms, constraints,​ data configuration-->​Yes No
 +
 + (2) Group delay editing and ambiguities--------------->​Yes No
 +
 + (3) Group ionosphere calibration:​--------------------->​Yes No
 +
 + (4) Met., cable, phase cal status:​-------------------->​Yes No
 +
 + (5) Ocean, relativity, pole tide status:​-------------->​Yes No
 +
 + (6) Phase delay editing and ambiguities--------------->​Yes No
 +
 + (7) Phase ionosphere calibration:​--------------------->​Yes No
 +
 +(N)ext Menu             ​(O)PTION ​   (R)efresh Screen ​ (D)efault standard
 +(T)erminate SOLVE       ​Re(S)elect Databases
 +</​code>​
 +
 +    * You'll be prompted to add a history entry via emacs at the next screen. Once emacs is started, add a line like "​aust19 NGS conversion AU". Close emacs and then press enter to update the file.
 +    * If it fails complaining about "Input experiment $14FEB05XT Ver.    3 not in catalog
 +" or "key not found",​ etc, this is usually due to the database having already been updated. If this fails, you'll need to exit calc/solve , delete the offending file from /​data/​vlbi/​mark3_dbh/​ and from the catalogue. You can do this with the ''​catlg''​ program. Use the ''​de''​ command (with ''​-1''​ as the "​password"​),​ select ''​e''​ for entry and then confirm the deletion of the most recent version. Once deleted, you should be able to run the update as per normal.
  
 +  * Once you have the 14FEB05XT_V004 file in /​data/​vlbi/​mark3_dbh/,​ you can now convert it with MK3NGS2.EXE. First, start a DOS command prompt with ''​wine cmd.exe''​. Then run ''​MK3NGS2.EXE /​data/​vlbi/​mark3_dbh/​14FEB05XT_V004''​. The output file will be written into the current directory as 140205XT.NGS and is now ready. Note that VieVS expects a filename like 14FEB05XT_N004 though.
/home/www/auscope/opswiki/data/attic/analysis/solve.1407807990.txt.gz · Last modified: 2014/08/12 01:46 by Jamie McCallum

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki