pyOptSparseDriver option hist_file
Good afternoon, colleagues.
pyOptSparseDriver option hist_file
Good afternoon, colleagues.
pyOptSparseDriver option hist_file
Good afternoon, colleagues.
pyOptSparseDriver option hist_file
Good afternoon, colleagues.
In OpenMDAO, is there an indication of how long the total Jacobian takes to assemble?
The openmdao driver results object outputs timing for derivative computation time (driver_res.deriv_time). Is there any way to see how that’s distributed between the sum of the compute_partials time and the assembly of the total jacobian?
In OpenMDAO, is there an indication of how long the total Jacobian takes to assemble?
The openmdao driver results object outputs timing for derivative computation time (driver_res.deriv_time). Is there any way to see how that’s distributed between the sum of the compute_partials time and the assembly of the total jacobian?
In OpenMDAO, is there an indication of how long the total Jacobian takes to assemble?
The openmdao driver results object outputs timing for derivative computation time (driver_res.deriv_time). Is there any way to see how that’s distributed between the sum of the compute_partials time and the assembly of the total jacobian?
How to handle large sparse inputs/outputs within an OpenMDAO model?
I’m looking for general advice for dealing with large, highly sparse inputs/outputs within OpenMDAO.
Problem with Implicit Component and Coupled components
I have a few questions on the strategy for my problem setup.
Discrete Controls in Dymos
I’m working on a dymos problem which represents a simplified building energy model. I would like to add some discrete controls – essentially just binary on/offs – and have some questions.