HOME -> RTNet

Introduction

Template Input
    (svn 15512)

  Realtime Proc.

  Post-Processing

  NRT Processing


RTnet Output

RTes FAQ

RTnet FAQ



RTNet FAQ (RTes FAQ)


Realtime Processing Post-Processing Input File Output File Status Station Tools Processing Strategy File Archive


Realtime Processing

Q: My real-time RTnet processing stopped suddenly without any error messages. What is the most plausible reason for the problem?
Be sure to log out of your terminal after running RTes and RTnet commands. Otherwise the jobs could be killed by a SIGTERM signal when you accidentally close your terminal or in your terminal times out.

We recommend to run rtnet with "nohup" command like as:
nohup rtnet RTNET_INPUT_FILE.INP &

RTes and RTnet are tested with about 50 types of input files (post-processing, realtime, and near real-time) before releasing of distribution. However new problem could occur when new types of data is used, for example. Please let us know when you find errors or SEGFAULT (wikipedia) in RTnet OUT (or OUT_i) files. Please note same problem could occur even in post-processing.


Post-Processing

Q: I tried post-processing by modifing the input file used for real-time processing. The new post-processing seems very slow. What is plausible reason for the problem?
Please check if you still set RANDOMDELAY or not in your modified input file. The option is used to avoid processing at the same moment in realtime processing with many semilar RTnet jobs (for example, in case of 30sec. PPP processing for 200 stations, RTnet tries to process data at the similar timeing every 30 sec.).

The option needs to be turned off in post-processing.


Input File

Q: I want to start new GNSS processing. How can I find optimal input file for my processing?
A: Please refer links to "Template Input" in the left panel of the page. You can find input files which is close to your new processing scheme. Then modify the input file (station anme, satellite products, etc), and start RTnet.


Q: How can I update my rtnet input file for updated RTnet (svn)?
A: Update of input file is done with the following RTnet command:
updinp.pl USER'S_INPUT_FILE.INP ~/gpss/INP/RTNET.INP > USER'S_UPDATED_INPUT_FILE.INP
  • Script to update RTnet input file: updinp.pl in ~/gpss/bin/
    where ~/gpss is symbolic link to RTnet distribution (See Section 1.3 Installation, page 5, in RTnet user manual [SVN9823])

  • Reference input file: ~/gpss/INP/RTNET.INP


Q: How can I know meaning of RTnet input parameters?
A: Please refer RTnet User Manual (current version SVN9823, April, 2014). All input parameters and the meanings are described with index.


Output File

Q: How can I read or diagnose Rtnet solutions?
A: Please refer links to "RTnet Output" in the left panel of the page. You can find format of RTnet output file. Also, detailed information is described in RTnet User Manual (current version SVN9823, April, 2014).


Status

Q: Is there an application to monitor rtnet is running ok?
A: There is web-based tool (independent from RTnet system) to monitor status of rtnet, called NPSM. This is an optional feature for monitoring RTnet server runs. Please inquire if interested.



Station

Q: How can I add new stations to the current processing?
A: Yes, user can add the new station which is registerd in RTes on the fly (OTF) by updating RTnet input file used for the current processing. To do so,
  • Register new station(s) in RTes (See "Start Station" in RTes online manual.
  • Update STAINFOFILE (see Section 4.4 in RTnet manual)
  • Check if ocean loading coefficient (BLQ file) is in the current BLQ file if used. If not, add the new station information if the new station doesn't exist.
  • Add station name and parameters in new RTnet input file.
  • Copy new input file to the current input file. RTnet automatically detect update of the input file, and add the station in the processing.


Tools

Q: Webpage mentions a java applet to add stations and start post process?
A: The java-based tools RTuser and RTmanager are optional software that can be used for the purpose.


Q: Do you have plotting scripts; e.g, 3 days, or zoom centered around a time for specific events?
A: There is the tool which only works for PPP and PPP-AR processing, but only for daily-based position solution plots. We will develop a more sophisticated plotting tool in future.


Strategy

Q: Can RTNet have products of TEC?
A: Yes, but need to set RTnet parameter to estimate TEC. See the Section 6.16 "Ionospheric Parameters" in RTnet manual for details. The template input file will be prepared soon.


Q: How high is the thin ionospheric layer used in Rtnet model?
A: It is roughly 506.7 km. More model will be implemented depending on user's needs.


File Archive

Q. Do past daily plots get archived in our server?
A: If the server is configured and processing is setup by GPS Solutions, all solutions, plots, and files are archived inside of your server. Otherwise users need to setup their own archiving scripts, and set RTes and RTnet parameter to save raw and RINEX observation. In RTes, and in RTnet see options "RXO_OUTPUTPATH" (see online manuals for details.) In RTes, the following option control to save files:
  save_raw enabled="true"
  save_raw->output_path
  save_raw->output_name
  save_raw->format
  save_raw->rinex_options
  save_raw->compress
See "Stat Station" tag in http://www.gps-solutions.com/rtes/