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
In an NMR lipids post, we talked some time ago about being consistent regarding which hydrogens are pro-R and which are pro-S. So far if we buildH on, say C31, we build H311 and H312. So we add 1 and 2 suffixes. The idea would be for example to assign 1 to the pro-R hydrogen, and 2 to the pro-S.
This is something we can do without too much pain in buildH. I describe the strategy in a recent issue of NMRlipids IVb.
In fact, I did a check for Berger POPC. What matters is the order of the helpers in the .json files. So the "only thing" we have to do, if we want this, is to do a check when we create the json file.
So we can think about whether we implement this or not.
The text was updated successfully, but these errors were encountered:
Samuli Ollila created a new issue on the Databank project of NMRlipids. We'll discuss there how to be consistent with the input files between both projects.
In an NMR lipids post, we talked some time ago about being consistent regarding which hydrogens are pro-R and which are pro-S. So far if we buildH on, say
C31
, we buildH311
andH312
. So we add1
and2
suffixes. The idea would be for example to assign1
to the pro-R hydrogen, and2
to the pro-S.This is something we can do without too much pain in buildH. I describe the strategy in a recent issue of NMRlipids IVb.
In fact, I did a check for Berger POPC. What matters is the order of the helpers in the
.json
files. So the "only thing" we have to do, if we want this, is to do a check when we create the json file.So we can think about whether we implement this or not.
The text was updated successfully, but these errors were encountered: