source: trunk/gui/apps/rerun.in @ 1159

Last change on this file since 1159 was 1159, checked in by dkearney, 16 years ago

updated driver to allow the user to revisualize old run files just as rerun did. if driver can find the tool.xml file and where the application is installed, it can also allow the user to run new simulations after preloading old simulations.

Finally figured out where the current tags in group objects were coming from. controlOwner was adjusted to stop putting current tags in things. this only seemed to happen when the application also contained a loader, because we were doing an xml copy of nodes.

rewrote rerun to be a small wrapper around the "driver -load" command. rerun is now a script like rappture, it is populated with rappture's install directory from configure, so configure.in was updated. added some stuff for finding mcc in the configure.in script for a future commit

changed Rappture::Analyzer to accept -notebookpage configure flag so we can specify which page of the analyzer notebook should be currently showing. also inside of the analyzer, changed behavior of simstatus to allow us to still show a message even if the simulation button is disabled. this is helpful because we can tell the user why the simulation button is grayed out. one example of this is the case when we load old run.xml files, but cannot find a tool.xml file. the user cannot run a simulation, even if they change an input, because we can't figure out where the app is installed. now we can tell the user, why they cannot run the simulation.
  • Property svn:executable set to *
File size: 1.3 KB
Line 
1#!/bin/sh
2# ----------------------------------------------------------------------
3#  rerun
4#
5#  script to view the output of a previously created run.xml file.
6#  this is just a wrapper around the "rappture -load ..." command
7#  you can use this command to load and compare run.xml files from
8#  the same application. loading xml files from different applciations
9#  will result in undefined actions, and possibly errors.
10#  after loading a run.xml file, you can still enter new values into
11#  the rappture gui and continue simulation experiments.
12#
13#  RUN AS FOLLOWS:
14#    rerun <runFile>,...
15#
16#      <runFile>      - the run.xml file containing an output
17#                       section you would like to re-generate.
18#      ...            - optional comma separated list of runFiles
19#
20#
21#   ex: rerun run1234.xml,run5678.xml,run0123.xml
22#
23# ======================================================================
24#  AUTHOR:  Derrick Kearney, Purdue University
25#  Copyright (c) 2004-2008  Purdue Research Foundation
26#
27#  See the file "license.terms" for information on usage and
28#  redistribution of this file, and for a DISCLAIMER OF ALL WARRANTIES.
29# ======================================================================
30#
31#
32
33RAPPTURE_INSTALL_DIR=@prefix@
34
35. $RAPPTURE_INSTALL_DIR/bin/rappture.env
36exec $RAPPTURE_INSTALL_DIR/bin/driver -load $*
Note: See TracBrowser for help on using the repository browser.