Open danielolsen opened 3 years ago
Parallel transmission line issue. Remove the other two parallel lines you will see the error pops up for some other parallel branches. Remove all parallel lines you will not see this error again anymore. It is an issue with SWITCH's post processing code.
Interesting. Perhaps Switch generates the outputs for BuildTx
based on looking up branches by their to/from pairs, and because of this it generates outputs for branch 88606 (the first of the parallel), but none of the others. For the purposes of running Switch successfully all the way through, perhaps we should combine all parallel branches when we generate the inputs.
@danielolsen, if we do that, should we then also keep the expanded grid this way? The we can keep the power flow as it is, i.e, we don't have to decompose the value since we will have always one line between two buses.
@danielolsen, if we do that, should we then also keep the expanded grid this way? The we can keep the power flow as it is, i.e, we don't have to decompose the value since we will have always one line between two buses.
I would say that it depends on what we want to use the expanded grid for. If we want to run it through a PCM, maybe we don't want to lose the information about the parallel paths. There would also be implications for reliability analyses, one big branch vs. several smaller ones makes a difference.
@danielolsen, if we do that, should we then also keep the expanded grid this way? The we can keep the power flow as it is, i.e, we don't have to decompose the value since we will have always one line between two buses.
I would say that it depends on what we want to use the expanded grid for. If we want to run it through a PCM, maybe we don't want to lose the information about the parallel paths. There would also be implications for reliability analyses, one big branch vs. several smaller ones makes a difference.
We would just combine the parallel lines into the grid_to_switch module then. In that case we could save the information to later quickly decompose the power flow.
:beetle:
Bug summary
When running a Switch model using the code currently in the
mvp
branch, the solver finds an optimal solution, and writes outputs to a pickle file, but then throws a ValueError.Code for reproduction
Preparation:
Launching:
Actual outcome
The output produced by the above code, which may be a screenshot, console output, etc.
Expected outcome
No error.
Environment
Please specify your platform and versions of the relevant libraries you are using:
git rev-parse origin/HEAD
):b162f259b1d678226246964f2980f695c2d21e19