luifire
luifire
The _no re-rolling_ part makes sense. However, I am switching the type quite a lot and the communication seems really expensive. Thus I would prefer not to call `setSpeedFactor` each...
I haven't. Thanks for pointing this out. :)
If we actually go forward with this, I would vote for a re-rolling. The reasons being: - _Having special vTypes that allow for a type switch where the speedFactor changes,...
A new speed factor gets assigned as expected. What I do in my simulation is to switch between a speed factor of 1 (vehicle drives exactly as expected - e.g....
As I understood @behrisch , this would only hold if the _initial_ speedDev is 0. Switching back and forth hasn't been discussed. From your post, I presume you have not...
Just a suggestion: as I understand you, you don't want to introduce a new member variable (which is fair enough). In case you have a bit-mask with an empty bit,...
> Once we have to deal with boundaries it might happen that one distribution has all valid values to the left of the mean and the next distribution only has...
> > one could simply store if we are left or right of the mean and then resample with every type switch > > Once we have to deal with...