We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
modulus-sym:1.5.0
No response
How to output loss value per iter when using BFGS optimizer? and the TensorBoard only output a loss value
[21:00:24] - lbfgs optimizer selected. Setting max_steps to 0 [21:00:24] - [step: 0] lbfgs optimization in running [21:19:36] - lbfgs optimization completed after 20000 steps [21:19:36] - [step: 0] record constraint batch time: 7.847e-02s [21:19:37] - [step: 0] record validators time: 3.937e-01s [21:19:37] - [step: 0] record inferencers time: 2.740e-01s [21:19:39] - [step: 0] saved checkpoint to outputs/ldc_2d_bfgs [21:19:39] - [step: 0] loss: 3.858e-03 [21:19:39] - [step: 0] reached maximum training steps, finished training!
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Version
modulus-sym:1.5.0
On which installation method(s) does this occur?
No response
Describe the issue
How to output loss value per iter when using BFGS optimizer?
and the TensorBoard only output a loss value
Minimum reproducible example
No response
Relevant log output
[21:00:24] - lbfgs optimizer selected. Setting max_steps to 0
[21:00:24] - [step: 0] lbfgs optimization in running
[21:19:36] - lbfgs optimization completed after 20000 steps
[21:19:36] - [step: 0] record constraint batch time: 7.847e-02s
[21:19:37] - [step: 0] record validators time: 3.937e-01s
[21:19:37] - [step: 0] record inferencers time: 2.740e-01s
[21:19:39] - [step: 0] saved checkpoint to outputs/ldc_2d_bfgs
[21:19:39] - [step: 0] loss: 3.858e-03
[21:19:39] - [step: 0] reached maximum training steps, finished training!
Environment details
No response
Other/Misc.
No response
The text was updated successfully, but these errors were encountered: