-
Notifications
You must be signed in to change notification settings - Fork 10
Improve the handling of multiple metric columns in datasets #274
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
Open
jtuomist
wants to merge
8
commits into
main
Choose a base branch
from
feature/multiple-metric-cols
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
4ef14cd
Longmont: Move trends from actions to nodes; stop using historical ac…
jtuomist 9d8bfec
Make DimensionalFlow.get_flow_node() more robust
jtuomist aae7c18
Longmont: Change ShiftActions to GenericActions with datasets
jtuomist cc7c612
Longmont: Fix additivity of building code and beyond building code
jtuomist 27b27ca
Longmont: Make beyond_building_code match excel logic
jtuomist e0ad9be
Merge branch 'main' of https://github.com/kausaltech/kausal-paths
jtuomist 805e74e
Longmont: Make benchmark_energy_use follow the excel logic to match v…
jtuomist e8e6b28
Improve handling of multiple metric columns in datasets
jtuomist File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For a strict drop of a missing literal column, this now raises a generic
Exceptionbefore Polars can raise its documentedColumnNotFoundError. Any caller that catches the Polars exception to distinguish a missing column from unrelated failures will no longer handle this case, despite the change being intended to improve only the error message. Raisepl.exceptions.ColumnNotFoundErrorwith the enhanced text instead.Useful? React with 👍 / 👎.