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
Need documentation / examples using artifact names #47
Comments
A couple comments/questions:
|
|
You may be interested in following the entirely in-memory approach to job submission. Take a look at the method It is possible to construct your job config entirely in memory, and only write to a temporary working directory for job submission, meaning you don't need to manually constuct your YAML file. If we follow this pathway, then we can begin to make use of more utility methods for populating your config classes within the driver script. |
The model artifact from a tuning is
run_name-model
, which means that if you want to load a model for an eval (e.g. lm-harness) where the run will be updated with eval results, you have to write the following:I think this is ok, but we might want to document it or put it into our examples/tutorials.
Also, all artifacts have a fixed name which is f"{run_name}-{artifact_type}". I currently do not see the need to allow for custom artifact names, but wanted to check your opinion on this.
The text was updated successfully, but these errors were encountered: