LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  Executing BRX: Picking up from where it failed

    Employee
    Posted 03-12-2007 05:49

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: skim

    In order to reduce the redundant work, I was trying to find a way to execute a graph (BRX) from where it failed. This is what I know so far: If I can get the BRS file name for the BRX file during execution, I can use "-s" option to pass the BRS file to brainController.py so that it will pickup from where it failed. What I do not know is how I can get the location of BRS file and supply it back to BRX execution for the subsequent iteration.

    Has anyone managed to accomplish this?<br><br>Post edited by: skim, at: 2007/03/12 07:49


  • 2.  RE: Executing BRX: Picking up from where it failed

    Employee
    Posted 05-07-2008 20:26

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: NerdMachine

    If you type brainController.py, you will get help on command line arguments. I think you are interested in -dump.



    usage: Controller [-P &lt;property&gt;=&lt;value&gt;] [-a &lt;argument&gt;=&lt;value&gt;] [-u &lt;username&gt;] [-p &lt;password&gt;] [-s &lt;brs file&gt;] [-dump &lt;brs dump&gt;]
    [-r &lt;run name&gt;] [-v] &lt;brx file&gt;

    Options:
    -P &lt;property&gt;=&lt;value&gt; Set property to value
    -a &lt;argument&gt;=&lt;value&gt; Set runtime argument to value
    -u &lt;username&gt; Use &lt;username&gt; for authentication to the server
    -p &lt;password&gt; Use &lt;password&gt; for authentication to the servrs file&gt; Resume execution from the state contained in &lt;brs file&gt;
    -dump &lt;brs dump&gt; Dump the state of the execution upon completion to &lt;brs dump&gt;
    -brdlog &lt;brd log&gt; Log in brd format to &lt;brd log&gt;
    -r &lt;run name&gt; Use the name &lt;run name&gt; for labeling this execution
    --debug Debug: use standard error and be verbose
    -v Verbose