[Cyan]<DATools6.1>SpiceOps>SpiceOpsDoc.tioga!2

SpiceOpsDoc.tioga

Christian LeCocq February 17, 1987 10:06:03 am PST

SPICEOPS: SPICE <-> DATOOLS PACKAGE

DATOOLS — FOR INTERNAL XEROX USE ONLY

SpiceOps: A link between Spice and the DATools

Christian Le Cocq

User Manual

Release as [DATools]<DATools6.1>SpiceOps>SpiceOpsDoc.tioga

Abstract: SpiceOps provides (as much as possible) simple ways to use the Spice Circuit simulator on the Vax in the Unix environment from our DATools in the Cedar environment.

Created by: Christian Le Cocq

Maintained by: Christian Le Cocq <LeCocq.pa>

Keywords: Circuit Simulation, Schematics Extraction,

XEROX Xerox Corporation
Palo Alto Research Center
3333 Coyote Hill Road
Palo Alto, California 94304

For Internal Xerox Use Only

Temporary Documentation

SpiceOps loads a "Sinix -> Spice" command in the Space-O CD menu. Clicking this command after selecting a cell will produce a file named ///YourDirectoryPath/(CellTypeName OR SpiceInputDeck).spice. The file contains the skeleton of the spice input. Read it, compare it to what you would have typed in, and let me know the differences !

The spice command is then executed in your spice local directory of the VaxC, provided that your Unix and Cedar password are identical. The exact line executed is:

cd spice ;spice yourFileName rw

which seems to suit the needs of the alpha user (Ed Richley). If your working environment is different on the Vax side, either change it to understand the preceding line, or let me know your preferences.

When the Spice listing comes back from the vax, it is automatically parsed and displayed as a PlotGraph viewer (that is Rosemary like), with the names converted back from Spice node numbers to CoreFlat names if the information is still available.

Last, you can replay your favorites by the Command tool command

SpiceOps fileName

which does the same as above with no name translation.