Open aozalevsky opened 2 years ago
SASDDD6 is the only one affected at the moment
SASDBV9.sascif:_sas_scan.unit 1/A
SASDBW9.sascif:_sas_scan.unit 1/A
SASDBX9.sascif:_sas_scan.unit 1/A
SASDBY9.sascif:_sas_scan.unit 1/A
SASDBZ9.sascif:_sas_scan.unit 1/A
SASDC29.sascif:_sas_scan.unit 1/A
SASDCG7.sascif:_sas_scan.unit 1/A
SASDDD6.sascif:_sas_scan.unit 1/nm
SASDEE2.sascif:_sas_scan.unit 1/A
SASDG85.sascif:_sas_scan.unit 1/A
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.
this is addressed in the dev_2.0
branch with a complete rewrite of sas
code.
I'll keep the issue open until the merge.
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:
https://github.com/salilab/IHMValidation/blob/c3bb0ef65f6104368a103ee429dcf264285ba936/master/pyext/src/validation/sas.py#L190
https://github.com/salilab/IHMValidation/blob/c3bb0ef65f6104368a103ee429dcf264285ba936/master/pyext/src/validation/sas.py#L217
https://github.com/salilab/IHMValidation/blob/c3bb0ef65f6104368a103ee429dcf264285ba936/master/pyext/src/validation/sas.py#L421
https://github.com/salilab/IHMValidation/blob/c3bb0ef65f6104368a103ee429dcf264285ba936/master/pyext/src/validation/sas.py#L481
https://github.com/salilab/IHMValidation/blob/c3bb0ef65f6104368a103ee429dcf264285ba936/master/pyext/src/validation/sas.py#L483
https://github.com/salilab/IHMValidation/blob/c3bb0ef65f6104368a103ee429dcf264285ba936/master/pyext/src/validation/sas.py#L491
The information about units is stored in the sascif file:
SASDC29
SASDDD6