Stats

  • Locked Locked
  • Replies 7
  • Subscribers 143
  • Views 15072
  • 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

bindkey to plot.il

thecalman

 I need to set a bindkey to schPlot("plot.il"), which I can do alright except that I need to have the outputfile to be different each time so that I am not overwriting anything!

I was thinking maybe append a date/time string to a base filename.  I tried to use the getCurrentTime() function but I need to format it somehow! for an example, I would like "Mar 1 05:23:37 2010" to be "03.01.2010.052337" and then concat this to become my outputfile. ex. "myplotfile_03.01.2010.052337.ps".  Could someone please help me.

Parents

  • This works great. Thank you.  Now I just need to generate jpeg images from my .ps files.  I was going to create a script that would loop through all files in the folder and use ghostscript to convert the .ps files.  I would have to execute this script manually!  Is there a way (I imagine there is...) to get this done using SKILL immediately after each .ps file is plotted?  I have been playing with the system() command and will keep experimenting to get its correct syntax!! ...maybe that is the command I need?  ...is there somewhere that I can get a good SKILL command reference manual?  

Reply

  • This works great. Thank you.  Now I just need to generate jpeg images from my .ps files.  I was going to create a script that would loop through all files in the folder and use ghostscript to convert the .ps files.  I would have to execute this script manually!  Is there a way (I imagine there is...) to get this done using SKILL immediately after each .ps file is plotted?  I have been playing with the system() command and will keep experimenting to get its correct syntax!! ...maybe that is the command I need?  ...is there somewhere that I can get a good SKILL command reference manual?  

Children
No Data

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.