Kernel unexpectedly dying; line of code: viz_cnmf.show
computer: window 11, 32GB RAM (15.6GB usable) processor: AMD Ryzen 7 7800X3D 8-Core Processor
I couldn't run viz_cnmf.show() with a 1200 frames movie. It was possible with a 600 frames movie with fewer much coutours.
I have dedicated video memory of 16GB.
Can you please use the template and describe everything.
I'm sorry I was not clear:
OS: Windows 11
mesmerize-core version: '0.4.0'
caiman version: ''1.11.1'
Hardware description: 16 GPU, 32GB RAM (15.6GB usable) processor: AMD Ryzen 7 7800X3D 8-Core Processor
The kernel died every time I tried to run viz_cnmf.show() with a 1200 frames cnmf processed movie. But it was possible with a 600 frames movie. I tried increase the dedicated VRAM to 16GB but the kernel still died when I ran viz_cnmf.show ().
Thank you very much for your help!
What gpu do you have? How many components are you trying to visualize?
On Sat, Jun 29, 2024, 2:09 PM CharlotteWenxin @.***> wrote:
I'm sorry I was not clear:
OS: Windows 11 mesmerize-core version: '0.4.0' caiman version: ''1.11.1' Hardware description: 16 GPU, 32GB RAM (15.6GB usable) processor: AMD Ryzen 7 7800X3D 8-Core Processor
The kernel died every time I tried to run viz_cnmf.show() with a 1200 frames cnmf processed movie. But it was possible with a 600 frames movie. I tried increase the dedicated VRAM to 16GB but the kernel still died when I ran viz_cnmf.show ().
Thank you very much for your help!
— Reply to this email directly, view it on GitHub https://github.com/nel-lab/mesmerize-core/issues/307#issuecomment-2198129326, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHXXRDFWJX6EZO2HHFS37DZJ2PXPAVCNFSM6AAAAABKCMQUPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGEZDSMZSGY . You are receiving this because you commented.Message ID: @.***>
I have integrated GPU and there are about 6000 components.
You're probably running out of VRAM. Do you expect 6000 components?
On Sat, Jun 29, 2024, 4:22 PM CharlotteWenxin @.***> wrote:
I have integrated GPU and there are about 6000 components.
— Reply to this email directly, view it on GitHub https://github.com/nel-lab/mesmerize-core/issues/307#issuecomment-2198212183, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHXXRDSNJWBSB32TA4UIBDZJ27LLAVCNFSM6AAAAABKCMQUPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGIYTEMJYGM . You are receiving this because you commented.Message ID: @.***>
I see.
No, only about 500, but there are a lot of rejected components along with false positive.
What does your movie look like, your parameters might be off. You shouldn't have to curate out thousands of components.
On Sat, Jun 29, 2024, 11:06 AM CharlotteWenxin @.***> wrote:
I see.
No, only about 500, but there are a lot of rejected components along with false positive.
— Reply to this email directly, view it on GitHub https://github.com/nel-lab/mesmerize-core/issues/307#issuecomment-2198225062, or unsubscribe https://github.com/notifications/unsubscribe-auth/ACHXXRB6VH3AYY66NKECNDLZJ3EQDAVCNFSM6AAAAABKCMQUPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOJYGIZDKMBWGI . You are receiving this because you commented.Message ID: @.***>
It looks like this:
I applied a mask to exclude the region without neurons and reduce k, then I can use viz_cnmf.show.
@CharlotteWenxin did you get an error message like this in the Jupyter log?
thread '<unnamed>' panicked at src/conv.rs:1182:30:
invalid size
stack backtrace:
0: rust_begin_unwind
...
If so, I think this is due to having contours with 0 points. Will make an issue or PR about it shortly.
I think mesviz might already filter out contours with size = 0
any development here?
I didn't get an error and adding a mask helped to reduce the number of false positive.
D 2024-09-20 16:38:35.397 ServerApp] 200 GET /ipyparallel/clusters?1726843115268 ([email protected]) 11.91ms
thread '
@Agrajag1984 this issue is fixed in #309, we're waiting for a new caiman release to merge it but you should be able to use this branch for now: https://github.com/proektlab/mesmerize-core/tree/contour-nan-fix
@Agrajag1984 please post a bug report new issue with all the details.
@ethanbb this appears unrelated to that.
Ah yes I agree it's different from Charlotte's issue, but I believe this is caused by removing nans from empty contours (I got the same error with my data and that was the problem). Anyway we can talk more on a different issue thread.