You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Access to the solver's Solve() function inner loop is of interest to third party software and clients of libcaffe. One obvious basic use-case is the tracking of the current model loss during training.
What would be the best practice for providing access to the inner loop ? I've looked at past issues and PR and it seems there was an effort to bring a custom callback into the loop (see #738), that appears to have eventually aborted.
The inner loop is very simple, which is good, and thus for my current use case, I do simply turn Solver's protected variables into public ones in solver.hpp, and rewrite a tiny loop outside of libcaffe. As ugly as it is, it remains a very minimal change ;)
How to best help you clear this issue if you believe it is relevant to others, as it is relevant to me ?
Thanks!
EDIT: another use-case is the ability to kill a training job, and this is better done from the inner loop.
The text was updated successfully, but these errors were encountered:
Access to the solver's Solve() function inner loop is of interest to third party software and clients of libcaffe. One obvious basic use-case is the tracking of the current model loss during training.
What would be the best practice for providing access to the inner loop ? I've looked at past issues and PR and it seems there was an effort to bring a custom callback into the loop (see #738), that appears to have eventually aborted.
The inner loop is very simple, which is good, and thus for my current use case, I do simply turn Solver's protected variables into public ones in solver.hpp, and rewrite a tiny loop outside of libcaffe. As ugly as it is, it remains a very minimal change ;)
How to best help you clear this issue if you believe it is relevant to others, as it is relevant to me ?
Thanks!
EDIT: another use-case is the ability to kill a training job, and this is better done from the inner loop.
The text was updated successfully, but these errors were encountered: