-
Notifications
You must be signed in to change notification settings - Fork 6
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
data normalization #6
Comments
Thank you for your question and for pointing this out! We do not perform inverse normalization during testing, as it does not affect the results of 2D reconstructions. However, we recommend applying inverse normalization after the reconstruction if you are planning to perform slice-by-slice reconstruction of 3D data. Additionally, while we normalize the k-space data, there is no specific input data range requirement—it depends on the characteristics of your data. |
Thanks a lot for your kind reply. I train your model with fastMRI single coil knee dataset. But the sampling results have large noise, as shown in the figure. The model was trained with the original hyperparameters provided in your code. Could you please give me some advice about training with the fastMRI knee dataset? many thanks. |
The sampling was testes with the checkpoint of the 275 epoch. |
There are some advice maybe helpful for you:
|
thanks for the wonderful work and open-source code.
I have questions about data normalization. In the dataset.py file, the data normalization was set as 'std' with a data.normalize_coeff. but I didn't find inverse normalization in the test code, should I perform inverse normalization during evaluation?
Could you please tell me the range of the data that should be as input, [0, 1] or [-1,1], or others, the range of the photom data you provided is [-25, 82]
Many thanks for your help
The text was updated successfully, but these errors were encountered: