Evaluate Command: Config Design and Functionality for Non-Training Model Evaluation

Ouverte
  • Quelque chose ne va pas ?
#285 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
À l'abandon
Stack technique
huggingface, python
Domaine
machine-learning

Piste de recherche

Start from the evaluate command that PR #264 added, and from the training config it reads to load the latest checkpoint. The issue asks for a config design for evaluating arbitrary models, including Hugging Face Hub downloads, so the first step is agreeing on that config shape in the thread rather than writing code. Done means an agreed config format and a tested evaluate path for models outside training runs.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement need update

🎯 Goal (What & Why)

With the merging of PR #264, we will have a separate evaluate command that uses the training config to evaluate a trained model by loading the latest checkpoint.

However, we also need the capability to evaluate arbitrary models — potentially with automatic downloading from the Hugging Face Hub for all supported models.

Here, let's discuss the features we need for such a command and what the configuration file should look like.

🚀 Execution Plan

(This section may start as an incomplete draft but must be defined before implementation begins.)

Step 1: What is the smallest working version?

(Describe the simplest way to implement this feature with minimal effort.)

Step 2: What additional optimizations are possible (but optional)?

(List potential refinements that can be added in later PRs if needed.)

📌 Acceptance Criteria (Must-Haves for Completion)

  • The feature must be functional and tested.
  • The implementation must be documented in practical terms.
  • The PR must include a performance/impact summary.
  • No refactors unless directly necessary for feature completion.

🛠️ Project Management

  • Assign the project to the Fast-LLM project.
  • Set the Estimate field (in days) in the GitHub project.
  • Use the Size field to categorize the PR size (Small/Medium/Large).
  • Assign an owner when opening the issue.
Langage dominant
Python
Étoiles
337
Forks
52
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de ServiceNow/Fast-LLM

Toutes les issues de ServiceNow/Fast-LLM

Issues similaires

Plus d'issues Python

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.