ADJUST_supplemental.txt 05/18/2020 ADJUST SUPPLEMENTARY DOCUMENTATION Introduction This document describes the current version of ADJUST and contains changes from the original NOAA Technical Memorandum NOS NGS-47, "ADJUST: The Horizontal Observation Adjustment Program" (Milbert and Kass, 1987; reprinted 1990 and 1993). ---------------------------------------------------------------------- ---------------------------------------------------------------------- Program Execution ---------------------------------------------------------------------- The following example will demonstrate a sample execution of program ADJUST. All files can have any filenames. The example assumes that the program is stored in a directory named ADJUST on a PC. However, the program has both Unix and PC executables and may be stored in any directory on any drive. Enter "adjust" on the command line and respond to the queries for the filenames (filename length is limited to 80 characters): C:\ADJUST>adjust WELCOME TO ADJUST VERSION 6.4.3 DATE(ccyy/mm/dd) 2020/05/14 ENTER INPUT BLUE BOOK FILENAME (DEFAULT='BBOOK'): bfile ENTER ADJUSTMENT FILE FILENAME (DEFAULT='AFILE'): afile ENTER GPS FILE FILENAME (DEFAULT='GFILE'): gfile ENTER THE DESIRED NAME FOR THE PRINTED OUTPUT : (Make sure it is not an existing filename.) adjust.out ENTER THE DESIRED NAME FOR THE OUTPUT BLUE BOOK FILENAME : (Make sure it is not an existing filename.) bfile.out ---------------------------------------------------------------------- ---------------------------------------------------------------------- ADJUST Changes ---------------------------------------------------------------------- 2020/05/17 Updated for IGb14 as new G-file coordinate reference system code = 37 (transformation parameters identical to IGS14 and ITRF2014). Added error handling for undefined coordinate reference system code in G-file. ---------------------------------------------------------------------- ---------------------------------------------------------------------- GFILE Changes ---------------------------------------------------------------------- 2020/05/17 Annex N lists 1 new code: 37 -– IGb14. Used by NGS from 5/17/2020 until the present. Update of IGS14, also aligned with ITRF2014 at epoch 2010.0. 2018/02/01 Annex N lists four new codes: 33 -– IGS14. Used by NGS from 1/29/2017 through 5/16/2020. Aligned with ITRF2014 at epoch 2010.0. 34 -- NAD 83 (2011) epoch 2010.00 (current). Applies to NAD 83 (2011/2007/CORS96/FBN/HARN) realizations referenced to the North America tectonic plate at any epoch. Defined by NGS in 1996 and code used from 1/29/2017 through present. 35 -- NAD 83 (PA11) epoch 2010.00 (current). Applies to NAD 83 (PA11/PACP00) realizations referenced to the Pacific tectonic plate at any epoch. Defined by NGS in 2003 and code used from 1/29/2017 through present. 36 -- NAD 83 (MA11) epoch 2010.00 (current) Applies to NAD 83 (MA11/MARP00) realizations referenced to the Mariana tectonic plate at any epoch. Defined by NGS in 2003 and code used from 1/29/2017 through present. 2016/06/06 The I record - Name of Antenna Pattern File was expanded: cc 2-21 Previous changes include (1) The B record or Group Header Record number of vectors field cc 26-27 only allows a maximum of 99 vectors per session. For a number of vectors larger than 99, leave this field blank and ADJUST will count the number of C or F vector records for the session. A maximum of 230 vectors per session is allowed. (2) The B record or Group Header Record has a project id in columns 91-104 (new for version 5.2). ---------------------------------------------------------------------- ---------------------------------------------------------------------- AFILE Changes ---------------------------------------------------------------------- This section contains a summary of the adjustment option file (AFILE) records. Changes from the previous ADJUST options are indicated. In several cases, a certain type of option record must precede another type of option record if they are both used in a given AFILE. If the option records are ordered alphabetically then all ordering will be correct. 2016/06/06 The MM record was expanded to include the ability to write non-shifted constraints to the output B-file CODE TYPE OF RECORD ----------------------------------------------------------------- ** Comment Record AA Ellipsoid Parameter Record BB Bypass Record CA Constrained Azimuth Record CC Coordinate Constraint Record CD Constrained Distance Record CH Constrained Height Difference Record CZ Constrained Zenith Distance Record DD Dimensionality Record EE Default Mean Sea Level Elevation Record GG Default Geoid Height Record HD Default Height Adjustment Record HC Control Point Height Adjustment Record II Iteration Record MM Adjustment Mode Record NL Network and Local Accuracy Record PP Print Output Record QQ Accuracy Computation Record RR GPS and Doppler Rotation Parameter Record SS Auxiliary Parameter Indicator and Constraint Record VS Scales Standard Deviation of GPS Residuals Record VV Variance Factor Indicator and Constraint Record ** - Comment Record: Comment records are ignored after they are read by the ADJUST adjustment program. They ONLY make the option file easier to read. They will be listed in the output with the other AFILE records. ADJUST assumes any option file record that starts with two asterisks "**" or two blanks " " is a comment. ************************************************************ Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 ** or blank 03-80 Anything. Any option record with columns 1 and 2 containing two asterisks or two blanks is treated as a comment and ignored. Totally empty lines are also ignored. ************************************************************ AA - Ellipsoid Parameter Record: The Ellipsoid Parameter record specifies new value(s) for the semi-major axis of the ellipsoid and/or for the square of the eccentricity of the ellipsoid. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 AA 03-12 Semimajor axis, unit of meters default 6378137. meters (real) 13-30 Square of Eccentricity, default 0.0066943800229034156 (real) 31-80 Reserved ************************************************************ BB - Bypass Record: The Bypass record directs the adjustment program to ignore certain types of observations. Horizontal directions (*20* and *22* Blue Book records), horizontal angles (*30* and *32* records), zenith distances (*40* and *42* records), distances (both *52* and *54* records), astronomic azimuths (*60* records), GPS observations (GFILE), and Doppler observations (DFILE) may be bypassed. Blue Book observations which are to be ignored are printed (but not given observation numbers) in the BLUE BOOK section of the output. If GPS observations are to be ignored, the GPS observation section of the output is not printed. Similarly if Doppler observations are to be ignored, the Doppler observation section of the output is not printed. Bypass records for a particular observation type also cause other AFILE options to be ignored. For example, if the AFILE has a SS record for observation type 52 (mark-to-mark distances) and a BB record with its sixth column non-blank, then this SS record is ignored. For this reason, the BB record MUST precede any DD, RR, SS, TT, and VV records. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 BB 03-03 Non-blank to bypass horizontal directions.(character) 04-04 Non-blank to bypass horizontal angles. (character) 05-05 Non-blank to bypass zenith distances. (character) 06-06 Non-blank to bypass distances. (character) 07-07 Non-blank to bypass astronomic azimuths. (character) 08-08 Non-blank to bypass GPS observations. (character) 09-09 Non-blank to bypass Doppler observations. (character) 10-80 Reserved ************************************************************ CA - Constrained Astronomic Azimuth Record: A Constrained Azimuth record creates a constraint for the azimuth angle between two stations. The CA records are ignored for one- dimensional adjustments. If CD parameters are being calculated, the constrained azimuths are applied at the reference time. That is, CA records do not give azimuths that are invariant across time. To do that put the same pseudo azimuth observations at two different times in the Blue Book (*60* records). This record has been changed to allow SSNs of four digits rather than three. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 CA 03-06 Standpoint Station Serial Number (integer) 07-10 Forepoint Station Serial Number (integer) 11-13 Reserved 14-16 Degrees Azimuth (integer) 17-18 Minutes Azimuth (integer) 19-22 Seconds Azimuth, units of 0.01 arc seconds (integer) 23-27 Azimuth Standard Deviation, units of 0.01 arc seconds, default of 0.01 arc seconds (integer) 28-80 Reserved ************************************************************ CC - Constrained Coordinate Record: A Constrained Coordinate record specifies that a station is a control point, that its coordinate(s) are constrained or "held fixed" during the adjustment. Only those coordinates which have values given on a CC record are constrained - i.e. there is no default for a constrained coordinate value. Standard deviations for any or all of the constrained coor- dinates on the record can also be specified by the CC record. The units for the standard deviations of the lati- tudes and longitudes as well as for heights are millimeters. The default is 0.1 millimeter for all coordinates. Latitudes and longitudes on CC records are not used for the constraints in one dimensional adjustments and elevations on CC records are not used for constraints in two dimensional adjustments. The elevation constraint for a 2.5 dimensional adjustment should be on one of the 3 dimensional stations (i.e. a station with a GPS or a Doppler observation at it). A blank elevation code indicates it is an orthometric height and a E code indicates it is a ellipsoidal height. This record follows the format of the Blue Book *80* record and has been changed to allow SSNs of four digits rather than three. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 CC 03-10 Reserved 11-14 Station Serial Number (integer) 15-20 Latitude Standard Deviation, units of cm default 0.01 cm (real) 21-26 Longitude Standard Deviation, units of cm default 0.01 cm (real) 27-32 Height Standard Deviation, units of cm default 0.01 cm (real) 33-44 Reserved 45-46 Degrees Latitude (integer) 47-48 Minutes Latitude (integer) 49-55 Seconds Latitude, units of 0.00001 arc sec. (integer) 56-56 Latitude Code N -- POSITIVE NORTH (default) S -- positive South 57-59 Degrees Longitude (integer) 60-61 Minutes Longitude (integer) 62-68 Seconds Longitude, units of 0.00001 arc sec.(integer) 69-69 Longitude Code E -- positive East W -- POSITIVE WEST (default) 70-76 Height, units of millimeters (integer) 77-77 Height Code E ---- ellipsoidal height blank -- orthometric height 78-80 Reserved ************************************************************ CD - Constrained Distance Record: A Constrained Distance record creates a constraint for a mark-to-mark distance between two stations. This record is used in 1, 2, 2.5, and 3 dimen- sional adjustments and thus, never ignored. This record has been changed to allow SSNs of four digits rather than three. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 CD 03-06 Standpoint Station Serial Number (integer) 07-10 Forepoint Station Serial Number (integer) 11-22 Mark-to-Mark Distance, units of 0.1 mm (integer) 23-27 Distance Standard Deviation, units of 0.1 mm, default of 0.1 mm (integer) 28-80 Reserved ************************************************************ CH - Constrained Height Difference Record: A Constrained Height Difference record creates a constraint for the difference between the heights of two stations. If the orthometric heights of both endpoints are adjusted, then the height difference given on this record is con- sidered to be orthometric. If the geoid heights of both endpoints are adjusted, then the height difference given on this record is considered to be an undulation difference. Lastly, if the orthometric height of one endpoint is adjusted while the geoid height of the other endpoint is adjusted, then the height difference given on this record is considered to be an ellipsoidal height difference. See the HC record for more information. CH records are ignored for two dimensional adjustments that are not 2.5 dimensional adjustments. For 2.5 dimensional adjustments, the height difference will be constrained only if both stations are dual height stations. This record has been changed to allow SSNs of four digits rather than three. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 CH 03-06 Standpoint Station Serial Number (integer) 07-10 Forepoint Station Serial Number (integer) 11-22 Height Difference, units of 0.1 mm (integer) 23-27 Height Standard Deviation, units of 0.1 mm, default of 0.1 mm (integer) 28-80 Reserved ************************************************************ CZ - Constrained Zenith Distance Record: A Constrained Zenith Distance record creates a constraint for the difference between the zenith angles of the two stations. CZ records are ignored for two dimensional adjustments that are not 2.5 dimensional adjustments. For 2.5 dimensional adjustments, the zenith distance will be constrained only if both stations are dual height stations. This record has been changed to allow SSNs of four digits rather than three. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 CZ 03-06 Standpoint Station Serial Number (integer) 07-10 Forepoint Station Serial Number (integer) 11-13 Reserved 14-16 Degrees Zenith (integer) 17-18 Minutes Zenith (integer) 19-22 Seconds Zenith, units of 0.01 arc seconds (integer) 23-27 Zenith Standard Deviation, units of 0.01 arc seconds, default of 0.01 arc seconds (integer) 28-80 Reserved ************************************************************ DD - Dimensionality Record: The Dimensionality record controls the number of spatial dimensions in which the program adjusts. ADJUST may adjust in 1, 2, 2.5, or 3 dimensions. If this record is not included in the AFILE, then the adjustment is three dimensional. There is no default if this record is included. If the adjustment is two dimensional, then any zenith distances (*40* and *42* records) in the BBOOK file are ignored. Similarly, if the adjustment is one dimensional, then horizontal directions (*20* and *22* records), horizon- tal angles (*30* and *32* records), and astronomic azimuths (*60* records) are ignored. In a two dimensional adjustment, a constraint with a stan- dard deviation of 0.001 meters is created for the elevation of each station. Similarly, in a 2.5 dimensional adjust- ment, a constraint with a standard deviation of 0.001 meters is created for the elevation of each station that does not have a 3 dimensional observation (GPS or Doppler) at it. The values for the elevations are obtained from the Blue Book *86* record orthometric height. In a one dimensional adjustment, constraints with standard deviations of 0.001 meters are created for the latitude and longitude of each station. The values for the latitudes and longitudes are obtained from the *80* record. These constraints are created before any other constraints or observations. Latitude and longitude constraints on CC records are ignored in one dimensional adjustments. Similarly, elevation con- straints on CC records are ignored in two dimensional adjustments. A one dimensional adjustment of the same data takes less time and less internal storage than a two dimensional adjustment which takes less time and internal storage than a three dimensional adjustment. Similarly, a 2.5 dimensional adjustment of the same data takes less time and internal storage than a 3 dimensional adjustment but more than a 2 dimensional adjustment. Thus, using a smaller dimension for the adjustment can help if space, and to a lesser extent time, are in short supply. This record has been changed to allow for a 2.5 dimensional adjustment. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 DD 03-03 Dimensions of adjustment, no default (integer) 04-05 ".5" for a 2.5 dimensional adjustment - ignored if column 3 is not a "2". 06-80 Reserved EE - Default Mean Sea Level Elevation Record: The Default Mean See Level Elevation record specifies a value for the default orthometric height of the adjustment. The default orthometric height is the orthometric height for any station which does not have an elevation in columns 17-23 of its Blue Book *86* (station location) record. This record has not been modified. ************************************************************ Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 EE 03-09 Default Orthometric Elevation, units of mm. default 0.0 (integer) 10-80 Reserved ************************************************************ GG - Default Geoid Height Record: The Default Geoid Height record specifies a value for the default geoid height in the adjustment. The default geoid height is used for all stations which do not have a Blue Book *86* record geoid height. This record has not been modified. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 GG 03-09 Default geoid height, units of mm., default 0. (integer) 10-80 Reserved ************************************************************ HC - Control Point Height Adjustment Record: A Control Point Height Adjustment record specified which height (the orthometric or the geoid) is to be adjusted for a control point (constrained location). All control points which do not have a HC record have their height adjusted as specified by the HD record (if there is one). If there is no HD record, then their orthometric height is adjusted. This record has been changed to allow SSNs of four digits rather than three. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 HC 03-03 Height Indicator E -- ADJUST ORTHOMETRIC HEIGHTS (default) G -- ADJUST GEOID HEIGHTS 04-07 Station Serial Number (integer) 08-80 Reserved ************************************************************ HD - Default Height Adjustment Record: A Default Height Adjustment record is used to select whether the orthometric or the geoid heights of the stations are adjusted. Thus it determines if the CC record column 70-76 heights are constrained as orthometric or geoid heights. If the HD record is not present, the orthometric heights will be adjusted. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 HD 03-03 Height Indicator E -- ADJUST ORTHOMETRIC HEIGHTS (default) G -- ADJUST GEOID HEIGHTS 08-80 Reserved ************************************************************ II - Iteration Record: The Iteration record options control the conditions for ceasing to iterate the adjustment solution and what is printed after the iterations are completed. After the adjustment program stops iterating it either aborts or continues to create the final sections of the output If the adjustment program is converging slowly it stops iterating after it has iterated the maximum number of iterations specified by this record. An option on this record may be used to control whether the program aborts immediately or continue through the final output sections. Printing a (possibly incorrect) output can be very useful for determining why the solution is converging slowly. The absolute value of the maximum allowable normalized residual may be changed with this record. If the absolute values of any of the residuals are larger than the maximum allowable normalized residual, the program aborts. The absolute value of the minimum normalized residual printed with an warning message may also be changed with this record. If on this record the user specifies the value 9999 for the maximum allowable residual, then it is changed to a MUCH larger number. This action effectively eliminates the possibility of large residuals causing the program to abort. Similarly, if the user specifies the value 999 for the minimum absolute normalized residual to be printed with a warning message, then it is also changed to a MUCH larger number - which causes no warning messages for large residuals. The adjustment program normally does not abort if the variance of unit weight is increasing, that is, if the solution is diverging. This option may be changed with this record. With this option and the maximum iterations options adjust- ment results may still be printed before the program aborts. This can be very useful for determining why the solution is not converging properly. The parameter adjustment is converged if BOTH the RMS change in the station locations AND the minimum number of iterations has been reached. If the parameter adjustment is converged and if variance factors are to be estimated, then the variance factor(s) are iterated (see the VV record). A option writes out the adjusted parameters to a new AFILE and a new Blue Book at the end of each iteration. In the updated AFILE the RR (GPS and Doppler Rotation Parame- ter) record, the SS (Auxiliary Parameter Indicator and Con- straint) record, and the VV (Variance Factor Indicator and Constraint) record have their values updated. On the II (Iteration) record the maximum number of iterations is decreased by the number of iterations already completed. In the updated Blue Book, the *80* records are updated. The latitude and longitude are updated in 2, 2.5 and 3 dimensional adjustment. The height is updated in a 1 or 3 dimensional adjustment. And, the ellipsoidal height is updated in a 2.5 dimensional adjustment. This record has been modified to allow updated files to be written at the end of each iteration. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 II 03-04 Maximum number of iterations, default 5 (integer) 05-08 Maximum allowable normalized residual, units of sigma, default 1200 (integer) 09-11 Minimum printed normalized residual, units of sigma, default 600 (integer) 12-17 RMS station coordinate convergence tolerance, units of millimeters, default 3 (integer) 18-18 Display results for slowly converging or for diverging solution N -- DO NOT DISPLAY (default) Y -- Display 19-19 Create adjusted option File (AFILE) and adjusted data (Blue Book) File at the end of each iteration N -- DO NOT CREATE ADJUSTED FILES (default) Y -- Create adjusted data file 20-26 Adjusted Option File Name, default is "NEWAF" 27-80 Reserved ************************************************************ MM - Adjustment Mode Record: The Adjustment Mode record controls the mode of adjustment, that is to not iterate (Mode 0) or what should be done after convergence (Modes 1-3). This record also controls whether or not the standard deviations of the residuals, parameters, and station locations values should be scaled by the a-posteriori standard deviation of unit weight. Regardless of the option indicated on this record, the standard deviations will not be scaled, if the a-posteriori standard deviation of unit weight is less than 0.01. The next option on this record controls whether or not a new Blue Book file should be created containing the adjusted positions. If it is to be created, the file name is specified by the user prompt. Note the file name is no longer obtained from the MM record. Note that the new option on the II record that writes out updated AFILE and Blue Book files at the end of each iteration will force a new Blue Book to be written. That option will use the new Blue Book file name given by the user prompt. This record is now used for three new options. The first is to determine if the adjustment will be aborted if the solution becomes singular. If the adjustment is not aborted, the singular parameter(s) will be constrained to its initial value. The last two options on this record control whether or not an adjusted position file should be created. Note that the default for this option is not the same as it is in the BIGADJUST program. This file will contain all the information on the adjusted positions of the stations that are given in the adjusted position section of the output, but the information is formatted with one line of informa- tion per station. This file can be used as an input file for graphic plots and if this file is to be created, a name for the file can be specified. There is not room here to explain in detail what each adjustment mode does. A complete explanation is in the documentation. Briefly however; Mode 0 - This is a simulation mode. There are no itera- tions. This mode is normally used for network design with simulated data. Mode 1 - The standard deviations of the residuals are assumed to be the same as the standard deviations of the observations. Also, the standard deviations of the parame- ters and station locations are not calculated. Mode 2 - Same as Mode 1 except standard deviations of param- eters and station locations are calculated. Mode 3 - Same as Mode 2 except standard deviations of resi- duals are calculated. This record has been modified to add parameters. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 MM 03-03 Mode indicator 0 -- Simulation, bypass columns 04-12 of this record 1 -- Compute quasi-normal residuals (default) 2 -- Compute quasi-normal residuals and inverse 3 -- Compute normal residuals and inverse 04-04 Post-adjustment indicator N -- Do not scale standard deviations by a-posteriori standard deviation of unit weight (default) Y -- Scale standard deviations by a-posteriori standard deviation 05-05 Create Adjusted Data (Blue Book) File N -- Do not create adjusted data file (default) Y -- Create adjusted data file 06-06 Output control stations in b-file (New in ADJUST v6.4.1) Y -- Write non-shifted constraints to output b-file N –- Write shifted constraints to output b-file (default) 07-12 Reserved 13-13 Abort if solution is singular Y -- ABORT IF SINGULAR (default) N -- Do not abort if solution is singular 14-14 Create Adjusted Position File N -- DO NOT CREATE ADJUSTED DATA FILE (default) Y -- Create adjusted data file 15-21 Adjusted Position File Name, default is "ADJPOS" 22-80 Reserved ************************************************************ NL - Network and Local Accuracy Record: Computes and writes network and local accuracies to the Blue Book and to the ADJUST output file. The network and local accuracies are written to the *91* and *92* records, respectively, of the output Blue Book file as standard deviations in latitude, longitude, and ellipsoid height (in centimeters) along with the horizontal correlation coefficient. The network and local accuracies are also written to the ADJUST output file as horizontal and ellipsoid height values (in centimeters) at the 95% confidence level. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 NL 03-03 Scale accuracies by standard deviation of unit weight Y -- Scale accuracies N -- Do not scale accuracies ************************************************************ PP - Print Output Record: The Print Output record contains the options for controlling what is listed in the output and with what format. A new fourth option has been added in columns 06-08 and the fields for the remaining options have been shifted to the right. The first option controls whether all of the Blue Book records are listed on the output or whether only the (non- rejected) observations are listed. Similarly, the second option controls whether all of the GFILE (GPS) records are listed on the output or whether only the (non-rejected) observations are listed. Normally all records should be listed. However, if one or the other of these files is very large and the output needs to be shortened, then these options could be used. The third option controls whether or not the constraints are listed in the output. Again, this option should be used ONLY if there are a very large number of constraints. If the constraints are not listed, then the only place that they appear in the output is in the residual section. Unless you know exactly what will be in the output, the GFILE, BBOOK, DFILE, and constraints should always be listed when some or all of the residuals are to be not listed. The fourth through the twelfth options control whether or not post-adjustment residuals of observations and con- straints are listed in the output. The fourth option specifies a residual output tolerance in units of 0.1 mm for GPS records. Only vectors in which at least one of the components residuals exceeds the specified criteria are printed. The fifth option specifies a normalized residual (residual divided by its standard deviation) output tolerance in units of 0.1 sigma for non-GPS records. The sixth through the eleventh options control the printing of each observation type and the twelfth controls the printing of the constraint residuals. Note that in Mode=0 post- adjustment residuals are never printed because they can not be calculated (see the MM option record). Normally, all post-adjustment residuals should be printed. Using this option does save some output space as residuals considered too small do not generate output records. However, the blank lines that would have been printed around the small residuals are still printed. This will often result in out- put that only consists of blank lines. It is also probably not a good idea to use these options along with any of the options that control the printing of Blue Book or G-file observations or of constraints as you may not have enough information to determine the cause of problems in the data. The thirteenth option is used to determine whether or not there should be a section in the output that groups the residuals around the intersection stations. The fourteenth option controls whether or not the shifts in the positions and heights of the stations are to be printed. These shifts are the difference between the final adjusted position and the position on the Blue Book *80* records and the differ- ence between the final adjusted height and the orthometric height on the Blue Book *86* records. Not listing these shifts might be used when the station locations on the *80* records are poor. This might occur, for instance, if the station locations are from the NAD27 coordinate system and the constraints are from the NAD83 coordinate system. The fifteenth option controls whether or not the Googe numbers are to be printed. The Googe numbers are always between zero and one. In the adjustment program they deter- mine at which parameters the solution breaks down. A Googe number may be considered a measure of the independence of a parameter. A Googe number of zero indicates that that parameter is completely dependent on the earlier parameters, while a Googe number of one indicates that that parameter is independent of the previous parameters. More information on Googe numbers may be found in the ADJUST documentation. The sixteenth option controls whether or not the full obser- vational summary is printed. This option may be used to shorten the output when a summary of what types of observa- tion were observed "from" or "to" each station is not of concern. If the full observational summary is not requested, the new version of Adjust will still print an abbreviated version. This version contains only stations that are constrained, undetermined, or no-check. The seventeenth option controls whether or not the adjusted positions are to be printed. This option may be used to shorten the output when the adjusted positions of the stations are not of concern. The eighteenth and nineteenth options control the printing of the Doppler data in a manner similar to the way the second and the eleventh options control the printing of the GPS data. That is, the eighteenth option controls whether all of the DFILE (Doppler) records are listed on the output or whether only the (non-rejected) observations are listed. Normally all records should be listed. The nineteenth option controls the printing of the Doppler residuals. Finally, the twentieth option controls the printing of GPS residuals rotated from the XYZ coordinate system to the local horizon system (north, east, up). This record has been modified. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 PP 03-03 Echo Blue Book File 0 -- ECHO ALL BLUE BOOK RECORDS (default) 1 -- Echo observations only 2 -- Echo large misclosures only 04-04 Echo G-Format File 0 -- ECHO ALL G-FORMAT RECORDS (default) 1 -- Echo observations only 2 -- Echo large misclosures only 05-05 Display Constraints Y -- DISPLAY CONSTRAINTS (default) N -- Do not display 06-08 Residual Output Tolerance, units of 0.1 mm (residual) for GPS 0 -- DISPLAY ALL RESIDUALS (default) 10 -- Display residuals for vectors in which at least one component's residual exceeds 1.0 mm 999 -- Display residuals for vectors in which at least one component's residual exceeds 99.9 mm 09-11 Residual Output Tolerance, units of 0.1 sigma (normalized residual) for non-GPS 0 -- DISPLAY ALL RESIDUALS (default) 10 -- Display residuals greater than or equal to 1.0 sigma (non-GPS normalized residuals). 999 -- Display no residuals (special 100,000,000) for non-GPS observations. 12-12 Display Direction Residuals Y -- DISPLAY DIRECTION RESIDUALS (default) N -- Do not display 13-13 Display Angle Residuals Y -- DISPLAY ANGLE RESIDUALS (default) N -- Do not display 14-14 Display Zenith Distance Residuals Y -- DISPLAY ZENITH DISTANCE RESIDUALS (default) N -- Do not display 15-15 Display Distance Residuals Y -- DISPLAY DISTANCE RESIDUALS (default) N -- Do not display 16-16 Display Astro-Azimuth Residuals Y -- DISPLAY ASTRO-AZIMUTH RESIDUALS (default) N -- Do not display 17-17 Display GPS Residuals Y -- DISPLAY GPS RESIDUALS (default) N -- Do not display 18-18 Display Constrained Residuals Y -- DISPLAY CONSTRAINED RESIDUALS (default) N -- Do not display 19-19 Display Residuals Grouped Around Intersection Sta. Y -- Display Residuals Grouped Around intersection stations N -- DO NOT DISPLAY (default) 20-20 Display Position Shifts Y -- DISPLAY POSITION SHIFTS (default) N -- Do not display 21-21 Display Position Googe Numbers Y -- DISPLAY GOOGE NUMBERS (default) N -- Do not display Googe numbers 22-22 Display Observational Summary Y -- DISPLAY OBSERVATIONAL SUMMARY (default) N -- Do not display Observational Summary 23-23 Display Adjusted Positions Y -- DISPLAY ADJUSTED POSITIONS (default) N -- Do not display 24-24 Echo D-Format File 0 -- ECHO ALL D-FORMAT RECORDS (default) 1 -- Echo observations only 2 -- Echo large misclosures only 25-25 Display Doppler Residuals Y -- DISPLAY DOPPLER RESIDUALS (default) N -- Do not display 26-26 Display N-E-U-H GPS Residuals Y -- DISPLAY N-E-U-H GPS RESIDUALS (default) (cc 14 = Y for cc 23 = Y) N -- Do not display 27-80 Reserved ************************************************************ QQ - Accuracy Computation Record: (No longer used as of ADJUST v6.4) An Accuracy Computation record directs that the adjusted value of the distance, azimuth, and vertical angle between two stations be calculated together with associated statistics indicating the accuracy of these adjusted quantities. These records are ignored if the Mode (from the MM Adjustment Mode record) is 1. The Station Serial Numbers of the two stations are required. If one (or both) are blank or are otherwise incorrect, a warn- ing message is printed but the program does not abort. The position shift values are needed for the computations of the accuracies. Thus, column 17 of the PP record (the Display Position Shifts option) must be left blank whether or not the adjusted positions are to be printed (column 20 of the PP record). The distances, azimuths, and vertical angles and their pro- pagated standard deviations are printed in the output sec- tion entitled "LENGTH RELATIVE ACCURACIES". The horizontal shift of the length and the accuracy fraction for the distance between the two stations are also listed. Note that the columns for the Station Serial Numbers on the QQ record corresponds to the columns for Station Serial Numbers on the Blue Book Horizontal direction (*20* and *22*) records. This record has been changed to allow SSNs of four digits rather than three and to include the classical and GPS sur- vey order type. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 QQ 03-10 Reserved 11-14 Station Serial Number, required (integer) 15-50 Reserved 51-54 Station Serial Number, required (integer) 55-80 Reserved ************************************************************ RR - GPS and Doppler Rotation Parameter Record: A GPS and Doppler Rotation Parameter record is used to obtain an esti- mate of the amount that the GPS or Doppler observations need to be rotated to best fit the classical horizontal data. This record should be used only if there is a very strong indication that the GPS or Doppler data is rotated. Each RR record creates a set of three auxiliary parameters for one observation type. The observations are grouped, for a particular observation type, by a range of dates. The defaults for the starting and ending dates are set to include all valid observation dates. There may be no over- lapping dates on rotation parameters for the same observa- tion type. The rotation parameters are automatically initialized to zero and, unlike the auxiliary parameters, may not be con- strained. This record has been modified to allow for Doppler observa- tions. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 RR 03-04 Observation Type 25 -- GPS (default) 99 -- Doppler 05-08 Start year, default 1801 (integer) 09-10 Start month, default 01 (integer) 11-12 Start day, default 01 (integer) 13-14 Start hour, default 00 (integer) 15-16 Start min., default 00 (integer) 17-17 Time Code, Start Time, default Z 18-21 End year, default 2099 (integer) 22-23 End month, default 12 (integer) 24-25 End day, default 31 (integer) 26-27 End hour, default 23 (integer) 28-29 End min., default 59 (integer) 30-30 Time Code, Start Time, default Z 41-80 Reserved ************************************************************ SS - Auxiliary Parameter Indicator and Constraint Record: An Auxiliary Parameter Indicator and Constraint record creates an auxiliary parameter. Auxiliary parameters are used to estimate (a) scale factors for GPS or Doppler data; (b) refraction parameters for zenith distances; or (c) scale factors for mark-to-mark distances. In this section, these will all be referred to as scale corrections. Each SS record creates an auxiliary parameter for one obser- vation type. The observations are grouped, for a particular observation type, by a range of dates. There is no default for the observation type. The defaults for the starting and ending dates are set to include all valid observation dates. There may be no overlapping dates on auxiliary parameters for the same observation type. The auxiliary parameters may be constrained or not con- strained to particular values. The initial values for the scale corrections may be specified with this record. If a standard deviation is included on this record, then the scale factor is constrained with that standard deviation. The auxiliary parameters estimate scale corrections for various types of observations from the observations within a given time period. In general, they should be included in an adjustment only after blunders and other non-systematic errors have been removed from the data set. However, if you suspect that the scale for a set of observations is large, the SS record may be included in the AFILE at any time. This record has been modified to allow for Doppler observa- tions. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 SS 03-04 Observation Type 25 -- GPS (scale) 40 -- Zenith distances (refraction) (also *42*) 52 -- Mark-to-mark distances (scale) (also *54*) 99 -- Doppler (scale) 05-08 Start year, default 1801 (integer) 09-10 Start month, default 01 (integer) 11-12 Start day, default 01 (integer) 13-14 Start hour, default 00 (integer) 15-16 Start min., default 00 (integer) 17-17 Time Code, Start Time, default Z 18-21 End year, default 2099 (integer) 22-23 End month, default 12 (integer) 24-25 End day, default 31 (integer) 26-27 End hour, default 23 (integer) 28-29 End min., default 59 (integer) 30-30 Time Code, Start Time, default Z 31-35 Scale Correction, units of .00000001 (.01 ppm), default 0 (integer) 36-40 Standard Deviation of Scale, units of .01 ppm, default 100 (integer) 41-80 Reserved ************************************************************ VS - Scales the Standard Deviation of GPS Residuals Record The presence of an VS record in the A-File scales the uncertainty of the horizontal and vertical components of the GPS vectors before beginning the adjustment. (new for version 4.32VF) Columns Descriptions and Defaults Type ------------------------------------------------------------ 01 02 VS 03-10 Factor by which to multiply horizontal components units of 0.000 11-18 Factor by which to multiply vertical components units of 0.000 19-31 Project Id ************************************************************ VV - Variance Factor Indicator and Constraint Record: A Variance Factor Indicator and Constraint record creates and, option- ally, constrains a variance factor. Variance factors esti- mate the variance component of a group of observations. If any variance factors are initialized, then the Mode is set to 3 regardless of the Mode indicated on the MM record (see the MM record). If all of the initialized variance factors are "fixed" then adjustment output appears as if no variance factors had been initialized (that is there are no variance factor iterations). The observations are grouped by observation types and dates. There is no default for the observation types. There may be no overlapping dates on variance factors of the same obser- vation type. The variance factors may be either absolutely constrained ("fixed") or freely determined ("free"). A constrained variance factor can be considered a rescaling of the vari- ance of the observations. The weight of an observation is 1.0 divided by the variance (the standard deviation squared) of the observation. A free variance factor is, in effect, calculating a scaling factor for the observation weights. The variance factors are used to estimate systematic errors or the proper a-priori variance for a group of observations. They should be used only after blunders and other non- systematic errors have been removed from the data set. Also they should be used only if the degrees of freedom is large with respect to the total number of parameters and stations coordinates (several times larger at least). If there are free variance factors then there are additional iterations in order to calculate variance factor values. The program first iterates to convergence on the parameters. After the parameter adjustment has converged the variance factor adjustment commences. The maximum number of itera- tions (see the II record) applies to the sum of the parame- ter adjustment iterations and the variance factor itera- tions. The minimum number of iterations applies only to the parameter adjustment iterations. This record has been modified with an observation type HU to Solve for variance factors for the horizontal and vertical components of the GPS observations. This is done by computing the sum of squares of the residuals for the horizontal and vertical observations separately, computing the redundancy numbers of the horizontal and vertical components of the observations, and estimating the standard deviation for each. This process is applied iteratively until the adjustment converges or the maximum number of iterations given on the II record is reached. (new for version 5.2) This record has also been modified to allow for Doppler observa- tions. Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 VV 03-04 Observation Type 25 -- GPS 20 -- Horizontal directions (also *22*) 30 -- Horizontal angles (also *32*) 40 -- Zenith distances (also *42*) 52 -- Mark-to-mark distances (also *54*) 60 -- Astronomic azimuths 99 -- Doppler HU (- GPS horizontal and vertical components (new for version 5.2) 05-08 Start year, default 1801 (integer) 09-10 Start month, default 01 (integer) 11-12 Start day, default 01 (integer) 13-14 Start hour, default 00 (integer) 15-16 Start min., default 00 (integer) 17-17 Time Code, Start Time, default Z 18-21 End year, default 2099 (integer) 22-23 End month, default 12 (integer) 24-25 End day, default 31 (integer) 26-27 End hour, default 23 (integer) 28-29 End min., default 59 (integer) 30-30 Time Code, Start Time, default Z 31-35 Initial Variance Factor, units of 0.01, default 100 (integer) 36-36 Absolute Constraint Y -- Impose Constraint N -- DO NOT CONSTRAIN (default) 37-80 Reserved ---------------------------------------------------------------------- ---------------------------------------------------------------------- DFILE (Doppler) Changes ---------------------------------------------------------------------- NOTE: As of version 6.2.3, ADJUST no longer prompts for Doppler observations (DFILES), although the functionality remains in ADJUST algorithms. ADJUST now adjusts Doppler observations. The Doppler observa- tions are inputted from a new input file. The name of this file is requested after the name of the GFILE. Its default name is DFILE. There is only one type of record in a DFILE file. Its format is: Columns Descriptions and Defaults Type ------------------------------------------------------------ 01-02 DP (anything other than a "DP" is a comment) default 6378137. meters (real) 03-03 Doppler data reference frame code. 1 -- NAD 83 datum observation (integer) -- Any other character will cause ADJUST to abort (default) 04-04 Reserved 05-08 Station Serial Number (integer) 09-19 X observation, units of mm., no default (integer) 20-30 Y observation, units of mm., no default (integer) 31-41 Z observation, units of mm., no default (integer) 42-46 X Standard Deviation, units of mm., no default (integer) 47-51 Y Standard Deviation, units of mm., no default (integer) 52-56 Z Standard Deviation, units of mm., no default (integer) 57-64 Correlation between North and East, units of 1 part per million, default of 0 (integer) 65-72 Correlation between North and Up, units of 1 part per million, default of 0 (integer) 72-80 Correlation between East and Up, units of 1 part per million, default of 0 (integer) 81-81 Rejection code - do not reject unless; R -- Reject observation O -- Office rejection F -- Field rejection 82-85 Year, no default (integer) 86-87 Month, default 07 (integer) 88-89 Day, default 01 (integer) If the Doppler observations are to be listed (see AFILE record PP, above), they will be listed after the GPS observations. Similarly, if the Doppler residuals are to be listed (see AFILE record PP, above), then they will be listed after the GPS residu- als. If the adjustment is a 2.5 dimensional adjustment (see AFILE record DD, above) then the Doppler observations will participate in the elevation adjustment. As with the other observation types, the Doppler observations may be bypassed using the AFILE BB record. The AFILE RR (Rotation Parameter), SS (Auxiliary Parameter), and VV (Variance Factor) records have been modified to allow Doppler observations to be chosen. The observation type for Doppler observations in those records is "99". In the case of the RR record where there had been no observation type parameter, the default observation type is GPS. The SS and VV records do not have defaults. ---------------------------------------------------------------------- ---------------------------------------------------------------------- Other Changes ---------------------------------------------------------------------- Changes made for ADJUST version 6.4.2 (2018/02/01): (1) Added IGS14 trasformation parameters. Includes use of the bluebook solution coordinate system code 33: IGS14 Aligned with ITRF2014 at epoch 2010.0 (2) Provided an F-test spreadsheet to determine the statistical equivalence between the resulting free and constrained adjustments. (3) Start weighting the vertical constraints. (4) CORS-Look for CORS with formal accuracies but use the RMS value on the short term plots rather than the published sigmas. Changes made for ADJUST version 6.4.1 (2016/06/06): (1) ADJUST-Allows non-shifted constrained coordinates to be written to the final B-file output. (2) GFILE-The I record - Name of Antenna Pattern File was expanded: cc 2-21 Changes made for ADJUST version 6.4 (2015/05/26): (1) Corrected output of the up component of local accuracies and slightly changed ADJUST output format. All previous versions wrote the up component network accuracy of the "to" station in the local accuracy field, in both the ADJUST output report and bfile. Local accuracies are now printed to the ADJUST output report with a line of dashes added between the last local accuracy of a set and the median values for that set. (2) Added a table of differences between constrained and adjusted coordinates to the ADJUST output giving shifts between constrained coordinates and their adjusted values. The table is located immediately below the adjusted coordinates list. Note that the table is only populated for stations that have ellipsoid heights in the afile (if there are no ellipsoid heights, the text "Vertical constraints is written in the shift fields). (3) Added the following note to the ADJUST output file to indicate if the input gfile was transformed by the NGS Horizontal Time- Dependent Postionining (HTDP) software (located near the beginning of the file in the block of text summarizing ADJUST settings and outputs): *************************************************************** NOTE:THE INPUT GPS VECTORS FILE (GFILE) WAS TRANSFORMED BY HTDP *************************************************************** (4) The B record or Group Header Record number of vectors field cc 26-27 only allows a maximum of 99 vectors per session. For a number of vectors larger than 99, leave this field blank and ADJUST will count the number of C or F vector records for the session. A maximum of 230 vectors per session is allowed. Previous changes made for ADJUST version 6.2.3 (2012/12/10): (1) ADJUST computes and writes network and local accuracies to the Blue Book and to the ADJUST output file. This is done using the NL code in the AFILE, as described under AFILE changes below. The network and local accuracies are written to the *91* and *92* records, respectively, of the output Blue Book file as standard deviations in latitude, longitude, and ellipsoid height (in centimeters) along with the horizontal correlation coefficient (these formats are described in Chapter 2 of the NGS Blue Book at http://www.ngs.noaa.gov/FGCS/BlueBook/). The network and local accuracies are also written to the ADJUST output file as horizontal and ellipsoid height values (in centimeters) at the 95% confidence level. (2) ADJUST writes the variance factor to the output Blue Book file in the *93* record as horizontal and vertical scale factors (this format is described in Chapter 2 of the NGS Blue Book at http://www.ngs.noaa.gov/FGCS/BlueBook/). The variance factors are determined using the HU option of the Variance Factor Indicator and Constraint (VV) record in the AFILE, as described under AFILE changes below. (3) Changed format of the input constrained coordinate standard deviation to centimeters. These values are part of the Coordinate Constraint (CC) record, as described under AFILE changes below. The values are in the same columns as previous version of adjust, but are instead entered as centimeters using the "real" numeric data type. (4) ADJUST no longer prompts for Doppler observation files (DFILES), although the functionality remains in the ADJUST algorithms. (5) ADJUST no longer writes orthometric heights to *80* record of the output Blue Book file. That is, columns 70-76 are now blank on this record, which is consistent with the current version of the NGS Blue Book. Previous changes made for ADJUST version 5.2 (2008/01/11): (1) The main change is that the Station Serial Number (SSN) is four digits rather than three. The fourth digit replaced the SSN suffix. In the previous version of ADJUST, if one of the SSNs on an observation record had a suffix, then that observation was ignored. This provision has, obviously, been removed. Classical observations are now rejected only if column 6 contains a "R" or a "F" or a "O" (instead of the sequence number or a blank). The sizes of the arrays that deal with SSNs have been increased. There may now be up to 9999 stations in a job. (2) Because of the above change the number of allowed intersection stations in a job has been increased to 3500 from 700. (3) Also because of change number (1), the maximum number of allowable horizontal direction sets per job has been increased to 8000 from 3000. (4) The *22* and *32* record now have the time of observation and time zone in columns 46-50. Only the date (year, month, and day) from columns 40-45 are saved from the previous *20* and *30* records, respectively. (5) The *84* record containing the geoid height has been removed from the Blue Book. In addition. the *80* record orthometric height in columns 70-75 is no longer used. The new *86* record has been incorporated into ADJUST and the values for the orthometric, geoid and ellipsoid heights are obtained from this record. (6) The *60* record has a new parameter in column 20 that deter- mines whether the azimuth observation is Astronomic or Laplace. An "A" indicates Astronomic while an "L" indicates Laplace. Since the previous version of ADJUST assumed that any astronomic observation was Laplace, the new version of ADJUST assumes that a blank indicates a Laplace azimuth. (7) The new Blue Book version has new *45* and *47* leveling observation records. These observation types have NOT been incorporated in ADJUST. They probably will be if enough users request it. (8) The B record or Group Header Record has a project id in columns 91-104. This version of ADJUST has been given a new version number and date. The new version is 5.2, and the new date is November 30, 2007. There are three new files associated with ADJUST. The first is the new output file discussed with the AFILE MM records. The second is the input file for Doppler observations. It is discussed above under DFILE. The third is the updated AFILE. It is discussed with the AFILE II record. ADJUST can create an adjusted position output file. This file contains all the information on the adjusted positions of the stations that is given in the adjusted position section of the output, but the information is formatted with one line of information per station. This file can be used as an input file for graphic plots of the data and other post processing programs. The AFILE MM (Adjustment Mode) record is used to request this output file and give it a name. The default name is "ADJPOS". The output of the new ADJUST is almost identical to the output of the old version. One major difference is that all lines in the new ADJUST output that contain station serial numbers have room for 4 digit numbers and all lines that contain an observation number have room for 6 digit numbers. Another difference is that if no printing of the observational summary is requested in the AFILE PP (Print Output) record, the new version of ADJUST will still print an abbreviated version. This version contains only stations that are constrained, undetermined, or no check. Also, in the summary file, the component number is printed for each station. This component number is the component number of the latitude parameter for 2 and 3 dimensional adjustments and of the height parameter for 1 dimensional adjustments. A component number of 0 indicates a trivial component, that is, a parameter not connected by an observation to any other component. In general, component number 1 will be the largest, component number 2 the second largest, etc.. But this won't always be true. There have been cases where components numbers 1 and 2 were trivial components - so only component number 3 was non-trivial! Optionally, ADJUST will now print the GPS residuals rotated to the local horizon coordinate system (NEU for north, east, up). The default is to automatically print these, but this can be changed with the AFILE PP record. The rotated values for observed and adjusted observations, the rotated values for the residuals, and the rotated values of the standard deviation of the residuals are printed. The standard deviation printed is the standard deviation appropriate to the mode of the adjustment (see AFILE MM record). A horizontal DN/DE combined component called DL has been added and listed before the DU component. The ssn now prints in the residual section for each vector in addition to the station designation. A session identifier has been added at the end of the DZ record. This identifier is from the C record cc 60-64 or the F record cc 66-70 and is 'DDDYS' where DDD is day of year, Y is the last digit of the year and S is a session designator. 'SESSION ID' has been added to the header column. Also, the PP record tolerance may be used to print only vectors in which at least one of the components residuals exceeds this criteria. Note, this value is the residual for GPS observations and normalized residual for non-GPS records. Also, in the residual summary section of the output there will be an additional summary section for the NEU residuals. This section has the RMS and the mean of the absolute values of the NEU residuals. Only residuals for those observations that contributed to the solution will be included in this summary no-check observations and the down weighted observations will not be included. For this reason, the value under N in this section is not necessarily the same as that for the GPS residuals in the residual summary section. New statistics in this section include the 20 observation numbers of the largest residuals, the 20 observation numbers of the largest GPS DU component residuals, the 20 observation numbers of the largest GPS DL component residuals and the maximum and minimum residual for each vector component. In the Adjusted Positions Section, the header 'M.S.L.' has been changed to 'Ortho. Ht.' Also the horizontal shift has been expanded to three decimal places. Optionally, ADJUST will no longer abort if the solution is singular (see AFILE record MM (Adjustment Mode). If the adjust- ment is not aborted, the singular parameter will be constrained to its initial value. If the full observational summary section was not printed, observation information will be printed for each singular parameter for the station to which the parameter refers. The information will be listed the same as in the observational summary section. For 2.5 dimensional adjustments, ADJUST will now adjust zenith distance observations, zenith distance constraints, and height difference constraints if both of the stations are dual height stations. Previously these observations and constraints were ignored for all 2 dimensional adjustments. This also allows vertical angle auxiliary parameters to be used. But care should be taken so that these parameters will have corresponding zenith distance observations. If there are no zenith distance observa- tions for a vertical angle auxiliary parameter, then the parame- ter will be singular. The AFILE now accepts comment records where comment records are defined as two blanks or two asterisks in columns one and two. Thus, totally blank lines are ignored. Notes NOTE: The MM record contains the output name for the Adjusted Position file and the II record contains the output name for the new AFILE. These names are a maximum of seven characters. If more characters are needed, they may be renamed on exiting ADJUST. The output name for the new Blue Book file is now obtained from the user prompt and is no longer obtained from the MM record. The MM record column 5 must contain a 'Y' for a new Blue Book file to be created however. If a new Blue Book file should not be created, the MM record column 5 should be 'N' which is the default value and press enter or use any name for the user prompt as the file will not be created. The BBOOK file *12* record 4-digit year field observations began cc 11-14 and 4-digit year field observations end in cc 17-20 are used to determine 4-digit years for classical observation records in which only 2-digit years are recorded. Invalid *12* record 4-digit years will terminate execution of ADJUST. ---------------------------------------------------------------------- ---------------------------------------------------------------------- System Dependent Code ---------------------------------------------------------------------- ADJUST now obtains the date and time from the operating system. This is done in a new subroutine SYSTIM. The call to this routine is: CALL SYSTIM (ITYPE, TBUF, DIFM, DIFM0) where ITYPE is integer, TBUF is a 26 character string, and DIFM and DIFM0 are double precision. If ITYPE=0, then system time is returned in the TBUF character string and the saved times are updated. If ITYPE=1, the time difference in minutes from the the last ITYPE=0 call is returned in TDIF0 and the time difference in minutes from the last call to GETTIM is returned in TDIF. This subroutine is called from the following subroutines; ADJUST (main), ADJST, SECOND, ABORT2, and FINAL. The other system dependent feature that has been added is a call to flush the output buffer in subroutine NORMAL. This is done by a call to the routine MYFLSH. The unit number of the output buffer is passed as a parameter. To adapt these routines to another system, it is necessary to be able to get the date and time from the operating system for the SYSTIM subroutine, and the flushing mechanism for the MYFLSH subroutine. This is non-standard FORTRAN and is done differently, when it is done at all, on each type of machine. Alternatively, these subroutines can be altered to do nothing. For the unix operating system, file makefile finds subroutine SYSTIM in file sysdep_ux.for (using f90 compiler). For the Windows (Win32) operating system, file makefile_g77.w32 finds subroutine SYSTIM in file sysdep_g77.for (using g77 compiler). ADJUST_supplemental.txt - end ----------------------------------------------------------------------