From 5d137974b2a8dc9d382d6bb0487ca142da2b2bfc Mon Sep 17 00:00:00 2001 From: jthorn Date: Sun, 6 Jul 2003 11:42:06 +0000 Subject: remove stuff for Jonathan Thornburg's interpolator (which is GPL and thus not allowed in CactusBase; it's now in AEIThorns/AEILocalInterp/) git-svn-id: http://svn.cactuscode.org/arrangements/CactusBase/LocalInterp/trunk@155 df1f8a13-aa1d-4dd4-9681-27ded5b42416 --- doc/TODO | 21 ------------------ doc/future-ideas.tex | 61 ---------------------------------------------------- doc/references | 15 ------------- 3 files changed, 97 deletions(-) delete mode 100644 doc/TODO delete mode 100644 doc/future-ideas.tex delete mode 100644 doc/references diff --git a/doc/TODO b/doc/TODO deleted file mode 100644 index 14accaf..0000000 --- a/doc/TODO +++ /dev/null @@ -1,21 +0,0 @@ -$Header$ - -Things to do on this thorn: -- make casts from datatype to CCTK_REAL explicit in - GeneralizedPolynomial-Uniform fetch routines -- clean up the horrible inefficiency of the - GeneralizedPolynomial-Uniform/Hermite interpolator - (cf Erik Schnetter's E-mails and CactusBase/1366) - - -- add the old "uniform cartesian" interpolator (by Paul Walker & Thomas Radke) - to CCTK_InterpLocalUniform() - -- allow scalar boundary_{off_centering,extrapolation}_tolerance - values in the parameter table (to mean using this value for each ibndry) - -- maybe change the defaults so off-centering is forbidden unless - the user explicitly asks for it to be allowed? - -- implement a "silent" parameter like in PUGHInterp? - alternatively, print warning msgs for some error returns? diff --git a/doc/future-ideas.tex b/doc/future-ideas.tex deleted file mode 100644 index 9495c15..0000000 --- a/doc/future-ideas.tex +++ /dev/null @@ -1,61 +0,0 @@ -$Header$ - -% This file contains documentation for features which aren't implemented -% yet, and which are far enough in the future that I (Jonathan) decided -% to remove them from documentation.tex for the time being. - -%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% - -\subsection{Caching} -\label{sect-generic-options/caching} - -Some interpolators may support special ``caching'' optimizations to -speed repeated interpolations where some or all of the interpolator -arguments and/or parameters are the same. For example, when interpolating -a tabulated equation of state the number of dimensions, the coordinate -origin and grid spacing, and the input arrays (the tabulated equation -of state data), will probably all be the same from one interpolator -call to another. - -If an interpolator supports caching, the following parameters should -be used to control this: - -\begin{verbatim} -const char cache_type[]; /* set with Util_TableSetString() */ -const char cache_control[]; /* set with Util_TableSetString() */ -CCTK_INT cache_handle; -\end{verbatim} - -There are three basic operations supported: -\begin{description} -\item[Create a Cache] - To set up caching, call the interpolator with \verb|cache_type| - set to describe what arguments and/or parameters will remain - the same in future interpolator calls, \verb|cache_control| - set to the string \verb|"create"|, and \verb|cache_handle| - {\em not\/} in the parameter table. The interpolator will - then do extra (possibly quite time-consuming) work to set - up cached information. The interpolator will delete the - key \verb|cache_control|, and return a handle to the cached - information in \verb|cache_handle|; this allows multiple caches - to be active concurrently. -\item[Use a Cache] - To use a cache (\ie{} to make an interpolation with the - hoped-for speedup), just call the interpolator with - \verb|cache_handle| set to the value returned when the cache - was created. Note that you still have to provide all the - ``will be the same'' interpolator arguments and/or parameters; - providing a cache handle is essentially just a promise that - these will be the same as in the cache-create interpolator - call. The details of what information is cached, and if/how - the ``will be the same'' arguments are still used, are up to - the interpolator. -\item[Destroy a Cache] - To destroy a cache (\ie{} free any memory allocated when - the cache was created), call the interpolator with - \verb|cache_handle| set to the value returned when the cache - was created, and \verb|cache_control| set to the string - \verb|"destroy"|. The interpolator will delete the keys - \verb|cache_handle| and \verb|cache_control|, and destroy - the cache. -\end{description} diff --git a/doc/references b/doc/references deleted file mode 100644 index 2602c39..0000000 --- a/doc/references +++ /dev/null @@ -1,15 +0,0 @@ -This file contains references which are or might in the future relevant -to interpolation. - -Thermodynamic consistency in EOS interpolation -@ARTICLE{2000ApJS..126..501T, - author = {{Timmes}, F.~X. and {Swesty}, F.~D.}, - title = "{The Accuracy, Consistency, and Speed of an Electron-Positron Equation of State Based on Table Interpolation of the Helmholtz Free Energy}", - journal = {Astrophysical Journal Supplement Series}, - year = 2000, - month = feb, - volume = 126, - pages = {501--516}, - url = {http://esoads.eso.org/cgi-bin/nph-bib_query?bibcode=2000ApJS..126..501T&db_key=AST}, - adsnote = {Provided by the NASA Astrophysics Data System} -} -- cgit v1.2.3