Hello,
I’ve been playing around with the ml-agents toolkit and one of my models needs to be trained for more than 500000 steps. I’ve used multiple example .yaml files, many of them with max_steps greater than 500000. However, whenever I start training, the console says under the hyperparameters that the max_steps is 500000. Each of my training runs ends after 500000. Thanks
Are you sure you run the same the YAML config file you configured? Check the directory of your file and your command.
Also make sure that the name you set in the Behavior Parameters → Behavior Name is the same that you defined in the config. Otherwise it will take the default one (if using a version prior to ML-Agents Release 3)
3 Likes
[EDIT: See reply below this one, fixed the problem]
I have this same problem! Changing the max_steps in the base config.yaml doesn’t seem to update the max_steps in the behavior once the program is run. For me, they get reset back to 500,000 (even though the number 500,000 doesn’t occur anywhere in the project, in it’s current state…). When I try to --resume training, ml-agents will create a new configuration.yaml (or update it, if it already exists), but the max_steps value of the Behaviour won’t reflect my changes in the base file. I’ve tried resetting the project, changing different .yaml files, deleting the child .yaml files and re-running the base with the updated max_steps, but nothing seems to be working.
Never mind, found out how to fix it! Here’s what I did: in the base .yaml file you used to train, each “group” under the “behaviors:” area represent a behavior. The name of the behavior is defined in Unity under Behavior Name in the Behavior Parameters script of your agent. The name of the behavior you’re changing (the one you want to extend the max_steps of) needs to match the one that appears in the .yaml file. If it doesn’t match, then ml-agents won’t say anything, but will resume with it’s own default settings (like what BotAcademy said above).
You can fix this by either:
1.) Changing the name of your behavior in the .yaml to match the one in Unity.
2.) Changing the name of your behavior in Unity to match the one in the .yaml (probably shouldn’t do this if you want to resume training, since the results will be based off the Unity behavior name).
3.) Or copying the behavior that already exists in the .yaml, pasting it below, and changing the name of the behavior to match what exists in Unity (this is what I did, since my training already took place with the behavior name).
Hope this helps 
3 Likes
@BotAcademy and @justingarrigus , I updated the behavior name in the .yaml file to match the Unity behavior and that fixed it! I was not aware this had to be edited, so its good to know. Thanks!
2 Likes
Hi there! Can you specify where the base config file is? I have searched all over for the main config file that is referenced.
All of our yaml configs live here.
1 Like
Thanks for your response! I am coming back around to the project.
My confusion stems from this error
I have created a config file to the best of my understanding.
This is the location in the project. I have created a virtual environment, aidojo.
This is the test behavior I have created. I just made a variation of the 3DBall yaml file.
I am assuming I don’t have things in the right location but have struggled finding any direction to go.
Perfect, thank you very much. I had copied a previous project and started doing different stuff with it and forgot to change the name on the script and this was causing me a lot of trouble.
Did you change the name of the behavior in the yaml file you created?
When can you post your mlagents-learn command and your yaml config
The third screenshot provided shows the yaml file open in notepad.
What about the mlagents-learn command?
1 Like
Ah! I see why it was not working.
This is the command that I am now using. I was referencing a tutorial that had the backslashes switched… They must have been working on a Mac or something?
From now on I will just reference the Unity documentation directly.
For anyone searching for config file issues specifically, reference these pages
Thanks Christopher for your help!!
1 Like
What I did, is changing the max steps in the yaml file located in the results folder, and giving the path to this yaml file as argument after the --resume command