================================================================================ Bernese GNSS Software, Version 5.4 Last mod.: 14-Jul-2022 -------------------------------------------------------------------------------- First steps ================================================================================ -------------------------------------------------------------------------------- Start and configure the Bernese user interface -------------------------------------------------------------------------------- WINDOWS-platforms: Click the icon on your desktop to start the menu of the Bernese GNSS Software. UNIX-platforms: Make sure that the environment variables are loaded. Depending on your shell use ". /home/BERN54/LOADGPS.setvar" or "source /home/BERN54/LOADGPS.setvar" (Adapt the path to LOADGPS.setvar if necessary). You may add this step to your login script. Type "G" on the command line to start the menu of the Bernese GNSS Software. You can change the size of the window, color, and fonts to your preferences using the items in the submenu "Configure > Menu layout". The settings will be recorded. Using "Configure > Menu layout > Reset menu layout" you can always reset the settings to the factory defaults (use the key sequence: "+f l r y" in case the font becomes illegible). -------------------------------------------------------------------------------- General overview -------------------------------------------------------------------------------- Read the general help file (menu item "Help > General") first to get an overview on the Bernese GNSS Software, in particular: - how to use the menu, - the configuration of the menu and the Bernese environment, - the selection of the current session and the active campaign, - the usage of the session table, and - the different types of variables and their usage. Inspect the list of the programs in the general help (alphabetical order) or in the menu item "Configure > Program names" (order corresponding to the menubar) to get an impression on all programs of the software package and where they are located in the menu. The structure of the subdirectories in the campaign may have changed since the last version. We suggest to browse (not change!) through the panels in the menu items "Configure > Paths and Extensions" to get an overview on the different file types of the Bernese GNSS Software and the new directory structure in the campaign. -------------------------------------------------------------------------------- Getting started -------------------------------------------------------------------------------- In the following, this file provides information how to start working with the new version of the Bernese GNSS Software: Section A) General dataflow Section B) Run the examples Section C) Setup a new campaign, prepare the processing Section D) Setup an automated processing Section E) How to proceed in case of an error in the BPE? A. GENERAL DATAFLOW =================== The Bernese GNSS Software can only process your GNSS data. The general organization of the dataflow must be organized by your own depending on your needs, projects, and infrastructure. From our own experience and from the contact with numerous users we recommend to organize the general dataflow as follows: 1) DATAPOOL: This is a area of your harddisk where you can collect external data (e.g., orbits, RINEX files from IGS stations, etc.) as well as the observation files from your project. This DATAPOOL can either be filled manually or by a set of download scripts. A proposal for a structure of the DATAPOOL is given together with the input data for the processing examples together with a description in ${D}/README_DATAPOOL.TXT (or %D%\README_DATAPOOL.TXT). 2) CAMPAIGN: In this area the processing campaigns are located. When starting to process data the necessary files are first copied from the DATAPOOL into the active CAMPAIGN. The programs of the Bernese GNSS Software can only process files sitting in the active CAMPAIGN. In this sense it is the working area to generate the final results for you project (or a certain session). 3) SAVEDISK: The result files from the processing in the campaign area are copied at the end in a result archive. Here you only need to store the important (final) results from your project before you can clean up the campaign directory you have used to generate these results. The copies from the main result files from the processing examples are provided as reference solution in a proposed structure of the SAVEDISK area. A description can be found in the file ${S}/README_SAVEDISK.TXT (or %S%\README_SAVEDISK.TXT). B. RUN THE EXAMPLES =================== The examples distributed with version 5.4 of the Bernese GNSS Software are designed as ready-to-use processes that cover already many standard applications of the software package. Each example is provided as a separate BPE: PPP.PCF Standard PPP with phase ambiguity resolution to obtain coordinate, troposphere, and receiver clock determination. Pseudo-kinematic and high-rate troposphere estimation is prepared and can be enabled. RNX2SNX.PCF Standard double-difference network solution based only on GPS data or a multi-GNSS solution with an extended ambiguity resolution scheme. BASTST.PCF Baseline by baseline processing for trouble shooting. CLKDET.PCF Zero-difference network solution based only on GPS data or a multi-GNSS solution providing clock corrections (e.g., w.r.t. an existing coordinate and troposphere solution) IONDET.PCF Zero-difference network solution based only on GPS data or a multi-GNSS solution providing station-wise, regional, or global ionosphere maps and the related biases LEOPOD.PCF Precise Orbit Determination for a Low Earth Orbiting Satellites based on on-board GPS-measurements with phase ambiguity resolution (e.g., for GRACE) SLRVAL.PCF Validation of an existing GNSS or LEO orbit using SLR measurements ITRF.PCF Derives a coordinate and linear velocity approximation from the ITRF solution containing non-linear PSD corrections. For each of the BPE a README file is accessible via Menu > Help > Readme > EXAMPLE BPE explaining the basic structure, the functionality and the input and result files. All example BPEs start with input files in the official international standard formats (observation RINEX; SP3c for precise orbit files, IERS format for Earth rotation parameters, bias SINEX and clock RINEX when needed), that are copied from the DATAPOOL into your CAMPAIGN. The examples may also be used to test the installation by checking the correct functioning of BPE and programs: Compare your results with the results generated on our compiler and available in the corresponding directories of the SAVEDISK ($S or %S%). To run a BPE example start the menu and follow the instructions: 1. NON Windows users only: Extract the examples using the "${X}/EXE/configure.pm" tool if this was not done before during the installation. 2. Add the name of the campaign "${P}/EXAMPLE" to the campaign list in the menu item "Campaign > Edit list of campaigns". Take care on the brackets: ${P} is an environment variable, see the general help for more details on the usage of variables. 3. Select the campaign "${P}/EXAMPLE" as the active campaign using the menu item "Campaign > Select active campaign". 4. The example contains data for the following sessions: day of year 044 and 045 of year 2019, day of year 179 and 180 of year 2020, and day of year 095 and 096 of year 2021. Select one of these days for the current session (e.g., day 044 of year 2019). Use the menu item "Configure > Set session/compute date" to set the day. The session character needs to be "0" and the provided session table has the default name "SESSIONS.SES". 5. The CPU control file is located in the "${U}/PAN"-directory ("%U%\PAN" on WINDOWS platforms) and has the default extension "CPU". An example of a CPU control file is distributed for WINDOWS and UNIX platforms. User with a WINDOWS-platform can skip this item because the file does not need any change. Users on an UNIX-platform are invited to inspect the CPU control file (menu item "BPE > Edit CPU file"). It contains an entry for the localhost that works for all shells because it uses a bourne shell. You can use this entry for a first run of the BPE. To invoke the full power of the BPE, adapt the example entries to your system (bourne-shell or c-shell syntax, or rsh/ssh access to remote hosts). We refer to the help panel for more details. 6. Now you are ready to run the BPE examples. Run the PPP.PCF (example of a precise point positioning) at first for session 044 of year 2019 to get a priori coordinates for all stations and to complete the list of abbreviations. Use the menu item "BPE > Start BPE process" to start the BPE. To run the BPE on WINDOWS-platforms make sure that the input field "Client's environment file" in panel "BPE 1: Client Environment/Session Selection" is empty (see online help). Using the default settings you will process the current session in the active campaign. Select the "PPP.PCF" as the "Process control file" in the panel "BPE 2: Process Control Options". Select the "CPU control file" (default name "USER.CPU"). In the panel "BPE 3: Output Filenames" you should select reasonable filenames (e.g., "Task ID" = "PP", "Status file" = "PPP.RUN", "Program output" = "PPP.OUT"). Please check in the last panel ("BPE 4: Server Variables Sent to Client") that - the variable V_UPD is set to "Y" (update files in the DATAPOOL with the PPP results) and - the variable V_SAV is set to "Y" (copy result files from PPP to the SAVEDISK area) Press the "^Run"-button to start the BPE. 7. Go into the directory ${D}/REF52 (%D%\REF52) and compare the EXAMPLE.CRD, EXAMPLE.VEL, and EXAMPLE.ABB file just generated by the BPE with the corresponding _REF-files delivered as reference together with the software. In the SAVEDISK area there are more reference files to verify your installation (subdirectories of ${S}/PPP/2010/ or %S%\PPP\2010, see ${S}/README_SAVEDISK.TXT or %S%\README_SAVEDISK.TXT for a list of files). We expect no (significant) differences between your solution and the reference files. 8. In a similar way you may process the remaining days for the PPP.PCF BPE or the other examples like RNX2SNX.PCF and CLKDET.PCF. Data and orbit information for the sessions listed above are included in the datapool as distributed with the software (Note, that for the LEOPOD.PCF the data are only distributed for the two days in 2019). Compare your result files in the SAVEDISK-directories with the reference files flagged with "_REF". If they are identical (within the "compiler noise") you can assume that your installation of the Bernese GNSS Software works correctly. The a priori coordinates must stem from the PPP.PCF of session 044 of year 2019 to get comparable results. After running the example BPEs you are invited to inspect the subdirectories of the campaign ${P}/EXAMPLE (or %P%\EXAMPLE) to become familiar with the directory structure and the location of the files. We also propose to inspect the input panels of the BPE examples (menu item "BPE > Edit PCF program input files") to become familiar with the layout of the new program panels and to get an overview on the new options in the version 5.4 of the Bernese GNSS Software. You can use the online help (menu item "Help > Help on context") to get more information on options in the cursor's focus. C. SETUP A NEW CAMPAIGN, PREPARE THE PROCESSING =============================================== This section is a cookbook to setup a new campaign and to prepare the processing. Depending on your application you may have to adapt the following procedures. 1. Add the name of your new campaign (e.g., "${P}/MYFIRST") to the campaign list in the menu item "Campaign > Edit list of campaigns". Note to WINDOWS-users: You have to use the same UNIX-style syntax here because the variables are handled by the Bernese Menu and the perl-environment. If it is located on a disk referred by another variable (e.g., ${Q}) the UNIX-users have to add the definition of the environment variable to the file "${C}/LOADGPS.setvar". WINDOWS-users must also define the corresponding environment variable in their registry. They also have to add the variable to the "BERNESE_VARIABLES" entry of the registry. All users also have to add this new environment variable to the list in the "${U}/PAN/MENU_VAR.INP" file (menu item "Configure > Menu variables"). 2. Select the campaign "${P}/MYFIRST" as the default campaign using the menu item "Campaign > Select active campaign". You will get a message that no session table is available in your actual campaign. Do not worry about it at this stage. 3. Create the directory structure using the menu item "Campaign > Create new campaign". On the right hand side of your panel is a field with the label "Copy files into the campaign" with the default entry from: ${PAN}/SESSIONS.SES to: GEN SESSIONS.SES is a session table (see step four) that is prepared for a daily processing scheme. If you plan to setup an hourly processing scheme, you should copy ${PAN}/HOURLY.SES instead. Note, that you need write protections especially in the top-level directory where the campaign directory will be created. 4. If you have decided to use the alternative session table ("GEN/HOURLY.SES" instead of "GEN/SESSIONS.SES") you have to enable it in the Date Selection Dialog ("Configure > Set session/compute date"), input field for "Session Table". The "Session Char" should also be changed from "0" to a letter between "A" and "X" in that case. Confirm the selection with the "OK"-button. Independent which of the two default session tables you have copied in step 3 into your campaign area we recommend to inspect the session table using the menu item "Campaign > Edit session table". The online help will provide more information on the philosophy of the session definition in the Bernese GNSS Software. We propose to use the "open session definition" whenever possible. Your campaign is now ready to process your data. In the next steps we fill up the DATAPOOL with the necessary information: 5. Copy your RINEX observation files into a specific subdirectory of the DATAPOOL (e.g., "myRINEX"). They may be UNIX-or gzip-compressed files in the Hatanaka compact format, in RINEX2 or a later format (with the related naming conventions). All BPEs contain a script "RNX_COP" copying the RINEX observation files from the DATAPOOL into the campaign. There is a BPE Server variable "V_RNXDIR" that must contain this directory name. You can either specify the name (e.g., "${D}/myRINEX") either directly in the PCF file or in the last input panel when you start the BPE using the menu ("BPE > Start BPE processing"). The mechanism how the RINEX files are selected for the processing when you are using the RNX_COP script is described in the README-files of the BPEs (accessible via Menu > Help > Readme > EXAMPLE BPE). 6. Transfer all other input data files to your local host and put them into the campaign directories: ${D}/COD/CODwwwwd.PRE.Z from http://ftp.aiub.unibe.ch/CODE/yyyy ${D}/COD/CODwwwwd.CLK.Z from http://ftp.aiub.unibe.ch/CODE/yyyy ${D}/COD/CODwwwwd.BIA.Z from http://ftp.aiub.unibe.ch/CODE/yyyy ${D}/COD/CODwwwwd.ERP.Z from http://ftp.aiub.unibe.ch/CODE/yyyy or ${D}/COD/CODwwww7.ERP.Z from http://ftp.aiub.unibe.ch/CODE/yyyy (before week 1706) Instead of the operational final products from CODE you may also use the operational CODE rapid (GPS+GLONASS+Galileo), the most recent processing series from CODE (GPS+GLONASS+Galileo) or even the experimental CODE-MGEX (GPS, GLONASS, Galileo, BeiDou, QZSS). In the file at http://ftp.aiub.unibe.ch/AIUB_AFTP.TXT you find the most recent download instructions. If you want to use IGS products instead you may find the download instructions at https://files.igs.org/pub/product/readme.txt Other files in Bernese formats: ${D}/BSW54/CODwwwwd.ION.Z from http://ftp.aiub.unibe.ch/CODE/yyyy (for higher order ionosphere corrections and/or QIF ambiguity resolution) ${D}/BSW52/P1P2yymm.DCB.Z from http://ftp.aiub.unibe.ch/CODE/yyyy (for ionosphere determination) ${D}/BSW52/P1C1yymm.DCB.Z from http://ftp.aiub.unibe.ch/CODE/yyyy (for clock estimation) Reference frame definition: ${D}/REF54/IGB14_R.CRD from http://ftp.aiub.unibe.ch/BSWUSER54/REF ${D}/REF54/IGB14_R.VEL from http://ftp.aiub.unibe.ch/BSWUSER54/REF VMF3-coefficients (if needed): ${D}/VMF3/VMFG_yyyymmdd.Hhh.gz from https://vmf.geo.tuwien.ac.at/trop_products/GRID/1x1/VMF3/VMF3_OP/yyyy The time stamps in the file names need to refer to the day to be processed - you may open the dialogue "Configure > Set session/ compute date" to get the value for the actual session: wwww ... GPS week d ... day of GPS week yyyy ... four-digit year yy ... two-digit year mm ... month of year dd ... day of month hh ... hours of the day In the following steps the project specific files in ${D}/REF54 are prepared. We recommend that all files belonging to one project have the same basename. They are copied into the campaign by the BPE-specific copy script (XXX_COP, where XXX is the identifier of the BPE, e.g., PPP). The basename of these files is given into the BPE by the BPE server variable V_CRDINF. 7. Create the "Station information file" You have three different ways to create your station information file: - You may use the entries from the RINEX headers as starting point for the generation of the station information file. For this purpose you need to extract all RINEX observation files into the RAW-directory of your campaign (no compress or Hatanaka compact format is permitted). You may use the menu item "Service > Station information files > Extract information from RINEX" to prepare a draft version of the station information file. - If the equipment information is available in SINEX format you can import these records into a station information file using the menu item "Service > Station information files > Extract information from SINEX". Of course you have to complete the list of stations if necessary. - You can simply create this file from scratch by hand with the support of the menu item "Campaign > Edit station files > Station information file". Extractions from the RINEX header or SINEX files should only serve as a draft version of the station information file. It is necessary to inspect and complete the obtained station information file using the menu ("Campaign > Station files > Station information") or with your favorite text editor. Check all entries with your observation protocols for the receiver and antenna information records. Make sure that the station name corresponds to the name you want to use for your analysis. For each station a record on the used equipment is expected ("RECEIVER TYPE", "ANTENNA TYPE", and "ANTENNA ECCENTRICITY"). If you write SINEX files also the "DESCRIPTION" field is recommended. For new result files that make use of the 9chrID of the station you need to fill the column "LONG NAME" as well. The columns "ANT #" and "ANTENNA SERIAL NBR" need only be filled for those stations where you want to introduce individual antenna calibration corrections (instead of type mean values). If you want to change the names of the stations in your processing with respect to the observation RINEX file you have to introduce the file in the PPP (step 10). Otherwise you can prepare the file also after the PPP step. 8. When importing the observations from the RINEX observation files into the Bernese format the header information are extensively checked with respect to the equipment given in the station information file. If there are known inconsistencies (e.g., a miss-spelled receiver type) they can be listed in Accepted station information inconsistencies. 9. Create a PLD-file (tectonic plate assignment for the NUVEL-model) for all your sites. You can use the menu item "Campaign > Station files > Tectonic plate assignment" to do this. If you have a Bernese coordinate file containing the station names it can be selected to support the creation of the PLD-file. Otherwise cancel the dialogue "Select Skeleton Coordinate File" when creating a new PLD-file. 10.If you have a priori coordinates from a phase solution for all your sites you may skip this item. Run the PPP.PCF for the current session in your individual campaign to update the coordinate, velocity, and abbreviation file. If your actual campaign is located on a disk referred by another variable than the default location ${P} (e.g., ${Q}) you have to make sure that this environment variable is listed in the "${U}/OPT/PPP_???/MENU_VAR.INP" file in each option directory used by PPP.PCF (use menu item "BPE > Edit single menu/program input file" to edit these files). The names of the input files of the processing are defined in the variable section of the PPP.PCF. They can be adapted in the panel "BPE 4: Server Variables Sent to Client" which is displayed when you start the BPE: V_RNXDIR: Directory with the RINEX files to be processed V_CRDINF: Project-related basename of the basic files to be used for the Tectonic plate assignment (default extension PLD -- generated in step 9), coordinate (default extension CRD), velocity (default extension VEL), and abbreviation table (default extension ABB). The CRD, VEL, ABB file may exist in ${D}/REF54 but they can also be created. V_STAINF: Station information file (the project-related filename is recommended -- from step 7); blank if no station information file is used (equipment records from the RINEX files are directly used) V_CRXINF: Accepted station information inconsistencies (project-related filename -- from step 8) or blank if no such file is needed V_BLQINF: Ocean tidal loading corrections if available (project-related filename -- from step 12) V_ATLINF: Atmospheric tidal loading corrections if available (project-related filename -- from step 13) It is important that the variable V_UPD is set to "Y" to allow an update of the coordinate, velocity, and abbreviation file in the reference file directory of the DATAPOOL. After running the BPE a processing protocol file OUT/PPP_yyyyssss.PRC is available. Information on its expected content is given in the corresponding README-file (Menu > Help > Readme > EXAMPLE BPE). In the STA-directory of your campaign the following files result from the PPP.PCF: STA/PPPyyssss.CRD: coordinate results for the epoch of the observations STA/REFyyssss.CRD: coordinate results for the epoch given in the BPE server variable V_REFEPO (e.g., 2010-01-01) the NUVEL-1A velocities if a PLD-file was given STA/APRyyssss.VEL: NUVEL-1A velocities for all stations included in the PPP. STA/(V_CRDINF).CRD: Content of STA/IGB14_R.CRD plus the coordinate results for all new stations STA/(V_CRDINF).VEL: Content of STA/IGB14_R.VEL plus the NUVEL-1A velocities for all new stations STA/(V_CRDINF).ABB: New or updated abbreviation table If you have allowed the BPE to update the files in the reference directory (V_UPD = "Y") the three files STA/(V_CRDINF).CRD, STA/(V_CRDINF).VEL, and STA/(V_CRDINF).ABB are copied to ${D}/REF54 directory and are ready for further use. 11.The station name abbreviation table is created or updated automatically in the PPP.PCF. The four and the two-character abbreviations for all stations are unique. You may inspect this file using the menu item "Campaign > Station files > Abbreviation table" or with your favorite text editor. If you change any value, please make sure that the abbreviations are still unambiguous for all stations. 12.Use the web-service at http://www.oso.chalmers.se/~loading/ to get the table of the ocean loading coefficients for your sites. The coordinates from the "${D}/REF54/(project-related filename).CRD" may be copied into the input field of the web-page (for efficiency, select only those sites where you have no coefficients yet). For the GNSS analysis you need the vertical and horizontal displacement. No corrections for the center of mass motion have to be applied. The ocean loading file is sent by e-mail in the BLQ-format to you. You have to save these information in a file with a project-related name and the extension "BLQ" in ${D}/REF54-directory. (See also "menu > Help > Readme > Customizing Models > Ocean tidal loading (BLQ)" for further information.) You may introduce the BLQ-file into the PPP (step 10) if you already have the corrections for your sites. In this case the corrections will be applied. In the protocol the stations are listed where no ocean loading corrections are available. The BLQ-file is not mandatory for the PPP. You can create this file later. It is recommended to apply the corrections for the ocean loading displacement at least for the final processing step of GPSEST. 13.Generate a atmospheric tidal pressure loading table using the menu item "Service > Coordinate tools > Extract atmospheric tidal loading coefficients". The corrections need to be consistent if you plan to apply atmospheric non-tidal pressure loading corrections. Otherwise you should extract the information from the grid file "${X}/GEN/s1_s2_def_ce.dat" (CoF: Center of Figure related corrections). The input coordinate file is the project-related coordinate file resulted from PPP.PCF; the result file should have the same name but with the extension ATL. S1/S2 center of mass corrections should be added consistently from the RAY_PONTE model. (See also "menu > Help > Readme > Customizing Models > S1/S2 Atmospheric tidal loading (ATL)" for further information.) Your campaign is now ready for any further analysis of your data. You can follow the tutorial from the Bernese Introductory Course available on the installation CD-ROM or online from the Bernese GNSS Software home page. It gives cookbook-like instructions for a manual processing of a regional network. Further information are available from the online help. It is intended as a guideline for the processing, especially for the new features of the Bernese GNSS Software, version 5.4, and their usage. D. SETUP AN AUTOMATED PROCESSING ================================ The BPE is the core tool for the automated processing of GNSS data using the Bernese GNSS Software. After going through step C. you are ready to run the example BPEs on your own data. As long as you still using the same structure of the DATAPOOL and SAVEDISK areas you can manage most the adaptions by the BPE server variables. If you start to change the structure (e.g., putting orbits in yearly subdirectories) you need to adapt the copy scripts at the beginning of each BPE accordingly (XXX_COP where XXX is an identifier for each BPE, e.g., PPP or CLK). All result files are only copied by the save scripts of the BPE into the SAVEDISK area (XXX_SAV with XXX again as the identifier for each BPE). Of course you are invited to adapt the example BPEs to your own needs. Do not forget to include new files that are created in your adapted BPE in the deletion script (XXX_DEL again stands XXX for the BPE identifier). We recommend to go through the panels (at least of the main programs) for the provided example BPEs (menu: "BPE > Edit PCF program input files") to become familiar with the options and features. This is in particular important for user of previous versions of the Software because the version 5.4 contains a lot of new features that might be useful also for your applications. We recommend to inspect the online help for a detailed description of all input fields. Starting BPE without menu: like in previous versions, it is also possible to start the BPE without going through the menu. We have prepared a Perl module, which is necessary for this. Also, you can find the Perl script rnx2snx_pcs.pl in the directory %U%/SCRIPT, which provides an example for the actual script used to run the BPE for the RNX2SNX example. This script can be called from the command line, or from any job scheduler. Note, that we highly recommend to use Perl for such tasks, although you could also use shell/batch scripts for this purpose. E. HOW TO PROCEED IN CASE OF AN ERROR IN THE BPE? ================================================= - Check that the campaign is set correctly. - Check that the session is set correctly. - Check the BPE output file ("^Output"-button). - Check protocol and log files from the BPE. These files are written into the BPE subdirectory of the campaign. Their filename include task-ID, session year and session, PID, and sub-PID. Protocol files (default extension PRT) provide information on the process started as well as warnings and error messages from programs executed in the scripts. Log files (default extension LOG) give the output from scripts and programs that is written to the standard output and to the error output. Debug output written in the scripts appears in the log file. - Check whether the CPU keywords you use in your PCF are available (MAXJOB > 0). - Make sure that your PCF is not in the list of "Suspended processes" (second panel in the CPU file "BPE > Edit CPU file"). The online help gives more insight about the algorithm behind. - Check that the corresponding jobsubmit commands are correct: WINDOWS-platforms: The line must be the default line reported in the online help as well as in the distributed CPU file (${PAN}/USER.CPU). UNIX-platforms: Take your command line from the CPU-file, replace by "ls", by "-l", and by "ls.out". Execute the command. It has to run in the background, without any further input from keyboard (e.g., entering of a password to get access to a remote host). The answer of the "ls -l" command is expected to be written into the "ls.out"-file. Check the command also with a "ls"-command for a file which does not exist to make sure that the error output is directed into the "ls.out"-file. - Reset the CPU-file (menu item "BPE > Reset CPU file"). This action sets the entries for the number of running jobs to zero. This is always required after a BPE job has been killed. The reset of the CPU file does no harm, even if executed while a BPE is running. ================================================================================