Note that internally the routine uses the range option so that it
only has to load the part of \inltt{file1.xml} that overlaps with each
partition of \inltt{file2.xml}.
The resulting output will lie in a directory called \inltt{file2.fld}, with each
of the different parallel partitions in files with names \inltt{P0000000.fld},
\inltt{P0000001.fld}, \dots, \inltt{P0000009.fld}. This is nearly a complete
parallel field file. However, when the output file is in the .fld format,
the \inltt{Info.xml} file, which contains the information about which elements
lie in each partition, is not correct since it will only contain the information for one of the partitions. The correct \inltt{Info.xml} file can be generated by using the command
Obviously the executable will have to have been compiled with the MPI option for this to work.
\subsection{Using the \textit{ part-only} and \textit{ part-only-overlapping} options}
The options above will all load in the full \inltt{file1.xml}, partition
it into \inltt{nparts} files in a director called \inltt{file1\_xml}.
This can be expensive if the \inltt{file1.xml} is already large. So instead you can
pre-partition the file using the using the \inltt{--part-only}
option. So the command
Loading full \inltt{file1.xml} can be expensive if the
\inltt{file1.xml} is already large. So instead you can pre-partition
the file using the using the \inltt{--part-only} option. So the
command
\begin{lstlisting}[style=BashInputStyle]
FieldConvert --part-only 10 file.xml file.fld
\end{lstlisting}
...
...
@@ -1218,13 +1168,6 @@ directory called \inltt{file\_xml}. If you enter this directory you will find
partitioned XML files \inltt{P0000000.xml}, \inltt{P0000001.xml}, \dots,
\inltt{P0000009.xml} which can then be processed individually as outlined above.
If you have a partitioned directory either from a parallel run or using the \inltt{--part-only} option you can now run the \inltt{FieldConvert} option using the command