POST /optimize in src/api/app.py constructs a PerDestinationConfig(model_names=["naive_forecaster"]) purely to satisfy LogisticsAPI.__init__, which requires a PerDestinationConfig even though optimize() never uses the forecasting config. This is functionally harmless but misleading — it looks like /optimize cares about forecaster selection when it doesn't.
Tasks:
- Consider decoupling
optimize() from requiring a PerDestinationConfig at construction time (e.g. a separate constructor path, or making optimize independent of forecasting config).
POST /optimizeinsrc/api/app.pyconstructs aPerDestinationConfig(model_names=["naive_forecaster"])purely to satisfyLogisticsAPI.__init__, which requires aPerDestinationConfigeven thoughoptimize()never uses the forecasting config. This is functionally harmless but misleading — it looks like/optimizecares about forecaster selection when it doesn't.Tasks:
optimize()from requiring aPerDestinationConfigat construction time (e.g. a separate constructor path, or makingoptimizeindependent of forecasting config).