More than one map
We are implementing now a grid map in a derived class from MapBase
. It required to create a factory for maps. Tt came up the idea that if a processor requires a type of map to be able to work, it can happen that two processors in the same setup require two different types of maps.. And even more, most of the current cases, do not require any map at all.
We may want to change to have a list of maps (with names) instead of a single map pointer in Problem
. And leave to the user (setup) the decision of which and how many maps are required.
Analogously to processors with sensors, a processor that requires an specific map to work with, can require the map name in the yaml.