Data Saver automatisation

Dear all, most likly David since this ins totaly undocumented in SDK

I am trying to add some custom data saver automatisation. and using the following line to "copy" data from datasaver to a number param.

dataStore.AddVolatileDataTree(dataSaver.VolatileData);

this seams to work fine. However when I save the file and reopen then the data is gone...

Any suggestions why?

Replies to This Discussion

Permalink Reply by David Rutten on July 27, 2016 at 8:13am

VolatileData is erased whenever an object expires. It's where the current solution is kept. If you want to store data permanently, then you need to assign the PersistentData.

Permalink Reply by Richard Schaffranek on July 27, 2016 at 10:24am

And how would that work?

I only get the reply that presistentData is read only...

Permalink Reply by Richard Schaffranek on July 27, 2016 at 11:29am

Hallo David,

I managed but please could you explain the following:

loop1 i=0 ...

dataStore.PersistentData.EnsurePath(i);

loop2 ii=0

adding data to List

end2

dataStore.PersistentData.AppendRange(tmp);

end1

this stores outputs a datatree?

Permalink Reply by David Rutten on July 27, 2016 at 12:34pm

PersistentData is a GH_Structure<T> where T is the type of the parameter. You should be able to cast the returned PersistentData to the correct GH_Structure<T> and then use MergeStructure to insert all your data in one go.

Permalink Reply by Andrew Heumann on July 27, 2016 at 8:33am

also, be careful with too much persistent data. it makes GH file sizes large which actually can be a HUGE pain because it slows down autosave, which happens every time you connect a wire or place a component. When it takes 2 seconds to "think" every time you do something, GH definitions become unusable and in some cases can even cause crashes on file open. As long as the data sets are small though this shouldn't be a problem.

Permalink Reply by Richard Schaffranek on July 27, 2016 at 10:52am

Hallo Andrew,

thx for the hint, however it seams to be the best working solution to record and store Simualted annealing runs and to reuse them within Grasshopper in an easy way. I am filtering upfront so...

we are not talking about millions of numbers...

RSS