- Rating
- 3(+1)
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper presents EvolveLight, a multi-agent framework for adaptive traffic signal control under changing demand. Its Planning, Modeling, and Skill Development Agents use DCMA-RL and simulation feedback to choose among timing, heuristic, and RL strategies and to develop new controllers. EvolveLight improves traffic metrics on several SUMO networks. However, the experiments do not clearly separate the effects of LLM reasoning, access to different controller families, and the extra training used for generated RL controllers.
Critical strengths
- The paper studies how traffic signal controllers can adapt when demand changes across locations and over time.
- EvolveLight uses LLMs for occasional planning and controller development, while lightweight controllers make the real-time signal decisions. This design avoids an LLM call at every decision step and makes the deployment setting more practical.
- The framework covers planning, controller generation, skill retrieval, simulation feedback, and continued adaptation. The evaluation uses multiple datasets and includes long-horizon experiments, ablations, and an analysis of inference cost.
Critical weaknesses
- The experiments do not separate the contributions of LLM reasoning, skill evolution, dynamic controller selection, training the generated controllers, or the individual DCMA-RL design choices. Most importantly, the evaluation lacks a non-LLM selector with access to the same controller portfolio.
- The training protocol is not described in enough detail to assess computational fairness. The paper does not explain how a generated RL controller is initialized and trained, or whether the baselines receive comparable training, simulation, and compute budgets.
Questions for authors
- What happens after the Modeling Agent produces an RL_PLAN? In particular, when does training begin, how is the controller initialized, and is it trained from scratch or warm-started? Please also report the RL algorithm, simulation horizon, episode or update budget, and stopping criterion.
- The released code appears to train an RL controller during TRAIN_AND_SIMULATION, before the candidate strategy is validated and deployed. Does this happen only once before deployment, or again at every strategy-update window during rolling evaluation? Is the checkpoint then frozen for the final evaluation?
- How does the trained controller's performance affect optimization of the outer LLM agents? Is the traffic outcome after RL training used as the terminal GDPO reward for the generated trajectory? Does the RL loss directly affect the LLM update, or do the two optimization processes interact only through the resulting traffic performance?
- The paper evaluates different levels of initial skill-library availability and includes a frozen-strategy variant. However, these experiments do not separately isolate the contributions of online skill updates, dynamic controller-family selection, generated-controller training, and the individual DCMA-RL design choices. Could the authors disable these components one at a time, especially role-wise optimization, reward decoupling, and reward normalization, to verify their individual contributions?
- How would EvolveLight compare with a rule-based or learned non-LLM selector that has access to the same timing, heuristic, and RL controller families? This comparison is needed to distinguish the benefit of LLM reasoning from that of the controller portfolio.
- Section 3.2 and Eqs. (7)–(8) assign the same downstream improvement reward to every skill invoked in a training-and-simulation round. How does this mechanism avoid misattributing improvements when multiple skills contribute differently? Separately, the released implementation includes counterfactual evaluation for training the Skill Agent. Was this mechanism used in the reported experiments, and does it affect only the Skill Agent’s DCMA-RL reward or also the per-skill utility scores used for retrieval? Please clarify the relationship between these two credit-assignment mechanisms.
Dear reviewers,
We have now received the author responses to your raised questions and concerns. Please go through them. Also, have they answered your questions appropriately? Please also look other reviewers' strengths / concerns. Have they changed your perception of the paper? In all cases, please communicate with the authors. It is important that we let them know what relevant issues still exist or have been answered. Please remember we have limited time to get any further responses from them.
Regards,