diff --git a/docs/geodezyx.operational.html b/docs/geodezyx.operational.html index 5b3f47a8..0071a274 100644 --- a/docs/geodezyx.operational.html +++ b/docs/geodezyx.operational.html @@ -1287,8 +1287,48 @@
High level function to run a GROOPS’s PPP job +This function download IGS’s products, convert them, and run the PPP job +see the Notes below for more details
+rinex_path (str) – the path of the RINEX file to process.
project_name (str) – a personalized name for your processing project
igs_ac_10char (str) – the 10 char. ID for the IGS AC you want to use +e.g. ‘COD0OPSFIN’ +can handle operational (OPS) and MGEX (MGX) lines
cfg_files_dict (dict) – a dictionary controlling the conversion/processing steps +and the corresponding config files.
log_root_dir (str) – directory path where the frontend logs will be written
vmf_tropo_root_dir (str) – directory path where the VMF3/ECMWF grids will be stored +(auto download)
prods_gnss_root_dir (str) – directory path where the IGS products (not converted) will be stored +(auto download)
cfg_files_root_dir (str) – directory path where the config files are stored.
groops_bin_path (TYPE, optional) – Path of the GROOPS bin. +The default is ‘/opt/softs_gnss/groops/bin/groops’.
Note
+the config files must be checked and edited manually +to fit your environnement config +it is the config files which contains the most useful parameters +use groopsGui to help you
+prototype for config files are in: +…/geodezyx/000_exemples/groops_frontend/configfiles/
+do not forget to update on a regular basis GROOPS’s data folder: +` https://ftp.tugraz.at/outgoing/ITSG/groops/data.zip`
+None.
+High level function to run a GROOPS’s PPP job +This function download IGS’s products, convert them, and run the PPP job +see the Notes below for more details
+rinex_path (str) – the path of the RINEX file to process.
project_name (str) – a personalized name for your processing project
igs_ac_10char (str) – the 10 char. ID for the IGS AC you want to use +e.g. ‘COD0OPSFIN’ +can handle operational (OPS) and MGEX (MGX) lines
cfg_files_dict (dict) – a dictionary controlling the conversion/processing steps +and the corresponding config files.
log_root_dir (str) – directory path where the frontend logs will be written
vmf_tropo_root_dir (str) – directory path where the VMF3/ECMWF grids will be stored +(auto download)
prods_gnss_root_dir (str) – directory path where the IGS products (not converted) will be stored +(auto download)
cfg_files_root_dir (str) – directory path where the config files are stored.
groops_bin_path (TYPE, optional) – Path of the GROOPS bin. +The default is ‘/opt/softs_gnss/groops/bin/groops’.
Note
+the config files must be checked and edited manually +to fit your environnement config +it is the config files which contains the most useful parameters +use groopsGui to help you
+prototype for config files are in: +…/geodezyx/000_exemples/groops_frontend/configfiles/
+do not forget to update on a regular basis GROOPS’s data folder: +` https://ftp.tugraz.at/outgoing/ITSG/groops/data.zip`
+None.
+High level function to run a GROOPS’s PPP job +This function download IGS’s products, convert them, and run the PPP job +see the Notes below for more details
+rinex_path (str) – the path of the RINEX file to process.
project_name (str) – a personalized name for your processing project
igs_ac_10char (str) – the 10 char. ID for the IGS AC you want to use +e.g. ‘COD0OPSFIN’ +can handle operational (OPS) and MGEX (MGX) lines
cfg_files_dict (dict) – a dictionary controlling the conversion/processing steps +and the corresponding config files.
log_root_dir (str) – directory path where the frontend logs will be written
vmf_tropo_root_dir (str) – directory path where the VMF3/ECMWF grids will be stored +(auto download)
prods_gnss_root_dir (str) – directory path where the IGS products (not converted) will be stored +(auto download)
cfg_files_root_dir (str) – directory path where the config files are stored.
groops_bin_path (TYPE, optional) – Path of the GROOPS bin. +The default is ‘/opt/softs_gnss/groops/bin/groops’.
Note
+the config files must be checked and edited manually +to fit your environnement config +it is the config files which contains the most useful parameters +use groopsGui to help you
+prototype for config files are in: +…/geodezyx/000_exemples/groops_frontend/configfiles/
+do not forget to update on a regular basis GROOPS’s data folder: +` https://ftp.tugraz.at/outgoing/ITSG/groops/data.zip`
+None.
+