You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CALPUFF_EXE/README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,10 +6,10 @@ Directory for the CALPUFF executables
6
6
7
7
## Build (recommended)
8
8
9
-
If your system has intel compilers ./Run_ext.sh will check if the executables exist here,
10
-
and build them here if not.
9
+
If your system has intel compilers ./Run_ext.sh will check if the executables exist here, and build them here if not.
11
10
12
11
## Prebuilt option (available on request)
12
+
13
13
The current set up uses proprietary intel compilers, if these are not available the executables must be place here alongside the relevant libraries in the libraries folder. Runing ./Run_ext.sh will add to the library path and use the prebuilt executables.
All user-editable input files for the various parts of the CALPUFF system are stored in subdirectory `CALPUFF_INP`. Template versions of these files have been set up specifically for the Masaya case and are version controlled. Various run-specific fields (e.g. run date) are then filled in at run-time. Information about setting up these input files for the Masaya case is also within [this](https://github.com/cemac/UNRESP/blob/master/Docs/CEMACUserGuide_UNRESP.tex) file.
1
+
# USER editable INPUT FILES
2
+
3
+
All user-editable input files for the various parts of the CALPUFF system are stored in subdirectory `CALPUFF_INP`.
4
+
5
+
* Template versions of these files have been set up specifically for the Masaya case and are version controlled.
6
+
7
+
* Various run-specific fields (e.g. run date) are then filled in at run-time.
8
+
9
+
Information on each input file can be found in the WIKI.
0 commit comments