NgSpice/Shared.py: Make ngspice warning detection more robust - #6
Open
e-dworkin wants to merge 1 commit into
Open
NgSpice/Shared.py: Make ngspice warning detection more robust#6e-dworkin wants to merge 1 commit into
e-dworkin wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughNgSpice stderr classification now recognizes ChangesWarning classification
Estimated code review effort: 1 (Trivial) | ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This single-line PR changes the way that PySpice/Spice/NgSpice/Shared.py:_send_char detects warnings versus errors. The current system detects warnings by
content.startswith('Warning:'). This is an issue or any warning message that does not start with the exact string'Warning:'. The fix is to make this more robust by checking'Warning:in content`.This was causing an issue with larger, stiffer netlists that required dynamic gmin stepping in order to converge. Ngspice can simulate these just fine with dynamic gmin stepping, but in doing so generates a line such as:
Trying gmin = [...] Warning: Further gmin increment. This is a benign warning, but is detected as a fatal error since'Warning:'appears in the middle of the string rather than at the beginning. Thus, PySpice then discards the simulation since it believes it has errored.Here is a sample netlist that was causing this failure and requiring dynamic gmin stepping, using FreePDK45 and ngspice 41. It was characterized through CharLib:
Summary by CodeRabbit