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

socetlinescankeywords modifications needed for Socet Set USGSAstrolinescanner sensor model #1741

Closed
ascbot opened this issue Feb 13, 2019 · 2 comments
Labels
bug Something isn't working

Comments

@ascbot
Copy link
Contributor

ascbot commented Feb 13, 2019


Author Name: Elpitha Howington-Kraus (Elpitha Howington-Kraus)

Original Date: 2013-05-31
Original Assignee: Elpitha Howington-Kraus


The isis3.4.3 version of socetlinescankeywords is not generating enough ephemeris points and quaternions to model HiRISE images in Socet Set adequately for bundle adjustment. Additional issues impacting HiRISE Socet Set processing are the precision of the USGSAstrolinescanner keywords values output by socetlinescankeywords, and the pixel-location of the center ephemeris time. Debugging of socetlinescankeywords and the USGSAstrolinescanner has taken place under Photogrammetry R&D, and we are now ready to commit the modified version of socetlinescamkeywords into ISIS for the next quarterly release.

@ascbot ascbot added this to the 3.4.4 (2013-06-25 Jun) milestone Feb 13, 2019
@ascbot ascbot added the bug Something isn't working label Feb 13, 2019
@ascbot
Copy link
Contributor Author

ascbot commented Feb 13, 2019


Original Redmine Comment
Author Name: Elpitha Howington-Kraus (Elpitha Howington-Kraus)
Original Date: 2013-06-21T17:27:08Z


As of the posting of this mantis ticket, we have determined an issue with the spacecraft velocity computations using the ISIS Spice Class(see mantis ticket #1684) Until a solution to the velocity computations is in place, we are temporarily modifying socetlinescankeywords to compute velocity values from the spacecraft positions. Because of interpolation differences, these values will be close, but not exact to values using, for example, NAIF routine spkez. Once the Spice Class issues are resolved, socetlinescankeywords will use the Spice Class to determine spacecraft velocity.

@ascbot
Copy link
Contributor Author

ascbot commented Feb 13, 2019


Original Redmine Comment
Author Name: Elpitha Howington-Kraus (Elpitha Howington-Kraus)
Original Date: 2013-06-25T18:29:18Z


Note on finished_effort_hrs: Most of the debugging work was done under Randy's R&D project. The hours listed here are for final validation of the changes, and the work to get the program committed into isis

@ascbot ascbot closed this as completed Feb 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant