Remove DynaML.xsd, including unit tests

[daleroberts]

This removes the need for DynaML.xsd file, see #346

Additional cleanups to remove dead code and unit tests since it's removed.

[ibaran73]

Hi Robert, Does the redeveloped DynAdjust benefit /use GPUs? Thank you Regards Irek Thank you Regards Irek Irek Baran | Principal Geodesist Land Boundaries, Location Services, Landgate 1 Midland Square, Midland WA 6056 t: +61 (0)8 9273 7135 e: ***@***.******@***.***> w: landgate.wa.gov.au www.linkedin.com/in/irek-baran<http://www.linkedin.com/in/irek-baran> [A picture containing art, graphic design, graphics, poster Description automatically generated] Work Location: Mon Tues Wed Thu Fri Office Office Office/Home Home Home From: Dale Roberts ***@***.***> Sent: Tuesday, 17 March 2026 11:45 AM To: GeoscienceAustralia/DynAdjust ***@***.***> Cc: Subscribed ***@***.***> Subject: [GeoscienceAustralia/DynAdjust] Remove DynaML.xsd, including unit tests (PR #348) This removes the need for DynaML.xsd file, see #346<#346> Additional cleanups to remove dead code and unit tests since it's removed.

…

________________________________ You can view, comment on, or merge this pull request online at: #348<https://github.com/GeoscienceAustralia/DynAdjust/pull/348> Commit Summary * 0de7660<0de7660> Remove DynaML.xsd, including unit tests File Changes (7 files<https://github.com/GeoscienceAustralia/DynAdjust/pull/348/files>) * M dynadjust/CMakeLists.txt<https://github.com/GeoscienceAustralia/DynAdjust/pull/348/files#diff-aa98f558c08f5d75ad409f368165e01eb25cc94206f06bed0433fc8182220e93> (10) * M dynadjust/dynadjust/dnaimport/dnainterop.cpp<https://github.com/GeoscienceAustralia/DynAdjust/pull/348/files#diff-70e7f257cdb4aee68a076d7cf8821cbdae632c46f8a2d84b32a38a649c0031b6> (16) * M dynadjust/dynadjust/dnaimport/dnaparser_pimpl.cxx<https://github.com/GeoscienceAustralia/DynAdjust/pull/348/files#diff-130e47ac3c234802f7599c73a9ffe44d6a2d83494bab8b310f1f74484c5d3788> (2) * M dynadjust/dynadjust/dnaimport/dnaparser_pskel.cxx<https://github.com/GeoscienceAustralia/DynAdjust/pull/348/files#diff-dc2015e425574cd565c01d920d998aaad53ed806310d05fadfd9b9e45afac85a> (2) * M dynadjust/dynadjust/dnaimportwrapper/dnaimportwrapper.cpp<https://github.com/GeoscienceAustralia/DynAdjust/pull/348/files#diff-1a4c2667de159bcfeb6ce51767c8673a22f635b1cdd189bb4409c999b72032ee> (9) * D dynadjust/include/io/DynaML-schema.cxx<https://github.com/GeoscienceAustralia/DynAdjust/pull/348/files#diff-59928f55c7391087edbbcf40d1e467e142c9fc8025bba254c72b257703fd7bae> (969) * D dynadjust/include/io/DynaML-schema.hxx<https://github.com/GeoscienceAustralia/DynAdjust/pull/348/files#diff-75808329dea5a34a1ca7c23791c828228c5318d875c1b4e491940dc41dd7308c> (8) Patch Links: * https://github.com/GeoscienceAustralia/DynAdjust/pull/348.patch<https://github.com/GeoscienceAustralia/DynAdjust/pull/348.patch> * https://github.com/GeoscienceAustralia/DynAdjust/pull/348.diff<https://github.com/GeoscienceAustralia/DynAdjust/pull/348.diff> — Reply to this email directly, view it on GitHub<#348>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ALBJ336V37R3SQJ6JASA4UL4RDC27AVCNFSM6AAAAACWUDI546VHI2DSMVQWIX3LMV43ASLTON2WKOZUGA4DMMBSGUZDQMI>. You are receiving this because you are subscribed to this thread.Message ID: ***@***.******@***.***>> Disclaimer The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful. This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

[daleroberts]

Does the redeveloped DynAdjust benefit /use GPUs?

Unfortunately not. It requires so much memory for large adjustments that we would have to shuffle the data to/from the main memory and I feel that would erase most of the gains. That said, I'm currently working on some memory usage improvements and speed enhancements for v1.4