Skip to content
This repository has been archived by the owner on Sep 18, 2024. It is now read-only.

gpuIndices #3628

Closed
creater-zq opened this issue May 11, 2021 · 7 comments
Closed

gpuIndices #3628

creater-zq opened this issue May 11, 2021 · 7 comments
Assignees
Labels

Comments

@creater-zq
Copy link

creater-zq commented May 11, 2021

Describe the issue:

Environment:

  • NNI version:2.2
  • Training service (local|remote|pai|aml|etc):local
  • Client OS:Windows 10
  • Python version:3.8.5
  • PyTorch/TensorFlow version:1.7.1
  • Is conda/virtualenv/venv used?:conda version 10.2
  • Is running in Docker?:False

Configuration:

  • Experiment config (remember to remove secrets!):config.yml
    authorName: default
    experimentName: test_nni
    trialConcurrency: 1
    maxExecDuration: 1d
    maxTrialNum: 30
    trainingServicePlatform: local
    searchSpacePath: search_space.json
    useAnnotation: false
    tuner:
    builtinTunerName: TPE
    classArgs:
    optimize_mode: minimize
    trial:
    command: python train_nni.py
    codeDir: .
    gpuNum: 1
    localConfig:
    useActiveGpu: true
    gpuIndices: 3

  • Search space:
    { "start_lr": {"_type": "choice", "_value": [0.0001, 0.001, 0.01, 0.1]},
    "batch_size": {"_type": "choice", "_value": [8, 12, 16, 32, 64, 128]}
    }

error:
ERROR: Config V1 validation failed: SchemaError('gpuIndex format error!')

@scarlett2018
Copy link
Member

error:
ERROR: Config V1 validation failed: SchemaError('gpuIndex format error!')

#3540
Adding error msg pr owner in to suggest.

@creater-zq
Copy link
Author

error:
ERROR: Config V1 validation failed: SchemaError('gpuIndex format error!')

#3540
Adding error msg pr owner in to suggest.

Thank you, but I don't quite understand your suggestion. Could you tell me more about it

@liuzhe-lz
Copy link
Contributor

This bug will be fixed in next release.
For now you can walkaround by replacing 3 (int) with '3' (str).

@kvartet kvartet added the config label May 13, 2021
@creater-zq
Copy link
Author

This bug will be fixed in next release.
For now you can walkaround by replacing 3 (int) with '3' (str).

nice, thanks!

@liuzhe-lz
Copy link
Contributor

Expected to be fixed in v2.3 release next week.

@scarlett2018 scarlett2018 added the bug Something isn't working label Jun 10, 2021
@kvartet
Copy link
Contributor

kvartet commented Jun 10, 2021

hello @creater-zq, I'm closing this issue as it had been fixed, free feel to reopen it if you still think it an active issue.

@kvartet kvartet closed this as completed Jun 10, 2021
@Delong-Zhu
Copy link

This bug will be fixed in next release. For now you can walkaround by replacing 3 (int) with '3' (str).

thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants