Re: Reasonable defaults
Until the system has two consecutive sweeps of a particular area, it cannot know if something is moving or not, so the initial status is static. But once it has detected movement, it should use the movement profile as the master and try and classify what is moving, as opposed to reclassifying the object, which resets the motion profile to static.
That is the problem. Either it needs to not drop the object when it is reclassified, but "rename" it, so that the movement profile stays with it, or it needs to use the movement profile as the primary "object" and classify what is moving. But their system just throws away its knowledge of the object and creates a new one.
I expect that they use classes, so you have object, which has child object vehicle, bike, pedestrian etc. and when it reclassifies, it has to drop the vehicle object and create and object object, then drop that and make a bike object, then drop the bike object and make an object object etc.
Better would be to have an object object, which has a "type" classification and loads a movement rules collection based on the type. That way the object and its movement history would remain constant, but the type and its movement rules would be added and removed from the parent object.
That way the movement history and a generic "it is moving to intercept my path" rule would be there even if it can't identify what it is, it can still take avoiding action. Stopping for or swerving around an unidentified piece of trash flying past is silly, but preferable to hitting an unidentified pedestrian.
Biting the hand that feeds IT
