-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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
No Callbacks for Validation Batch Step - How To Get Progress of Validation? #1165
Comments
hello, as you stated you want to have a logger, not a callback, you can write a custom logger... |
Hi, @Borda, thanks for the reply. I looked over the documentation for Loggers and it will indeed be helpful for my future work. However, looking at LightiningLoggerBase, I don't see anything for capturing the epoch or batch progress for training (i.e. Epoch 1 of 5 or Batch 1 of 200) as I am doing above so that I can use Streamlit's I do think a Streamlit logger would be an excellent addition to Lightning but I am still in the early exploratory phase of using Streamlit myself and it currently seems like it would require a bit of work to make a useful generic dashboard a la Tensorboard. I'll continue experimenting on my end to see where it goes. |
In case this is still relevant to you, we now also have callbacks for validatation and test batches! |
Closing this. As far as i can tell, with the recently introduced new callback methods (validation_batch_start etc) it is now possible to track the progress as you desired. |
🚀 Feature
The Callbacks has two functions
on_batch_start
andon_batch_end
. The documentation and code execution shows that these are only called for training batches, not validaton (or test). I am building a Callback for my own logging/dashboarding via Streamlit and I have a requirement to track the progress of both the train batch steps and validation batch steps during training. I see that there is a validation progress bar in the console during training - how is this implemented (if not via a Callback)?Current Code
The text was updated successfully, but these errors were encountered: