Currently, bruker.guess_udic and bruker.add_axis_to_udic fail when acqus files are unavailable or if they are called with read_acqus=False. Most of the parameters which it tries to look up in acqus are also available in procs. I have added conditionals to bruker.add_axis_to_udic where spectral width, carrier offset, axis name and acquisition mode will be looked up in procs as well as acqus. Most of the places, preference is given to the acqus files, but there are some use cases (such as post-acquisition re-scaling of spectral widths) where one should be reading specifically from the procs files.
This PR does not change the default behaviour of the functions.
Coverage decreased (-0.07%) to 21.067% when pulling 30cd8e8f14710ca39f2b96a9e2d43008183eedc2 on kaustubhmote:master into 485deb34d1adf4c3988d0e3da59181720314d7ae on jjhelmus:master.
Coverage decreased (-0.07%) to 21.07% when pulling 30cd8e8f14710ca39f2b96a9e2d43008183eedc2 on kaustubhmote:master into 485deb34d1adf4c3988d0e3da59181720314d7ae on jjhelmus:master.
Currently,
bruker.guess_udic
andbruker.add_axis_to_udic
fail when acqus files are unavailable or if they are called withread_acqus=False
. Most of the parameters which it tries to look up in acqus are also available in procs. I have added conditionals tobruker.add_axis_to_udic
where spectral width, carrier offset, axis name and acquisition mode will be looked up in procs as well as acqus. Most of the places, preference is given to the acqus files, but there are some use cases (such as post-acquisition re-scaling of spectral widths) where one should be reading specifically from the procs files. This PR does not change the default behaviour of the functions.