psexec
, see e.g. this link for details on psexec setup.# contains the scripts from the cluster-scripts repository
path/to/base
# contains the scenery git repository and JARs
path/to/base/scenery
cluster-scripts
repository need to be adjusted for your local setup, in particular the username and password for the rendering node accounts need to be changed, as well as their names, and the name of the network share used. Go through the scripts carefully, they contain comments in places that need to be changed and are very short.pom.xml
file from the scenery repository needs to be imported into IntelliJ on the control node. Open IntelliJ, select the file via File > Open
, and follow the instructions.match
block. Here, Property
means the appropriate screen is determined using the JVM system property scenery.ScreenName
. This property gets set by the run-cluster.bat
and run-test.bat
scripts. An arbitrary numbers of screens is possible, but the YAML file and run-cluster.bat
script need to be adjusted accordingly.DemoReelExample
. This example can be found in the project in the src/test/tests/graphics/scenery/examples/cluster
directory. In the example, make sure that the IP given for TrackedStereoGlasses
matches that of your tracking system, and the YAML file given matches the name of your screen configuration. Then, click the Run
button to run this locally and verify all data is found.Run > Edit Configurations...
to adjust the parameters of this test for it in order to run on all nodes. The VM options of DemoReelExample should look like the following:run-cluster.bat
script needs to be run to launch scenery instances on the projection nodes. The External Tool setup for that script should look like the following image:Shift
1
Shift
2
Shift
3
I
, K
J
,L
killall-java.bat
script.