benjamin-heasly
commented
11 years ago On Rhino, I made a script that runs a large "epic" test of example recipes. The script invokes the Rhino head node to generate renderer-native scene files. Then it invokes Rhino worker nodes to produce renderings. The script is
/home2/brainard/render-toolbox-3/epic-scene-test/epic-scene-test.shIt puts outtput files at
/home2/brainard/render-toolbox-3/epic-scene-test/temp
/home2/brainard/render-toolbox-3/epic-scene-test/data
/home2/brainard/render-toolbox-3/epic-scene-test/imagesI also made a script that replaces reference data in the GitHub RenderToolbox3-ReferenceData repository, with the epic-scene-test ouputs. It also tag the results for a RenderToolbox3 version. The script is
/home2/brainard/render-toolbox-3/epic-scene-test/replace-gitub-reference-data.sh
Here is a laundry list of stuff to do for launching version 1.0:
Some of these things are kind of a pain. I want to write utility scripts to make them easier in the future.
A script on Rhino should take care of the epic scene test on Rhino. It should be able to invoke the scene file creation on the Rhino head note, then invoke "parmgo" to do rendering on Rhino worker nodes.
Another script on Rhino should hose the existing repository at RenderToolbox3-ReferenceData and upload the new renderings there.
These scripts should just be on Rhino, since Rhino is not a public resource.
A script on iMac should produce a RenderToolbox3 "release". It should commit a tag for the RenderToolbox3 master branch. It should regenerate the doxygen documentation, then commit a tag for RenderToolbox gh-pages branch. It should commit a tag for the RenderToolbox3 wiki. It should commit a tag for the RenderToolbox3 reference data.
This script could live in the RenderToolbox3 repository. Any contributor with permissions at the GitHub repositories would be able to make a RenderToolbox3 release. This script would also document the release process.