Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Why doesn Analyzer see my average data nodes when I try to use the GrandAverage transform?

0
Posted

Why doesn Analyzer see my average data nodes when I try to use the GrandAverage transform?

0

One potential reason for this behavior could be the following: In building your Grand Averages you specify files and node(s) for each of these files. Analyzer then goes and looks through the files for the first (!) occurrence of the node(s) you specified. Now, you will have seen that Analyzer tries to be intelligent (~) about naming history nodes with conflicting names. Creating a second average with different or the same parameters based on the exact same data would lead to two nodes called “Average”, so Analyzer goes and names the second one “Average 2”, etc. However, if the averages are computed in different branches of your history file, Analyzer sees no problem in these Averages all having the name “Average” and does not change any names. This in turn can easily lead to a situation where you are expecting Analyzer to find a certain node called “Average” for instance in the third branch, but there also is one such node in the first branch. This node in the first branch is the one t

Related Questions

What is your question?

*Sadly, we had to bring back ads too. Hopefully more targeted.

Experts123