Comparison of double and floating point in collision grid meta data

[jolting]

Is it safe to add some epsilon in here, so that collision grids don't regenerate if they are close enough?

https://github.com/MRPT/mrpt/blob/master/libs/nav/src/tpspace/CParameterizedTrajectoryGenerator.cpp#L625

[jolting]

@jlblancoc Actually this bug is more severe than I originally thought.
Collision grids will always regenerate.

This commit broke it:
e5db1da

This writes doubles to the file.

        *f << m_x_min << m_x_max << m_y_min << m_y_max;
        *f << m_resolution;

And this reads floats.

        *f >> ff; if(ff!=m_x_min) return false;
        *f >> ff; if(ff!=m_x_max) return false;
        *f >> ff; if(ff!=m_y_min) return false;
        *f >> ff; if(ff!=m_y_max) return false;
        *f >> ff; if(ff!=m_resolution) return false;

It doesn't appear that MRPT does any type checking when deserializing.

[jlblancoc]

Thanks for the discovery @jolting !!

I'll verify it and correct it ASAP.
Type-checking if only done at the object (CSerializable and derived classes) level. POD types are not checked to avoid the huge overload that it would represent...

[jlblancoc]

@jolting please, get the changes from that commit above.