CurrentModeTime greater than defined limit #5
Description
Issue observed for CaseID: 20191030149
From TraderCollection consider BRAEMAR1. The unit's CurrentMode is '1' and T1 is '1', but the CurrentModeTime is '5'. My understanding is that CurrentModeTime should be less than or equal to limit defined for that mode.
{
"@TraderID": "BRAEMAR1",
"@TraderType": "GENERATOR",
"@FastStart": "1",
"@MinLoadingMW": "110",
"@CurrentMode": "1",
"@CurrentModeTime": "5",
"@T1": "1",
"@T2": "1",
"@T3": "1",
"@T4": "1",
"@SemiDispatch": "0",
"TraderInitialConditionCollection": {
"TraderInitialCondition": [
{
"@InitialConditionID": "AGCStatus",
"@Value": "0"
},
{
"@InitialConditionID": "HMW",
"@Value": "146.699996948242"
},
{
"@InitialConditionID": "InitialMW",
"@Value": "0"
},
{
"@InitialConditionID": "LMW",
"@Value": "5.99949359893799"
},
{
"@InitialConditionID": "SCADARampDnRate",
"@Value": "720.021572113037"
},
{
"@InitialConditionID": "SCADARampUpRate",
"@Value": "720.021572113037"
},
{
"@InitialConditionID": "WhatIfInitialMW",
"@Value": "0"
}
]
},
Perhaps a unit can stay in a given mode for longer than the specified duration i.e. it is a strict lower bound, but not necessarily an upper bound on the mode time. Need to investigate further and perhaps reformulate the fast-start unit inflexibility profile constraints. Will not touch for now though - can do this when implementing fast-start unit multi-solve approach. Need to specify this as a caveat for users.