Showing papers on "Batch file published in 2010"

iTOUGH2 Universal Optimization Using the PEST Protocol

Abstract: iTOUGH2 (http://www-esd.lbl.gov/iTOUGH2) is a computer program for parameter estimation, sensitivity analysis, and uncertainty propagation analysis [Finsterle, 2007a, b, c]. iTOUGH2 contains a number of local and global minimization algorithms for automatic calibration of a model against measured data, or for the solution of other, more general optimization problems (see, for example, Finsterle [2005]). A detailed residual and estimation uncertainty analysis is conducted to assess the inversion results. Moreover, iTOUGH2 can be used to perform a formal sensitivity analysis, or to conduct Monte Carlo simulations for the examination for prediction uncertainties. iTOUGH2's capabilities are continually enhanced. As the name implies, iTOUGH2 is developed for use in conjunction with the TOUGH2 forward simulator for nonisothermal multiphase flow in porous and fractured media [Pruess, 1991]. However, iTOUGH2 provides FORTRAN interfaces for the estimation of user-specified parameters (see subroutine USERPAR) based on user-specified observations (see subroutine USEROBS). These user interfaces can be invoked to add new parameter or observation types to the standard set provided in iTOUGH2. They can also be linked to non-TOUGH2 models, i.e., iTOUGH2 can be used as a universal optimization code, similar to other model-independent, nonlinear parameter estimation packages such as PEST [Doherty, 2008] or UCODE [Poeter and Hill, 1998].more » However, to make iTOUGH2's optimization capabilities available for use with an external code, the user is required to write some FORTRAN code that provides the link between the iTOUGH2 parameter vector and the input parameters of the external code, and between the output variables of the external code and the iTOUGH2 observation vector. While allowing for maximum flexibility, the coding requirement of this approach limits its applicability to those users with FORTRAN coding knowledge. To make iTOUGH2 capabilities accessible to many application models, the PEST protocol [Doherty, 2007] has been implemented into iTOUGH2. This protocol enables communication between the application (which can be a single 'black-box' executable or a script or batch file that calls multiple codes) and iTOUGH2. The concept requires that for the application model: (1) Input is provided on one or more ASCII text input files; (2) Output is returned to one or more ASCII text output files; (3) The model is run using a system command (executable or script/batch file); and (4) The model runs to completion without any user intervention. For each forward run invoked by iTOUGH2, select parameters cited within the application model input files are then overwritten with values provided by iTOUGH2, and select variables cited within the output files are extracted and returned to iTOUGH2. It should be noted that the core of iTOUGH2, i.e., its optimization routines and related analysis tools, remains unchanged; it is only the communication format between input parameters, the application model, and output variables that are borrowed from PEST. The interface routines have been provided by Doherty [2007]. The iTOUGH2-PEST architecture is shown in Figure 1. This manual contains installation instructions for the iTOUGH2-PEST module, and describes the PEST protocol as well as the input formats needed in iTOUGH2. Examples are provided that demonstrate the use of model-independent optimization and analysis using iTOUGH2.« less

Aminonet-a tool to construct and visualize amino acid networks, and to calculate topological parameters

Abstract: AMINONET is a Java-based software tool to construct different protein contact networks (unweighted and weighted; long range, short range and any range; hydrophobic, hydrophilic, charged or all-amino-acid networks). The networks thus constructed can be visualized. The software will also help in the calculation of the values of the different topological parameters of the constructed networks. The user can either provide a PDB ID or upload a structure file in PDB format as input. If necessary, the user can also do the same for a large number of proteins, uploading a batch file as input (details described in the document available online).

Evicting data from a cache via a batch file

Abstract: In an embodiment, a plurality of keys are evicted from a first cache at a primary server. A first key is evicted from the first cache because the first key satisfied a first evict policy during a first time range. A second key is evicted from the first cache because the second key satisfied the first evict policy during a second time range, but the second key did not satisfy the first evict policy during the first time range. The plurality of keys are added to a batch file. If the batch file is full, the batch file is sent to a replica server, and the batch file requests the replica server to evict the plurality of keys from a second cache at the replica server. If the batch file is not full, the batch file is not sent to the replica server.

Multi-toolchain engineering construction method and system

Abstract: The invention provides a multi-toolchain engineering construction method which comprises the following steps of: creating a batch file and a main makefile containing same compiling environment part in more than one toolchain; creating more than one sub makefile which respectively corresponds to different toolchains; selectively invoking corresponding toolchains by the main makefile according to input toolchain invoking parameters in the batch file, and compiling and outputting an executable file. The invention also provides a multi-toolchain engineering construction system which comprises an inlet module, a compiling engine module and a compiling module. The method and the system can realize the united construction of a plurality of compiling environments and reduce the workload of software developers at the same time of greatly lightening the maintenance difficulty.

Uploading and Executing Command Line Scripts

Abstract: A mechanism is provided for a non-root-level user to execute command line script files via a generic command line interface. A command line interface in the data processing system receives a shellscript command from a non-root-level user via a client system. A security module in the data processing system determines whether the non-root-level user is logged on at a command line interface shell level access. Responsive to the non-root-level user being logged on at the command line interface shell level access, a storage controller at the request of a command line interface identifies a script file associated the shellscript command in a storage of the data processing system. The storage controller executes the script file and the command line interface sends the results of the execution of the script file to the non-root-level user via the client system.

A Macro to Create a Batch Submit SAS Program

Abstract: It is very common to run a group of SAS programs together in batch mode. For example, often we run a large number of individual SAS programs to generate listings and tables for a clinical trial. These programs are submitted to run together in a batch job. There are different ways to create the batch program. For instance, a shell script for a UNIX system can be created to do it on the server side (SUGI 145-31), or a .BAT file for Windows OS can fulfill this task on a specific PC (SUGI 105-27). In this article, we present another approach. We use a simple macro to create the SAS batch program in the Windows environment that can be used for batch-submit later in either operating system. This macro can run on any PC which has the SAS system installed.