-
Notifications
You must be signed in to change notification settings - Fork 14
Add sv_run_id to training data ingest #202
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
Merged
wagnerlmichael
merged 10 commits into
master
from
201-add-sales-val-run_id-to-res-model-outputs
Feb 2, 2024
Merged
Changes from 6 commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
ce10410
Add sv_version to training data ingest
wagnerlmichael 02f4d66
Switch to correct column
wagnerlmichael 0abe909
Add run_id to assessment outputs
wagnerlmichael 4636f8a
Remove selection criteria
wagnerlmichael f9d7e71
Fix linting errors
wagnerlmichael 1690868
Fix linting errors
wagnerlmichael e45ca4a
Remove assess stage changes
wagnerlmichael 142c451
Fix spacing
wagnerlmichael c8e26c6
Fix spacing
wagnerlmichael 50c8c4a
Merge branch 'master' into 201-add-sales-val-run_id-to-res-model-outputs
dfsnow 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
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
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.
[Nitpick, non-blocking] You can leave out the
sv_outlier_typestuff since it's only pertinent to my PR (#199), one of us can just resolve merge conflicts if the other merges first!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.
Also, a question for @dfsnow: Do we actually need
sale_recent_{n}_run_idin the assessment data? I figure it's most pertinent in the training data, right?Uh oh!
There was an error while loading. Please reload this page.
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.
I suppose we could always merge the training data back to the assessment data to get the run ID. Alright, @wagnerlmichael I think @jeancochrane is right, let's actually nix this from the
assessstage. Sorry for the extra work.