Open mattholc opened 1 month ago
I think the only reason to wrap the data in a json str was to prevent future name collisions. We might have a mixture of energies in the future from QM, scrubber, pka prediction, and so on. Could also use the name of the property to that end. Not sure if one way is better than the other. Currently, you can pass that string to json.loads() to get the dict.
If you create a mol from an sdf generated by mk_export, it has only the property 'meeko' which contains a dictionary of docking information ('is_sidechain', 'free_energy', etc) formatted as a string. It would be preferable to expose direct access to the properties through rdkit molprops.