Note the final \inltt{:info} extension on the last argument is necessary to
tell FieldConvert that you wish to generate an info file but the extension
to this file is .xml. This syntax allows the routine not to get confused with
the input/output xml files.
Note the final \inltt{:info} extension on the last argument is necessary to tell
FieldConvert that you wish to generate an info file, but with the extension
\inltt{.xml}. This syntax allows the routine not to get confused with the
input/output XML files.
\subsection{Using the --part-only and --part-only-overlapping options}
\subsection{Using the --part-only and --part-only-overlapping options}
Another approach to serially proessing a large file is to intiially process the file into multiple partitions. This can be done with the \inltt{part-only} option. So the command
Another approach to serially proessing a large file is to initially process the
file into multiple partitions. This can be done with the \inltt{--part-only}
option. So the command
\begin{lstlisting}[style=BashInputStyle]
FieldConvert --part-only 10 file.xml file.fld
\end{lstlisting}
will call the mesh partitioner for 10 paritions and write the
partitions into a director called file\_xml. If you enter this
directory you will find parititoned xml files \inltt{P0000000.xml},
\inltt{P0000001.xml},...,\inltt{P0000009.xml} which can then be
processed individually.
will partition the mesh into 10 paritions and write each partition into a
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.
There is also a \inltt{part-only-overlapping} option
There is also a \inltt{--part-only-overlapping} option, which can be run in the