Closed hongbo-zhu-cn closed 7 years ago
Thanks for this patch. Could you provide a minimal example showing how the current implementation causes unwanted behaviors? Maybe submitted separately as an issue?
I don't see why the change in line 98 is needed. The function calculateCoordinates
does not create any coordinate vectors from scratch but rather obtains them from atoms or using the Vector
constructor. Please check whether you can remove your change in line 98 and have things still work.
I agree the changes in lines 980 to 982 are needed.
Because function calculateCoordinates()
returns D as an instance of Bio.PDB.Vector, which is not an array. This still causes the ValueError (I just double-checked). But now I change it to D.get_array()
instead of using type conversion. This shall look neater.
Yes, I prefer this, thanks!
Hi, the coordinates for an atom in Bio.PDB.Atom is an instance of Numpy Array. Currently it is a mixture of vector and list. This may lead to unwanted behaviors when atom coordinates are concerned. best,