search

Unity-Technologies / ml-agents

The Unity Machine Learning Agents Toolkit (ML-Agents) is an open-source project that enables games and simulations to serve as environments for training intelligent agents using deep reinforcement learning and imitation learning.
https://unity.com/products/machine-learning-agents
Other
16.93k stars 4.14k forks source link

KeyError when training with Curriculum #3337

Closed nic126 closed 4 years ago

nic126 commented 4 years ago

hey, guys,
I'm just trying to get my agent with curriculum training up and running. In my scene I have an agent and a NavMeshAgent.

To start the training, I use the command line from the docs: mlagents-learn config/trainer_config.yaml --curriculum=config/curricula/chaser/ --run-id=chaser-curriculum_test --train

In the trainer_config.yaml I have defined the following parameters:

ChaserLearning:
    use_curiosity: true
    summary_freq: 1000
    time_horizon: 128
    batch_size: 128
    buffer_size: 2048
    hidden_unity: 256
    beta: 1.0e-2
    max_steps: 1.0e6

and I have created a folder in \ml-agents\config\curricula\ named chaser. In it is the file ChaserLearning.json. The file has the following values:

{
    "measure" : "reward",
    "thresholds : [-0.1, 0.7, 1, 1.5, 1.7, 2],
    "min_lesson_length" : 80,
    "signal_smoothing" : true, 
    "parameters" : 
    {
        "speedMultiplicator" : [0.5, 0.75, 0.9, 1.0, 1.25, 1.5, 1.75]
    }
}

The BehaviourParameter Script in the Unity Editor is named chaser-Curriculum_test01 When I start the training, I get the following error in the shell:

KeyError: 'chaser-Curriculum_test01'

I have attached a screenshot of the shell below. Did I make a mistake somewhere, or is it because of the ML-Agents version? Inkedshell_LI

thanks in advance

anupam-142857 commented 4 years ago

Hi @nic126 github issues is for bugs and feature requests. Could you please post your message in the Unity ML Agents forum. here's a link to the forum page. Thanks!

github-actions[bot] commented 3 years ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.