Liebe Gitlab-Nutzer, lieber Gitlab-Nutzer, es ist nun möglich sich mittels des ZIH-Logins/LDAP an unserem Dienst anzumelden. Ein Anmelden über dieses erzeugt ein neues Konto. Das alte Konto ist über den Reiter "Standard" erreichbar. Die Administratoren

Dear Gitlab user, it is now possible to log in to our service using the ZIH login/LDAP. Logging in via this will create a new account. The old account can be accessed via the "Standard" tab. The administrators

Commit 2daa8f2e authored by Praetorius, Simon's avatar Praetorius, Simon
Browse files

Documentation of Arh2 file format ver. 3.0 added

parent 2a483789
......@@ -45,8 +45,8 @@ Please send comments on ARH to the AMDiS form:\\ \url{https://fusionforge.zih.tu
\item[Version 1.0: July 29, 2010] First format description of original ARH file format. Implemented by MeshConv.
\end{description}
\section{The file format}
The ARH2 file format consists of three sections:
\section{The sARH file format}
The sARH file format to describe local macro-element wise mesh structure and data on the macro elements consists of four sections:
\begin{enumerate}
\item The first section contains a file format descriptor and version informations. This can be used to distinguish between the old ARH format and the ARH2 format and all of its versions, i.e. test whether the reader supports the actual format.
......@@ -75,7 +75,7 @@ The concrete structure is given in the table below:
\first{\#fes} & 4 & uint & number of Finite Element spaces \\
\first{\#vec} & 4 & uint & number of value vectors \\
\first{\#el} & 4 & uint & number of macro elements \\
\first{cps} & 4 & int & compression flag: \texttt{0}: no compression, \texttt{1}: ZLib compression\footnote{Details of ZLib Version, Parameters etc.} \\\hline
\first{cps} & 4 & int & compression flag: \texttt{0}: no compression, \texttt{1}: ZLib compression\footnote{Details of ZLib Version, Parameters etc.}, \texttt{2}: BZip2 \\\hline
& & & & \\
\first{\for $i=0,\ldots,$\#el-1} & & &\\
......@@ -89,7 +89,8 @@ The concrete structure is given in the table below:
& & & & \\
\first{\for $i=0,\ldots,$\#fes-1} & & &\\
\ldelim[{3}{1mm} & fe[i]$\rightarrow$ID & 16 & string & ``\texttt{costum}'', or name of file with description of Finite Element in AFED format \\
\ldelim[{3}{1mm} & fe[i]$\rightarrow$nl & 4 & uint & length of filename w.o. suffix (0: default Lagrange elements) \\
\ldelim[{3}{1mm} & fe[i]$\rightarrow$ID & nl & string & name of file (w.o. suffix) with description of Finite Element in AFED format \\
& fe[i]$\rightarrow$DOFs/pos & 16 & $4\times$uint & number of DOFs per position (vertex, edge, face, center) \\
& & & & \\
......@@ -117,13 +118,20 @@ The concrete structure is given in the table below:
& & & & & & \\
& \second{\for $j=0,\ldots,$\#fes-1} & & & \\
& \ldelim[{5}{1mm} & \first{\#el\_val} & 4 & & number of values per vector in fespace fe[j] \\
& \ldelim[{5}{1mm} & \first{\#el\_val} & 4 & uint & number of values per vector in fespace fe[$j$] \\
& & & & & & \\
& & \first{\for $k=0,\ldots,$n-1} & & & \\
& & \ldelim[{2}{1mm} & data[k] & $X\times$\#el\_val & & sequence of values, X: size of data-type (vec[i(j,k)]$\rightarrow$type), n: number of value vector belonging to fe[j].\\
& & \first{\for $k=0,\ldots,N_j-1$} & & & \\
& & \ldelim[{2}{1mm} & data[$i_k(j)$] & $X\times$\#el\_val & \texttt{T} & sequence of values\footnote{Value vectors are ordered in the same way as in the vec array of the header, when assigned to an fespace. Thus fe[j]$\rightarrow$vectors=\{vec[$i_0(j)$], vec[$i_1(j)$],\ldots\}, with $i_0(j) < i_1(j) < \ldots$ and vec[$i_k(j)$]$\rightarrow$fe == $j$ for $k=0,\ldots,N_j-1$ and $N_j:=$size(fe[j]$\rightarrow$vectors)}, $N_j$: number of value vector belonging to fe[$j$], $X$: size of data-type \texttt{T} $\triangleq$ vec[$i_k(j)$)]$\rightarrow$type.\\
& & & & & & \\\hline
\end{longtable}
\section{The pARH file format}
To describe the distribution of macro elements and the partition of a macro mesh among several processors a container format is defined. This can be used to improve performance of parallel file reading. The file consists of four section:
\begin{enumerate}
\item The first section contains a file descriptor and version information, as in the sARH file.
\item In the second part information about the
\end{enumerate}
\end{document}
\ No newline at end of file
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment