-
Notifications
You must be signed in to change notification settings - Fork 88
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
Process_pipe_3d:There seems to be some issues with the processing script #187
Comments
Can you share more information about what these spectra are? Are they acquired in the Echo-Antiecho manner or the States/TPPI/States-TPPI? |
Also, can you share any of the undersampled datasest to debug this issue? |
Of course, I will privately send it to your email. |
In this case, you will have to manually do the echo-antiecho processing. You can take a look at #149 for suggestions on how to do this. |
Sorry, I have privately sent the undersampling data to your email kaustubh.mote@gmail.com three times, but they were all returned. Do you have another email address? |
Strange. Maybe you can share the folder in dropbox/google-drive and send the link. |
About reading the non-uniformly sampled data: the dic, data = ng.bruker.read(".")
data = data.reshape(*data.shape, 1) # reshapes data to a 3d
udic = ng.bruker.guess_udic(dic, data) # this now reads 3 dimensions correctly
data = data.reshape(data.shape[:2]) # reshape back to original 2d if necessary I will add the custom code for nus when I find some time to do it. For now I have added the bug label to this. |
Thank you very much for your reply, this is a simple and effective method, however, in this case the third dimension is 1, maybe I should use the nuslist file to reshape the data to the three dimensions I want. |
I just realized that bruker seems to also save a file called dic, data = ng.bruker.read(".", bin_file="ser_full")
data = data.reshape(128, 128, 1024) # reshapes data to a 3d, these numbers seem to be lost in acqus files
udic = ng.bruker.guess_udic(dic, data) # this now reads 3 dimensions correctly This still needs a proper fix though. |
Ah, it seems to be coming from nmrpipe! No problem. Then this is simpler to work with. |
Yeah,but in this case, we first need to read the raw data with the help of nmrpipe. We hope that nmrglue can directly read the undersampled raw data and reshape it into a three-dimensional array (for example, the data is 128x128x1024). |
a:
b:
d:
e:
f:
At the same time, we use NMRPipe to process the direct dimension of the 3D data, and then use nmrglue to process the two indirect dimensions of the 3D data and find that the results are consistent with the NMRPipe results. So we think the problem should lie in the processing of the direct dimension.
2.Also, it seems that nmrglue's bruker and varian also have problems reading raw data. It is normal when we use bruker and varian to read 3D fully sampled raw data, but when we use bruker and varian to read 3D undersampled raw data, the read data becomes 2D data.
We hope the author can provide some help, it is greatly appreciated!
The text was updated successfully, but these errors were encountered: