jakobaxelsson
commented
12 months ago A partial implementation is ready. It handles the model generation and UI parts. However, some things remain to do:
- Serialization: JSON cannot be generated, since there are type objects in the data structure.
- Command line arguments has been prepared, but is incomplete and not tested.
- Vehicle params work as before (i.e., no configuration), but configuration handling should be extended to that as well. Also, there are some more parameters for road network generation that are still hardcoded. Maybe the road network should also take the configuration object as a parameter with all its settings?
Configurations are parameters that control the model generation and simulation. The parameters have default values, that can be updated in batch mode using the command line interface, and in interactive mode using dialogues. In the future, it would also be nice to be able to save a configuration to file, and to reload it later.
Currently, the configuration is handled as parameters to the init functions of different classes. A better approach would be to instead have a Configuration class that gathers all the parameters in one place, together with meta information that can be used to generate both the command line interface and the UI dialogs. The whole configuration can be passed to class init's, who extract whatever they are interested in from there. The class can also have methods for saving and loading itself from files.