Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fixed bug where Lat/Lon/Radius point corrections are wrong in points.csv when running a rectangular (XYZ) bundle adjustment #5688

Open
wants to merge 2 commits into
base: dev
Choose a base branch
from

Conversation

kledmundson
Copy link
Contributor

Description

When performing a rectangular (XYZ) bundle adjustment, the Lat/Lon/Radius point corrections written to the points.csv file are incorrect and do not match those written to the bundleout.txt file.

Fixed the method BundleSolutionInfo::outputPointsCSV() so that the code to write point corrections matches that in BundleControlPoint::formatBundleLatitudinalOutputDetailString. Also modified the ctest FunctionalTestJigsawBundleXYZ to exercise this fix by spot checking six lines (points) in points.csv.

Related Issue

#5646

How Has This Been Validated?

All jigsaw/bundle related tests continue to pass, including the updated test FunctionalTestJigsawBundleXYZ.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Documentation change (update to the documentation; no code change)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Infrastructure change (changes to things like CI or the build system that do not impact users)

Checklist:

  • I have read and agree to abide by the Code of Conduct
  • I have read the CONTRIBUTING document.
  • My change requires a change to the documentation and I have updated the documentation accordingly.
  • I have added tests to cover my changes.
  • I have added myself to the .zenodo.json document.
  • I have added my user impacting change to the CHANGELOG.md document.

Licensing

This project is mostly composed of free and unencumbered software released into the public domain, and we are unlikely to accept contributions that are not also released into the public domain. Somewhere near the top of each file should have these words:

This work is free and unencumbered software released into the public domain. In jurisdictions that recognize copyright laws, the author or authors of this software dedicate any and all copyright interest in the software to the public domain.

  • I dedicate any and all copyright interest in this software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

…when performing a rectangular (XYZ) bundle adjustment, the Lat/Lon/Radius point corrections written to points.csv are incorrect and do not match those written to bundleout.txt. Also modified the ctest FunctionalTestJigsawBundleXYZ to spot check six lines (points) in points.csv. Addresses DOI-USGS#5646.
Copy link

github-actions bot commented Dec 3, 2024

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_5688".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.

…ordinates in method BundleSolutionInfo::outputPointsCSV. Addresses DOI-USGS#5646.
Copy link

The build and test suite have started for your pull request.

To view your build log, please reference the build with source version: "PR_5688".

Additionally, check the latest "dev" source version to identify existing test failures. Please note that you are not responsible for the test failures that exist on both your PR and the dev branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants