Check functionality and stability of add_RES_constraints

[ekatef]

Currently, we have a warning when running add_RES_constraints which mentions that some unexpected results can occur if temporal clustering is applied or due to an unexpected change of technologies.

Describe the feature you'd like to see

There is a need to clarify which particular problems can be expected and implement fixes for them. #1276 implements refactoring changes for add_RES_constraints which could be probably helpful in this investigation.

[ekatef]

@yerbol-akhmetov I know you have been working a lot on this part. May you have any insights on particular issues which can be expected for add_RES_constraints?

[yerbol-akhmetov]

@yerbol-akhmetov I know you have been working a lot on this part. May you have any insights on particular issues which can be expected for add_RES_constraints?

Hi, @ekatef. The constraint worked well when we last checked it. It was working as intended. But I have not checked it after merge with sector coupled model. I am not quite sure about the warning there.

[ekatef]

@yerbol-akhmetov I know you have been working a lot on this part. May you have any insights on particular issues which can be expected for add_RES_constraints?

Hi, @ekatef. The constraint worked well when we last checked it. It was working as intended. But I have not checked it after merge with sector coupled model. I am not quite sure about the warning there.

Thanks a lot for the explanation. Great to hear that there is no known pitfalls there, and a great point for testing with the sector-coupled model. I also have an impression that the constraint works pretty well after having tested it for linopy PR. So, hopefully we may be able to remove the warning after a couple more additional tests.