-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Processing parameters for pipelines #1
Comments
FWIW 76.0 is stored as the 41st value in the NMRPipe header in the AMX
This value is not mapped into the metadata dictionary in nmrglue but likely should be. Also note that the AMX and DMX dataset have different sizes 1024 x 2048 vs 1024 x 1970. When NMRPipe removes the digital filter it also re-sizes the first dimension. |
This parameter is named #define FDDMXVAL 40 /* Added for NMRPipe. */
#define FDDMXFLAG 41 /* Added for NMRPipe. */
#define FDDELTATR 42 /* Added for NMRPipe. */ I will update nmrglue to include this and any other new NMRPipe metadata values unless someone beats me to it. Until then there is no easy method for accessing this value. |
Thank you. :) |
A last doubt: must the additional PS operation be performed also on the other dimension, for DMX files? |
No. Only the direct dimension is affected by the digital filter. None of the other dimensions will have this correction. |
With jjhelmus/nmrglue#144 the DMX value is available in the metadata dictionary in the |
Maybe you can try with the following script:
As you can see, there are some differences, but even the position where there is noise, it is very similar in all 4 cases. The minor differences still remain (due to slight differences in the baseline, phases). Since the height is 1e11, these get really magnified, so
np.allclose
might not be the best way to compare the spectra, at least if you use a low tolerance.The text was updated successfully, but these errors were encountered: