Changes between Initial Version and Version 1 of doc/app/palmrun_quickstart

Timestamp:

Nov 19, 2018 10:27:58 AM (6 years ago)

Author:

kanani

Comment:

--

doc/app/palmrun_quickstart

@@ +1 @@
+= PALM Quickstart Guide =
+{{{
+#!div style="align:'left'; width: 450px; border: 0px solid; float:right"
+[[Image(file_tree_1.png, 450px, right, margin-right=2, margin-top=0, border=2)]]\\
+'''Fig. 1''' Directory structure of PALM installation.
+}}}
+{{{
+#!div style="align:'left'; width: 450px; border: 0px solid; float:right"
+[[Image(file_tree_1.png, 450px, right, margin-right=2, margin-top=0, border=2)]]\\
+'''Fig. 2''' Directory structure of PALM simulation setup.
+}}}
+Ideally, you have successfully installed PALM using the [automatic installer]. If so, the installer has 
+* [downloaded] PALM from the subversion control (svn) repository into a predefined directory structure on your local PC (see Fig. 1),
+* created the required palmrun [configuration file], e.g. .palm.config.default (hidden file),
+* pre-compiled ([palmbuild]) the UTILities and SOURCE code,
+* run some small test simulations (JOBS).
+Somewhere near the end of the automatic installation process, the following lines should have appeared in your UNIX terminal:\\
+{{{All found tests passed. PALM installation successful}}} and \\
+{{{PALM installer finished.}}}\\
+Further, the installer has printed an example command for starting a PALM simulation, e.g.
+{{{
+palmrun -r example_cbl -a \"d3#\" -c \"default\"        -X \"4\" -T \"4\" "
+                |           |             |              |        |                "
+            run identifier  |  configuration identifier  |        tasks per node   "
+                     I/O control list                 number of cores           "
+}}}