Stats

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

Sleeping in SKILL

gsimard

Hi,

 

 I need a function that would do a sleep for X milliseconds or seconds. I need to wait for an asynchronous task to complete so I'm polling a flag regularly, but I don't want to take the whole CPU in a while loop. Any idea ?

 

 Thank you,

Guillaume

Parents

  •  Thank you both for these tips !

     

    I noticed that the asynchronous function I was talking about is strangely refusing to execute at the same time as other SKILL code. I first call a function, responsible for the start up of the asynchronous task (it's a layout extraction by the way). That function returns quite fast, but the extraction continues in the background, and it sends me text to the ICFB during this time. Meanwhile, I can enter SKILL commands, like (plus 3 4), etc, and get answer from cadence. However, if I try to execute a loop with some delay in it (I found that (system "sleep 1") could also work for a delay), it seems the background task extracting the layout doesn't quite continue ! In fact, I have to stop my waiting loop for it to complete.. this is quite anoying as right now I am unable to run the layout extraction process as a command line instead of a SKILL command.

     I guess the reason for this is that the SKILL interpreter must be single threaded. However, I REALLY need to execute the wait_function just once, and it must return when the background task is done.. which it won't do because the wait_function gets all the attention of cadence.... Any idea how I could break the circle ?

     I hope I'm being a bit clear !

    Thank you,

    Guillaume

Reply

  •  Thank you both for these tips !

     

    I noticed that the asynchronous function I was talking about is strangely refusing to execute at the same time as other SKILL code. I first call a function, responsible for the start up of the asynchronous task (it's a layout extraction by the way). That function returns quite fast, but the extraction continues in the background, and it sends me text to the ICFB during this time. Meanwhile, I can enter SKILL commands, like (plus 3 4), etc, and get answer from cadence. However, if I try to execute a loop with some delay in it (I found that (system "sleep 1") could also work for a delay), it seems the background task extracting the layout doesn't quite continue ! In fact, I have to stop my waiting loop for it to complete.. this is quite anoying as right now I am unable to run the layout extraction process as a command line instead of a SKILL command.

     I guess the reason for this is that the SKILL interpreter must be single threaded. However, I REALLY need to execute the wait_function just once, and it must return when the background task is done.. which it won't do because the wait_function gets all the attention of cadence.... Any idea how I could break the circle ?

     I hope I'm being a bit clear !

    Thank you,

    Guillaume

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.