The main difference between running commonly used SWAN in parallel and running the unstructured mesh version of SWAN in parallel on
a multi-core cluster is the need to explicitly decompose the unstructured mesh and input files, e.g. fort.14 and fort.15,
into smaller pieces, so that each piece can run on its own core on the cluster.
The program adcprep is used to perform the decomposition. The actual mesh partitioning is done by
the well-known METIS package (http://glaros.dtc.umn.edu/gkhome/views/metis).
In order to break up the original input files (which describe the full domain) into smaller pieces (called subdomains), go to the directory where the input files are located and execute adcprep. You need to specify the number of cores that you plan to use for the simulation. The program will decompose your input files into that number of subdomains and copy each of them into the corresponding local PE sub-directories. Finally, it will copy the SWAN command file into the local PE sub-directories. If you decide later that you want to run on more (or fewer) cores, you must perform this step again.
So, more specifically, run adcprep and indicate the number of processors. First, you need to do mesh partition using METIS by selecting
1. partmeshNext, rerun adcprep and continue with full pre-processing by selecting
3. prepspecand specify the necessary ADCIRC files (fort.14 and fort.15; you may skip the file fort.19). Be sure that the initialisation file swaninit has been created before running adcprep. You may adapt this initialisation file by renaming INPUT to your own SWAN command file. Otherwise, you may copy your command file to INPUT.