You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I just ran into an issue with 1HDQ, where the ligand, INF, is wrongly converted to a floating point number representation of positive infinity, which causes issues downstream.
When dumped into json the ligand name becomes Infinity (without quotes) instead of 'INF' (with quotes) so I cannot get the ligand back. When dumped with ujson an OverflowError is raised.
There are other ligand names which can be interpreted as numbers, for instance 1ONY has a ligand named 588, and a ligand named NAN exists, although it isn't used in any PDB entry so far.
The text was updated successfully, but these errors were encountered:
I just ran into an issue with 1HDQ, where the ligand, INF, is wrongly converted to a floating point number representation of positive infinity, which causes issues downstream.
And then:
When dumped into json the ligand name becomes
Infinity
(without quotes) instead of'INF'
(with quotes) so I cannot get the ligand back. When dumped withujson
anOverflowError
is raised.There are other ligand names which can be interpreted as numbers, for instance 1ONY has a ligand named 588, and a ligand named NAN exists, although it isn't used in any PDB entry so far.
The text was updated successfully, but these errors were encountered: