Results 1 to 4 of 4

Thread: BRD data missing from automated graph

  1. #1
    Contributor
    Join Date
    Jun 2017
    Location
    Melbourne, Australia
    Posts
    19

    Default BRD data missing from automated graph

    I have a number of graphs scheduled and are running fine. I have come to load in the latest BRS file to look at the progress and counts, from the last run, and I have found that I am not able to view all the data that has been output.

    For example, I have an X-Ref node in the graph and when I have imported the BRS file I can see the data and record count for output 2 (matches) and output 3 (right orphans), but for output 1 (left orphans) I can only see count displayed. I have attached a screenshot to show what I mean.
    X-Ref_Node_Example.PNG.

    Why am I not able to see all the sets of data?

    Carl

  2. #2
    Lavastorm Employee gmullin's Avatar
    Join Date
    May 2014
    Location
    Chicago
    Posts
    146

    Default

    When a graph runs as scheduled, by default it will use streaming. This means it will wipe out temp files when its done with them. If you want to turn it off and have all temp files saved you can update the parameter:

    ls.brain.controller.scheduler = "default"
    # "debug", "non-streaming", "streaming", "default"

    "non-streaming" would mean it will save all your temp files. It will mean that your jobs will take up a lot more space in their temp dir. There's a detailed explanation of it in the link below. BRX or run through Logistics Manager, has the same effect in this case.

    http://community.lavastorm.com/threa...ecute-BRX-Node

  3. #3
    Lavastorm Employee stonysmith's Avatar
    Join Date
    Nov 2006
    Location
    Grapevine Tx
    Posts
    771

    Default

    Note that the top output pin is white, while the other two are green.
    This quickly tells you which nodes were streamed, and which were not.

    If a node has been executed, the white on the output or input pin is telling you that the data was streamed into or from the connected node, and there was no (disk) temp file created for that data path.

  4. #4
    Contributor
    Join Date
    Jun 2017
    Location
    Melbourne, Australia
    Posts
    19

    Default

    Thanks for the information. We will make the changes and retest this.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •