Resource of free step by step video how to guides to get you started with machine learning.
Friday, May 8, 2020
Divide-and-Conquer Monte Carlo Tree Search For Goal-Directed Planning (Paper Explained)
When AI makes a plan it usually does so step by step, forward in time. But often it is beneficial to define intermediate goals to divide a large problem into easier sub-problems. This paper proposes a generalization of MCTS that searches not for the best next actions to take, but for the best way to sub-divide the problem recursively into problems so tiny that they can each be solved in a single step. Paper: https://ift.tt/3cj5znk Site: https://ift.tt/2yuv7iH Abstract: Standard planners for sequential decision making (including Monte Carlo planning, tree search, dynamic programming, etc.) are constrained by an implicit sequential planning assumption: The order in which a plan is constructed is the same in which it is executed. We consider alternatives to this assumption for the class of goal-directed Reinforcement Learning (RL) problems. Instead of an environment transition model, we assume an imperfect, goal-directed policy. This low-level policy can be improved by a plan, consisting of an appropriate sequence of sub-goals that guide it from the start to the goal state. We propose a planning algorithm, Divide-and-Conquer Monte Carlo Tree Search (DC-MCTS), for approximating the optimal plan by means of proposing intermediate sub-goals which hierarchically partition the initial tasks into simpler ones that are then solved independently and recursively. The algorithm critically makes use of a learned sub-goal proposal for finding appropriate partitions trees of new tasks based on prior experience. Different strategies for learning sub-goal proposals give rise to different planning strategies that strictly generalize sequential planning. We show that this algorithmic flexibility over planning order leads to improved results in navigation tasks in grid-worlds as well as in challenging continuous control environments. Authors: Giambattista Parascandolo, Lars Buesing, Josh Merel, Leonard Hasenclever, John Aslanides, Jessica B. Hamrick, Nicolas Heess, Alexander Neitz, Theophane Weber Links: YouTube: https://www.youtube.com/c/yannickilcher Twitter: https://twitter.com/ykilcher BitChute: https://ift.tt/38iX6OV Minds: https://ift.tt/37igBpB
Labels:
Video
Published by Free artificial intelligence and machine learning video tutorial resource
Related video tutorials
Subscribe to:
Post Comments (Atom)
Most watched
-
Quick answer: Qwen 3 32B needs about 22.7 GB of VRAM at Q4_K_M with a 4k-token context — a used 24 GB card like the RTX 3090 is the minimu...
-
Using GPUs in TensorFlow, TensorBoard in notebooks, finding new datasets, & more! (#AskTensorFlow) [Collection] In a special live ep...
-
Inside TensorFlow: Summaries and TensorBoard [Collection] Take an inside look into the TensorFlow team’s own internal training sessions-...
-
Quick answer: For an 8B model at Q4, local electricity costs roughly $0.05 per million output tokens — against about $0.53 per million ble...
-
Quick answer: For machine-learning work, buy an external SSD over a spinning hard drive, pick USB 3.2 Gen 2 (10 Gbps) or faster, and size f...
-
Quick answer: DeepSeek V4 Flash is a Mixture-of-Experts model: all 284 billion parameters must be stored, so combined RAM plus VRAM — not ...
-
Quick answer: Yes, for most budget builders: a used RTX 3090 is still the cheapest route to 24 GB of VRAM with full CUDA support. Capacity...
-
Hey everyone This is Ujjwal kapil B.tech 2nd year Ai and Ml In this video we covered one of the most important question "COLLEGE KAB O...
-
Quick answer: The cheapest path to serious local-AI VRAM is not one new flagship card — it is two used ones. A single RTX 5090 costs $1,999...
-
Quick answer: FLUX.1 dev needs about 10 GB of VRAM at Q4/NF4 quantization for 1024×1024 image generation, so a 12 GB GPU such as the GeFor...
No comments:
Post a Comment