Least squares adjustment software
This release addresses several defects and introduces new enhancements across all applications and documentation, including:
This release addresses a defect, incorporates code enhancements, and closes an issue relating to ignored measurements.
*.snx file with the default reference frame (GDA2020) instead of the user-supplied reference frame. Several changes have been introduced to use the reference frame supplied to import or reftran.*.msr files.find_package call to CMakeLists.txt to improve detection and linking of OpenMP on build.This pull request addresses a bug, and incorporates several code enhancements. These include:
install_dynadjust_prerequisites.sh and make_dynadjust_gcc,sh for linux installation and builddynadjust.props file to manage paths for boost and xsd/xerces-c headers and librariesresource.h and dynadjust.rc) to assist with managing versioning and copyright information in Windows binary buildsThis release contains various code enhancements that address issue #24. Specifically, this release provides support for handling the WGS 84 ensemble and six specific WGS 84 realisations, including WGS 84 (Transit), WGS 84 (G730), WGS 84 (G873), WGS 84 (G1150), WGS 84 (G1674), WGS 84 (G1762), and WGS 84 (G2139).
The DynAdjust binaries attached to this release are for Windows 10 (x64) and have been built using Intel® oneAPI version 2022.1.3.
Several code changes and enhancements effecting multiple programs include:
wgs84 | wgs84 (transit) | wgs84 (g730) | wgs84 (g873) | wgs84 (g1150) | wgs84 (g1674) | wgs84 (g1762) | wgs84 (g2139)
wgs84 is taken to mean the WGS 84 ensemble, whereas wgs84 (xxxx) is taken to mean any one of the specific WGS 84 realisations (e.g. wgs84 (g2139)).wgs84 is synonymous with wgs 84, and both are interpreted case-insensitively.--reference-frame).wgs84 (i.e. the WGS 84 ensemble) is supplied as the default reference frame.Several changes have been made to reflect the new behaviour, including:
DynAdjust v1.2.4 has been built using Intel® oneAPI version 2022.1.3. In order to successfully run DynAdjust v1.2.4 binaries, users will need to upgrade to the latest version of Intel® oneAPI (see https://www.intel.com/content/www/us/en/developer/tools/oneapi/base-toolkit-download.html). The specific dll dependencies are:
Special thanks to Joel Haasdyk for his help in shaping the preferred behaviour for handling WGS 84 data.
This release contains various code enhancements and bug fixes addressing issues #167, #169, #170 and #173.
.vcxproj files (for all projects) to permit use of Intel OneAPI for MKL libraries and header files (issue #167).<Epoch>...</Epoch>) and imported/exported/simulated accordingly. With a date of observation and the introduction of a discontinuity file on import (via --discontinuity-file), terrestrial measurements connected to sites with known discontinuities will be updated with renamed station names (addressing issue #170).
XML
<!--Type E Ellipsoidal Distance -->
<DnaMeasurement>
<Type>E</Type>
<Source></Source>
<Epoch>01.01.1900</Epoch>
<Ignore/>
<First>TID1</First>
<Second>TS7276</Second>
<Value>218.8460</Value>
<StdDev>0.0055</StdDev>
<MeasurementID>203049279</MeasurementID>
</DnaMeasurement>
E TID1 TS7276 218.8460 0.005 01.01.1900 203049279
Due to a change in the way Intel distributes its Math kernel Library (MKL), users of the DynAdjust Windows binaries (from v1.2.3 onwards) will need to install the Intel® oneAPI Math Kernel Library from https://www.intel.com/content/www/us/en/developer/tools/oneapi/onemkl.html. The specific dll dependencies are:
Special thanks to @ibaran73 and @nicgowans for their contributions to tracking issues and supplying sample datasets.
This release contains several code enhancements and bug fixes, and addresses issues #15, #30, #78, #81, #80, #82, #85, #150 and #160. The following summarises the related (major) pull requests associated with these code changes.
Numerous (too many to list) code enhancements have been applied to address issues identified by Codacy, Coveralls and Codecov. New (GitHub Actions) CI/CD scripts have been developed to invoke automated workflows on code push/pull request events:
FindXercesC.cmake, where installation failed to find a pre-existing installation of xerces-c in /opt/xerces-c/3.1.4.make_dynadjust_gcc.sh, to streamline build behaviour across clone and no-clone options, and install_dynadjust_prerequisites.sh, which now cleans up any temporary folders created when downloading prerequisites.*.m2s files.*.bst files created by earlier versions of import cannot be reused by this or future versions of DynAdjust.station-name-a and station-name-b) are provided within the one <DnaStation> record, as shown below. Whilst not strictly an import defect, parsing the second name (permissible by the schema) resulted in replacing the first name and thereby led to malformed station-to-measurement associations.
<DnaStation>
<Name>station-name-a</Name>
<StationCoord>
<Name>station-name-b</Name>
...
<StationCoord>
</DnaStation>
.adj and .dbg files on verbose execution.*-rva.mtx. This defect led to strange values for SD(e), SD(n) and SD(up) in *simult.adj files when executing adjust in report results mode (i.e. --report-results).Special thanks to @harry093, @BatchelorJ, @nicgowans, @wapayze, @jameslevershadelwp, @stratiform and @tekwan for their contributions to tracking issues, reviewing algorithms and testing the release candidates.
This beta release contains several code enhancements and bug fixes, and addresses issues #15, #30, #78, #81, #82, #85 and #160. The following summarises the related (major) pull requests associated with these code changes.
Numerous (too many to list) code enhancements have been applied to address issues identified by Codacy, Coveralls and Codecov. New (GitHub Actions) CI/CD scripts have been developed to invoke automated workflows on code push/pull request events:
FindXercesC.cmake, where installation failed to find a pre-existing installation of xerces-c in /opt/xerces-c/3.1.4
*.bst files created by earlier versions of import cannot be reused by this or future versions of DynAdjust..adj and .dbg files on verbose execution*-rva.mtx. This defect led to strange values for SD(e), SD(n) and SD(up) in *simult.adj files when executing adjust in report results mode (i.e. --report-results)This beta release contains several code enhancements and bug fixes, and addresses issues #15, #30, #78, #81, #82, and #85. The following summarises the related (major) pull requests associated with these code changes.
Please provide feedback or comments on issues experienced with this beta release in the discussion (rather than creating a new issue).
*.bst files created by earlier versions of import cannot be reused by this or future versions of DynAdjust..adj and .dbg files on verbose executionThis release contains code enhancements relating to a new feature that resolves #53. Specifically, this includes:
--plate-model-option arg:
0: Assume all stations are on the Australian plate (default)
1: Interpolate plate motion model parameters from a defined
set of global tectonic plates. For this option, a global
tectonic plate boundary file and corresponding Euler
plate motion parameters file must be provided.
--plate-boundary-file arg), and--plate-pole-file arg).<network-name>.rft). Depending on verbose level (via --verbose-level arg), output can include information about calculated transformation parameters from Euler pole parameters; sequence of steps involved in reference frame transformations; and reduced Helmert parameters and time duration.This release contains several code enhancements, fixes and updates, including:
--output-database-ids) when adjusted measurements were sorted on criteria (e.g. correction, n-statistic, etc.) other than the default sort order (original input file order). This release enables database IDs to be printed irrespective of adjusted measurement sort order.--sort-adj-msr-field 7), GNSS baselines are now sorted using the maximum of the 3 n-statistic components, whereas previously the sorting of GNSS baselines was based upon the magnitude of 3 (x, y, z) n-statistic components.