Skip to content

Dropped Range from the PrVeloUT input

Sebastien Ponce requested to merge PrVeloUTNoRange into future

Range cannot be used so easily as the default Range for Track is base on vector while the Container is a KeyedContainer. As we stored containers, we can only get back ranges if they are based on KeyedContainer also. This is probably a bug in the event model. But for the moment, I've dropped the Range usage, and that make mini Brunel happy :-)

Merge request reports