Baiyu Chen

It can be avoided by simply replacing https://github.com/mhamilton723/STEGO/blob/d1341b9bac32f27039db1c924eb8c4b4e6b9298a/src/eval_segmentation.py#L118 with ```python from multiprocessing import get_context with get_context('spawn').Pool(cfg.num_workers + 5) as pool: ... ```

https://github.com/mhamilton723/STEGO/issues/16#issuecomment-1168772107 It should help.

The inappropriate model-saving approach might cause this issue. https://github.com/pytorch/pytorch/issues/18325#issuecomment-661759359 Saving only the state dict instead of the whole model object is more recommended. https://pytorch.org/docs/master/notes/serialization.html#recommended-approach-for-saving-a-model

This may be caused by the wrong path to datasets. Have you checked it within the ```src/configs/train_config.yml```?

You may try installing PyTorch using pip within your stego_m environment: ``` pip install torch ```

It should be the same issue as https://github.com/mhamilton723/STEGO/issues/33#issuecomment-1184122727 You can install the [mamba](https://github.com/mamba-org/mamba) to tackle the stuck problem. First, install the ```mamba``` using the following command: ```conda install mamba -n...

> Then I operated on my Ubuntu system again, but I will encounter such problems when performing this step >  Sorry, I really want to help, but the whole...