Stats

Locked Locked
Replies 4
Subscribers 124
Views 13543
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

forking ocean scripts?

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

Andrew Beckett over 15 years ago

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
Cancel
Vote Up 0 Vote Down

Cancel
markbeck over 15 years ago

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.
Cancel
Vote Up 0 Vote Down

Cancel
Andrew Beckett over 15 years ago

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.
Cancel
Vote Up 0 Vote Down

Cancel
markbeck over 15 years ago

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
Cancel
Vote Up 0 Vote Down

Cancel

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.