Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. We have updated the language to the Editor Terms based on feedback from our employees and community. Learn more.
    Dismiss Notice

Key Error When Using Curriculum Learning

Discussion in 'ML-Agents' started by haoyang1995, Mar 10, 2020.

  1. haoyang1995

    haoyang1995

    Joined:
    Feb 19, 2020
    Posts:
    2
    unexpected.png
    Hello. I was getting unexpected termination because of key error in the middle of every training.
    This is my yaml file from curricula folder. I carefully compared its format with yaml written by others but found no clue.
    Any idea of what is causing this?
    Thanks so much!
    Screen Shot 2020-03-10 at 10.46.54 AM.png
     
  2. TreyK-47

    TreyK-47

    Unity Technologies

    Joined:
    Oct 22, 2019
    Posts:
    1,799
    We'll send this over to the team to review, @haoyang1995. Which version of C# and Python are you using?
     
  3. haoyang1995

    haoyang1995

    Joined:
    Feb 19, 2020
    Posts:
    2
    I feel so sorry for the late reply.

    I am using Python 3.7 and C# version 4.0.30319.42000(got from "Debug.Log(System.Environment.Version)").
    I somehow found a workaround using try except to catch and suppress the key error. It worked after catching and ignoring the error but I will be so thankful if you guys can review this issue.
     
  4. asad133

    asad133

    Joined:
    Apr 1, 2020
    Posts:
    22
    I have exactly the same issue. It does not happen on every run but is very frustrating since training can terminate at a late stage and waste so much computation. It happens when the agent lesson changes. Used Try, Except as a workaround
     
    Last edited: Apr 11, 2020
  5. harpj

    harpj

    Unity Technologies

    Joined:
    Jun 20, 2017
    Posts:
    6
    Hi @haoyang1995 and @asad133 -- I apologize for the late reply on this issue, but it should be resolved in the latest version of ML-Agents (0.16.0 / 1.0.0).