Application Document Guideline and Template

From PRAGMAgridWIKI

Jump to: navigation, search

(Please don't change in this page. Click edit, then cut/paste the wiki contents to a new page for your application, and edit them in your new page.)

Contents

[edit]

Application Name and Description

Please describe what scientific problem your application solves, what's the methods and goals of your experiments, also the possible applications of your results.

[edit]

Application driver and contact

Please specifies the application driver's name, institution and email.

[edit]

Applicaiton Requirements

[edit]

Hardware requirements

If any. This will help with matching site resources.

  • CPU architecture (i686, x86_64, ia_64, etc.)
  • Minimum number of CPUs (per cluster/system)
  • Memory size (default is per node, unless you specify per CPU)
  • Storage size (default is online and shared within a cluster. If not, specify.)
  • Any other requirements (Specify)
[edit]

Software requirements

First, see current software availability info at http://goc.pragma-grid.net/cgi-bin/scmsweb/swcatalog.cgi?grid=PRAGMA.
If you need other software and if the software size below 200MB and does not require root priviledge to install, try to install/copy it yourself to your home directories on each cluster or on a shared file system.
If the software size is over 200MB or it requires root priviledge to install, specify each and follow the format and example below:

[edit]

(Name of first software)

  • Version requirement: (Specify exact version number or range.)
  • URL and instruction for software download:
  • URL and/or instruction for the software installation:
  • Command-line and output for software version query:

For example, if the software is intel fortran compiler: 

$ ifort --version
ifort (IFORT) 9.0  20051201
Copyright (C) 1985-2005 Intel Corporation.  All rights reserved.
  • Execution paths: (Specify the executables directory paths relative to the software installation root. The paths will be added into $PATH variable in PRAGMA login script at every site.)
    • For example, on my cluster, software xyz is installed in /opt/xyz, the executables are in /opt/xyz/bin and /opt/xyz/local/etc, then the executaion paths should be specified as:
      • PATH: bin, local/etc
  • Other specifications and comments
[edit]

(Name of second software)

...

If you do need site admins to install software, make sure to notify Cindy after you finish documenting this list.

[edit]

Site access status

As each PRAGMA grid site inform you of your account setup, test access following section 4 in http://goc.pragma-grid.net/pragma-doc/userguide/pragma_user_guide.html, then document and update each site access status or problems.

[edit]

Application Run

Please document memos, mile stones, progress reports, issues, results, publication links, etc. and feel free to add other categories.

Retrieved from "http://goc.pragma-grid.net/wiki/index.php/Application_Document_Guideline_and_Template"
Personal tools