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

[FEATURE] Add a "debug mode" to help detailed analysis #929

Open
sarthakpati opened this issue Sep 9, 2024 · 1 comment
Open

[FEATURE] Add a "debug mode" to help detailed analysis #929

sarthakpati opened this issue Sep 9, 2024 · 1 comment

Comments

@sarthakpati
Copy link
Collaborator

Is your feature request related to a problem? Please describe.

Currently, when a model fails to train, there is nothing a user can do other than to get into the code and start putting print statements everywhere, which is cumbersome.

Describe the solution you'd like

It would be good to have this as a parameter so that a few things can be recorded under a new ${output_dir}/debug_info directory.

Describe alternatives you've considered

N.A.

Additional context

The following things can be added (per epoch):

Notes from SP

  • wandb would be great for this, but it needs server deployment [ref], and this is a major bar for a regular user. If we ever have enterprise support, this can be explored as a cloud-hosted solution.
  • From what I have seen, for local deployment, torchexplorer provides the majority of the items we need.
Copy link
Contributor

github-actions bot commented Nov 8, 2024

Stale issue message

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