Next: V.I Registration
Up: V. Reference
Previous: V.G Error Messages
This is a list of current bugs in the latest version. To see a history of squashed
bugs for eariler versions, click here. If you think you
have found a new bug, first check the FAQ to be sure it's not a
"feature!" Then send e-mail to
ww@lanl.gov that includes a description
of the bug, the version of DeltaE and type of computer you are using, and the input file (at
least the portion of it you think is important) that produces the problem.
- DELTAE's internal solver is very efficient at converging to solutions for
complicated systems; however, it knows nothing about acoustics, or any part of
physics, for that matter. If it ventures too far, it can give you more
wavelengths than you intended before reaching resonance. DELTAE does not know that
negative frequencies, negative
pressures, or negative lengths are improper; it simply does the math.
In short, the
reasonableness of the answers produced will almost always depend on the quality of
the initial guesses. Because of the variety of variables that can be used in the
solution vector, and the
potential to confuse the solver if we try to fix it midstream, this behavior is not
easily cured; however, it is usually fairly simple to correct a model back into the
proper `quadrant,' changing signs where appropriate, once it has converged.
- Comments (lines starting with "!") in the input .IN files are lost in the .OUT files!
The only comments that are preserved are the segment titles...the spaces to the right of each
segment name. We have known about this limitation since before the first DeltaE version,
and the fix is not trivial, or we would have implemented it already. Still, we plan to devise
an acceptable way to do it soon. For now, limit comments you want to keep to the segment title
field, and if you need more, keep a printed copy of your initial .IN file.
- Numbers stored in .out files are stored with much less precision than
DELTAE actually maintains internally. Sometimes, after storing a file in a
particularly difficult computation, the solver will converge a little differently
if the file is loaded back in and run again.
- Not all floating point errors are successfully trapped; some can cause the
program to crash and lose unsaved work.