# contains the scripts from the cluster-scripts repository path/to/base # contains the scenery git repository and JARs path/to/base/scenery
cluster-scriptsrepository 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.xmlfile 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.
Propertymeans the appropriate screen is determined using the JVM system property
scenery.ScreenName. This property gets set by the
run-test.batscripts. An arbitrary numbers of screens is possible, but the YAML file and
run-cluster.batscript need to be adjusted accordingly.
DemoReelExample. This example can be found in the project in the
src/test/tests/graphics/scenery/examples/clusterdirectory. In the example, make sure that the IP given for
TrackedStereoGlassesmatches that of your tracking system, and the YAML file given matches the name of your screen configuration. Then, click the
Runbutton 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.batscript 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: