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

spice4qucs: DC analysis not found in netlist #564

Closed
ldpgh opened this issue Oct 5, 2016 · 5 comments
Closed

spice4qucs: DC analysis not found in netlist #564

ldpgh opened this issue Oct 5, 2016 · 5 comments
Assignees

Comments

@ldpgh
Copy link
Contributor

ldpgh commented Oct 5, 2016

Hello, it seems the DC analysis is not exported to Ngspice (no .DC in the netlist seen)

If Qucsator is used saveOp=yes provides all device information as desired.

spice4qucs 0.0.19 @ Win7Pro

@ldpgh
Copy link
Contributor Author

ldpgh commented Oct 5, 2016

AC analysis works as expected
TRAN analysis works as expected

@ra3xdh ra3xdh self-assigned this Oct 6, 2016
@ra3xdh
Copy link
Contributor

ra3xdh commented Oct 6, 2016

DC analysis in Qucs is approximate equivalent of SPICE .OP analysis. OP is performed automatically when TRAN or AC is executed and .DC don't require to be explicitly added into the SPICE netlist. Also you can use "Show bias" (press F8 key) to see operation point. SPICE .DC is emulated with Qucs DC+ParSweep. I haven't previously used saveOp option to look at DC bias. I will consider later how to add putting OP into dataset feature.

You may use the following two places for bugtracker for Qucs-S:

  1. The following spice4qucs discussion thread Spice4qucs. A tool to simulate Qucs circuit with ngspice #77
  2. My home repository https://github.com/ra3xdh/qucs You can open issues related to SPICE supports here. Don't use it to report bugs of mainline Qucs!

I think main Qucs repository should not be used for posting issues on spice4qucs (except #77 and #181), because it can lead to mixing up of mainline Qucs and Qucs-S bugs.

@ldpgh
Copy link
Contributor Author

ldpgh commented Oct 6, 2016

Regarding 1.

  • With all those very intersting informations (w.g Xyce) in #77 I did not mixed it with my small issues.
  • What about adding a Wiki page for those nice informations.

Regarding 2.

  • There is no "issue" Tab on this page ... that's the main bottleneck for me.
  • 1st tried http://qucs.sourceforge.net bug-tracker, but got the impression all folks are running GitHub.

Agree with you keeping spice4qucs separated from main-line.

@ra3xdh
Copy link
Contributor

ra3xdh commented Oct 6, 2016

I have enabled issues at my home repository. See https://github.com/ra3xdh/qucs/issues

@ra3xdh
Copy link
Contributor

ra3xdh commented Oct 30, 2016

Transferred to my home repository as related to spice4qucs subsystem only. See https://github.com/ra3xdh/qucs/issues/10 to continue discussion.

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

2 participants