Home > Community > Forums > Custom IC Design > forking ocean scripts?

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 forking ocean scripts? 

Last post Fri, Sep 25 2009 9:42 AM by markbeck. 4 replies.
Started by markbeck 22 Sep 2009 12:08 PM. Topic has 4 replies and 1998 views
Page 1 of 1 (5 items)
Sort Posts:
  • Tue, Sep 22 2009 12:08 PM

    • markbeck
    • Top 150 Contributor
    • Joined on Thu, Jun 30 2011
    • Beaverton, OR
    • Posts 45
    • Points 1,355
    forking ocean scripts? Reply

    I'm trying to figure out amethod to fork a simulation from ICFB. 

    Currently, I'm creating an ocean script that sets up the simulation in ICFB, and then spawns off an ocean session that then runs the simulation.  I'm doing this to keep the simulation from hanging the ICFB session while running.  This is working fairly well, but the main issue I'm encountering is that when I'm running small jobs, the time it takes the ocean session to spawn and statup is longer than the actual simulation.

    Does anyone know how to issue a 'run()' command inside of ICFB that will fork off a new process that doesn't hang the ICFB session?

     Mark

    Filed under: , ,
    • Post Points: 20
  • Tue, Sep 22 2009 1:06 PM

    Re: forking ocean scripts? Reply
    You can use run(?block nil) to get the simulation to run in non-blocking mode, but you wouldn't know when it finished.

    If you are running in distributed mode, non-blocking is the default, and you can use the wait() function to wait for one or more simulations to complete - passing the job id returned by run().

    Regards,

    Andrew
    • Post Points: 20
  • Tue, Sep 22 2009 3:35 PM

    • markbeck
    • Top 150 Contributor
    • Joined on Thu, Jun 30 2011
    • Beaverton, OR
    • Posts 45
    • Points 1,355
    Re: forking ocean scripts? Reply

     Ok. the run(?block nil) seem to keep the run() command from freezing the CIW... but now I've got a new problem.  It's spewing all of the simulation stuff in the CIW. 

     Is there a way to block that as well?  I only want the simulator information to reside in the spectre.out file.

     

    • Post Points: 20
  • Fri, Sep 25 2009 1:38 AM

    Re: forking ocean scripts? Reply

    If you use:

    option(?categ 'analog 'info "no")
    option(?categ 'analog 'warn "no")
    option(?categ 'analog 'note "no")

    that will massively reduce the output produced.

    Regards,

    Andrew.

    • Post Points: 20
  • Fri, Sep 25 2009 9:42 AM

    • markbeck
    • Top 150 Contributor
    • Joined on Thu, Jun 30 2011
    • Beaverton, OR
    • Posts 45
    • Points 1,355
    Re: forking ocean scripts? Reply

    Thanks, that definately helps....  It still spews more stuff than I would like to see but it's of a more managable size now.

    Mark

    • Post Points: 5
Page 1 of 1 (5 items)
Sort Posts:
Started by markbeck at 22 Sep 2009 12:08 PM. Topic has 4 replies.