Skip to content

get rid off the pytorch dependency that comes with lm_eval harness #8

@timurcarstensen

Description

@timurcarstensen

right now we introduce a pytorch (cpu) dependency because lm-eval harness depends on torch. We only depend on lm_eval harness because we want to be able to download the eval datasets a-priori to scheduling evals since compute nodes don't have internet access. We should be able to get that functionality out of lm eval harness somehow to reduce the install size of our package

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions