Enumerate models and datasets accessible from HELM#21
Open
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is a WIP for wrangling all 'officially' available models and scenarios with metadata from HELM. The goal is to expose the applicable HELM APIs in MAGNET for resolving evaluation queries. Right now, models and scenarios each have a simple helper class that attempts to collect callable definitions and link metadata.
Models
The published model descriptions and deployments (i.e. docs list) can be found in HELM under
/helm/config/model_[deployments, metadata].yamland are read inhelm/benchmark/config_registry.py. Models with unsupported or deprecated tags are removed in this helper to align the metadata and models.Scenarios
Scenarios (i.e. docs list) do not have a single exhaustive source. Instead,
RunSpecFunctiondefinitions from/helm/benchmark/run_specs/*.pyare read inhelm/benchmark/run_spec.py. If you can instantiate aRunSpec, then thescenario_specattribute contains the HELM path to aScenariodefinition. This helper replicates therun_spec.pyfunctionality to also collect allScenariodefinitions fromhelm/benchmark/scenarios/*.py. The current gap is matching eachScenarioto aRunSpec.Next steps:
Scenario->RunSpec