| 1 |
# Copyright(C) 1999-2020 National Technology & Engineering Solutions |
| 2 |
# of Sandia, LLC (NTESS). Under the terms of Contract DE-NA0003525 with |
| 3 |
# NTESS, the U.S. Government retains certain rights in this software. |
| 4 |
# |
| 5 |
# See packages/seacas/LICENSE for details |
| 6 |
############################################################################## |
| 7 |
# GENERAL NOTES |
| 8 |
# |
| 9 |
# 1) Any line beginning with a "#" is considered a comment and will be |
| 10 |
# ignored by the file parser. |
| 11 |
# |
| 12 |
# 2) The order of the lines IS NOT significant. |
| 13 |
# |
| 14 |
# 3) Any lines that are optional are marked as such in this file. Unless |
| 15 |
# otherwise noted a line is required to exist in any input file. |
| 16 |
# |
| 17 |
# 4) The default file name expected by nem_spread is "nem_spread.inp". This |
| 18 |
# can be overridden on the command line (see the nem_spread.man file for |
| 19 |
# more on this). |
| 20 |
# |
| 21 |
# 5) The case of words IS NOT significant, e.g., "file" IS equivalent |
| 22 |
# to "FILE" or "File", etc. |
| 23 |
# |
| 24 |
# 6) The amount of blank space in between words is also significant. Each |
| 25 |
# word should only be separated by a single space. |
| 26 |
# |
| 27 |
# 7) Blank lines are ignored. |
| 28 |
# |
| 29 |
############################################################################## |
| 30 |
|
| 31 |
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
| 32 |
# Input FEM file = <filename> |
| 33 |
# |
| 34 |
# This line contains the name of the input ExodusII FEM file which is |
| 35 |
# to be spread over the parallel disks. |
| 36 |
#----------------------------------------------------------------------------- |
| 37 |
Input FEM file = ps.gen |
| 38 |
|
| 39 |
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
| 40 |
# LB file = <filename> |
| 41 |
# |
| 42 |
# This line contains the name of a scalar Nemesis load-balance file as |
| 43 |
# generated by the nem_slice utility. |
| 44 |
#----------------------------------------------------------------------------- |
| 45 |
LB file = ps-slice.nem |
| 46 |
|
| 47 |
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
| 48 |
# Scalar Results FEM file = <filename> |
| 49 |
# |
| 50 |
# This line is OPTIONAL. |
| 51 |
# |
| 52 |
# This line contains the name of the ExodusII file from which the restart |
| 53 |
# variables to be spread will be read from. If this file is not given, then |
| 54 |
# the results will be read from the "Input FEM file" file. |
| 55 |
#----------------------------------------------------------------------------- |
| 56 |
Scalar Results FEM file = ps.res |
| 57 |
|
| 58 |
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
| 59 |
# Debug = <integer> |
| 60 |
# |
| 61 |
# This is an OPTIONAL line and if omitted defaults to the value of 0. Valid |
| 62 |
# values are 0 <= value <= 10. |
| 63 |
# |
| 64 |
# A value of 1 or 2 essentially causes nem_spread to output more information |
| 65 |
# about where it is and what it's doing. As the value is increased more |
| 66 |
# and more information about the operations nem_spread is performing and |
| 67 |
# the results of those operations is output to the screen. Values above 2 |
| 68 |
# are probably only useful for small example problems and those users |
| 69 |
# familiar with the specifics of how nem_spread works. |
| 70 |
#----------------------------------------------------------------------------- |
| 71 |
Debug = 4 |
| 72 |
|
| 73 |
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
| 74 |
# Restart Info = <options> |
| 75 |
# |
| 76 |
# This line is OPTIONAL. |
| 77 |
# |
| 78 |
# This line contains information about results that will be spread with |
| 79 |
# the mesh file. The options for this line are as follows: |
| 80 |
# all - nem_spread will spread all of the variable in |
| 81 |
# the mesh file (either "Scalar Results FEM file" |
| 82 |
# or "Input FEM file"). |
| 83 |
# off - no results will be spread. |
| 84 |
# list={list} - a list of time indices to be spread. |
| 85 |
# block=<integer> - when this is set, nem_spread will read and |
| 86 |
# spread the results in blocks before writing |
| 87 |
# the results to disk, intsead of handling them |
| 88 |
# one at a time. This will speed up runs where there |
| 89 |
# are many time steps to be spread. |
| 90 |
# |
| 91 |
# If this line is left out, nem_spread will check for results in the |
| 92 |
# input FEM file (or the scalar results file) and spread all of them. This |
| 93 |
# feature can be turned off by using the keyword "off". |
| 94 |
# |
| 95 |
#----------------------------------------------------------------------------- |
| 96 |
Restart Time list = list={1,2,5,9,12}, block=2 |
| 97 |
|
| 98 |
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
| 99 |
# Reserve space = nodal=<integer>, elemental=<integer>, global=<integer> |
| 100 |
# |
| 101 |
# This OPTIONAL line causes nem_spread to reserve space in the parallel files |
| 102 |
# for a specified number of nodal, elemental, and/or global variables. This |
| 103 |
# can help prevent an application from going into the infamous netCDF define |
| 104 |
# mode and place the burden on nem_spread. Default value is "0". |
| 105 |
# |
| 106 |
# A warning is generated if this line is used and restart information |
| 107 |
# was already requested. The two are mutually exclusive. |
| 108 |
#----------------------------------------------------------------------------- |
| 109 |
Reserve space = nodal=0, elemental=0, global=0 |
| 110 |
|
| 111 |
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
| 112 |
# Parallel Disk Info = <options> |
| 113 |
# |
| 114 |
# This line gives all of the information about the parallel file system |
| 115 |
# being used. There are a number of options that can be used with it, |
| 116 |
# although for most cases only a couple will be needed. The options are: |
| 117 |
# |
| 118 |
# number=<integer> - this is the number of parallel disks that the |
| 119 |
# results files are spread over. This number must |
| 120 |
# be specified, and must be first in the options |
| 121 |
# list. |
| 122 |
# list={list} - OPTIONAL, If the disks are not sequential, then a |
| 123 |
# list of disk numbers can be given. This list should |
| 124 |
# be enclosed in brackets "{}", and the disk numbers |
| 125 |
# can be separated by any of the following comma, |
| 126 |
# blank space, tab, or semicolon. |
| 127 |
# offset=<integer> - OPTIONAL, This is the offset from zero that the |
| 128 |
# disk numbers begin with. If no number is specified, |
| 129 |
# this defaults to 1. This option is ignored if |
| 130 |
# "list" is specified. |
| 131 |
# zeros - OPTIONAL, This specifies that leading zeros are |
| 132 |
# used in the parallel file naming convention. For |
| 133 |
# example, on the Paragon, the file name for the |
| 134 |
# first pfs disk is "/pfs/tmp/io_01/". If this is |
| 135 |
# specified, then the default is not to have leading |
| 136 |
# zeros in the path name, such as on the teraflop |
| 137 |
# machine "/pfs/tmp_1/". |
| 138 |
# stage_off - OPTIONAL, This turns off staged writes. The default |
| 139 |
# is to stage the writes. |
| 140 |
# |
| 141 |
#----------------------------------------------------------------------------- |
| 142 |
Parallel Disk Info = number=4, list={1,2,10,12}, offset=1, zeros, stage_off |
| 143 |
|
| 144 |
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ |
| 145 |
# Parallel file location = <options> |
| 146 |
# |
| 147 |
# This line gives all of the information about where the parallel files are |
| 148 |
# located. There are only two options for this line, and both must be |
| 149 |
# specified. The options are: |
| 150 |
# root=<root directory name> |
| 151 |
# This line is used to specify what the name of the root directory is |
| 152 |
# on the target machine. This can be any valid root directory |
| 153 |
# name. For example, if one is running on an SGI workstation and |
| 154 |
# using the "tflop" numbering scheme then you could use something |
| 155 |
# similar to "/usr/tmp/pio_" in this field so that files would be |
| 156 |
# written to root directories named: |
| 157 |
# /usr/tmp/pio_1 |
| 158 |
# /usr/tmp/pio_2 |
| 159 |
# . |
| 160 |
# . |
| 161 |
# . |
| 162 |
# /usr/tmp/pio_<Parallel Disk Info, number> |
| 163 |
# |
| 164 |
# subdir=<subdirectory name> |
| 165 |
# This line specifies the name of the subdirectory, under the root |
| 166 |
# directory, where files are to be written. This is tacked onto |
| 167 |
# the end of the "root" after an appropriate integer is added to |
| 168 |
# "root". Continuing with the example given for "root", if "subdir" |
| 169 |
# had a value of "run1/input" files would be written to directories |
| 170 |
# named: |
| 171 |
# /usr/tmp/pio_1/run1/input/ |
| 172 |
# /usr/tmp/pio_1/run1/input/ |
| 173 |
# . |
| 174 |
# . |
| 175 |
# . |
| 176 |
# /usr/tmp/pio_<Parallel Disk Info, number>/run1/input/ |
| 177 |
# |
| 178 |
#----------------------------------------------------------------------------- |
| 179 |
Parallel file location = root=/pfs/tmp_, subdir=glh/run1 |