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
IIRC, Sai had a few entries that didn't have corresponding data in SASBDB, so she couldn't reliably determine the units. But agreed, if we know the units are 1/nm (or you can use a heuristic to figure it out) then we should not hardcode 1/A.
It looks like the code is hardcoded for the
1/A
units, thus it is failing on files with1/nm
units (related to #53)There are multiple places using a hardcoded A to nm conversion:
IHMValidation/master/pyext/src/validation/sas.py
Line 190 in c3bb0ef
IHMValidation/master/pyext/src/validation/sas.py
Line 217 in c3bb0ef
IHMValidation/master/pyext/src/validation/sas.py
Line 421 in c3bb0ef
IHMValidation/master/pyext/src/validation/sas.py
Line 481 in c3bb0ef
IHMValidation/master/pyext/src/validation/sas.py
Line 483 in c3bb0ef
IHMValidation/master/pyext/src/validation/sas.py
Line 491 in c3bb0ef
The information about units is stored in the sascif file:
SASDC29
SASDDD6
The text was updated successfully, but these errors were encountered: