Autocalibration may be fixing the sign of eigenvalues incorrectly #44664

Closed
opened 2015-05-11 10:28:15 +02:00 by Keir Mierle · 10 comments
Member

Originally from: https://code.google.com/p/libmv/issues/detail?id=32#makechanges

What steps will reproduce the problem?
Reference:

  Path: libmv\src\libmv\multiview\autocalibration.cc
  Lines: 105 to 109 (see below)
// Eigen values should be possitive,
Vec temp_values = eigen_solver.eigenvalues();
if (temp_values.sum() < 0) {
  temp_values = -temp_values;
}

After execution of these lines, I am still finding negative eigen values in temp_values.

What is the expected output? What do you see instead?
If I am not wrong, this should code should replaced with the code given below to ensure non-negative eigen values:

  for( int i = 0; i < 4; i++)
  {
      if(temp_values[i] < 0){
          temp_values[i] = -temp_values[i];
      }        
  }
Originally from: https://code.google.com/p/libmv/issues/detail?id=32#makechanges **What steps will reproduce the problem?** Reference: ``` Path: libmv\src\libmv\multiview\autocalibration.cc Lines: 105 to 109 (see below) ``` ``` // Eigen values should be possitive, Vec temp_values = eigen_solver.eigenvalues(); if (temp_values.sum() < 0) { temp_values = -temp_values; } ``` After execution of these lines, I am still finding negative eigen values in temp_values. **What is the expected output? What do you see instead?** If I am not wrong, this should code should replaced with the code given below to ensure non-negative eigen values: ``` for( int i = 0; i < 4; i++) { if(temp_values[i] < 0){ temp_values[i] = -temp_values[i]; } }
Author
Member

Changed status to: 'Open'

Changed status to: 'Open'
Author
Member

Added subscriber: @Keir

Added subscriber: @Keir
Sergey Sharybin was assigned by Bastien Montagne 2015-05-26 14:39:46 +02:00

Added subscriber: @mont29

Added subscriber: @mont29
Sergey Sharybin removed their assignment 2016-01-26 13:59:40 +01:00

Added subscriber: @Sergey

Added subscriber: @Sergey

Added subscriber: @dr.sybren

Added subscriber: @dr.sybren

I'm tempted to close this task, as there is no description of what error occurs or how to reproduce it. @Keir, @Sergey, is this still a change that should be applied?

I'm tempted to close this task, as there is no description of what error occurs or how to reproduce it. @Keir, @Sergey, is this still a change that should be applied?

Changed status from 'Confirmed' to: 'Needs User Info'

Changed status from 'Confirmed' to: 'Needs User Info'

Added subscriber: @AdamKalisz

Added subscriber: @AdamKalisz

This comment was removed by @AdamKalisz

*This comment was removed by @AdamKalisz*
Member

Changed status from 'Needs User Info' to: 'Archived'

Changed status from 'Needs User Info' to: 'Archived'
Ankit Meel self-assigned this 2020-05-02 20:49:24 +02:00
Sign in to join this conversation.
No Milestone
No project
No Assignees
6 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: blender/libmv#44664
No description provided.