Skip to content
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

Design and add a useful CLI #28

Open
lebrice opened this issue Jul 5, 2024 · 0 comments
Open

Design and add a useful CLI #28

lebrice opened this issue Jul 5, 2024 · 0 comments

Comments

@lebrice
Copy link
Collaborator

lebrice commented Jul 5, 2024

We'd need to think about the kinds of commands that people will be running, and what kind of things we can setup for them.

Ideas:

  • project sync (sync the codebase across all the clusters so it can be used for jobs)
  • project train (...): training run, with a validation set when applicable. No testing.
  • project eval (...): training (without a validation set), (or load from a checkpoint) then evaluate on the test set.
    • I'd ideally like to encourage not using the test set for validation whenever possible.
    • Other "good ML practices" should also be encouraged or even enforced, if that's desirable.
  • project profile (...) same as train, but shorter, with more profiling tools setup?

Idk, just throwing ideas out there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant