cartographer-project/cartographer
Serialized SparsePoseGraphs can easily be too big for default proto deserialization
Ouverte
#433 ouverte le 27 juil. 2017
enhancementhelp wanted
Métriques du dépôt
- Stars
- (6 665 étoiles)
- Métriques de merge PR
- (Métriques PR en attente)
Description
I'm working with some very large multi-trajectory SLAM problems (10s of kms, indoor), and the resulting serialized SparsePoseGraph objects are too big to deserialize, as they're much larger than the default 64MB limit. (Seriously: I'm up to about 1.3GB for the SPG alone.)
There are three solutions:
- Modify the serialization of SPG to use the pbstream, writing the pieces out one-by-one.
- Improve pbstream to use a
google::protobuf::io::CodedInputStreamdirectly, so we can callSetTotalBytesLimitwith a bigger value. - "Mac, you're out of your mind, make yourself a branch and leave the rest of us out of this."
(I've currently implemented 3, via 2, in macmason/cartographer and macmason/cartographer_ros, in branches both called mass_map.)
Thoughts?
FYI @brandon-northcutt