-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
False error reported? #415
Comments
Yes, Qucs-S shows "Simulation error" message if the log contains the string "error". It is not obvious how to fix it, because Ngspice has no unified format for the error message. Maybe some RegExp would help. |
I am not sure and don't know the model but I think error_amp_out is a node name - the output of the regulator error amplifier. So don't worry - no ngspice problem. |
Yes the "error" is false. Unfortunately after I GREP'd the ngspice source I found dozens of different "Error" text strings. Most contain "Error:" but a lot don't. It would be hard to parse so many variations and the number only increases every release. |
@dwarning , The solution may be to flag "Simulation error" in the Qucs-S only if the log contains "Error" or "ERROR" strings. The "error" in lower case most probably means the node name. |
I searched the ngspice forum and GREP'd the source and found the following error strings. There are many more... Error: |
I have added TODO list for this issue. |
I have implemented pattern recognition for error messages. The node name error should not raise error flag anymore. Closing this as completed. |
An error was reported during simulation but the Log only shows the term "error_amp_out" which isn't an actual error.
Attached is the project and a ngspice test folder using DuSpice including the log file.
TODO
LM317_LM337_prj.zip
LM337_ripple.zip
The text was updated successfully, but these errors were encountered: