diff options
| author | jthorn <jthorn@0a4070d5-58f5-498f-b6c0-2693e757fa0f> | 2005-05-20 13:19:56 +0000 |
|---|---|---|
| committer | jthorn <jthorn@0a4070d5-58f5-498f-b6c0-2693e757fa0f> | 2005-05-20 13:19:56 +0000 |
| commit | 2f9378fe1f03a73153bbc82d5efb2f5d282d15c4 (patch) | |
| tree | c2af83da282a93f3a319a0ddc60c71ad474a9bca | |
| parent | 2995148248d0375113932157ba86d2b45e513c26 (diff) | |
note some problems with this thorn
(which I have _not_ fixed in my current set of commits)
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinInitialData/IDAxiBrillBH/trunk@68 0a4070d5-58f5-498f-b6c0-2693e757fa0f
| -rw-r--r-- | doc/TODO | 15 |
1 files changed, 15 insertions, 0 deletions
diff --git a/doc/TODO b/doc/TODO new file mode 100644 index 0000000..a339e11 --- /dev/null +++ b/doc/TODO @@ -0,0 +1,15 @@ +Things that Could be Improved in This Thorn +=========================================== + +This thorn works with non-unigrid Cactus, but it doesn't work very +efficiently: it does the 2D elliptic setup and solve all over again +for each local Cactus (3D) grid. It would be more efficient to move the +2D elliptic stuff out into a separately scheduled routine which would +be done once (for Carpet, it would be scheduled in level or global +mode), and have only the interpolation to the 3D grid done for each +local Cactus grid. + +Part of this same change might also be to store the 2D elliptic results +in Cactus grid arrays rather than native Fortran 90 arrays. This would +let us use standard Cactus I/O methods to output the 2D elliptic results +instead of the hard-wired code we use right now. |