blob: 431266dc65a40d1ef7b36917629ff3b45bb87879 (
plain)
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
|
small things
set centroid variables for drift correction
add an option to compute/output the surface radius on a latitude/longitude
grid
I should set CXXFLAGS for this thorn to turn off automagic template
instantiation on those platforms (eg lemieux, modi4) where it's on
by default (Thomas Radke says to copy FlexIO's scheme for doing this)
there should be an option to specify using the parameter-file initial
guess at selected times (or cactus iteration numbers) instead of always
using the AH posn from the previous time step -- this would be useful
if there are an inner & outer horizon which start out coincident
and you want to track them separately
implement "physics highlights" verbosity level
implement a log file where the full "algorithm highlights" (or whatever)
messages can go even if stdout (= the Cactus run's log file) only gets
less-verbose messages
medium things
compute Gaussian curvature, cf AHFinder/src/AHFinder_gau.F
HDF5 data files (simple format and/or Werner Benger's fancy one)
move origin point to track moving BHs
read AHFinder Fourier coeffs for initial guess
write data files giving intersection of AH with a Cactus output plane
(or more generally, with a hyperslab)
export a "compute h(theta,phi)" function
so other thorns could test point membership in/outside AH etc
prevent h from going negative if the iteration isn't converging
(maybe use log(h) in Newton iteration?)
handle excision properly
(detect when interpolator tries to use data from excised region
and treat this as failure to evalute H(h) --> failure to find horizon
checkpoint/recover doesn't remember the current horizon shape
for an initial guess
(needs storage of h gridfn in Cactus arrays,
or else some equivalent mechanism)
what's worse, right now restart will overwrite the original
BH_diagnostics file(s)! :( :(
if two apparent horizons appear together, then move apart, right now
even with N_horizons > 1 we will probably have each of our AHs track
the same one; there should be some way to say "use AH 1 + something
as the initial guess for AH2" or suchlike, so we could find both AHs
large things
handle quadrant/octant grids with rotating BCs
(needs Jacobian of one ghost zone to cover two different ghost zones)
"isolated horizons" computation of BH mass and spin
detect Cartoon and rotate geometry interpolation into Cartoon plane
|
