Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in
Toggle navigation
C
codes
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
38
Issues
38
List
Boards
Labels
Milestones
Merge Requests
8
Merge Requests
8
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
codes
codes
Commits
40a3950d
Commit
40a3950d
authored
May 29, 2015
by
Jonathan Jenkins
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
documentation updates, pointed out by Xu Yang (thanks!!)
parent
fa06ccc5
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
with
28 additions
and
6 deletions
+28
-6
doc/BUILD_STEPS
doc/BUILD_STEPS
+19
-4
doc/GETTING_STARTED
doc/GETTING_STARTED
+8
-1
src/workload/codes-workload-dump.c
src/workload/codes-workload-dump.c
+1
-1
No files found.
doc/BUILD_STEPS
View file @
40a3950d
NOTE: see bottom of this file for suggested configurations on particular ANL
machines.
0 - Checkout, build, and install the trunk version of ROSS. At the time of
0 - Checkout, build, and install the trunk version of ROSS
(https://github.com/carothersc/ROSS). At the time of
release (0.4.0), ROSS's latest commit hash was 44b7b9a, so this revision is
"safe" in the unlikely case incompatible changes come along in the future. If
working from the CODES master branches, use the ROSS master branch.
...
...
@@ -20,6 +21,12 @@ working from the CODES master branches, use the ROSS master branch.
<the result should be that the latest version of ROSS is installed in the
ROSS/install/ directory>
For more details on installing ROSS, go to
https://github.com/carothersc/ROSS/blob/master/README.md .
If using ccmake to configure, don't forget to set CMAKE_C_COMPILER and
CMAKE_CXX_COMPILER to mpicc/mpicxx
1 - If you are building codes-base directly from the repository, run
./prepare.sh
...
...
@@ -32,10 +39,18 @@ working from the CODES master branches, use the ROSS master branch.
cd build
../configure --with-ross=/path/to/ross/install --prefix=/path/to/codes-base/install CC=mpicc
To enable network tracing with dumpi, use the option
--with-dumpi = /path/to/dumpi/install with configure.
To enable network tracing with dumpi
(http://sst.sandia.gov/about_dumpi.html), use the option
--with-dumpi=/path/to/dumpi/install with configure.
NOTE: we only require libundumpi for trace processing. Hence, if building
dumpi from source you may configure with --disable-libdumpi and
--enable-libundumpi (this is especially useful if you have mpich3, which
breaks libdumpi's function wrappers through const'ifying the MPI
interface).
To enable using the darshan I/O generator, use the option
To enable using the darshan I/O generator
(http://www.mcs.anl.gov/research/projects/darshan/), use the option
--with-darshan=/path/to/darshan with configure
3 - Build and install codes-base
...
...
doc/GETTING_STARTED
View file @
40a3950d
...
...
@@ -137,7 +137,14 @@ The following restrictions currently apply to the IO language:
Our
primary
network
workload
generator
is
via
the
DUMPI
tool
(
http
://
sst
.
sandia
.
gov
/
about_dumpi
.
html
).
DUMPI
collects
and
reads
events
from
MPI
applications
.
See
the
DUMPI
documentation
for
how
to
generate
traces
.
MPI
applications
.
See
the
DUMPI
documentation
for
how
to
generate
traces
.
There
are
additionally
publically
-
available
traces
at
http
://
portal
.
nersc
.
gov
/
project
/
CAL
/
doe
-
miniapps
.
htm
.
Note
on
trace
reading
-
the
input
file
prefix
to
the
dumpi
workload
generator
should
be
everything
up
to
the
rank
number
.
E
.
g
.,
if
the
dumpi
files
are
of
the
form
"dumpi-YYYY.MM.DD.HH.MM.SS-XXXX.bin"
,
then
the
input
should
be
"dumpi-YYYY.MM.DD.HH.MM.SS-"
==
LP
-
IO
...
...
src/workload/codes-workload-dump.c
View file @
40a3950d
...
...
@@ -198,7 +198,7 @@ int main(int argc, char *argv[])
}
if
(
du_params
.
file_name
[
0
]
==
'\0'
){
fprintf
(
stderr
,
"Expected
\"
--
r-trace-dir
\"
argument for dumpi workload
\n
"
);
fprintf
(
stderr
,
"Expected
\"
--
dumpi-log
\"
argument for dumpi workload
\n
"
);
usage
();
return
1
;
}
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment