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

Draw FTA diagram using javascript

medini_1065646292

Hello! I already have a .js script that:

- creates the FTA model

- generates events, gates and connection in the model browser (under the FTA model previously created).

To draw the fault tree I use a 'workaround': I select the FTA model in the model browser, then click expand all button, select all events, gates etc, drag and drop into diagram window. Just wondering if the drawing can be done with .js scripting?

Many thanks

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1023909254

Hi Francesco,

at least some manual steps could be simplified in the manual approach:

Just drag&drop the top-level event onto the diagram and then select Restore Sub-Tree:

So no need to unfold in the model-browser. Also in case you have events which are only target of transfer gates and not connected in another way to the FTA you could apply the same way (even have separate diagrams for them in the same FTA model).

Eckhardt

All comments

medini_1023909254

Hi Francesco,

at least some manual steps could be simplified in the manual approach:

Just drag&drop the top-level event onto the diagram and then select Restore Sub-Tree:

Eckhardt

medini_1024169437

And to add: there is currently no API to "draw a diagram" or to put elements on a diagram, there were multipel requests already (for FTA and SysML) but we don't have it yet.

Jan

medini_1065646292

Thanks Eckhard, definitely a good tip!

Thanks Jan, good to know!

medini_1024169437

Francesco, please check this new article: https://medini.freshdesk.com/support/discussions/topics/1000112375

Jan

medini_1040753747

Is there a way to set "Model" and "Use Rate From" option for event nodes with represented failure modes in the FTA using javascript?

medini_1023909254

Hi Johan,

these properties are available at Metamodel.FTA.Event associated with the EventNode. "Use rate from " is derived from represents and Model goes into probabilityData (you can create the appropriate model using the factory).

Eckhardt

medini_1024169437

Johan, I quickly checked the factory.js and it seems it lacks support for Metamodel.FTA.RiskTimeProbabilityModel so in case you want to create that, it may not work. You can extend the factory.js yourself though, search for Metamodel.FTA.RiskTimeProbabilityModel and extend it until we have done so.

Happy Scripting

Jan

medini_1024169437

Hi Johan, I unfortunately forgot about this thread. I had patched the factory.js already a while ago but forgot to post an update here. Find now attached a version of factory.js that supports RiskTimeModel, see the test script how to create it.

Happy Scripting

Jan

medini_1063548292

Hi,

I have also found missing Pmodel in factory and as you i updated the factory.js with two last mossing models,m namely

TrueFalse and LogNormal

 if (type == Metamodel.FTA.LogNormalProbabilityModel) {
	 return __createCustomProbabilityModel(scope, type);
	 }
 if (type == Metamodel.FTA.TrueFalseProbabilityModel) {
	 return __createCustomProbabilityModel(scope, type);
	 }

In my factory.js I have done a bit optimization using check of superType ... to collect all statements into one ..

// support all available Probability Models by checking for underling Interface ProbabilityModel
 // Abstract: TimeDependentProbabilityModel
 // Classes: TrueFalseProbabilityModel,TimeIndependentProbabilityModel
 //ScriptedProbabilityModel,ExponentialProbabilityModel,WeibullProbabilityModel
 //LogNormalProbabilityModel,NormalProbabilityModel,RiskTimeProbabilityModel
 try {
 if (type.eAllSuperTypes.contains(Metamodel.FTA.ProbabilityModel) && !type.abstract && !type.interface){
 return __createCustomProbabilityModel(scope, type);
 }
 } catch (e) {
 // type not compatible with expected argument (EClass) 
 console.error("Factory: Warning type Argument not compatible with Metamodel EClass {0}, continuing ...]\n Catch message: {1}",type,e);
 }

I moved this section to the very end of the createElement block as they are cases with type argument being string ( "FRVariable" but i believe that one is only valid for 2019 medini as the current Metamodel contains the FRVariable ..

 // Reliability (HACK! not in Metamodel yet with R19.0)
 if (type == "FRVariable") {
 return __createFRVariable(scope);
 }
	if (this.isV2000OrLater) {
	 if (type == Metamodel.failureratecatalogs.FailureRateData) {
	 return __createFailureRateData(scope);
	 }
 // Reliability (No hack needed since Metamodel has it with R20x)
 if (type == Metamodel.failureratecatalogs.FRVariable) {
 return __createFRVariable(scope);
 }
	}

Note: I have also added support for Component FTA stuff.. Interfaces, CFTDiagram . is someone is interested

Marian.

medini_1024169437

Nice Marian,

I will incorporate your modifications into the factory.js on my side. The idea with super class is nice, but as you recognized, it breaks passing a type as string. One way could be to extend the if statement by:

// before
if (type.eAllSuperTypes.contains(Metamodel.FTA.ProbabilityModel)

// improved and safe
if (("eAllSuperTypes" in type) && type.eAllSuperTypes.contains(Metamodel.FTA.ProbabilityModel)

Thanks again

Jan

PS: Your last comments reads as if you had planned to attach the factory.js but there is none :-)

medini_1063548292

Hi Jan,

You are right as always!

Here is attached factory .
I started form your version posted in this thread.

You can use diff to check the modifications . You will find some things for CFTA and also update for __createDiagram.

Fell free to check and improve

Marian.

medini_1024169437

Perfect, will do that, thanks Marian for your contribution and your activities in this forum, highly appreciated.

Happy Scripting

Jan

medini_1063548292

Hi Jan,

Happy to help !

I forgot to add one tiny thing being a SysMLTable.

This article https://medini.freshdesk.com/support/discussions/topics/1000116591triggered my memory so I made an additional update.

Marian

medini_1024169437

SysMLTablke was also on my agenda so I already added support for that in 24.2, it wasn't even in the Metamodel singleton.

I will merge the additions as well.

Jan

medini_1024169437

Marian, what I do not fully understand are your changes to __createDiagram, creating nested diagram was possible before as well, why did you change the behavior, any more details?

Jan

medini_1024169437

.... anyway, here is an *intermediate* version of a merge of (1) the latest from us, (2) changes done by Nils and (3) changes done by you. Pending: changes to __createDiagram waiting for your comments and changes to creation of FMEA worksheets (done by Nils, also waiting for some explanation).

I anyway post an intermediate version here to let you see my small corrections and modifications I had to do to get it through the tests (using latets Test Factory.js). Please check on your side and comment if necessary.

If you have sample code to create the new elements you have added, please post them here too.

Thanks

+Jan