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

ValueError: No objects to concatenate in query_physical_crossborder_allborders #390

Open
fleimgruber opened this issue Feb 18, 2025 · 0 comments

Comments

@fleimgruber
Copy link
Contributor

fleimgruber commented Feb 18, 2025

During the time interval 23:00--02:00 (UTC) the function query_physical_crossborder_allborders consistently errors with ValueError: No objects to concatenate.

The result of my analysis is that in

df = pd.concat(imports, axis=1, sort=True)
imports is the empty list [] because in

entsoe-py/entsoe/entsoe.py

Lines 2270 to 2273 in c03c604

except NoMatchingDataError:
continue
im.name = neighbour
imports.append(im)
there are only NoMatchingData errors and thus imports is never appended to.

I would suggest to raise an error message that is meaningful for the user, for instance "NoMatchingData error for all neighboring crossborder flow queries" instead of letting the Pandas ValueError bubble all the way up to the user.

If you are ok with that proposal, I am going to prepare a PR.

@fleimgruber fleimgruber changed the title ValueError: No objects to concatenate for query_physical_crossborder_allborders ValueError: No objects to concatenate in query_physical_crossborder_allborders Feb 18, 2025
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

1 participant