subprocess.CalledProcessError: Command
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- machine-learning
Research direction
Start with train_panoptic.py and seamseg/config/config.py, then inspect how the installed package is expected to provide seamseg/config/defaults. Reproduce the shown torch.distributed.launch command and verify that the installed package contains the defaults directory before training begins; done means the import succeeds without the reported FileNotFoundError.
Written by the indexing model from the issue text.
Description
root:/data/research/seamseg-master/scripts# python -m torch.distributed.launch --nproc_per_node=2 train_panoptic.py --log_dir ./log.log "/data/research/seamseg-master/seamseg/config/defaults/panoptic.ini" /common-data/jlong.yuan/segmentation/seamseg/Mapillary/
Traceback (most recent call last):
File "train_panoptic.py", line 21, in
from seamseg.config import load_config, DEFAULTS as DEFAULT_CONFIGS
File "/data/config/anaconda3/lib/python3.6/site-packages/seamseg-3.3.3-py3.6-linux-x86_64.egg/seamseg/config/init.py", line 1, in
from .config import load_config, DEFAULTS
File "/data/config/anaconda3/lib/python3.6/site-packages/seamseg-3.3.3-py3.6-linux-x86_64.egg/seamseg/config/config.py", line 11, in
for file in listdir(_DEFAULTS_DIR):
FileNotFoundError: [Errno 2] No such file or directory: '/data/config/anaconda3/lib/python3.6/site-packages/seamseg-3.3.3-py3.6-linux-x86_64.egg/seamseg/config/defaults'
Traceback (most recent call last):
File "train_panoptic.py", line 21, in
from seamseg.config import load_config, DEFAULTS as DEFAULT_CONFIGS
File "/data/config/anaconda3/lib/python3.6/site-packages/seamseg-3.3.3-py3.6-linux-x86_64.egg/seamseg/config/init.py", line 1, in
from .config import load_config, DEFAULTS
File "/data/config/anaconda3/lib/python3.6/site-packages/seamseg-3.3.3-py3.6-linux-x86_64.egg/seamseg/config/config.py", line 11, in
for file in listdir(_DEFAULTS_DIR):
FileNotFoundError: [Errno 2] No such file or directory: '/data/config/anaconda3/lib/python3.6/site-packages/seamseg-3.3.3-py3.6-linux-x86_64.egg/seamseg/config/defaults'
Traceback (most recent call last):
File "/data/config/anaconda3/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/data/config/anaconda3/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/data/config/anaconda3/lib/python3.6/site-packages/torch/distributed/launch.py", line 235, in
main()
File "/data/config/anaconda3/lib/python3.6/site-packages/torch/distributed/launch.py", line 231, in main
cmd=process.args)
subprocess.CalledProcessError: Command '['/data/config/anaconda3/bin/python', '-u', 'train_panoptic.py', '--local_rank=0', '--log_dir', './log.log', '/data/research/seamseg-master/seamseg/config/defaults/panoptic.ini', '/common-data/segmentation/seamseg/Mapillary/']' returned non-zero exit status 1.
- Dominant language
- Python
- Stars
- 301
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from mapillary/seamseg
-
ImportError during testing pre-trained model with test_panoptic.py, possibly a circular import?Open
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
-
Creating a ColabOpen
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
All issues in mapillary/seamseg
Similar issues
-
customer-reported
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Azure/azure-cli#34150 · 1 comment ·
Maintainers usually reply within 1 day
-
community-request
Difficulty 1/5 Under an hour Newbie friendliness 95/100
NVIDIA-NeMo/Curator#2464 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
WeblateOrg/translation-finder#1099 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
trezor/trezor-firmware#7997 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day