diff options
author | jthorn <jthorn@e296648e-0e4f-0410-bd07-d597d9acff87> | 2005-04-30 16:44:36 +0000 |
---|---|---|
committer | jthorn <jthorn@e296648e-0e4f-0410-bd07-d597d9acff87> | 2005-04-30 16:44:36 +0000 |
commit | d3fd16971a57e0a07fedb2f7fc42afc764b34902 (patch) | |
tree | 6e5702faf2815524e4e3d1e432ac12118765d97c | |
parent | a8d3a7248bf04b1a18033d37784659d197106c1e (diff) |
restore file which was mistakenly deleted
git-svn-id: http://svn.einsteintoolkit.org/cactus/EinsteinInitialData/Exact/trunk@224 e296648e-0e4f-0410-bd07-d597d9acff87
-rw-r--r-- | doc/TODO | 63 |
1 files changed, 63 insertions, 0 deletions
diff --git a/doc/TODO b/doc/TODO new file mode 100644 index 0000000..7eb398e --- /dev/null +++ b/doc/TODO @@ -0,0 +1,63 @@ +Things to do for this thorn +=========================== +$Header$ + +---------------------------------------- +Jonathan Thornburg: +*Every* model should be described in the thorn guide! +As of Wed Apr 27 16:51:44 CEST 2005, the cvs logs show recent additions +of "shifted gauge wave" and ""Schwarzschild/BL" solutions to param.ccl +with no corresponding updates to documentation.tex. :( :( +---------------------------------------- + +Jonathan Thornburg: +* make the hard-wired 1.0e-6 finite differencing grid spacing in + Bona_Masso_data.F77 a parameter +* Are we setting the initial data at the right time level + (there are comments in gauge.F77 that we're half-a-time-step off)? + Is this still a problem now that we always use MoL? + Do we still need to support the non-MoL case? +* add options to set ALL time levels of initial data, not just the + current level + +---------------------------------------- + +Ian Hawke: +It would be nice to be able to output the difference between a +numerical evolution and the exact solution. + +---------------------------------------- + +Sascha Husa: +It would be nice if Exact could set up variables other than the ADM ones +(indeed it appears to not even grok BSSN right now). + +---------------------------------------- + +Sascha Husa: +The boundary setup needs to be generalized to handle ghost zones wider +than 1 point. + +---------------------------------------- + +Every model should have .ge. 1 test case! Right now most of the +models have no test cases at all, and this makes it way too easy for +bugs to creep in and go undetected for a long time. + +For models satisfying the Einstein eqns, it would be nice to also have +test cases which compute the Hamiltonian constraint (and maybe the +momentum constraints too) and check that it (they) are suitably small. + (The down side of that is that is that those test + cases would then need at least ADMConstraints + to be compiled into your Cactus binary, and that + in turn requires ADMMacros.) +This would help guard against typos, wrong formulas, and other +"consistent, but wrong" cases. + +---------------------------------------- +It would be nice if Exact supported fisheye. +Failing that, it could at least check if FishEye is active + and cleanly report an error. +---------------------------------------- +It would be nice if Exact supported the "static conformal" metric type. +---------------------------------------- |