From b71f064f3ef8e64cb46554bfaaf56211fca0a34f Mon Sep 17 00:00:00 2001 From: Robert Nishihara Date: Thu, 4 Aug 2016 17:39:14 -0700 Subject: [PATCH] small documentation fixes (#348) --- doc/using-ray-on-a-cluster.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/doc/using-ray-on-a-cluster.md b/doc/using-ray-on-a-cluster.md index bf31a923f..2fb35e386 100644 --- a/doc/using-ray-on-a-cluster.md +++ b/doc/using-ray-on-a-cluster.md @@ -132,7 +132,6 @@ source code to it, you can pass in the local path to the directory that contains your Python code. For example, `cluster.start_ray("~/example_ray_code")`. This will copy your source code to each node on the cluster, placing it in a directory on the PYTHONPATH. - The `cluster.start_ray` command will start the Ray scheduler, object stores, and workers, and before finishing it will print instructions for connecting to the cluster via ssh. @@ -161,9 +160,9 @@ to the cluster's head node (as described by the output of the - `cluster.install_ray()` - This pulls the Ray source code on each node, builds all of the third party libraries, and builds the project itself. - - `cluster.start_ray(user_source_directory, num_workers_per_node=10)` - This - starts a scheduler process on the head node, and it starts an object store - and some workers on each node. + - `cluster.start_ray(user_source_directory=None, num_workers_per_node=10)` - + This starts a scheduler process on the head node, and it starts an object + store and some workers on each node. - `cluster.stop_ray()` - This shuts down the cluster (killing all of the processes). - `cluster.update_ray()` - This pulls the latest Ray source code and builds