Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPLEX: Warning, line 133208941: Name 'x10609872' does not exist. #385

Open
thomgeo opened this issue Nov 26, 2024 · 2 comments
Open

CPLEX: Warning, line 133208941: Name 'x10609872' does not exist. #385

thomgeo opened this issue Nov 26, 2024 · 2 comments

Comments

@thomgeo
Copy link

thomgeo commented Nov 26, 2024

Dear all,

I am getting several of these warnings when using linopy with PyPSA:

Warning, line 133208941: Name 'x10609872' does not exist.

It looks to me like a constraint or variable, that CPLEX expects is not available? The network is a modified pypsa-eur network, to which I added different system components.

Best,
Georg

@FabianHofmann
Copy link
Collaborator

hey georg! this shouldn't happen .... could you look which constraint should contain the variable "133208941"? you can do that with n.model.variables.get_name_by_label(133208941)

I could imagine that there is a wrong masking of the variable which does not happen in the constraint. so in consequence the variable would appear in the constraint definition but not in the variable definition as where it is masked/filtered

@thomgeo
Copy link
Author

thomgeo commented Nov 27, 2024

Thanks Fabian! After your comment, I wanted to investigate whether this has to do with linopy/PyPSA releases that came after the latest PyPSA-Eur version (0.13), and indeed I managed to solve the issue now by downgrading PyPSA (and thereby linopy) to the lowest version that was mentioned in the environment.yaml.

Don't know if this is even worth following up on, but with the latest version I also got some mentions of repeating rows, which was usually an indicator that the run would fail (for example "Row 'c6164160' repeats.")

I will just leave it here, in case it might be helpful. But it might also just be a result of incompatible packages, so feel free to ignore it, of course :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants