Plots to file from schematic editor

I removed the ":EPSPreviewType=none: \" line and it generates previews
fine. The ":EPSPreviewByteOrder=BigEndian: \" line doesn't seem to
have any effect (I tried changing it to LittleEndian).

Cheers,

Roger

 

We don't appear to have a raptor PNG output filter here (although
perhaps I misunderstood what you meant), but I have been playing
around and using Richard Griffith's post as a start I have
successfully used:

---
PNGOut|HP Office Jet D Color: \
:manufacturer=Hewlett Packard PCL: \
:type=intCLR: \
:spool=/eee/vlsi/Cadence/cdsPNG.sh: \
:maximumPages#1: \
:resolution#600: \
aperSize="A4" 4758 6846 0 0:
---

as an entry for .cdsplotinit, with the following as cdsPNG.sh:

---
setenv PATH /opt/csw/bin:$CDSDIR/tools/plot/bin:$PATH
setenv file /var/tmp/cadPlot$$

cat - > $file

raptor -a -m color $file | XWDout > ${file}.xwd
convert -trim ${file}.xwd ~/plot.png
rm -f $file
rm -f ${file}.xwd
---

Where convert is one of the Image Magick ( http://www.imagemagick.org/
) tools.

Cheers,

Roger

 

You could combine the postscript .cdsplotinit entries and the hpjet to

As the responses have indicated, most likely you'll write a shell
or perl script to run the pdf conversion.

However, there's another way which is totally automatic.
No scripts whatsoever to write!

a) Install the Adobe Acrobat Distiller & tell it to 'watch' a directory.

b) Then, simply placing any number of PostScript files into the
watched directory (thousands at a time if you desire),
will AUTOMATICALLY distill any number of PostScript plots to PDF.

c) A log file will log the events.

Nothing could be simpler.
John Gianni

 

You could combine the postscript .cdsplotinit entries and the hpjet to

Thank you!
It works with the following:
in .cdsplotinit

SaveAsPDF|PDF, PS:\
:manufacturer=Adobe: \
:type=postscript2: \
:resolution#600: \
:maximumPages#1: \
aperSize="A4" 4688 6806 160 130: \
:spool=/pathtoskript/cds2pdf:

in cds2pdf:

#!/bin/csh
cat - > /tmp/cdsplot.ps
ps2pdf /tmp/cdsplot.ps ~/cdsplot.pdf
/bin/rm -f /tmp/cdsplot.ps

My stupid error, not having it working right away, was not setting
executable permissions to the file :-(
But afterwards it works fine.
Regards Harald

 

.... or a little bit simpler (assuming ps2pdf is in your PATH):

:spool=ps2pdf - > cdsplot.pdf:


BTW to all in this news group:
Why the hell cadence developers and the most of users are writing/using
this horrible csh-scripts???

Hint: google on "10 to 1000 reasons why not to use csh for scripting"


Regards

 

I agree, csh is a good interactive shell, but pretty lousy for scripting. sh
is far better for scripting (it has functions, for a start).

However, if the script is only a few lines long and pretty simple, it's not that
bad, and there's nothing particularly compelling to make you use either sh or
csh.

There's a real mix in the IC tools. A quick (rough) measurement:

csh:

In tools/bin : 25
In tools/dfII/bin: 20

sh/ksh

In tools/bin: 43
In tools/dfII/bin: 32

Personally I tend to use a bit of a mixture. csh for simple things I'm throwing
together, or sh if I'm feeling better behaved, or perl or awk if I need
something moderately fancy (or even tcl).

Andrew.