LAE

Welcome to the LAE community!  Please feel free to start a discussion in the discussion tab or join in a conversation.

Discussions

Members

Resources

Events

 View Only
  • 1.  using parameters to store values to be used later

    Employee
    Posted 10-06-2014 07:25

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: dhrobertson

    hi all,

    I want to be able to use a number calculated earlier in a graph in order to work out some percentage numbers.
    there is the ability in Lavastorm to use parameters. I'm wondering whether it s possible to work out a number in an AggEx node and assign that number to a global parameter, which I can then call later from a separate node in order to do further calculations?

    if this is possible and you let me know what type of parameter I should set up and how any statement in a filter node or otherwise would look in order to use the parameter?

    thanks

    regards

    douglas


  • 2.  RE: using parameters to store values to be used later

    Employee
    Posted 10-07-2014 07:00

    Note: This was originally posted by an inactive account. Content was preserved by moving under an admin account.

    Originally posted by: ejones

    So what I am understanding is that you'd like to have a way to pass a single value from one node to another where it will be used. I've been in situations where I've wanted this before too.

    What I've had to do is add the value to the data where it will be used. And yes, this may mean the data gets repeated on every record in the data stream. I often try to very strictly follow the pattern where all the data retrieval happens on the left side of the graph, to the point where I have a data stream that starts on the left with one record including the RunDate and some other values that can be used in various places throughout the graph and at the end of the graph when renaming output files to include the date.

    There have also been times when I had a value produced by one node, but didn't really want to draw the connection from that node in that composite to a node in another composite where it would be used because it seemed that it would add too much clutter to the graph and make it harder to understand. I have considered writing the data to a BRD file that would exist only during the run of the graph and then have a later node read the BRD file and delete it. This would allow data to pass from one part of the graph to another without having to draw the line. But so far I have only done this in cases where it is impossible to actually carry the data in the data stream.