Skip to content
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

The value of the FRC map is all NaN #8

Open
yrl1120 opened this issue Apr 10, 2023 · 4 comments
Open

The value of the FRC map is all NaN #8

yrl1120 opened this issue Apr 10, 2023 · 4 comments

Comments

@yrl1120
Copy link

yrl1120 commented Apr 10, 2023

When I use eSRRF->Parameters sweep-->Calculate FRC, the value of the FRC map is all NaN, I am confused about why this is happening, and is there any way to avoid or solve it, I would appreciate it if you could answer me.

@HannahSHeil
Copy link
Collaborator

Hi, could you try again with a different crop of the image? This sometimes happens if the FRC estimation is not able to optimize. If it only happens for single parameter pairs in the sweep those will be disregarded, but if it happens for the whole sweep, either your parameter range is very off or your image area does not fit well.

@yrl1120
Copy link
Author

yrl1120 commented Aug 10, 2023

Thank you very much for your reply. Now I have some confusion about calculating FRC and error maps, if we have 1k frames raw image sequence, and we split raw data into odd/even frames and reconstruct it (500 frames), is the corresponding raw sequence also reconstruct with 500 frames? Compare error maps with this result(500 frames)? It means that 1000 frames are divided into odd (500)/even (500) frames to calculate the resolution value, should we also choose frame number 500 for raw image sequence reconstruction? I would appreciate it if you could help me.

@HannahSHeil
Copy link
Collaborator

Hi,
you always need the double amount of frames for the parameter sweep and it will for example only create a reconstruction out of 500 of the 1000 frames. In the final reconstruction you can use the information of all 1000 fr, this could give slightly better results. Maybe there is no detectable difference, just try it.

@yrl1120
Copy link
Author

yrl1120 commented Aug 10, 2023

Thanks for the reply, I'll try it. So this means that the input of 1000 frames is actually calculated at the FRC resolution of 500 frames reconstruction?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants