1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
|
% *======================================================================*
% Cactus Thorn template for ThornGuide documentation
% Author: Ian Kelley
% Date: Sun Jun 02, 2002
%
% Thorn documentation in the latex file doc/documentation.tex
% will be included in ThornGuides built with the Cactus make system.
% The scripts employed by the make system automatically include
% pages about variables, parameters and scheduling parsed from the
% relevant thorn CCL files.
%
% This template contains guidelines which help to assure that your
% documentation will be correctly added to ThornGuides. More
% information is available in the Cactus UsersGuide.
%
% Guidelines:
% - Do not change anything before the line
% % START CACTUS THORNGUIDE",
% except for filling in the title, author, date, etc. fields.
% - Each of these fields should only be on ONE line.
% - Author names should be separated with a \\ or a comma.
% - You can define your own macros, but they must appear after
% the START CACTUS THORNGUIDE line, and must not redefine standard
% latex commands.
% - To avoid name clashes with other thorns, 'labels', 'citations',
% 'references', and 'image' names should conform to the following
% convention:
% ARRANGEMENT_THORN_LABEL
% For example, an image wave.eps in the arrangement CactusWave and
% thorn WaveToyC should be renamed to CactusWave_WaveToyC_wave.eps
% - Graphics should only be included using the graphicx package.
% More specifically, with the "\includegraphics" command. Do
% not specify any graphic file extensions in your .tex file. This
% will allow us to create a PDF version of the ThornGuide
% via pdflatex.
% - References should be included with the latex "\bibitem" command.
% - Use \begin{abstract}...\end{abstract} instead of \abstract{...}
% - Do not use \appendix, instead include any appendices you need as
% standard sections.
% - For the benefit of our Perl scripts, and for future extensions,
% please use simple latex.
%
% *======================================================================*
%
% Example of including a graphic image:
% \begin{figure}[ht]
% \begin{center}
% \includegraphics[width=6cm]{MyArrangement_MyThorn_MyFigure}
% \end{center}
% \caption{Illustration of this and that}
% \label{MyArrangement_MyThorn_MyLabel}
% \end{figure}
%
% Example of using a label:
% \label{MyArrangement_MyThorn_MyLabel}
%
% Example of a citation:
% \cite{MyArrangement_MyThorn_Author99}
%
% Example of including a reference
% \bibitem{MyArrangement_MyThorn_Author99}
% {J. Author, {\em The Title of the Book, Journal, or periodical}, 1 (1999),
% 1--16. {\tt http://www.nowhere.com/}}
%
% *======================================================================*
% If you are using CVS use this line to give version information
\documentclass{article}
% Use the Cactus ThornGuide style file
% (Automatically used from Cactus distribution, if you have a
% thorn without the Cactus Flesh download this from the Cactus
% homepage at www.cactuscode.org)
\usepackage{../../../../doc/latex/cactus}
\begin{document}
% The author of the documentation
\author{Erik Schnetter \textless schnetter@cct.lsu.edu\textgreater}
% The title of the document (not necessarily the name of the Thorn)
\title{InterpToArray}
\date{June 30, 2010}
\maketitle
% Do not delete next line
% START CACTUS THORNGUIDE
% Add all definitions used in this documentation here
% \def\mydef etc
% Add an abstract for this thorn's documentation
\begin{abstract}
Interpolate grid functions to grid arrays on a regular grid of
locations, so that these can e.g.\ be output more easily.
\end{abstract}
% The following sections are suggestive only.
% Remove them or add your own.
\section{Introduction}
Some post-processing and visualisation tools cannot handle mesh
refinement or multi-block systems. These tools then require
interpolating the result onto a regular, uniform grid. This is what
this thorn does.
InterpToArray can interpolate to 0D, 1D, 2D, and 3D grids. The
interpolation result is stored in grid arrays. These can be either
replicated or distributed over all processes. Note that using
replicated (DISTRIB=constant) grid arrays can require a substantial
amount of memory on each process.
\section{Numerical Implementation}
InterpToArray uses standard Cactus interpolators such as PUGHInterp or
CarpetInterp.
\section{Using This Thorn}
The variables which should be interpolated are specified by
parameters; currently, up to 100 variables can be interpolated.
The interpolator and its options are also specified via parameters.
Finally, the locations of the points of the regular grid are also
specified via parameters. These grid points are specified via an
\emph{origin} and \emph{offsets}, and they do not have to be aligned
with the coordinate axes. For example, a 2D grid is specified via
three (real) vectors $x^a$, $di^a$, and $dj^a$, and via its (integer)
size $ni$ and $nj$. The coordinates of the grid points are then given
via
$$
x^a(i,j) = x^a + i \cdot di^a + j \cdot dj^a
$$
for $0 \le i < ni$ and $0 \le j < nj$. Grids with other dimensions
are specified equivalently.
% Do not delete next line
% END CACTUS THORNGUIDE
\end{document}
|
