Derating and temperature violation cost functions

[mariagrazia-tristano]

Hello,

While looking at scores from some preliminary simulations I came across something odd. Looking at the baseline scores file, for some of the tracks the velocity derating cost function J_v and the temperature violation cost function J_T are zero, which is perfectly plausible when no derating is necessary and no temperature violation occurs. On the other hand, the two corresponding competitor cost functions can be bigger than 0, in case of temporary violation of the battery temperature constraint or in case derating is deemed necessary in some time instants.

However, looking at how the normalisation is performed, the score-checking MATLAB function seems to "punish" the competitor by setting the normalised cost to be infinite when the baseline cost is zero and the competitor one is bigger than zero. So if the competitor incurs in that second "if" case of the score-checking function, essentially the entire cost function becomes infinite. Is there a reason why it was set that way?

Moreover, since the temperature violation cost function in the Simulink file saves the maximum temperature without any following integration, wouldn't this imply that say a 1°C temperature violation for 1s would affect the cost function in the same way as if one kept the battery temperature constantly at 1°C above the maximum for the whole duration of the simulation?

Many thanks.