Talk:SPICE

Hi, the article states
Hi, the article states "The original SPICE program was released under a restrictive license, which makes it difficult for others to improve upon the original software." and yet I have read in print ( I think it was in the IEEE Spectrum ) that SPICE was originally "public domain" and I think they implied it was the first "open source" program. Can someone source the assertion about the original license, and change it if necessary ? --Rob

Question moved from article:

Does anyone know the revision level of the first C implementation of SPICE?

If you know the answer add it to the article in the appropriate paragraph. dave 10:02, 1 Sep 2003 (UTC)


 * not currently known, but check the following for clues... Waveguy


 * http://www.intusoft.com/isspice4.htm

Found it. SPICE 2G.6 (1983) is the last FORTRAN version. SPICE 3 is C. -- RTC 20:08, 9 Sep 2003 (EDT)

Hello, I am Paolo Nenzi, ngspice developer. Ngspice is not covered by the GPL license, it is still covered by the old BSD license. We asked Berkeley's Regents some years ago to change spice license to new BSD (no obnoxious clause) but we got no answer. Thanks for citing ngspice in wikipedia!

I feel that this article could also include information about the SPICE elements such as their function, computational methods, parameters, etc. -- Peter 1:53 AM, 2 Apr 2006 (EST)

XSPICE merged
The brief text from the page XSPICE has now been merged to this article. The XSPICE page has been changed to a simple redirect. DFH 08:05, 19 October 2006 (UTC)

restrictive license?
SPICE was released under what amounts to the BSD license (or Don Pederson's force of will, depending on how you look at it). There's a line in the article (poorly placed) which asserts BSD is restrictive. It's not gnu, and in many senses it's less restrictive than gnu. Can we remove this line? A note about licensing is probably appropriate, since SPICE was probably the first open source program, but the emphasis should be switched to point out how the nascent IC industry benefitted from a freely available open source circuit simulator. 66.69.212.211 15:10, 4 November 2006 (UTC) Steve

This point is moot; Berkeley went to BSD licensing per their download page. YoungGeezer 17:31, 10 November 2007 (UTC)

SPICE Acronym Meaning
The explanation of the SPICE acronym has been changed to match standard usage (previously C was 'circuits', now 'circuit'). 25 Jan 2007, Steve

External/commercial links
I propose eliminating the links to commercial simulators. This has gotten out of hand and has been flagged by Wikipedia as excessive and in need of cleanup. To replace them, I think it would be sufficient to simply say, "There are many commercial circuit simulators, some of which are direct descendants of SPICE2," with a possible mention of PSPICE and HSPICE as being two of the earliest and most popular. Steve, 66.69.212.211 14:13, 25 January 2007 (UTC)

I've moved the Macspice link from 'Open Source' to 'Commercial', as it's not open source. However, it is free (as in beer), so it doesn't really belong there. The thing is there are so many commercial spice implementations, and it's not really as if a few dominate the market so it's got to be all or nothing.144.173.6.75 11:39, 2 February 2007 (UTC)

Open source
SPICE has been referred to for many years as one of the first open source programs. The open source article mentions source code available to the general public with relaxed or nonexistent IP restrictions; as I remember, the SPICE license was essentially BSD, which is certainly one of the less restrictive. However, now I can't find the original language in the source code or elsewhere, and the current software agreement is about as open as can be found. I suggest the language in the article about restrictions and an acknowledgment clause can be removed. YoungGeezer 05:04, 29 June 2007 (UTC)

This point is moot; Berkeley went to BSD licensing per their download page. YoungGeezer 17:31, 10 November 2007 (UTC)

Compact model council purpose
The CMC mainly exists to make it easy to port model parameters from one simulator to another. This requires standard models and standard model parameters. The reason this is important is primarly for fabless (or fab-lite) semiconductor companies, who need to take the model parameters given by the foundry and use them in various simulators. While there are still syntax differences between the different simulators, a standard model will at least ensure that a given set of model parameters will produce a known result on each of the simulators (assuming the implementation follows the reference implementation faithfully, which is again somewhat iffy but at least there's a standard to use to beat on the implementations that deviate).

All that said, the CMC website mentions this obliquely through the first sentence in their vision statement: "Standardized compact models for all major technologies so that customer communication and efficiency can be enhanced." "Customer communication" basically comes down to sets of model parameters to run into standard models.

As it turns out, the "standard interfaces" thing dropped out. Eight or nine years ago a couple of standard interfaces were proposed, but neither caught on, because of their implicit assumptions about simulator architecture. A better approach is being pursued now, using Verilog-AMS as an executable specification and a program like ADMS to translate the Verilog-AMS into simulator code (with some intervening steps and a bit of work).

So I'm reverting the change regarding the purpose of the CMC.

YoungGeezer 18:02, 12 November 2007 (UTC)
 * Thanks for the explanationBrews ohare 18:10, 12 November 2007 (UTC)

Vaccardi link does not work
I undid this link because it didn't work Brews ohare (talk) 01:10, 24 November 2007 (UTC)

Tina-TI?
There seems to be a toggling of the TI simulator reference from TISPICE to Tina-TI and back. The paragraph in question is about industrial circuit simulators. TISPICE is a SPICE derivative which is written, supported and used in TI. Tina-TI is a give-away for marketing purposes, was not written in TI, and as far as I know is not used (except by marketeers) in TI. The proper reference for the paragraph is to TISPICE. YoungGeezer (talk) 14:14, 24 December 2007 (UTC)

Lists of compact models
I (somewhat regretfully) removed the recently added list of 'alternative compact models'. The article is about SPICE; the GEIA Compact Model Council and standard models is somewhat related, but I don't think the SPICE article is the correct place for a list of all possible compact models -- there are sooo many of them, everyone has their favorites, and most have only limited usage. Perhaps the transistor models article would be a better place. YoungGeezer (talk) 19:11, 26 January 2008 (UTC)

perhaps some discussion of gnucap could be added?
Perhaps there are complicated reasons for not doing so, but it seems that adding some reference to gnucap as an open source project largely inspired by the SPICE program family might be in order?  71.197.225.209 (talk) 00:13, 31 May 2008 (UTC)


 * Gnucap is to be commended for being an independent circuit simulation development and open source.   But, other than being a circuit simulator, it is about as unrelated to SPICE as is possible:  It did not originate at Berkeley, and as far as I know is not derived from SPICE (I think Al is somewhat proud that it is new and perhaps better code).  I'm interested in the SPICE article remaining focused on SPICE -- the article history shows that excessive links to commerical simulators were purged some time back and I'd just as soon not accumulate another mass of links to other simulators, open source or not.  There is a category for Electronic Circuit Simulators and separate articles on a number of simulators -- perhaps that would be the better route for mentioning gnucap... YoungGeezer (talk) 05:28, 28 June 2008 (UTC)

Reversion of citation inserted by 132.178.10.11
After thinking about this for a week, I removed this citation. For starters, it referenced an IC design textbook by a Boise State faculty member, posted from a Boise State IP address. Looks bad, at minimum. Secondly, the citation was added in proof of the assertion that simulation with SPICE is an industry-standard practice. Probably every circuit-design-related textbook written in the last 25+ years mentions using SPICE -- perhaps one of the great classics might be mentioned (Gray & Meyer, Mead & Conway, Weste, etc.) but I'd really like to not see an accumulation of "cite my text too" cruft. (And really, the canonical reference for the assertion is probably the IEEE Spectrum article on Don Pederson, if needed.) YoungGeezer (talk) 23:54, 13 July 2008 (UTC)

Blog links, etc.
I just removed a link to a blog, which was formatted as a reference. Referencing your own blog is a bit on the self-serving side, and when the blog content is trivial it doesn't help keep the quality up. The reference was in regards to translation of a netlist to equations; a better reference would be to a standard text on the subject, e.g. Singhal and Vlach -- if it fit more cleanly into the article as it stands. YoungGeezer (talk) 01:05, 30 May 2009 (UTC)


 * Hi YoungGeezer. I understand your concern about linkspam, but I'm wondering if you'd reconsider your deletion of the reference to my blog posting. I believe the deletion is a case of "throwing out the baby with the bath water." The reason for my blog posting and my linking to it is that, as a product manager for a commercial version of SPICE, I find that my customers benefit from a short explanation of how SPICE works. I agree that implementers of circuit simulators need to invest the time on the textbooks. But I believe that textbooks aren't a great investment of time for SPICE users and that something shorter works best, hence the blog posting. Although the posting is short, and the introductory paragraph reviews the history of SPICE, I object to your characterizing the article as "trival." Larry Nagel (with whom I correspond occasionaly by email) left a comment on the posting, and several readers sent me messages that they found it helpful. I'm not going to undo your deletion because I don't want even the appearance of being "self serving." But I do appeal to you to read the posting in full, consider it (and its intended audience), and restore to reference as it was. Thanks in advance for your consideration. Woz2 (talk) 14:22, 1 June 2009 (UTC)
 * The point is moot now because the info was printed in traditional media (EMC Journal). Updated ref to reflect this.Woz2 (talk) 12:02, 9 July 2009 (UTC)


 * Colin, I've reverted your edit. It's still apparently self-serving and a possible conflict of interest, whether you and I disagree on 'trivial' or not. (And I still think the article is trivial. Publishing in a trade journal doesn't raise the level.) On Wikipedia, you shouldn't write your own biography and generally you shouldn't cite your own material unless you really are a notable person in that area, but probably not even then.  Also, the Wikipedia conflict of interest guidelines may apply here: You’re selling a circuit simulator and stand to benefit from attention to it.  If someone other than you (a disinterested third party, not a marketing colleague, etc.) thinks your article is appropriate for citation, please let them make the case. YoungGeezer (talk) 13:39, 17 July 2009 (UTC)
 * YoungGeezer, Here's my response:


 * Non-Triviality 1) Larry Nagel liked the article enough to leave a positive comment. I seems to me that Larry Nagel's opinion is worth something. 2) An editor in a traditional media publication thought it worthy. From my perspective it seems your threshold for worthiness is a moving target. First your objection seemed to be "blogs aren't worthy, only traditional media." Now that tradition media has picked it up it's "Only certain traditional media sources are worthy." It seems to me that the data are changing, but your opinion is not. Where does it say (in wikipedia policy, not in your opinion) that EMC Journal is unworthy?


 * WP:COI says "Do not edit Wikipedia to promote your own interests, or those of other individuals or of organizations, including employers, unless you are certain that the interests of Wikipedia remain paramount" (my emphasis). I am certain that the interest of the community are paramount in placing this reference, and the community is poorer because of your deletion. Everyone who has communicated to me about this article (except you) has found it useful, as I mentioned above. The article (which is applicable to any version of SPICE, free or commercial, Agilent or non-Agilent) mentions my company's product only tangentially. Thus, the remain paramont condition is satisfied.


 * BTW, unlike me, you don't reveal your identity so I'm unable to determine whether your deletion of my contribution is in your interest or the community's. I'd be grateful if you'd rectify that situation by stating your name and affiliation either publically (preferably) or privately via the email link Special:EmailUser/Woz2 that I have enabled on my user page (and which BTW you have not: It's an opt in check box under "My preferences"). Best regards, Woz2 (talk) 11:37, 18 July 2009 (UTC)


 * Woz2: It’s nice that Larry made a comment. Larry is a nice guy. But basically, though, it comes down to you saying your stuff is wonderful, and insisting that it be cited in this Wikipedia article. Further, you are certain that you are not in a conflict of interest situation and "the community is poorer" since your article isn’t referenced. Sorry, but I disagree. I think citing one’s own writing is often self-serving and hubris, especially when better references exist. If it is a great contribution and it fits, someone will cite it for you.  And I still think prima facie evidence suggests a conflict of interest.


 * The dozens of other SPICE-ish software vendors have, for the most part, had the decency to not inject links to their own blogs, application notes, trade press articles, press releases and such, and I’m grateful just from the standpoint of not having to sort through the mess. The SPICE article was earlier flagged for a problem with vendor link-spam, and it would be nice to avoid similar situations in the future.


 * Anyway, we disagree. As I mentioned, if others, e.g. a third-party editor, become convinced of the appropriateness and quality of your work, they can make a case for inclusion if so inclined.


 * About my identity: This episode leaves me happy that I’m semi-anonymous. Suffice it to say, I work in circuit simulation but my simulator is not sold. I’ve cited none of my publications. If anything in the SPICE article hints as to a conflict of interest, you’re free to point it out or edit it out.  This is Wikipedia, after all. YoungGeezer (talk) 14:51, 25 July 2009 (UTC)
 * Neutral editor: Please undo the deletion http://en.wikipedia.org/w/index.php?title=SPICE&action=edit&undoafter=301176119&undo=302597842 Woz2 (talk) 12:31, 27 July 2009 (UTC)
 * I got here from the requested edit template placed on this page. I'm treating this more like a third opinion request since there is a dispute here between two parties.  Regarding the edit in question, although it was made within a conflict of interest I do believe the source was added is reliable, and I don't think it overtly promotes the editor who made it.  I have performed the requested edit (while tidying up the added reference) but feel free to revert and discuss if there is an issue with it other than the conflict of interest.  Them  From  Space  11:20, 4 August 2009 (UTC)

Reproduce chunks of the SPICE manual in this article?
Thanks to bassplr19 for being bold in adding the model parameter tables, but I'd like to revert and discuss whether we should reproduce the SPICE manual here in this article. I think not. I think it would be better to add a link to the UCB archive. See WP:NOTAMANUAL Thanks Woz2 (talk) 14:25, 7 August 2009 (UTC)


 * I heartily concur, an encyclopedia article is not a manual. It appeared bassplr19 got midway through the edit and thought better of it - and just as well, since the various MOSFET tables go forever. The article has links to a manual, Berkeley pages and the standard models; best to leave it at that, I think... YoungGeezer (talk) 03:14, 8 August 2009 (UTC)

djo
hej —Preceding unsigned comment added by 87.58.167.33 (talk) 18:03, 16 November 2009 (UTC)

Multisim
I removed the association of Multisim and XSPICE because the cited article contradicts the claim. The Multisim article says "Multisim is one of the few circuit design programs to employ the original Berkeley SPICE based software simulation" not XSPICE. BTW, the claim in the Multisim article is itself unsourced, but that's another can of wax... Woz2 (talk) 14:28, 10 March 2010 (UTC)

Fast-SPICE
I've reverted the addition on Fast-SPICE, mainly because it detracts from the topic. I'd encourage anyone interested in the topic to write an article about it and put a link in the SPICE entry. In particular, start with Hermann Gummel's MOTIS, some similar work at UC Berkeley, then to on to mention the current crop of commercial fast-SPICE programs: nanosim, hsim, ultrasim, etc. The only real relation to SPICE that any of these have is that they are not SPICE, and are often much faster but also often not very accurate. YoungGeezer (talk) 17:40, 10 July 2010 (UTC)

Simulator links
In the interest of not getting into the situation this article had in 2007, when it was flagged for excessive external/commercial links, I've removed a list of links to other simulators. Since a list exists, the List of free electronics circuit simulators, and a category, Category:Electronic circuit simulators already exist for this purpose, let's please use them and not clutter this article. YoungGeezer (talk) 18:11, 10 July 2010 (UTC)

Versions with source code available
The contents of this list is somewhat mixed and does not always follow the two topics "Spice Version" and "Source code available".

Spice2 and Spice3:  o.k.

Cider:              o.k.

ngspice:            o.k.

Spice+: This is a graphical user interface, but not Spice itself. Many others of this kind are available (kjwaves, GNU Spice GUI, gsim ...).

tclspice:           o.k.

XSPICE:             o.k.

Spice Opus: Free spice simulator. Some source code is available on code models, but no source code on the simulator itself.

PyOPUS: An optimization framework with source code, but not Spice itself. Others are available (ASCO ...).

LTSpice: Probably the most widely used free Spice simulator, but definitely no source code available.

Because I am a little bit biased, somebody else might take care of an update to this list.

James HV (talk) 09:14, 26 December 2011 (UTC)

CANCER was an acronym for "Computer Analysis of Nonlinear Circuits, Excluding Radiation," a hint to Berkeley's liberalism of 1960s
Can someone explain this sentence? Is this comment about the use of a morbid acronym? Unless someone can clarify "a hint to Berkeley's liberalism of 1960s" it should be removed. — Preceding unsigned comment added by 192.12.184.6 (talk) 21:07, 11 July 2012 (UTC)


 * Sure. I added a citation in Larry Nagel's own words. Woz2 (talk) 22:49, 11 July 2012 (UTC)


 * Unfortunately, neither Berkley or liberalism are discussed in the citation given. So I'm tagging it as having failed verification. 67.51.98.218 (talk) 04:17, 18 July 2014 (UTC)


 * In the cited talk Nagel says: "The name CANCER was a brash statement that this program never would simulate radiation and was not funded by the defense industry. It was developed at Berkeley in the sixties, remember!" I think that opposition to the defense industry within American liberalism are well established. I'm going to remove the tag if you don't mind. Markluffel (talk) 23:19, 30 September 2014 (UTC)


 * Right before I read this, I found an article that specifically mentions radiation effects. If these programs are the predecessors to CANCER and SPICE, then the statement about not simulating radiation effects makes sense. Gah4 (talk) 07:55, 14 January 2020 (UTC)

TISPICE
Judging by this it appears it was just a user-contributed TI-92 program. I doubt it was the company's internal design/simulation software. JMP EAX (talk) 10:57, 7 October 2014 (UTC)


 * Oh, good grief. I worked at TI when SPICE2 came out. TISPICE was the internal version of SPICE2 and the group that did TISPICE had a tight relationship with Berkeley. The main people involved at that point were Robert Colon and Bert Epler; later Ping Yang joined TI and made some contributions (although he was actually in research rather than design automation); Lawrence Arledge and I believe Farid Najm came later to continue improvements to TISPICE. Lots of other sharp folks were involved. Google some of those names (e.g. Lawrence Arledge Texas Instruments) if you're disbelieving. YoungGeezer (talk) 17:50, 4 September 2019 (UTC)

External links modified
Hello fellow Wikipedians,

I have just added archive links to 2 one external links on SPICE. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
 * Added archive https://web.archive.org/20140706082430/http://www.analog.com/en/content/adisimpe/fca.html to http://www.analog.com/en/content/adisimpe/fca.html
 * Added archive https://web.archive.org/20060926034314/http://www.cs.sandia.gov/nacdm/talks/Nagal_Larry_NACDM2004.pdf to http://www.cs.sandia.gov/nacdm/talks/Nagal_Larry_NACDM2004.pdf

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

Cheers. —cyberbot II  Talk to my owner :Online 01:47, 17 October 2015 (UTC)

External links modified
Hello fellow Wikipedians,

I have just added archive links to 1 one external link on SPICE. Please take a moment to review my edit. If necessary, add after the link to keep me from modifying it. Alternatively, you can add to keep me off the page altogether. I made the following changes:
 * Added archive https://web.archive.org/20110511071827/http://www.geia.org/index.asp?bid=597 to http://www.geia.org/index.asp?bid=597

When you have finished reviewing my changes, please set the checked parameter below to true to let others know.

Cheers.—cyberbot II  Talk to my owner :Online 07:43, 7 February 2016 (UTC)

Adding a section on coolSPICE
Hey everyone, this is my first time on a talk page so excuse me if my etiquette is a little rough. I was on the SPICE page and realized that there is no information on coolSPICE, which is not too surprising because coolSPICE is a relatively newly developed version of SPICE circuit simulators. That being said, I think it is imperative that it be added to this page because the things that the coolSPICE simulator can do, no other SPICE simulator can. Basically, it is specially built for the simulation of cryogenic-temperature CMOS circuit modeling as well as wide bandgap semiconductor transistor modelingZossA (talk) 15:08, 25 May 2016 (UTC)


 * I forgot to include some sources sorry. Here they are: http://www.techbriefs.com/component/content/article/ntb/tech-briefs/software/19394 and http://coolcadelectronics.com/proj4.html

ZossA (talk) 15:10, 25 May 2016 (UTC)

Main links to SPICE dubious
The main links in the box at the top right at the page all point to the same software which is NOT SPICE for electronics. Could someone fix this? — Preceding unsigned comment added by Polariseke (talk • contribs) 04:46, 18 April 2017 (UTC)

FIXED! Kenji Akano (talk) 13:13, 21 April 2017 (UTC)

It seems wikipedia automatically adds this URL from wikidata. Removed it there, is this sufficient to keep this link from popping up? — Preceding unsigned comment added by 131.111.185.12 (talk • contribs) 5 jun 2017 20:13 (UTC)
 * That should do it. We should keep an eye on the Wikidata page, in case the guy adds the links again. --Ajv39 (talk) 20:37, 5 June 2017 (UTC)
 * The guy did add them again. He apparently had no clue what he'd done wrong. (It doesn't help that Wikidata's editing interface gives you no way that I can see to add an edit summary.) I've just cleaned up all the incorrect info in the Wikidata entry (an unrelated repository and Gentoo package and an incorrect claim that SPICE used C++), which were all caused by confusion with the SPICE remote-display system. I modified the Wikidata description to point out the confusion, added a more detailed explanation of the confusion to the item's Talk page, and also added a message to that Wikidata editor's talk page explaining what I had done and why his fixes were incorrect. Hopefully that will solve the problem. --Colin Douglas Howell (talk) 01:14, 28 July 2017 (UTC)
 * OK, the problem should now be solved for good. Once that Wikidata editor learned that there were two different entities named SPICE, he created a new Wikidata item for the remote-display system and added a "different from" property to both items to indicate that they are distinct. I just sent him a thank-you response. :) So I don't think we'll have any more issues with that. --Colin Douglas Howell (talk) 20:10, 1 August 2017 (UTC)

External links modified
Hello fellow Wikipedians,

I have just modified 2 external links on SPICE. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
 * Added archive https://web.archive.org/web/20150224064144/http://www-device.eecs.berkeley.edu/bsim/?page=BSIMSOI to http://www-device.eecs.berkeley.edu/bsim/?page=BSIMSOI
 * Added archive https://web.archive.org/web/20071017140132/http://pspmodel.asu.edu/ to http://pspmodel.asu.edu/

When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.

Cheers.— InternetArchiveBot  (Report bug) 01:08, 3 September 2017 (UTC)

LTSpice now owned/maintained by Analog Devices
Since AD bought linear technology and now owns/maintains LTSpice, some of the text on this page probably needs to be updated to reflect that Nrjank (talk) 04:10, 5 December 2019 (UTC)


 * AD bought LT 3 years ago, but every article hasn't been cleaned up to change this fact. You don't need to post anything in talk sections, just change the company name, just like I did before posting a reply.  •  Sbmeirow  •  Talk  • 11:37, 5 December 2019 (UTC)

ECAP
I wonder if SPICE has any connection to the earlier ECAP from IBM? Gah4 (talk) 07:57, 14 January 2020 (UTC)
 * OK, I hear from people from Berkeley that, through intermediate programs, there is lineage from ECAP to SPICE. I don't know about finding an actual WP:RS, though. Gah4 (talk) 10:27, 1 March 2020 (UTC)
 * It seems that after ECAP, the path goes through SCEPTRE and CIRCUS, to satisfy demand for understanding the effects of radiation of circuits. Then CANCER, specifically not for radiation effects, and then SPICE. Gah4 (talk) 11:46, 21 June 2021 (UTC)
 * It seems that after ECAP, the path goes through SCEPTRE and CIRCUS, to satisfy demand for understanding the effects of radiation of circuits. Then CANCER, specifically not for radiation effects, and then SPICE. Gah4 (talk) 11:46, 21 June 2021 (UTC)
 * It seems that after ECAP, the path goes through SCEPTRE and CIRCUS, to satisfy demand for understanding the effects of radiation of circuits. Then CANCER, specifically not for radiation effects, and then SPICE. Gah4 (talk) 11:46, 21 June 2021 (UTC)

Open Source
SpiceOpus is free, but is not open source. There is some source code available from the SpiceOpus web site covering only the XSPICE code models, code that has be published elswhere as well. But there is no source code for the simulator core made available.

There is a very recent open source spice available, in that Stephen R. Whiteley has made his former commercial WRSpice open source (see http://wrcad.com).

Other companies based on Spice have ended their commercial activities as well and have made their programs freely available, but not open source: Spectrum Software with Microcap (http://www.spectrum-soft.com/download/download.shtm), AnaSoft with SuperSpice (https://www.anasoft.co.uk/) as well as 5Spice (http://www.5spice.com/, only with limited features).

Thus it may be advisable to add, in addition to "Open Source" and "Commercial", a category "Free Spice Simulators" to reflect this quickly changing environment.

James HV (talk) 09:15, 14 June 2020 (UTC)

Removal of "Exclusion" chapter
I have removed this chapter, summarizing its previous content in a single sentence. In my view it does not make any sense to write a lengthy report on what SPICE cannot do (it fails to do many, many things indeed).
 * I agree with this Constant314 (talk) 17:40, 6 May 2022 (UTC)

Removal of "Transient Simulation" chapter
This chapter has been completely inconsistent with the SPICE wiki. Being only one of several simulation types, it does not make sense to describe one method only, however it also does not make sense to repeat the many books and manuals on SPICE usage here. There also had been decribed commands (e.g. .op 20ns) which are not available in most SPICEs, and there has been no citation where this might stem from.

James HV (talk) 13:52, 06 May 2022 (UTC)

Removal of Ellis Cohen as creator of the memory management
Previously, the article said Spice2 had "an innovative FORTRAN-based memory allocation system developed by another graduate student, Ellis Cohen." I removed the portion about Ellis Cohen because Nagel said in 2013 "There is this persistent rumor that Ellis Cohen added dynamic memory allocation to SPICE 2. Both Ellis and I will tell you that it was I who added dynamic memory allocation to SPICE 2.  It's in my thesis." with ref to where he said this (ltwiki.org)

This was however the only reference to Cohen. I added his role in "Ellis Cohen led development from version 2B to the industry standard SPICE 2G6, released in 1983" per Nagel's comment about this at Nagel's site. 88.18.98.188 (talk) 19:57, 26 November 2022 (UTC)

Links to the SPICE1/2/3 no longer work
The website bwrcs.eecs.berkeley.edu/Classes/IcBook/SPICE/ no longer seems to work, however its archive is available: https://web.archive.org/web/http://bwrcs.eecs.berkeley.edu/Classes/IcBook/SPICE/ 78.177.143.13 (talk) 13:24, 30 January 2024 (UTC)


 * ✅ • Sbmeirow  •  Talk  • 15:02, 30 January 2024 (UTC)