Trevor Barnes

Thank you for raising the issue, @jaclynr109! And sorry you are experiencing so many environment issues. Just to confirm, you only get this error when you run on the HPC?...

Pretty hacky solution, but to at least get it to run you can just delete the subnetwork from the network, and then re-determine the network topology. This is a band-aid...

As @ktehranchi suggested, changing the `weighting-strategy` in the `clustering.simplify_network` config may resolve this issue. I was running with `demand-capacity` but did not try `population`. https://github.com/PyPSA/pypsa-usa/blob/105edcb08df3a9906b5c9459befd2ce44460e7b8/workflow/repo_data/config/config.default.yaml#L158-L163

See [here](https://docs.pypsa.org/latest/user-guide/v1-guide/#breaking-changes) for breaking changes we may need to be aware of

@ricnogfer To reproduce, are you able to drop in your `scenario`, `foresight`, and `model_topology` settings from the configuration file, please!

Hey @ricnogfer! So the issue with `simplify_network` can be solved by setting the weather year to 2018. Currently, residential and commercial load profiles are tied to 2018 weather data, so...

I do get a very similar error to your original error now, but at `solve_network`, which is kinda odd. Just looking into that now. ``` INFO:gurobipy: INFO:linopy.constants: Optimization successful: Status:...

You changed the snapshots as well? Sorry, should have mentioned that in the original comment. I havent sorted out the issue in solve network, yet. Just trying to trace back...

Hmm... your running on main or develop? I doing my testing off of main right now.

Hey @ricnogfer, sorry, just following up on this. This error persists for you in `simplify_network` still, or you get to `solve_network`? On the `solve_network`, the issue has to do with...