data structure as list without using param viewer

Replies to This Discussion

Permalink Reply by Luis Fraguada on February 21, 2011 at 3:37am

In that particular case, the data structure is not so difficult and could be generated with list length + series +  a few panels with '{' and '}' + a bit of string concatenation...

Permalink Reply by Aron Fidjeland on February 21, 2011 at 3:42am

Thru, but i have a lot of more complicated structures that i use in the same definition. The drawing is so slow that the computer freezes up for about 10 seconds every time you pan over the param component. Really annoying. 

 

I would guess that you could get the data out of the path mapper in some way, but i can't figure out how.

Permalink Reply by Andrew Heumann on February 21, 2011 at 4:21am

david has previously mentioned that the param viewer is based on a pretty inefficient draw algorithm - it gets really slow with long lists of paths. You'll find that if you cluster a lone param viewer you can plug its output data into a panel and see nearly the same thing, without the slowness. (you may need to insert intermediate "data" parameters between the viewer and the input/output arrows to get the cluster to function right).

Permalink Reply by taz on February 21, 2011 at 3:11pm

Excellent performance tip!

Permalink Reply by Aron Fidjeland on February 21, 2011 at 5:03am

Works Perfect! Thanks a lot!

 

posting image for furure reference.

 

/aron

Attachments:

• slow param viewer workaround.JPG, 80 KB

Permalink Reply by Luis Fraguada on February 22, 2011 at 9:19am

By the way, using a script node also should do the trick rather quickly.  Input your tree into the 'x' input (or rename this input to whatever you want) making sure you specify 'tree access.'  Then enter the code below:

 

A = x.Paths

 

x is the name of the input you connected the tree into...by default, it is named x.

Permalink Reply by Robert Beach on April 6, 2011 at 7:31pm

I've been borderline homicidal about 3 times with long lists fed to the param viewer while my screen stuttered as if I were on a 486 with 4mb of RAM playing "Full Throttle".  I must've got smarter since last I worked on this here stuff to think to check the boards this time! Thanks again for figuring it out for me :)_