Very odd - when running my notebooks such as scattering_conv_playground.ipynb on JupyterHub on rusty, the wavelets stored in scattering.psi have NaNs dotted around them which obviously breaks all the convolutions. When running the exact same notebook on my desktop or laptop, I get no NaNs (same random seed, and I have verified that the wavelet parameters are the same). I have checked kymatio, python, numpy and torch versions are the same. I am running JupyterHub using a kernel constructed from my conda environment on rusty. When I rerun the same code block from the terminal in this environment, I also get no NaNs, so I don't think this is an environment issue.
So just to be clear:
- The filter parameters are definitely not causing it (same filter params on either terminal or a different cluster produces no NaNs)
- Running the same code in the same conda environment from the terminal produces no NaNs
- The versions of the key packages like numpy and torch are not producing the NaNs.
A bit at a loss on this one at the moment.. perhaps something unusual is being done when Jupyter imports the conda environment kernel, maybe the best option is to contact scc. @eickenberg have you ever encountered anything like this?
Very odd - when running my notebooks such as
scattering_conv_playground.ipynbon JupyterHub on rusty, the wavelets stored inscattering.psihave NaNs dotted around them which obviously breaks all the convolutions. When running the exact same notebook on my desktop or laptop, I get no NaNs (same random seed, and I have verified that the wavelet parameters are the same). I have checked kymatio, python, numpy and torch versions are the same. I am running JupyterHub using a kernel constructed from my conda environment on rusty. When I rerun the same code block from the terminal in this environment, I also get no NaNs, so I don't think this is an environment issue.So just to be clear:
A bit at a loss on this one at the moment.. perhaps something unusual is being done when Jupyter imports the conda environment kernel, maybe the best option is to contact scc. @eickenberg have you ever encountered anything like this?