Primary competition visual

Smart Energy Supply Scheduling for Green Telecom Challenge by ITU

18 000 CHF
Completed (~2 years ago)
Prediction
840 joined
157 active
Starti
06 Aug 24
Closei
30 Sep 24
Reveali
03 Oct 24
User avatar
meganomalyZindi Staff
Zindi staff member
Zindi
Scoring Function
Help · 22 Aug 2024, 10:33 · 14

Hello!

Thanks for bearing with us. We're pleased to share the scoring function with you. Please find it here - https://zindi.africa/competitions/smart-energy-supply-scheduling-for-green-telecom/data

Please note that -1 submissions will be removed from the leaderboard today. Moving forward you will be provided with an error message in these cases.

Good luck!

Discussion 14 answers
User avatar
EbiendeleAmbassador
Zindi Ambassador

I'VE BEEN GETTING The site name or time length is wrong, please check your submission

Upvotes 1
User avatar
EbiendeleAmbassador
Zindi Ambassador

I'VE BEEN GETTING The site name or time length is wrong, please check your submission and The strategy is unfeasible, please re-design your strategy. every time i make submision or am i the only one experiencing ths?

Upvotes 0
User avatar
marching_learning

Hi @meganomaly THERE IS AN ERROR in the calcSingleSiteScore function (below) with potential huge impact on the leaderboard.

Indeed when the battery discharges, the function uses the discharge coefficient till the end. But the discharge coefficient (1.2) is greater than the charge coefficient (0.2). This will artificially increase the stage of charge (SOC) and WILL MAKE FEASIBLE SOME STRATEGIES THAT SHOULD NOT HAVE BEEN FEASIBLE. And it adds randomness to the evaluation because once it discharges for the first time, the charging steps are calculating with the discharge coefficients. Strategies that forced earlier discharges will be advantaged.

This is the two problematic lines of the function:

if sum < 0:
coe = float(config["disCoe"])

#

To solve it, it suffices to put the following line just after the for loop. :

coe = float(config["coe"])

😎

Upvotes 7
User avatar
wizzard

Nice Catch. @Zindi @meganomaly

Upvotes 2
User avatar
meganomalyZindi Staff
Zindi staff member

Thank you @marching_learning! We are taking a look

Upvotes 2
User avatar
Upvotes 0
User avatar

this problem solved and error metric script updated

Upvotes 0
User avatar
marching_learning

Huge important catch @Yisakberhanu. So I was right to insist concerning scoring function 😎. Now this is the second error in the scoring script. This makes the competition even sweeter. Couldn't wait for the scoring script update. Potentially this will increase the feasibility solutions space.

Upvotes 1
User avatar

My bad, thank you :) !

EDIT: I don't know why my original message got deleted, in case someone else makes the same mistake as me (debunked below by marching_learning):

I had thought that there was a mistake in the scoring function, that the rated_voltage of the battery was not taken into account in the state of charge dynamics. But it's my mistake.

Upvotes 0
User avatar
marching_learning

No in this case they got it right because of the second line:

capacity = float(config["ratedCapacity"]) * float(config["ratedVoltage"])

Read it back, you'll see 😎.

Upvotes 1
User avatar

Without the 1/4 it would be the SOC after 1 hour, but the time step is 15 mins, I think it is ok.

Upvotes 0
User avatar

This has been affecting my submission. @meganomaly. Please when it is corrected let us know!

Upvotes 0
User avatar

@meganomaly

Could you clarify if this is a bug and if yes if you are going to fix it?

I guess there's a way to check the plausibility of this, if you know that outages are either very frequent or very sparse or if you know if they are more supposed to be at night or during the day.

Upvotes 0
User avatar

where is the test data?

Upvotes 0