Sunday, October 12, 2008     Register | Login | Search | Contact Us
     
   
     
     

Many of you already received communications about the move of the Cadence user community into cadence.com. And many of you have already joined, with over 4000 registrations in the first two weeks.

The new Cadence Community enhances the ability of Cadence users to connect and collaborate. In addition to moving the community into cadence.com -- enabling single sign-on for community, Sourcelink and Cadence events -- the new site is organized around nine technology segments, giving you easy access to product information, training, forums and blogs. Some of the new features include:
  • Ability to respond to posts via e-mail
  • Technology-specific blogs
  • Latest Web 2.0 social networking capabilities
  • Public profile options
  • Private messaging
  • Friends lists
Visit the new Cadence Community today at www.cadence.com/community and join the discussions!

Registration note: Due to the scope of the enhancements and the new SSO registration system, we were not able to migrate existing cdnusers.org member accounts. So new registrations are required, but this enables a broader set of functionality we think you'll enjoy.

Forum note: Under the guidance of forum moderators, we have taken the 20+ cdnusers.org forums and consolidated them into 11 forums on the new site. Posts have been brought over so you can leverage that posting history. CDNusers forums will be set to read only starting 7/30, and cdnusers.org will be redirected to the new community on 8/4.

Best regards,
Mike and Tom

Michael A. Catrambone - Steering Committee Chairman
Distinguished Engineer
PCB/Mechanical
UTStarcom, Inc.

Tom Diederich
Cadence Community Manager
Home
Forums
Forums > Functional Verification > Verification Planning

Subject: Quick and easy way to debug your run_scripts in eManager
Posting to forums is available to community members only.
Login or Register
Rate this topic:
   
Author Messages
adielkhan
Posts: 6
Online: User is Offline
9/12/2007 4:18 PM  
Hi, I often see eManager environments that over use environment variables, overload already overloaded MAKE variables, pass redundant commands into complex shell scripts, launch LSF mulitple times all because end-users are sure about which SHELL or even which type of SHELL is launching the simulations. What we end up doing is launching xterm shells to see what environment variables and Shell types are actually being used and setup by the Cad teams. Then we can run the commands manually from within the xterms. Once we have streamlined and fixed any issues then we can replace the required commandline into the VSIF. Below is a simple XTERM.VSIF which helps us debug and streamline our scripts and environments. /////////////////////////////////////////// session debug_subsystem { top_dir : "./"; output_mode: terminal; pre_session_script: "xterm -title pre_session"; }; group debug_group { scan_script: "$VMANAGER_HOME/bin/vm_scan_default.pl $VMANAGER_HOME/bin/ius_hdl.flt $VMANAGER_HOME/bin/shell.flt "; run_script: "xterm -fg white -bg navy -title run_script"; test debug_test { }; }; /////////////////////////////////////////// Obviously, you can launch xterms from post_session etc. thanks, Adiel.
adielkhan
Posts: 6
Online: User is Offline
9/12/2007 4:28 PM  
Hi,
I am reposting this at it seems the carriage returns got eaten.

I often see eManager environments that over use environment variables, overload already overloaded MAKE variables, pass redundant commands into complex shell scripts, launch LSF mulitple times all because end-users are sure about which SHELL or even which type of SHELL is launching the simulations.

What we end up doing is launching xterm shells to see what environment variables and Shell types are actually being used and setup by the Cad teams.

Then we can run the commands manually from within the xterms. Once we have streamlined and fixed any issues then we can replace the required commandline into the VSIF.

Below is a simple XTERM.VSIF which helps us debug and streamline our scripts and environments.

///////////////////////////////////////////
session debug_subsystem {
top_dir : "./";
output_mode: terminal;
pre_session_script: "xterm -title pre_session";
};
group debug_group {
scan_script: "$VMANAGER_HOME/bin/vm_scan_default.pl $VMANAGER_HOME/bin/ius_hdl.flt $VMANAGER_HOME/bin/shell.flt ";
run_script: "xterm -fg white -bg navy -title run_script";
test debug_test { };
};
///////////////////////////////////////////

thanks,
Adiel
Posting to forums is available to community members only.
Login or Register
Forums > Functional Verification > Verification Planning > Quick and easy way to debug your run_scripts in eManager


ActiveForums 3.6
     
Copyright 2006 Cadence Design Systems, Inc.