Data structures parsing wierdly through Firefly components

Not quite sure how to explain this.. (so apologies for the verbosity)
but certain components seem unable to parse data trees (or lists), specifically:

Smoothing Temporal
Smoothing Moving Average
Data Log

I've been aware of it in the Smoothing components for a while now, in that if I have a list or a grafted tree of numbers, the component will try to smooth all numbers as if they were part of a single data stream, rather than as multiple data streams (even across tree branches)

With Data Log, I recently tried to input a tree with 2 branches of 3 items each (as well as trying to graft it for 2 branches of 3 branches of 1 item each), whereby the logged data structure superficially resembles the expected outcome, but with the values jumbled all over the place from different branches.

Is this a known bug?
Are there plans to fix this?
Or is this unique to my set-up somehow?

Thanks

Replies to This Discussion

Permalink Reply by Andy Payne on March 4, 2016 at 1:44pm

Hi. Yes, this is partly by design. These components are setup specifically to work with a single incoming value (not lists or trees). This is partly because of the Code Generator which will convert those functions into Arduino compatible code. It's not impossible to have it work on lists, but its more complicated. And data trees are a completely separate beast all together. I'd prefer to leave these as they are even though it's more cumbersome in some workflows.

Regarding the Data Log... You may look into the built in Data Recorder component. I wrote the Data Log component before this was available, but David has improved on it quite a bit. The Data Recorder will accept any type of input (where as the Data Log component only works on numbers) and (I believe) the Data Log will work on all list structures.

Permalink Reply by Vongsawat Wongkijjalerd on March 6, 2016 at 9:21pm

Huh, it seems I've underestimated the Data Recorder component :)

Guess I'll have to grok something up for the smoothing components, a shame as your smoothing components are so useful otherwise

Thanks for the interesting information anyways Andy :)

RSS