Why won't schPlot() work here?

So I have a .il file, let's call it blah.il. It's used to define
schPlotOptions. It looks like this:

schPlotOptions = '(nil
library "library"
cell "circuit"
view "schematic"
version "0.0"
multisheet nil
indexsheet nil
hierarchy t
viewlist "schematic"
ignorelibs "basic sample"
stopcells ""
copy 1
outputfile "/directory/chip/project/process/me/circuit.ps"
plotter "djet" <-- (So I get color .ps)
papersize "A"
plotsize (8.0 6.5)
offset (0.0 5.5)
units "inches"
orientation "Portrait"
display "display"
tmpdir "/usr/tmp"
mail nil
)

So, in the CIW, I type schPlot("blah.il") and out comes:

Start Plotting...
plotServ 7.02, build a, 03.01, static
*Error* greaterp: can't handle (nil > 0)

Doing everything in the GUI works, but I want to do this kind of thing
in batches, so I need this SKILL thing to work. What am I doing wrong
here?

Thanks,
Jake

 

20.09.2005: Thread 'Using schPlot() to send a plot to a file'
PM

 

I checked that thread. The problem here is that it doesn't plot at
all. If I bring up the plot menu after loading "blah.il", all of the
options are correct, and if I tell it to then plot from the GUI, it
works fine. However, typing in schPlot("blah.il") brings up the error
message above. Isn't the GUI just running schPlot()?

 

How did you create your template?

Comparing those thread
' unit "mm"'

with yours:
' units "inches"'

i would say there is at least one typo in your template ...
PM

 

Well, it's like I said in the last post, if I just load the template:
load("blah.il")
it returns "t", and if I then bring up the GUI window, all of the
options are just how I want them. Then, if I tell it to plot in the
GUI, it works just as I want it to. However, if I run schPlot() from
the CIW, I get the error. Again, my question is, what command is the
GUI running? My "blah.il" has to be correct because everything loads
fine and shows up correctly if I run schHiPlot().

 

Hi,

This code works fine in batch mode on my side.
Verify the options you set are compliant
with definition of "djet" plotter in your cdsplotinit file:

; Set options for plotting
schPlotOptions = '(nil
library nil
cell nil
view nil
bBox nil
outputfile nil
plotsize (10.0 7.0)
papersize "A4"
plotter "djet"
scale 1.0
grid nil
multisheet nil
indexsheet nil
hierleveldown 0
hierarchy nil
unit "inches"
center t
area "whole"
plotToFile t
plot "cellview"
header nil
notes nil
noteText "Generated by myself."
time "now"
copy 1
offset (0.0 0.0)
orientation "landscape"
tmpdir "/usr/tmp"
mailto ""
mail nil
display "display"
scope "/"
)

; Define lib, cell, view, bbox, and output file to be plotted.
schPlotOptions->library = library
schPlotOptions->cell = cellname
schPlotOptions->view = viewname
schPlotOptions->bBox = list( list(-5 -5) list(5 5))
schPlotOptions->outputfile =
"/directory/chip/project/process/me/circuit.ps"

; Exec plot command
schPlot()




Sam.

 

I've played around with it some more, and I've come to the conclusion
that something is just buggy within Cadence. For instance, if I open
up the submit plot window, and click on the various radio buttons,
depending on what order I select them, they will either cooperate or
not. For instance, if I want a centered plot that is fit to the page
in portrait, if I select the options in this order:
1) fit, 2) center, 3) portrait
It works fine.
If I select portrait first, clicking on the center radio button causes
it to select itself and then instantaneously deselect itself. Loading
the template file that is created by selecting everything I want works,
except that I don't the same offset everytime. So, erasing some of
those options and letting the plotting engine choose its own defaults
causes it to break. It seems to be a function of the size of the
schematic I try it on as well. Sometimes it works, sometimes it
doesn't, it just depends which schematic I'm pointing the thing to. I
think I've done everything I can on my end. I think I'm just going to
have to end up doing the file plotting manually. It's a shame, because
the rest of my script works so well, this is the only little bug that I
can't seem to track down.