The final assignment is upon us. It must be awesome.
Here's the idea. Use the two Kuka Agilus cells to create animated 3D light objects. One robot will hold a phone or iPad, playing an animation and moving it at a fixed rate to produce a frame of the animation. The other robot will hold the camera, and gradually move for every frame.
Inspiration:
and with a panning camera...
Movie shot: Missy - Director, Dan - Photographer, Yun - Leading Actress, Yi - Leading Utility Man
Movie shot: Missy - Director, Dan - Photographer, Yun - Leading Actress, Yi - Leading Utility Man
Ready, GO RoboDance!
Testing some long exposure shots stitched together as a movie.
Trying different paths and orientations of the screen relative to the camera.
sMT
The new sMT is rather buggy and crashes often. But after hours and hours of blood and sweat and frowns and tears and... you get the idea, our roboteam is programmed and simulated!
As described above, Mitey is the panning dolly for the camera, whereas Titey holds our mobile device that will spell ROBODANCE.
The biggest difficulty about the new sMT is that it gives inconsistent results and any click is prone to a crash. Some major crash triggers for us were
1. Selecting motion paths
(after selecting fixed paths)
(after selecting order of reference paths)
2. Choosing robot sync options
We should like to share with you some cures that helped us, of course, in no particular order.
P.S. Random thought: could sMT actually stand for super Mitey Titey?
sMT
The new sMT is rather buggy and crashes often. But after hours and hours of blood and sweat and frowns and tears and... you get the idea, our roboteam is programmed and simulated!
As described above, Mitey is the panning dolly for the camera, whereas Titey holds our mobile device that will spell ROBODANCE.
The biggest difficulty about the new sMT is that it gives inconsistent results and any click is prone to a crash. Some major crash triggers for us were
1. Selecting motion paths
2. Choosing robot sync options
We should like to share with you some cures that helped us, of course, in no particular order.
1. Running script by selecting "reset engine and debug" under green play button
2. Copying the Rhino file into another folder then run it anew
3. Copying the geometry into a new Rhino file and run it anew
4. On robot sync, we chose "Sync Motion," which could result in the alien abduction of one or more robot geometries, and further efforts to simulate is likely to crash the program. However, the same settings may stick when running the script again, without errors
5. Wait for it, let it take its time
P.S. Random thought: could sMT actually stand for super Mitey Titey?
No comments:
Post a Comment