Stats

  • Locked Locked
  • Replies 1
  • Subscribers 64
  • Views 13094
  • 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

Quick and easy way to debug your run_scripts in eManager

archive

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.


Originally posted in cdnusers.org by adielkhan

  • 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


    Originally posted in cdnusers.org by adielkhan

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.