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

How to programatically access safety mechanisms of sysml elements

medini_1063646795

Hello,

While generating FTA models we had an idea that we think
would be super helpful. We would like to be able to access the safety
mechanisms that are attached to a SysML model element (single point and latent)
in order to be able to create the FTA events for them in the model as well and
connect them with the appropriate malfunctions and gates. So the question I
have is how to access them through JS. I’m assuming it would be something like
element.safetMechanism.latent or element.safetMechanism.singlePoint, but I would like to know what the exact command is to be able to access those safety mechanisms that are attached to a sysml malfunction

Thanks,

Tom

Find more posts tagged with

medini

medini legacy

Accepted answers

All comments

medini_1024169437

Hi Tom,

safety mechanisms are attached to failures in medini. Assuming you have this example of an assignment:

There are several ways to access,either via derived property allSafetyMechanisms or via spfSafetyMechanisms resp. mpfSafetyMechanisms

Hope that helps.

Jan

medini_1023909254

Hi Thomas,

an in addition to Jan's reply: In case you are just interested in the SM which are associated to the failuree modes of a component (idependent whther they are SPF-SM or LF-SM), then you can also use the property allSafetyMechanims of the component/SysMLPart (which aggregates all SM of the failure mdoes of the component):

Eckhardt

medini_1028367136

Team, I need a little help here.

If I have a variable "foo" that is equal to some sysml element in some model:

* I can use "foo.the_owned_elements" to obtain the set of objects that are children of "foo".

If I have a variable "foo" that is equal to some failure in some port in some sysml element in some model:

* I can use "foo.causedBy" to obtain the set of objects that are causes of "foo".

* I cannot get "foo.allSafetyMechanisms" to work like "causedBy" works, what am I doing wrong?

* * Note: This question also applies to "spfSafetyMechanisms" and "mpfSafetyMechanisms".

Thanks in advance for your help.

medini_1023909254

Hi Roy,

can you be a little more clear on what you mean with:

I cannot get "foo.allSafetyMechanisms" to work like "causedBy" works, what am I doing wrong?

The result of this should actually give you a (potentially empty) array of Safety Mechanisms

Eckhardt

medini_1028367136

I expected "foo.allSafetyMechanisms" to return an array of Safety Mechanisms but could not get it to work.

I only mentioned "causedBy" because it works ok and I'm able to access it.

medini_1024169437

Hi Roy,

maybe you can sue this snippet to test it against (a) a selected failure mode and (b) selected sysml element:

alert(selection[0].allSafetyMechanisms.size());

It works on my end. Note that the returned value is a list, not an array. To make it an array use

alert(selection[0].allSafetyMechanisms.size());

Jan

medini_1023909254

and the conversion of the list to an array would be done with:

selection[0].toArray()

That's probably what Jan wanted to write.

Eckhardt

medini_1040753747

What is the syntax to assign (spf) safety mechanisms to failure modes?

It seems this topic is unanswered: https://medini.freshdesk.com/support/discussions/topics/1000101440

medini_1024169437

Thanks Johan, for reminding us on that article, it somehow slipped completely.

Anyway, the syntax should be like this (following the style above):

selection[0].allSafetyMechanisms.add(xxx)

So, to remember: allSafetyMechnisms is a 0..* reference and its represented by a list so you can use size(), add() and remove() and that kind of operations.

Happy Scripting

Jan

medini_1040753747

So I get this "Failed to execute Java Script: Wrapped java.lang.UnsupportedOperationException" error message when trying to "add" a Safety Mechanism object to the allSafetyMechanisms list.

var failure_sm_list = req_failure.allSafetyMechanisms;
//failure_sm_list.add(new_safety_mechanism);
failure_sm_list.add(failure_sm_list.get(0));

I tried to add a safety mechanism that is not in the list and then tried to add one that is already in the list; got the same error both ways. I also printed the list and object trying I'm trying to add and it seems to be the same type.

Does this work on your end? Not sure what I am doing wrong...

medini_1023909254

Hi Johan,

I suppose you are referring to allSafetyMechanism property of safetyModel::FailureMode - is that correct? As this is a generated list, you will not be able to write to it (you can only read it). The list contains always all SPF and all LF Safety Mechanisms which are associated to the failure mode. If you want to add further safety mechanisms, you need to add them to spfSafetyMechanisms or to mpfSafetyMechanisms.

Note, allSafetyMechanism would contain a safety mechnisms at most once - even if it is used as SP and LF mechanism (so there is some kind of Set-semantics behind it)

Eckhardt

medini_1040753747

What does failure.allSafetyMechanisms.toArray() return? It does not seem to be an array of SafetyMechanism objects...

medini_1023909254

Hi Johan,

this should be a Java Array-Object. So you can check for it's size and access/read the elements in the array (or make a copy into a Javascript-Array).

Please note failure.allSafetyMechanisms is a derived property (i.e. result of a function in Java) - so you can not modify it.

Anyway, can you please clarify what exactly you want to do reps. where you have a problem?

Eckhardt

medini_1040753747

"access/read the elements in the array" - what type are the elements? I was expecting them to be SafetyMechanisms...

medini_1023909254

yes - they are SafetyMechanisms - you can even check it this with

alert(selection[0].allSafetyMechanisms.toArray()[0] instanceof Metamodel.safetyModel.SafetyMechanism);

... just select a failure mode and run this code snippet.

Eckhardt

PS: In general of course you should check the size before accessing it with an index.