You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
92
94
93
95
### Visualization
94
96
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"
114
116
```
115
117
116
118
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.
120
121
121
122
### Prediction
122
123
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