Coordinate System can now be set directly in file, which is the better place for this information, and thus the switch here is no longer needed. kai, feb'24
Coordinate System can now be set directly in file, which is the better place for this information, and thus the switch here is no longer needed. kai, feb'24
Coordinate System can now be set directly in file, which is the better place for this information, and thus the switch here is no longer needed. kai, feb'24
Coordinate System can now be set directly in file, which is the better place for this information, and thus the switch here is no longer needed. kai, feb'24
– try to use services.addPlanStrategyFactory or services.addPlanSelectoryFactory. There are cases when this does not work, which is in particular necessary if you need to re-configure the StrategyManager during the iterations, and you cannot do this before the iterations start. In such cases, using this method may be ok. kai/mzilske, aug'14
– one can achive many (all?) of the same functionality at the config level, see QSimComponentsConfigGroup. Doing it through the config group is consistent with other places where we have similar functionality (which is to bind things by Guice, but activate them separately), e.g. related to org.matsim.core.config.groups.ReplanningConfigGroup. I think that the parallel functionality here just makes it more difficult, since maintainers need to learn another dialect. kai, jan'25
– I don't know why this method exists; it makes reading code harder rather than easier. Maybe there used to be something more complicated which eventually got refactored into the current version? kai, feb'20
– I don't know why this method exists; it makes reading code harder rather than easier. Maybe there used to be something more complicated which eventually got refactored into the current version? kai, feb'20