Closed rdrighetto closed 2 years ago
Just a short update: there were no issues in prediction when using models from later iterations (e.g. iter30). The error above occurred when using models from iterations 5-10. I agree it may not be a good idea to look at such early models, but still would like to know why this happens and how to avoid it.
Hi,
Thank you for reporting this. I know another user also encounter this NaN problem recently, but I can not reproduce it on my computers.
I would like to know whether this model can successfully be used to predict other tomograms?
Thanks for the reply! Good idea, I will try to predict a different tomogram with these models that were giving the error. I'll report back next week, I'm currently traveling.
Strange that now I can not only predict other tomograms using those same problematic models, but also predict the same tomogram that was having this problem before, without issues. Maybe it was an issue with the specific computing node/GPU where I was running it before on our cluster. I will close the issue now for failing to reproduce the problem.
Hi,
I'm getting the following error in prediction:
I know the "Bad file descriptor" error is harmless, but mrcfile is complaining that the resulting tomogram has NaN values. This is the part that concerns me: /scicore/home/engel0006/GROUP/pool-engel/soft/isonet/venv_isonet/lib/python3.9/site-packages/mrcfile/mrcobject.py:545: RuntimeWarning: Data array contains NaN values warnings.warn("Data array contains NaN values", RuntimeWarning)
It does write out an MRC volume, but it cannot be displayed because of the NaN-valued voxels. Has anyone encountered this error before and knows how to correct this?
Thank you!