Request for Extended Runtime in Phase 2

Control Track: CityLearn Challenge
#1

I’d like to address a crucial issue regarding Phase 2 of the CityLearn Challenge: runtime limitations.

In Phase 2, we’re tasked with controlling 9 buildings over three months, including public and private evaluations. However, the 30-minute runtime limit poses challenges, especially for algorithms like Model Predictive Control (MPC). These algorithms need more time, especially on systems with limited CPU resources (e.g., 2 CPUs).

In real-world applications, optimizing nine buildings over three months doesn’t require such tight constraints. The current time limit could limit the diversity of control strategies and discourage the use of valuable algorithms.

I kindly suggest extending the runtime limit to encourage diverse control strategies and inclusive participation. This change would benefit all participants and foster innovation.

#2

Hi @reggie, it is 6 buildings not 9 in Phase private evaluation :). Maybe if runtime is an issue we can extend a bit. Please, any thoughts on this @dipam?

#3

@kingsley_nweye Apologies for any confusion. To clarify further, I was counting both the public and private evaluations. In the public evaluation, we are tasked with controlling three buildings, and in the private evaluation, we control 6 buildings (public 3+private 3）. This brings the total to nine buildings that are being optimized over the three-month period.

#4

Yeah no worries I see what you mean. That’s one way to look at it. just remember you are double counting the public 3 that way since the same public 3 buildings are used in the public and private evaluations.