So following #278 , I encountered this annoying problem which makes us to restart the google colab notebook's runtime after the first Fuse's installation. Unfortunately I couldn't find a really good solution for that. The best workaround I came up with is to add a clear explanation for the FuseMedML installation 😵 . (OPEN FOR SUGGESTIONS)
Changes:
Fixed prefix for model's outputs
Added a clear explanation for the FuseMedML installation on the google colab notebook.
Improved UI
Re-open the notebook's unit-test
Thanks @simona-rc for raising those issues 😄
Update:
double checked on Jenkins:
Update 2:
Fix typos in the installation instructions:
[all+examples] -> [all,examples]
Visit here to watch the updated notebook
So following #278 , I encountered this annoying problem which makes us to restart the google colab notebook's runtime after the first Fuse's installation. Unfortunately I couldn't find a really good solution for that. The best workaround I came up with is to add a clear explanation for the FuseMedML installation 😵 . (OPEN FOR SUGGESTIONS)
Changes:
Thanks @simona-rc for raising those issues 😄
Update: double checked on Jenkins:
Update 2: Fix typos in the installation instructions:
[all+examples]
->[all,examples]