wiki:CommandLineOptions

Version 3 (modified by trac, 12 years ago) ( diff )

AstroBEAR Command-Line Options

Note: Discussion of general command-line options in Fortran may be found here.

Unbeknownst to many, AstroBEAR has the capability to accept a small number of command-line arguments. These arguments are intended to reflect, in small or great detail, the state of the source code and environment when the executable was compiled.

This is accomplished by the following. When compiling, a PERL script (svninfo.pl) collects information about some environment flags as well as information relating to the source code's SVN status. It then creates a svninfo.f90 file which contains this information, and incorporates it into the build. If the PERL script encounters an error, it creates an empty skeleton file and quits quietly.

Thus, in every build(1) the user can pass certain command-line arguments to find out information regarding their specific executable.

List of options

The below list is copied directly from the svninfo.pl file.

Argument Information
-v, -V Print version-related information only (skipping *.mod files); also print LD_LIBRARY_PATH, and compiler as they were at compilation
[-dir] Print directory structure (e.g. to see where symbolic links pointed)
[-diff] Print version-related information, perform a 'svn diff' on any modified files, and print out the full source on any *.f90 files which are not recognized by the repository.

The second and third arguments are presented here in brackets because these will be available ONLY if SVNINFO=yes in the user's Makefile.inc.

Below is an example output:

user@keyboard> ./mpibear -v
 
  -------------------------------------------------------------
   SVN information for this executable:                        
  -------------------------------------------------------------
 
 Path: /grassdata/yirak/bearclaws/arf2/newbearclaw/contrib/astro  
 URL: https://data-store.pas.rochester.edu/svn/orda/bearclaw1/dev/contrib/astro 
  
 Repository Root: https://data-store.pas.rochester.edu/svn/orda/bearclaw1  
 Repository UUID: fa850eeb-f90e-0410-8a6a-8dd517416c1a  
 Revision: 522  
 Node Kind: directory  
 Schedule: normal  
 Last Changed Author: johannjc  
 Last Changed Rev: 522  
 Last Changed Date: 2010-05-25 16:26:10 -0400 (Tue, 25 May 2010)  
   
   
 M      /grassdata/yirak/bearclaws/arf2/newbearclaw/Makefile.grass.inc  
 
 
  The compilers were ifort, mpif90
  The compile flags were  -g -traceback -check bounds -check pointers -check uni
 nit
  The PATH was /opt/openmpi/bin:/opt/visit/bin:/opt/intel/fce/10.1.015/bin:/opt/
 ActiveTcl-8.5/bin:/usr/lib64/qt-3.3/bin:/opt/modules/Modules/3.2.6/bin:/usr/ker
 beros/bin:/usr/lib64/ccache:/usr/local/bin:/bin:/usr/bin:/usr/NX/bin:/home/yira
 k/bin/:/grassdata/yirak/bin:/grassdata/yirak/btfs/newbtf/
  The LD_LIBRARY_PATH was /opt/pgplot:/opt/openmpi/lib:/usr/local/hdf5-1.6.5b/li
 b:/opt/intel/fce/10.1.015/lib:/opt/ActiveTcl-8.5/lib:
 
 


1) Excepting bg/p, which due to its architecture would require a recompile with a compiler which is appropriate for the login node, not the compute nodes. It presumably would be possible to pass the arguments in the jobscript, however.

Note: See TracWiki for help on using the wiki.