this is just a visualization at (well in this case) t=0.
so we know initial-conditions and shapes/objects info at t=0. we can
visualize it.

for animation we would certainly require json generated from this
output + numerical-vals from odeint.
although if we want to implement the visualization at any specific
time other than initial(t=0), then it would certainly require
numerical-vals.
but on the other hand, in future we will allow user to fast fwd
animations to specific time, so it might be deprecated.

On 6/24/13, Jason Moore <notifications@github.com> wrote:
>> +numerical_vals = odeint(right_hand_side, init_conditions, t)
>> +
>> +#Now for each t, we have numerical vals of coordinates ..
>> +#Now we set up a visualization frame,
>> +
>> +frame1 = VisualizationFrame('frame1',I , O)
>> +
>> +frame1.add_rigidbodies(links)
>> +
>> +frame1.add_particles(particles)
>> +
>> +param_vals_for_viz = {'g':9.8, 'l1':1.0, 'l2':1.0, \
>> +                      'l3':1.0, 'm1':2, 'm2':2, 'm3':2, \
>> +                      'M1':5, 'M1':5, 'M1':5]
>> +
>> +json = frame1.generate_json(initial_conditions, q)
>
> Shouldn't this take the results from odeint + some output equations
> numerical results and then generate a json file? It doesn't seem like the
> correct info will be available here.
>
> ---
> Reply to this email directly or view it on GitHub:
> https://github.com/PythonDynamics/pydy_examples/pull/11/files#r4846400
>