Skip to content

Commit 02c3960

Browse files
committed
update README
1 parent 011b7d4 commit 02c3960

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

README.md

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -88,7 +88,9 @@ This is an example of generating 50000 trajectories of 2 balls over 60 timesteps
8888
> node demo/js/generate.js -e walls -n 2 -t 60 -s 50000 -w U
8989
```
9090

91-
It takes quite a bit of time to generate 50000 trajectories, so 200 trajectories is enough for debugging purposes.
91+
It takes quite a bit of time to generate 50000 trajectories, so 200
92+
trajectories is enough for debugging purposes. In that case you may want to
93+
change the flags accordingly in the examples below.
9294

9395
### Visualization
9496
Trajectory data is stored in a `.json` file. You can visualize the trajectory by opening `src/js/demo/render.html` in your browser and passing in the `.json` file.
@@ -114,9 +116,8 @@ Here is an example of training on "O" and "I" wall geometries and testing on "U"
114116
```
115117

116118
Be sure to look at the command line flags in `main.lua` for more details. You
117-
may want to change the number of training iterations if you are just debugging,
118-
for example (In that case you may want to change the dataset name in the examples above). The code defaults to cpu, but you can switch to gpu with the
119-
`-cuda` flag.
119+
may want to change the number of training iterations if you are just debugging
120+
. The code defaults to cpu, but you can switch to gpu with the `-cuda` flag.
120121

121122
### Prediction
122123
This is an example of running simulations using trained model that was saved in `src/lua/logs/balls_n4_t60_ex50000_m__balls_n4_t60_ex50000_m_layers5_nbrhd_rs_fast_lr0.0003_modelnpe_seed0`.

0 commit comments

Comments
 (0)