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; } } }

When to use mediniGetTracedElements or mediniGetOpposites? And how?

medini_1035261689

Hi all,

I'm playing around with the Methods mediniGetTracedElements and mediniGetOpposites and I try to find when and how these methods can be used.

My setup contains a Safety Goal "sg" and a derived FTA with TLE "tle" for "sg". Within the Properties View I can see for both elements in the "Trace" property for sg.

Within a javascript both following calls sg.mediniGetTracedElements(Metamodel.FTA..Event) and tle.mediniGetTracedElements(Metamodel.FTA..Event) are delivering the trace.

What is not clear to me is what the method mediniGetOpposites is really delivering and how the correct use would be?

sg.mediniGetOpposites(xxx) is delivering DCWorksheetImpls.

tle.mediniGetOpposites(xxx) is delivering EventNodes.

What should I use for xxx? How do I know what I can expect as a return result? What is the relationship to Properties and "What is this? Attributes".

Best regards,

Michael

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Hi Michael,

the general rule is: use mediniGetTracedElements if you want to navigate "trace" relationships, so anything that is shown in the "Trace" tab as you wrote.

Traces cannot be navigated otherwise, so you cannot access a trace using a reference or attribute of an object.

Use mediniGetOpposites if you want to to navigate a "uni-directional" reference reverse. So assuming A references B (unidirectional) but

you want to navigate from B to A, use mediniGetOpposites.

Hope that clarifies the question.

Happy Scripting

Jan

medini_1035261689

Hi Jan,

Thanks for the quick answer. This clarifies a lot. But I'm struggeling with the Parameter for mediniGetOpposites. It seems that the parameter is not using the Metamodel types. It seems it uses some strings, e.g. 'ISO26262_safetyGoal'. Is there a list available with the available parameters?

I have another issue, where neither traces nor opposites seem to help:

In "System Design" I have defined a Failure Mode. For this Failure Mode I have derived a FTA Event and DC Worksheet Entry. With a "Right Click" on the element and the "Related Element" I able to find the relation between these elements. But in "Attribues" or "Properties" I don't find these Information and also with scripting I can find anything.

Could you please describe how to Access the "Related Element" function by Scripting?

Thanks a lot in advance,

Michael

medini_1035261689

Hi Jan,

I just had a discussion with Peter Ploss and our understanding for mediniGetOpposites is this:

x.mediniGetOpposites("reference") provides all objects, which "point" to x with a member named "reference".

"reference" could something like: "represents", "element" or other members. This list then can be filtered with types from the Metamodel.

Is this understanding correct?

Thanks and regards,

Michael

medini_1024169437

Hi Michael,

about the first question: many of the "Related Elements" menus in fact work more or less the same way as ".mediniGetOpposites" so they navigate uni-directional references backwards.

You cannot see those references (or these "Related Elements" links in the attributes view.

> x.mediniGetOpposites("reference") provides all objects, which "point" to x with a member named "reference".

>"reference" could something like: "represents", "element" or other members. This list then can be filtered with types from the Metamodel.

>Is this understanding correct?

This is absolutely correct.

Jan

medini_1040753747

Can you elaborate on how to use ".mediniGetOpposites" to get the objects in "Related Elements"? For example, can I return the same list of "Input Nodes" using ".mediniGetOpposites"? What is the correct parameter to use? How do I correct this...

var input_nodes = logical_gate.mediniGetOpposites('input nodes');

Thx for your support with regards to this!

medini_1024169437

The "Related Elements" menu is mainly addressing relations and references that are (1) either not visible on user interface or (2) are indeed opposite references, and by that also not visible on user interface. One example is the reference from a hazardous event to a safety goal:

The HARa shows the reference from the HARA entry to the goal but not the opposite. The "Related Elements" menu instead shows *both* directions, one direction it simply follows the reference, for the opposite directions it uses "medinigetOpposites":

You simply pass the name of the unidirectional reference as argument, here its "ISO26262_safetyGoal" or "safetyGoal" (2020.1.1) and you will retrieve a list of *all* hazardous events for a given safety goal:

var goal = ...
var events = goal.mediniGetOpposites("ISO26262_safetyGoal");

Note that input nodes in FTA is not a good example because its a normal metamodel reference that you can traverse.

Happy Scripting

Jan

medini_1040753747

If I am using safety goals, I still do not know where to find the list of unidirectional references...

var reqs = goal.mediniGetOpposites("some_param");

What argument do I pass for "some_param" in order to get the requirements that are related to a safety goal?

medini_1024169437

Johan,

requirements do not reference safety goals directly, in the sense of "object reference". Instead they refer to a Relation object ("Contributes") which is technically an object of itself. That object is referenced from the requirement and references the safety goal.

So in your case you would have to start with "targetRelations", so some_param is "targetRelations".

That way you get all Relation objects and from there you can navigate to the requirement via "source":

Happy Scripting

Jan

medini_1040753747

When I use "ISO26262_safetyGoal" I get the Hazardous Events. But when I use "targetRelations" I get zero objects returned.

I ended up using getCrossReferencedElements() and filter on SafetyReqRelation; then use source to get the Requirement...

medini_1024169437

Weird, because "mediniGetOpposites" is basically also just using the cross referencer.

I can have a look why this is not working as supposed.

But glad you found a very good solution!

Jan