• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC SKILL
  3. How to start these jobs one after another

Stats

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

How to start these jobs one after another

acom
acom over 9 years ago

Hello , 

I have 2 jobs which are needed to be run one after another automatically.But i didn't know how to tell skill that  job1 has been finished and you could  begin job2.

The only signal is that when job1 is done, there is a job1ResultFile which contains words "job1 run successfully." Is it possible to let job2 to recieve the signal as the start signal? It is a little hard to use ipcSleep.Because the running time of job1 varies from cell level to chip level for us.And it seems like that job1 cann't be used as the childprocess of ipcBeginProcess either.

I have given some tries like below:

job1~>job2

I check the running status of job1 manually to make sure it ends.  Then input the below command, Job2 begins successfully.

ipcBeginProcess("grep 'job1 run successfully' job1ResultFile "" 'LAYdatahandle nil 'Job2 "")

But it fails, when i submit job1 and the sentence together.it seems like that at the moment i submit job1, the job1ResultFile has not been gotten compelely.

  • Cancel
Parents
  • acom
    acom over 9 years ago
    It works.Thanks Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • acom
    acom over 9 years ago
    It works.Thanks Andrew
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information