-
data found here: /duke/projects/ivadomed/gm_dwi_exvivo (supposedly the data used for this model):
Otherwise we might "clean" it without knowing what it is/was used for.
-
@mariehbourget can inform as she is currently working on a BEP to add this field
-
ivadomed's adaptive loader currently uses HDF5 to load data and parse metadata. HDF5 allows to load data in RAM or "on the fly". Do we want to migrate ivadomed's loader to HDF5?
-
When using the CLI `ivadomed_automate_training`, 4 parameters cannot be changed in the hyperparameter file: `gpu`, `command`, `log_directory`, `model_name`, and `debugging`. The script assumes that th…
-
Currently, training a model with the standard `ivadomed --config config.json` syntax doesn't support multi-GPU usage; this is only meant for `ivadomed_automate_training`.
I found [this page](https…
-
From: https://github.com/neuropoly/spinalcordtoolbox/issues/2993#issuecomment-723146400
Investigation import durations.
1. Create a test file that simply imports ivadomed.
```
# import_ivadmed…
-
I am facing with loading error for intervertebral disc labeling using `ivadomed`. I am using the latest version (`2.7.4`) of `ivadomed` and already tried the sample 2D segmentation example (`ivadomed …
-
I don't think that we have documentations that points to the pre-trained, pre-packaged multi-center model, which is one of our singularity.