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

What's the goal? #1

Open
leloykun opened this issue Dec 22, 2024 · 0 comments
Open

What's the goal? #1

leloykun opened this issue Dec 22, 2024 · 0 comments

Comments

@leloykun
Copy link

Hi all! I find this interesting, and I would like to participate.

However, it's unclear to me what the "goal" is. I.e., when should we stop the clock?

  1. When we reach a certain training validation loss?
  2. When we reach a certain generation quality, according to some fidelity metric?
  3. Both?

Additionally, when should the clock be running? In the modded-nanogpt speedrun, we only allow the clock to run during training loops, including data fetching between steps, but not during validation. I propose we do the same as modded-nanogpt and make this explicit and also log everything into text files.

And IMO, it's best to have an initial, downloadable benchmark logs we can compare against.

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