-
Notifications
You must be signed in to change notification settings - Fork 1
Training fixes #53
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
Training fixes #53
Conversation
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
76a923a to
2046bad
Compare
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
AnkitaNaik
left a comment
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.
LGTM!!
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
33e0ffd to
5b87887
Compare
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
Co-authored-by: siyuhuo <[email protected]>
Signed-off-by: Benjamin Elder [email protected] <[email protected]>
AnkitaNaik
left a comment
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.
LGTM!!
| print(f"Datasets Loaded for {format} turn data.") | ||
| print("------------------------------------------------------------------------------------------------------------------------------------------------------------------------------") | ||
| assert set(data_no_scenarios_dict.keys()) == set(data_with_scenario_dict.keys()) | ||
| # assert set(data_no_scenarios_dict.keys()) == set(data_with_scenario_dict.keys()) |
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.
Is this assertion not valid in exploratory trajectories? @benjamin-elder
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.
@AnkitaNaik yeah that seems to be the case. The alternate traces are sort of randomly dispersed I guess, so there's no guarantee that you won't have a case where the non-scenario doesn't have one and the scenario does, or vice-versa.
| from transformers import AutoModelForCausalLM, AutoTokenizer | ||
| device = "auto" | ||
| model_path = "ibm-granite/granite-3.0-8b-base" | ||
| model_path = "ibm-granite/granite-4.0-micro" |
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.
Good catch!!
Changes to the training loader to use context response pairs.
Changes to tool call env and evaluation.py to enable parallel/multiprocess inference.