cnetcombinept should set merged control measure types to Candidate so that pointreg can be run efficiently
cnetcombinept should set merged control measure types to Candidate so that pointreg can be applied to only those merged measures when registering to the (typically) new reference measure.
It would be best if the actual image measure coordinates could be updated to match the new reference in the master point, but not enough information is available (need, at a minimum, the pixel resolution of both images at that measure). If the reference measures are the same, then the measure type should NOT be modified.
NOTE: It is highly recommended that pointreg be run after cnetcombinept with this new change as merged measures are very likely only registered to within IMAGETOL pixels at best (remember: IMAGETOL is compared to the average offset of all common measures in merge point pairs so some measures could be greater than IMAGETOL pixels from the reference measure).
#9 Updated by Tyler Wilson over 1 year ago
To make things easier for testing, I have combined all three of the cnetcombinept tickets into one ticket which can be tested by pointing your ISIS version here:
The other two tickets are:
#11 Updated by Kris Becker over 1 year ago
Umm, this comment applies to this ticket as well but is duplicated in #4869 as well.
One additional change that needs to be made is to determine if the reference measures on both points are the same. In this case, you will not set the point to Candidate but leave the type unchanged.
This should be test for prior to the loop that merges individual measures and a flag set to make the update if reference measures are different.
This is an unlikely case, but will save time if it does occur.