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
Different isomers of lipids have been discussed many times during the NMRlipids meeting, including the NMRlipids online meeting on 26th of February 2021.
Two different questions have been discussed.
Should we include isomer information into the mapping files?
Should we check which isomers are present in the contributed simulations?
In principle, answer to both questions is yes. However, practical details on how these would be done are not clear.
This is technically doable as we have done for PG lipids before (Isomers of PG lipids NMRlipidsIVPEandPG#38). However, it not clear to me how we would automatically decide which parts of each molecule should be checked. Therefore, we should maybe also wait with this until we have isomer specific mapping files.
The text was updated successfully, but these errors were encountered:
Different isomers of lipids have been discussed many times during the NMRlipids meeting, including the NMRlipids online meeting on 26th of February 2021.
Two different questions have been discussed.
In principle, answer to both questions is yes. However, practical details on how these would be done are not clear.
Conclusions in the online meeting was that the isomer information will be included into the mapping files when this can be done automatically. Some progress in this direction is previously discussed in issues Isomers in the databank NMRlipidsIVPEandPG#41 and Isomers of PG lipids NMRlipidsIVPEandPG#38. We can continue the discussion here.
This is technically doable as we have done for PG lipids before (Isomers of PG lipids NMRlipidsIVPEandPG#38). However, it not clear to me how we would automatically decide which parts of each molecule should be checked. Therefore, we should maybe also wait with this until we have isomer specific mapping files.
The text was updated successfully, but these errors were encountered: