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

Qucs-S 25.1.0 win 10/64 #1263

Closed
mikhailmihalkov opened this issue Mar 7, 2025 · 6 comments
Closed

Qucs-S 25.1.0 win 10/64 #1263

mikhailmihalkov opened this issue Mar 7, 2025 · 6 comments

Comments

@mikhailmihalkov
Copy link

With a simple simulation, the simulation completion window hangs for 10-20 seconds on the win 10 platform (on different machines) at the end of the process. On the Linux platform, it happens instantly without hanging. If necessary, I can provide a sample

@ra3xdh
Copy link
Owner

ra3xdh commented Mar 7, 2025

Sorry, I cannot reproduce this issue. The Ngspice simulation works without delay on my Windows 10 machine. Please check the settings in Simulation->Simulation settings Maybe you have set wrong Ngspice version.

@mikhailmihalkov
Copy link
Author

mikhailmihalkov commented Mar 7, 2025

Sorry, I cannot reproduce this issue. The Ngspice simulation works without delay on my Windows 10 machine. Please check the settings in Simulation->Simulation settings Maybe you have set wrong Ngspice version.

bug.zip
Default Simulator Settings ngspice-44.2

@dwarning
Copy link

dwarning commented Mar 7, 2025

The root cause is the 1ns edges in pulse pwm source which follow in a huge result file of 160Mbyte in cache dir and 114Mbyte in working dir. Needs roughly 10-20s on my win11 too.

@mikhailmihalkov
Copy link
Author

The root cause is the 1ns edges in pulse pwm source which follow in a huge result file of 160Mbyte in cache dir and 114Mbyte in working dir. Needs roughly 10-20s on my win11 too.

On Linux, under the same conditions within one machine, it takes 1-3 seconds

@ra3xdh
Copy link
Owner

ra3xdh commented Mar 7, 2025

The root cause is the 1ns edges in pulse pwm source which follow in a huge result file of 160Mbyte

This cannot be fixed. One should avoid the huge simulation datasets. The huge datasets indicates that you are doing something wrong.

@ra3xdh ra3xdh closed this as completed Mar 7, 2025
@mikhailmihalkov
Copy link
Author

mikhailmihalkov commented Mar 7, 2025

The root cause is the 1ns edges in pulse pwm source which follow in a huge result file of 160Mbyte

This cannot be fixed. One should avoid the huge simulation datasets. The huge datasets indicates that you are doing something wrong.
I gave an example to understand the difference in performance, and not an example of a correct simulation of 1-3 seconds and 20-30 seconds? Is it 20 times different? Or is it some kind of Linux glitch?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants