Integrate road surface condition model

[behrisch]

this serves as a reminder to integrate the model presented at SUMO 2019 (https://easychair.org/publications/paper/3S4X)

Some leftover tasks

• [ ] tests
  • [ ] network input,
  • [ ] simulation behavior
  • [ ] variableSpeedSign
• [ ] documentation
  • [ ] network input,
  • [ ] simulation behavior
  • [ ] variableSpeedSign
• [ ] error handling code is missing (coefficient may become negative, see below plot)
• [ ] apply friction within duarouter? how to handle probabilistic effects?

road speed factor as a function of the 'measuredFriction' (which is itself derived by randomly disturbing the actual road friction)

[namdre]

Was already discussed on the mailing list:

After some internal discussion we would prefer to keep a distinction between 'core' road attributes and extended attributes. Core attributes are configured directly within the edge or lane element e.e <edge id="1" speed="13.89" ../> Extended attributes are configured as <param> elements within the edge or lane element. Currently, the core attributes mostly pertain to "immutable" qualities of the network (e.g. posted speed limits or lane count). The 'friction' attribute as well as 'visibility', and 'water clogging' mostly pertain to temporal aspects of the road network so we would delegate them to the extended mode of input specification.

No files need to be modified to add new attributes. The <param> values are directly accessible from within the simulation models (e.g. the car following model just as the core attributes are). Also, netedit allows editing these attributes. For details, see https://sumo.dlr.de/docs/NETEDIT.html#generic_parameters The only major change that needs to be done is to rework the variableFriction object into a variableParam object (it should be capable of modifying arbitrary lane at specified times. This would also fit well with modelling time-variations for all the other road quality parameters you mentioned. https://github.com/eclipse/sumo/issues/6532

Also, the way <params> for multiple elements are modified at the same time needs to be improved in netedit. I've described the task in more detail at https://github.com/eclipse/sumo/issues/6531

[behrisch]

We nevertheless integrated it using #10450. Documentation and tests for the dynamic modification are still missing