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

pyomo.doe adding more verbose output for sensitivity analysis #3525

Draft
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

smondal13
Copy link

Fixes # .

Summary/Motivation:

  • Adding more verbose is helpful to analyze the problem

Changes proposed in this PR:

  • added eigenvalues, determinant of FIM and trace of FIM for sensitivity output
  • changed the method to calculate the eigenvalues

Legal Acknowledgement

By contributing to this software project, I have read the contribution guide and agree to the following terms and conditions for my contribution:

  1. I agree my contributions are submitted under the BSD license.
  2. I represent I am authorized to make the contributions and grant the license. If my employer has rights to intellectual property that includes these contributions, I represent that I have received permission to make contributions and grant the required license on behalf of that employer.

@smondal13 smondal13 marked this pull request as draft March 19, 2025 14:13
@smondal13
Copy link
Author

@adowling2 @djlaky ready for early feedback

@adowling2
Copy link
Member

Next step:

  • Also add solver status

Comment on lines 1534 to 1536
if abs(E_vals.imag[E_ind]) > 1e-8:
self.logger.warning(
"Eigenvalue has imaginary component greater than 1e-6, contact developers if this issue persists."
"Eigenvalue has imaginary component greater than 1e-8, contact developers if this issue persists."
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: this is why "embedded constants are evil". An improved solution would be to declare a module-level constant (maybe IMAG_THRESHOLD) and then use that both in the test and in the message.

@adowling2
Copy link
Member

@smondal13 See #3532 for an example of what @jsiirola is suggesting

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

Successfully merging this pull request may close these issues.

3 participants