Trusted, Bureaucrats
4,223
edits
Changes
Tracker links with full descriptions.
* Updated the memory_leak_test_relax_fit.py development script for the C module changes. This is only the docstring description which changed.
* Epydoc docstring fixes for the lib.io module - keyword arguments were not correctly identified. These were identified by Troels in the post at http://thread.gmane.org/gmane.science.nmr.relax.scm/24565/focus=7384.
* Created the State.test_bug_23017_ieee_754_multidim_numpy_arrays system test. This is to catch bug #23017 ([https://gna.org/bugs/?23017)bug #23017, the multidimensional numpy arrays are not being stored as IEEE 754 arrays in the XML state and results files]. This test checks a rank-2 float64 numpy array stored in the current data pipe against what the IEEE 754 int list should be for it.
* Grammar fix for a warning from the pymol.display user function.
<section end=changes/>
<section begin=bugfixes/>
* Bug fix for the pymol.view user function for when no PDB file exists. The pymol.view user function would fail with an AttributeError when the currently loaded data does not exist as a PDB file. This is now caught and the non-existent PDB is no longer displayed. A better solution might be to dump all the current structural data into a temporary file and load that, all within a try-finally statement to be sure to delete the temporary file. This solution may not be what the user is interested in anyway.
* Simple fix for bug #23017 ([https://gna.org/bugs/?23017). This is bug #23017, the multidimensional numpy arrays are not being stored as IEEE 754 arrays in the XML state and results files]. The problem was a relatively recent regression caused by a change to the is_float_matrix() function of the lib.arg_check module. It was simply that the default dims keyword argument value was changed from None to (3, 3). Therefore any call to the function without supplying the dims argument would fail if the matrix was not of the (3, 3) shape.
<section end=bugfixes/>