Stats

  • Locked Locked
  • Replies 3
  • Subscribers 125
  • Views 15886
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Plot Schematic Hierarchy into single file

HoWei

Hi,

I did set up my .cdsplotinit to call a script, which allows me to print into PDFs. That is working fine for single schematic pages.

When doing a hierarchical plot from a schematic, it seems like for every plot a new print job is spooled into the print queue.

For this case I do have the workaround, to concatenate all jobs (postscript files) into a single postscript-file and generate a PDF (which is overwritten during each job process) - by the last job I do have a PDF containing all schematic pages from the hierarchy. The problem is, that the concatenated postscript file still exists and I have to delete it manually to get an empty file for the next print-job.

Question 1: Is it possible to have only one print job started for a hierarchical plot, containing all schematic pages ?

This would simplify the plotting and I would not need to concatenate print jobs.

Question 2: Is it possible to get a trigger/function after the last print job that allows me to delete the concatenated postscript-file ?

I can see the log in the CIW window that says "INFO (SCH-1272): Successfully plotted 3 cellviews" and I would make use of this function if possible.

Parents
  • HoWei

    A trigger before the first print job is queued might also help to cleanup the concatenated postscript file. ...

Reply
  • HoWei

    A trigger before the first print job is queued might also help to cleanup the concatenated postscript file. ...

Children
  • Andrew Beckett
    in reply to HoWei

    I don't believe there's any control over the number of jobs submitted, and there's no trigger at the end. I just took a quick look at the source code, and there's no triggers which can be used for this currently.

    A solution would be to call schPlot() yourself, and then you know when it's done because it then returns...

    Regards,

    Andrew.

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.