nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Heatmaps for Component Fault Trees

medini_1060292729

Hi,

I really like the Component Fault Tree Feature and want to use it for my project. After evaluating such a fault tree I wanted to follow the cut set using the heat map. This is unfortunately not possible yet, as I got to know.

Therefore the question if I can script it?

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Good question Henning,

I need to check myself, my gut feeling is, that should be feasible.

Stay tuned.

Jan

medini_1024169437

Henning,

seems CFT and RBD were excluded from heat map intentionally as it needs some more work of heatmap framework to get it work properly.

Scripting a heat provider in the heatmap tool, might be complex, I am not sure I can provide a starting point.

Jan

medini_1060292729

Hi Jan,

thanks for the reply!

Is it planned already to include this feature? I really like CFTs, but not having the heatmaps is making analysis of bigger FTAs a lot more difficult for me.

medini_1059007410

Hi Henning,

one possibility might be:

Run a script on the cut set, which
1. may have to ask for the tree to display the path in (not exactly sure - the actual calculation is done on a generated FTA, so either one finds the original FTA via script, or it has to ask for it),
2. then calculates the path through the FT with CFT usages (I have a script which does this in a normal FT, you could adapt it to also work with CFTs),
3. and stores heatmap information (color) in event / gate profile properties
Afterwards run a scripted heatmap, which picks up the profile property heatmap information and displays it accordingly

These two steps seem to be necessary, because the scripted heatmap couldn't ask for a context (neither cut set nor different FT), while a normal script can do.

Alternative to the scripted heatmap would be to directly change the color of the events/gates with the initial script - but that's then permanent (until a potential "clean" run) and might overwrite existing colors.

Would that be an approach for you?

Happy Scripting,

Nils

medini_1060292729

Hi Nils,

this sounds like a plan :-) Im not entirely sure if I'm not even prefering the second option as this immediately brings some ideas for reporting purposes :-)

Following question:

- The FT should be present as the cut set itself is run on a specific FT or am I missing something?

- Can you share the script which calculates the path?

- Could you describe how the coloring then is triggered? Would u directly adapt fill color of the elements? or can the coloring of the heatmap be accessed?

medini_1059007410

Every saved AnalysisModel carries its own set of events, which are independent of the events of the actually analyzed tree (to keep it saved, even if the original tree is modified afterwards). You can see that via "The element is contained via the 'analyzedEvents' feature." in the header of the Attributes view.

But I checked, the ".topEventNode" property in the AnalysisModel directly refers to the original top event node (as nodes and thus tree logic are not stored in the AnalysisModel).

My script is a bit messy (a lot of other stuff done directly in the traversal function) - currently not time for clean-up, but I'll send you the current file directly via SecureTransfer.

Coloring can be done via looking for the representing "shape". See this snippet, and check the Cybersecurity templates for the paintTreeShape function.

 event.nodes.toArray().forEach( function iterateNodes(eventNode) {
 eventNode.mediniGetOpposites("element").toArray().forEach( function iterateOpposites(shape) {
 if (shape instanceof Metamodel.notation.Shape) {
 var lineColor = eopColor(EoP_hidden, "integer");
 paintTreeShape(shape, lineColor, enable_heatmap, use_line_color);
 }
 });
 });

medini_1024169437

Nice idea Nils,

just to add the idea that instead of writing to a own custom property you can use the general purpose tags to add information to elements.

There is special tag support for scripting, for example in the FInder API as well.

Regards

Jan

medini_1052680584

Hi Jan,

I also use often custom properties, but find it too cumbersome.

Can you please expand on how the tagging would be helpful here or point out to a link?

I assume it would need some kind of parsing to get all information put in the tag.

Thanks!

Regards, Andre

medini_1024169437

I just tought very simple, for example that you could write a pretty generic heatmap script which checks for tags like "heat-10", "heat-20", "heat-30" or maybe "cold", "warm", "hot":

Script:

if (self.mediniTags.contains('cold')) {
 10;
} else if (self.mediniTags.contains('warm')) {
 50;
} else if (self.mediniTags.contains('hot')) {
 90;
} else {
 -1;
}

then the batch script could assign those tags to the elements:

element.medinitags.add('cold');

Regards

Jan