User Instructions
and Technical Guide
OPUS Projects
98 |
P a g e
NOAA |
National Geodetic Survey
of the processing setup. The OPUS Projects Team will respond with additional questions or
confirmation that the problem has been fixed.
Q.
I processed a session, but received a message saying "Unable to retrieve or
create a precise
ephemeris at this time." What should I do?
A.
This is a symptom of a temporary drop in communication between OPUS and CORS. Wait a few
minutes and try again.
Q.
Why didn't OPUS Projects add the CORS named "abcd" into my project as I instructed?
A.
The most like reason is that a CORS data file doesn't exist for that particular day. Check the
availability of the CORS site "abcd" on the day in question by looking here:
http://www.ngs.noaa.gov/CORS/
. If you find the file there please contact the OPUS Projects Team with
your concern.
Q.
The Manager web page has appeared, but no marks are shown and a popup has appeared
saying: "Stop running this script? A script on this page is causing the browser to run slowly." What
should I do?
A.
Your project is probably large or complex thereby requiring many seconds to display the web
page. This is more common in older versions of
Internet Explorer, but can happen with any browser.
Click "No" as often as needed until the web page fully displays. Projects this complex may result in slow
browser response.
Q.
I just uploaded, in my haste, a file that processed fine but I put in the wrong ANTCAL code and
wrong ARP height. How can I change or remove this out of my project?
A. There are several options:
1) Upload the file again using the correct ANT name and ARP height. The re-uploaded file and its information will
overwrite the existing file and information.
2) Navigate to the mark page as the project manager. Look for the Mark occupation table below the
description. Most of the fields in that table are editable. Change the ANT name and ARP height there.
The OPUS solutions
will remain, but the updated information will be used in all subsequent processing in
your project.
3) Navigate to the mark page as the project manager. Look for the Mark occupation table below the
description. To the upper-right of that table is a button labeled "Manage Data Files." Click that button
and a popup window appears listing the data files for that mark. Find the offending data file in the
table, click Removed and Apply Changes. But then you have to upload the file again if you still want to
use it, so see (1) or (2).
OPUS Projects
User Instructions and Technical Guide
NOAA |
National Geodetic Survey
P a g e
|
99
Appendix B.
Using Various Internet Browsers
B.1
Print reports displayed by the project web pages
The reports displayed using the Show File control can be printed using instructions specific to the
browser being used. The following may be helpful printing.
B.1.1 Printing with Google Chrome™
With Google Chrome™, there is an extension to enable printing a text box frame, i.e. the report text, to
a local printer (Figure B.1), but this has not been tested. Without this extension to the browser, the
remaining option is to copy and paste the report text into a file.
Figure B.1 - Printing with Google Chrome™
User Instructions and Technical Guide
OPUS Projects
102 |
P a g e
NOAA | National Geodetic Survey
Appendix C.
Session Solution and Network Adjustment Summary Report
The first section is an overall summary of the solution. An example report is shown in the shaded (gray)
area. Artificial breaks were inserted into this example to make possible a description of the report in
this format. The breaks are indicated using vertical ellipses. Annotations for each section follow that
section, are identified by numbers on the far right and the corresponding text is highlighted.
1.
Scaling of the formal uncertainties reported.
2. Processing program name and version.
3. The standard error of unit weight should be 1, but values between 0.1 and 1.1 are acceptable. No
rescaling of the coordinate sigmas used in the constraints or assumed uncertainties of the observations
is performed as part of the solution. As a result, the standard error of unit weight is dependent upon
these and other a priori information used in the processing and is rarely exactly 1. Experience has shown
that values nearer 0.1 should be expected when TIGHT constraints are used; values will be nearer 1.0
when NORMAL or LOOSE constraints are used. Values for the standard error of unit weight outside this
range are not absolutely indicative of a processing problem, but do imply that additional evaluation of
the solution is warranted.
4. Smaller is better. The project preference should supersede the following, but an overall RMS ≤ 2 cm is
recommended because experience indicates that a value in this range is consistent with having no
serious data processing problems. Values > 2 cm are not absolutely indicative of a processing problem,
but do imply that additional evaluation of the solution is warranted.
5. As used in OP, PAGES shifts from using L1-only data for shorter baselines to the ionosphere-free
combination for longer baselines. This helps insure that the lowest noise, and therefore conventionally
preferred, observable is being used regardless of baseline length. The baseline length for this transition
is at approximately 7 km.
6. The satellite elevation mask chosen in OP processing. This may differ from that set in the receiver.
7. The neutral atmosphere (tropo) correction parameterization interval and style.
NGS OPUS PROJECTS SESSION SOLUTION REPORT
===========================================
All coordinate accuracies reported here are 1 times the formal
uncertainties from the solution. For additional information:
geodesy.noaa.gov/OPUS/Using_OPUS-Projects.html#accuracy
These positions were computed without any knowledge by the National
Geodetic Survey regarding the equipment or field operating procedures used.
USER: your.name@your.address
SOLUTION SOFTWARE: page5(1203.19)
SOLUTION DATE: 2012-03-21T15:20:52 UTC
STANDARD ERROR OF UNIT WEIGHT: 0.722
TOTAL NUMBER OF OBSERVATIONS: 7048
TOTAL NUMBER OF MARKS: 2
NUMBER OF CONSTRAINED MARKS: 1
OVERALL RMS: 1.4 cm
START TIME: 2011-10-25T12:31:30 GPST
STOP TIME: 2011-10-25T18:01:00 GPST
PROGRAM OPERATION:
FULL RUN
FREQUENCY: L1-ONLY TO ION-FREE [BY BASELINE LENGTH]
OBSERVATION INTERVAL: 30 s
ELEVATION CUTOFF: 15 deg
TROPO INTERVAL: 1800 s [STEP-OFFSET PARAMETERIZATION]
DD CORRELATIONS: ON
⋮
1
2
3
6
7
4
5