Screenshot instructions:
Windows
Mac
Red Hat Linux
Ubuntu
Click URL instructions:
Rightclick on ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)
From: Amitha Perera <perera@cs...>  20030121 04:01:18

Hi Why is vnl_numeric_traits<float>::real_t a double instead of a float? The comment says "result when multiplied by double", but that's not quite how it is used. It generates a warning is vnl_vector::cos_angle when instantiated with complex<float> because there is an attempt to create a complex<float> from a double, which implies a loss of precision. Changing the real_t to float would also fix things like vnl_matrix.txx:834: // FIXME need correct rounding here // There is e.g. no *standard* operator*=(complex<float>, double), hence the T() cast. this>data[i][j] *= T(scale); Here, scale has type real_t, which means double, and therefore the problem. I think we should have typedef vnl_numeric_traits<float>::real_t float; typedef vnl_numeric_traits<double>::real_t double; typedef vnl_numeric_traits< complex<float> >::real_t complex<float>; typedef vnl_numeric_traits< complex<double> >::real_t complex<double>; The comment could be from //: Name of type which results from multiplying this type with a double to //: Name of type which results from multiplying this type with a float However, I have no experience in using vnl except with doubles, so I don't know what would break from this change. Can someone who knows better comment? Thanks, Amitha. 
From: Andrew Fitzgibbon <awf@ro...>  20030121 10:17:17

> Why is vnl_numeric_traits<float>::real_t a double instead of a float? > The comment says "result when multiplied by double", but that's not > quite how it is used. So, the comment is correct, but the usage is wrong. If we need another sort of real_t, then we should add it. But the existing one has a welldefined meaning, and is used in contexts like T t; traits<T>::real_t product = 1.0 * t; Now, maybe it should be renamed to double_product_t, but it does have a meaning and use at the moment. > It generates a warning is vnl_vector::cos_angle > when instantiated with complex<float> because there is an attempt to > create a complex<float> from a double, which implies a loss of > precision. So that function should be fixed. Where did the double come from? acos? In which case either the float>float acos should be used, or we must narrow to complex<float> > > Changing the real_t to float would also fix things like > vnl_matrix.txx:834: > > // FIXME need correct rounding here > // There is e.g. no *standard* > operator*=(complex<float>, double), hence the T() cast. > this>data[i][j] *= T(scale); > > Here, scale has type real_t, which means double, and therefore the > problem. > > I think we should have > typedef vnl_numeric_traits<float>::real_t float; > typedef vnl_numeric_traits<double>::real_t double; > typedef vnl_numeric_traits< complex<float> >::real_t > complex<float>; > typedef vnl_numeric_traits< complex<double> >::real_t > complex<double>; > > The comment could be from > > //: Name of type which results from multiplying this type > with a double > > to > > //: Name of type which results from multiplying this type > with a float > > > However, I have no experience in using vnl except with doubles, so I > don't know what would break from this change. Can someone who knows > better comment? > > Thanks, > Amitha. > > >  > This SF.NET email is sponsored by: > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! > http://www.vasoftware.com > _______________________________________________ > Vxlmaintainers mailing list > Vxlmaintainers@... > https://lists.sourceforge.net/lists/listinfo/vxlmaintainers > 
From: Peter Vanroose <Peter.Vanroose@es...>  20030121 11:22:51

> the existing one has a welldefined meaning, and is used in contexts like > > T t; > traits<T>::real_t product = 1.0 * t; Well, let's then change the meaning to traits<T>::real_t product = 1.0f * t; It is less harmful to cast from float to double than from double to float.  Peter. 
From: Andrew Fitzgibbon <awf@ro...>  20030121 11:44:34

No, what I said was "the existing one has a welldefined meaning". Therefore we should not change it. It is harmful either way. Make a new one if we need a new one. > Original Message > From: Peter Vanroose [mailto:Peter.Vanroose@...] > Sent: 21 January 2003 11:22 > To: Andrew Fitzgibbon > Cc: 'Amitha Perera'; vxlmaintainers@... > Subject: RE: [Vxlmaintainers] vnl_numeric_traits > > > > the existing one has a welldefined meaning, and is used in > contexts like > > > > T t; > > traits<T>::real_t product = 1.0 * t; > > Well, let's then change the meaning to > > traits<T>::real_t product = 1.0f * t; > > It is less harmful to cast from float to double than from > double to float. > > > >  Peter. > 
Sign up for the SourceForge newsletter:
No, thanks