![]() ![]() If you run an episode manually, your total return may be less than you expected, due to the discount rate ( -d to change 0.9 by default).Look at the console output that accompanies the graphical output (or use -t for all text). Not the finest hour for an AI agent.Note: The Gridworld MDP is such that you first must enter a pre-terminal state (the double boxes shown in the GUI) and then take the special 'exit' action before the episode actually ends (in the true terminal state called TERMINALSTATE, which is not shown in the GUI). A full list of options is available by running: python gridworld.py -hThe default agent moves randomly python gridworld.py -g MazeGridYou should see the random agent bounce around the grid until it happens upon an exit. Please offer suggestions regarding how to get the standard debugging functionality.Such is the life of a Gridworld agent!You can control many aspects of the simulation. I tried the suggestions here: Delphi: why breakpoints from time to time are not usable (green highlighted line on IDE)?.I have verified that Debug Information and Local Symbols are enabled.I tried the solutions here: Delphi2010-IDE keeps stoping on CPU debug window.deleted all the dcus for the project and verified that Building the project put them in the expected location (which is the same folder as the EXE).verifying that the debugging settings for the project are consistent with those for other projects that do debug correctly.deleting the DPROJ file and letting Delphi recreate it.The Event Log indicates that the module has debug info. After the first breakpoint is reached, I can't set any additional breakpoints (the breakpoint is displayed as invalid - a red dot with an X), even if it is the next line after the breakpoint (with a green arrow displayed). However, when I try to inspect variables or view watches, I am told that the variable is undeclared. The Event Log correctly indicates the source line number with the breakpoint and the name of the file with the breakpoint indicated in the Event log matches the name and path of the source file open in the editor (the one where I placed the breakpoint). The problem is that the CPU window opens when the breakpoint is reached. In one of my projects, I can't get breakpoints to work as expected. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |