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

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.

Parents

  • Hello Andrew,

    Here it is my detailed information.

    Background :

    we have a skill gui which helps us to intergrate 3 steps based on calibre drc.That is ,In the skill gui, we have already intergrated 3 steps(that is (1)calibre -drc step1; (2)calibre -drc step2;(3)calibre -drc step3).By clicking button 1 manually in the gui, we could submit the job1 (calibre -drc step1) into the remote server.The same for step2 and step3.Now we would like to run these 3 steps one after another automatically.

    The virtuoso we are using is 6.1.6.14.

    Issues: 

    I am thinking whether it is possible for us to fullfill this kind of automation by skill too.( we could manuplate the gui button by skill script).But the difficult part is that how we could know step1 (calibre -drc step1)has been done.The only signal is that there is some file job1ResultFile which contains words "job1 run successfully" when it is done.  

    Examples:

    step 1: calibre -drc step1;

    step 2 :calibre -drc step2

    step 3: calibre -drc step3

    Base on the skill gui, submit step1 in machine 1~>Base on the skill gui, submit step1 in machine 2~>Base on the skill gui, submit step3 in machine 3.

    Is there any way for skill to know :

    yes, step 1 has been done because i could got the sentence  "job1 run successfully"  in   job1ResultFile.Now i could start step2.

Reply

  • Hello Andrew,

    Here it is my detailed information.

    Background :

    we have a skill gui which helps us to intergrate 3 steps based on calibre drc.That is ,In the skill gui, we have already intergrated 3 steps(that is (1)calibre -drc step1; (2)calibre -drc step2;(3)calibre -drc step3).By clicking button 1 manually in the gui, we could submit the job1 (calibre -drc step1) into the remote server.The same for step2 and step3.Now we would like to run these 3 steps one after another automatically.

    The virtuoso we are using is 6.1.6.14.

    Issues: 

    I am thinking whether it is possible for us to fullfill this kind of automation by skill too.( we could manuplate the gui button by skill script).But the difficult part is that how we could know step1 (calibre -drc step1)has been done.The only signal is that there is some file job1ResultFile which contains words "job1 run successfully" when it is done.  

    Examples:

    step 1: calibre -drc step1;

    step 2 :calibre -drc step2

    step 3: calibre -drc step3

    Base on the skill gui, submit step1 in machine 1~>Base on the skill gui, submit step1 in machine 2~>Base on the skill gui, submit step3 in machine 3.

    Is there any way for skill to know :

    yes, step 1 has been done because i could got the sentence  "job1 run successfully"  in   job1ResultFile.Now i could start step2.

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.