Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
CHiPS
Manage
Activity
Members
Plan
Wiki
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Analyze
Contributor analytics
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
external
CHiPS
Commits
c3d7688f
Commit
c3d7688f
authored
5 years ago
by
Gab
Browse files
Options
Downloads
Patches
Plain Diff
modified exemple as defined during today's team meeting
parent
ddffa4d4
No related branches found
Branches containing commit
No related tags found
Tags containing commit
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
application-exemple/README.md
+4
-3
4 additions, 3 deletions
application-exemple/README.md
application-exemple/compile.sh
+21
-0
21 additions, 0 deletions
application-exemple/compile.sh
application-exemple/testcase_small/prepare.sh
+14
-0
14 additions, 0 deletions
application-exemple/testcase_small/prepare.sh
with
39 additions
and
3 deletions
application-exemple/README.md
+
4
−
3
View file @
c3d7688f
...
@@ -44,12 +44,13 @@ For instance:
...
@@ -44,12 +44,13 @@ For instance:
Compile the code using:
Compile the code using:
```
```
source machines/occigen-bdw/env
./compile.sh occigen-bdw
./compile.sh
```
```
`machines/occigen-bdw/env`
contains the information for compilation (module load gcc openmpi lapack hdf5 ...)
`machines/occigen-bdw/env`
contains the information for compilation (module load gcc openmpi lapack hdf5 ...)
You can create your own machine directory under
`machines`
to define the appropriate environment.
Run and validate the simulation:
Run and validate the simulation:
--------------------------------
--------------------------------
...
@@ -62,7 +63,7 @@ For each test case, given in a separate folder (e.g. testcase_small), you can fi
...
@@ -62,7 +63,7 @@ For each test case, given in a separate folder (e.g. testcase_small), you can fi
For running and validating the simulation, one should be able to do:
For running and validating the simulation, one should be able to do:
```
```
cd testcase_XXX
cd testcase_XXX
./prepare.sh
./prepare.sh
occigen-bdw
./run.sh
./run.sh
./validate.sh
./validate.sh
```
```
...
...
This diff is collapsed.
Click to expand it.
application-exemple/compile.sh
+
21
−
0
View file @
c3d7688f
#!/bin/bash
if
[
-z
"
$1
"
]
then
echo
"Please provide the targeted machine from:"
ls
machines/
echo
""
echo
"Example: ./compile.sh occigen-bdw"
exit
1
fi
env_file
=
"machines/
$1
/env_bench"
if
[
!
-f
$env_file
]
then
echo
"ERROR:
$env_file
not found!"
exit
1
else
source
$env_file
fi
#Here give compilation info
This diff is collapsed.
Click to expand it.
application-exemple/testcase_small/prepare.sh
+
14
−
0
View file @
c3d7688f
#!/bin/bash
if
[
-z
"
$1
"
]
then
echo
"Please provide the targeted machine from:"
ls
../machines/
echo
""
echo
"Example: ./prepare.sh occigen-bdw"
exit
1
fi
machine_dir
=
"../machines/
$1
"
cp
$machine_dir
/env_bench
.
cp
$machine_dir
/batch_small.slurm
.
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment