Diana -- known bugs

Last modified: Wednesday, 22 June 2005 17:50

For the Topology Editor bugs look the "news" for the Topology Editor.

1. User transparent: change clock() to getrusage() in calculation of the total elapsed time. Note, tml timers still use clock()! Fixed in 2.36.
2. User transparent: possible buffer and integer overflow in utils.c:long2str fixed. Fixed in 2.36.
3. User transparent: some cleaning of signed/unsigned integer conversions in rexec.c and macro.c Fixed in 2.36.
4. First \gettoken() after \scannerinit() may fail, if \scannerinit() is performed after \scannerdone() was invoked in the middle of the scanned line. Fixed in 2.36.
5. Diana crashes if the order of fermionic interaction is not 2. So in the revision 2.33 it is allowed to be only 2. In future, will be changed.
6. In the revision 2.31: client failed starting directly from the operator \_exec() Fixed in 2.32.
7. The following situation: 1) momenta come from a full topology table; 2) direction of line in the table is opposite "reduced" direction. Then the direction of momentum was wrong. Fixed in 2.32
8. Positive direction of momentum on a majorana propagator must coincide with the direction of fermion number flow, while it was unspecified. Fixed in 2.30
9. Positive direction of momentum of fermionic external legs must me in agreement with the direction of fermion number flow while it was + for ingoing and - for outgoing. Fixed in 2.30
10. Maximal Y coordinate of a picture were defined incorrectly, when a tadpole occurs at the top. Fixed in 2.28
11. Full topology table entry for pure topologies faild exporting momenta. Fixed in 2.28
12. Full topology table entry for pure topologies ignore provided shape. Fixed in 2.28
13. Crush at momenta balance checking if zero momentum is undefined. Fixed in 2.28
14. The user specified unique topology names may conflict with the automatically generated ones in case if the user will use the same name as automatical. To resolve the conflict, "A#" will be added to automatically generated names (here # is some number). Fixed in 2.27
15. If the additional (not unique) topology name coincides with the unique topology name of one of already defined topologies, it overrides this unique name. This means that coordinates/line/vertexmarks/remarks will relates to a wrong topology! Fixed in 2.27
16. When the value of the lats command line option is not specified, the program crashed. Fixed in 2.27
17. At some condition the program chashed on fail. Not dangerous, the execution is failed, anyway. Fixed in 2.27 Conditions are: TML program consists in one main program, i.e., no any TML functions; Translation was performed successively, but BEFOR the first run somethin was happen, and Diana failed, e.g., QGRAF file appears to be corrupted.
18. Preprocessor directives \GET() and \CMDLINE() were non-reenterable. When they appeared into an argument of anothe macro, and were undefined, they return their argument instaed of en empty string. Fixed in 2.26
19. Translation table in the working topology table can be erased by the Topology editor. Now is fixed: DIANA adds this table in the operator \loadIntTable(). Fixed in 2.26
20. Amplitudes with Majorana fields have wrong sign.
21. At present, the style file "createsymmetry.tml" is broken. In previous distributions it works, but possibly with errors.
22. Bug with the extrenal line indices, fixed in the Revision 2.18, was NOT fixed completely. If the user forgot all external line indices, then they appeared as a garbage. Now is fixed: Revision 2.21.
23. Expansion of multiply keywords in FORM id (num, fnum, etc.) was performed only once. The remain keywords appeared as a garbage. Now all keywords are expanded correctly. Fixed in 2.21.
24. During calculating of the topology coordinates in some conditions there can be devision by 0.0, if all 3 points of some line coincide. Even this is not a case, the postscript code for such a degenerated line appeared to be broken. Now such coinciding points are splitted by a small x - shift. Fixed in 2.21.
25. In the function s_gcmp ( tools.c) the priority of logical operators in the last return() is changed. This bug may appear in build_momentum when somebody asks not a full momentum, but only a specific group. I am not sure that this bug really affects on the Diana output. Fixed in 2.19.
26. In the TM operator \find() there was incorrect integer format. This bug may appear in systems where "long" integers differ form "int", e.g., DOS. Fixed in 2.19.
27. In read_inp.c top_text++ for a tadpole is moved outside the cycle. The previous version was incorrect -- some of text[] may be uninitialised. This can leads a crash at new_diagram() (never observed). Fixed in 2.19.
28. The size of tadpoles in the PostScript subroutine getMinMax now assumes the tadpole as the square. Previous version leads to incorrect definition of the size of the tadpoles -- fixed in 2.19.
29. Very dangerous! At sertain (seldom) conditions, on some compilers ( in particular, gcc 2.7.2.1 under Linux; on Alpha does not appear) in tadpoles the second index may contain trailing garbage. On multiindex ( many groups) in tadpoles this bug may crash the program (in principle, never observed). Fixed in 2.19.
30. Possible bug ( may appear in future developig ) The function "sortinternaltopology" returns nothing! -- Fixed in 2.19.
31. Currently, Diana will fail in pure vertex diagrams, when there are no internal lines at all. Fixed in the Revision 2.23.
32. There are several bugs in the PostScript drivers. Fixed in the Revision 2.18
33. There are no any verifications in the external line indices. If the user accidentally forgets to define the external particle index, then the Diana output appears to be broken. Fixed in the Revision 2.18