-
Notifications
You must be signed in to change notification settings - Fork 3
[SC-15520] Expose qualitative text agent to vm library #493
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
juanmleng
wants to merge
10
commits into
main
Choose a base branch
from
juan/sc-15520/expose-qualitative-text-agent-to-vm-library
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
10 commits
Select commit
Hold shift + click to select a range
79329c3
Add AI-assisted text generation to log_text
juanmleng 8cb15b9
Add content ID helper for section-based text generation
juanmleng 1c47bc7
fix lint
juanmleng 892e691
Add text generation result workflow
juanmleng 4dc7fa4
Update text generation result metadata
juanmleng 1a6c9d3
Update qualitative text generation notebook
juanmleng 8beb29d
Update notebook
juanmleng c19e9f5
Update text generation revision logging
juanmleng 49a74ac
Update text generation section handling
juanmleng 77d997f
Fix lint in result imports
juanmleng 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
975 changes: 975 additions & 0 deletions
975
notebooks/how_to/qualitative_text/qualitative_text_generation.ipynb
Large diffs are not rendered by default.
Oops, something went wrong.
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
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.
The content_id for
model_overview_textshould bemodel_overview, otherwise you would not be reusing the pre-existing block:Similarly, I get an error for:
Error:
The correct
content_idshould bedataset_summary_text:Similarly, the last cell should be fixed so it can run on the current version of the chun template, without modifications. This will require 2 changes:
content_idsi.e.model_overviewinstead ofmodel_overview_textcontent_iddoes not exist in the template. For example, the blockintended_use_textdoes not exist in the template, so we should be able to specify thesection_idwhere it should be appended. Note that this is already supported by test results blocks, e.g.:For the case of
intended_use_textwe could call.log(section_id="intended_use").With these changes in place we should be able to populate 100% of the churn document with this notebook.