-
Notifications
You must be signed in to change notification settings - Fork 20
/
TODO
60 lines (47 loc) · 1.97 KB
/
TODO
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
$Id: TODO,v 1.19 2004-07-23 19:34:05 wilsonp Exp $
When claiming a task from this list, please immediately place your
name beside it, change the date from the date that it was added to
the date that you claimed the task, send an email to
"group/[email protected]", and checkin this file to the repository.
alaradev Members
PW - Paul Wilson
PP - Phiphat "Nor" Phruksarojanakun
MF - Milad Fatenejad
DP - David Paige
BUG FIXES
------------------
NEW FEATURES
------------------
[PW] Adjoint dose in zones
[MF] Sequential Charged Particle Reactions
**** (08/08/2002) Direct writing of SRCDX (?) gamma source file for DANTSYS
[MF] (08/08/2002) Direct reading of MCTAL files from MCNP
**** (08/08/2002) Alternative approximations for dose (e.g. line source)
**** (08/08/2002) Improve volume calculation and output
* automatically change units to reduce significant figures (e.g. cm3->m3)
* rigorously report volume units in 1-/2-D problems (e.g. cm3 per cm)
**** (08/08/2002) Add support for user defined output screen/line width
CODE FEATURES
------------------
[MF] (08/08/2002) Improve comments under doxygen
[MF] (06/12/2003) HDF5 support for nuclear data & dump files
USER DOCUMENTATION
------------------
[PW] (08/08/2002) bring up to date with current features
[PW] (23/06/2003) Edit & reformat user manual
**** (08/08/2002) add tutorials
**** (08/08/2002) add/improve description of supported ASCII Library formats
OTHER
-------------------
**** (08/08/2002) investigate automatic logging and/or mailing of commit info
RESEARCH
------------------
* data infrastructure [MF]
* investigate round-off error issues in bateman and inversion methods
NOTES
--------
*********************** ROUND-OFF ERROR ********************
Note that bateman(...) and laplaceInverse(...) currently take the
absolute value of negative results, which is only valid when assuming
that they are inconsequential. This is a source of numerical error!!!
but a positive wrong answer is better than a negative wrong answer.