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

Update DC sheet by function call

medini_1035403171

Hi everyone,

When you add elements to your system design (using factory.js), it seems that they do not simultaneously appear in the allotted DC sheet so that you can edit that one as well. The DC sheet is only updated after the script finished. Now I wondered if there is any possibility to update the DC sheet while the script is running so that I can edit the according entries afterwards.

I know that I could split up the script and run one part, let the DC sheet update and run the second part but I would like to omit that because I create quite a large data structure in the first part of the script which I need for the DC sheet and don't want to lose that information (or have to collect it again).

So, is there any solution or advice from your side?

Thank you,

Johannes

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hi Johannes,

well, I started to play a bit and the first attempt seems to work.Attached you will find a new library called "fmea.js". Please copy the file and the code as you like. Here is a sample how to use it, it works for FMEA but also DC worksheets:

// $EXPERIMENTAL$ $STRICT_MODE$ $WARNING_AS_ERROR$
/* 
 * Copyright (c) 2019 ANSYS medini Technologies AG
 * All rights reserved.
 */
var FMEATool = load(".lib/fmea.js");

// main script to test hara.js library
function main() {
	var fmea = finder.findByType(Metamodel.FMEA.FMEAWorksheet).first();
	var dc = finder.findByType(Metamodel.dc.DCWorksheet).first();

	FMEATool.synchronizeWorksheet(fmea);
	FMEATool.synchronizeWorksheet(dc);
}

main();

Note that this is highly unstable and just a first shot! I am not fully sure about all consequences yet,

Regards Jan

All comments

medini_1024169437

Hi Johannes, just to get it right: your script relies on entries in the DC sheet, that are only created by the DC worksheet sync, is that correct? So its not about the user, its about the script?

I remember that we have a solution to trigger the worksheet sync by script. I will check.

Jan

medini_1035403171

Hi Jan,

I import data from excel, create the system design and want to edit the DC worksheet and add values from the excel file. To do so, the DC worksheet needs to be updated during runtime of the script as you correctly mentioned.

Therefore, such a script to trigger the sync would be very helpful!

Cheers,

Johannes

medini_1024169437

Ok, I got the point. I think from a general perspective its feasible and I will try to come up with a solution.

Regards

Jan

medini_1035403171

Hi Jan,

I hope you had nice Easter holidays and some time off:-)

I just wanted to ask for the status of the DC sheet update functionality. Is there already any update?

Thanks for your support,

Johannes

medini_1024169437

Not yet Johannes, searching Easter eggs took all my time :-)

But I am confident to have something within the next days.

Jan

medini_1024169437

Hi Johannes,

// $EXPERIMENTAL$ $STRICT_MODE$ $WARNING_AS_ERROR$
/* 
 * Copyright (c) 2019 ANSYS medini Technologies AG
 * All rights reserved.
 */
var FMEATool = load(".lib/fmea.js");

// main script to test hara.js library
function main() {
	var fmea = finder.findByType(Metamodel.FMEA.FMEAWorksheet).first();
	var dc = finder.findByType(Metamodel.dc.DCWorksheet).first();

	FMEATool.synchronizeWorksheet(fmea);
	FMEATool.synchronizeWorksheet(dc);
}

main();

Note that this is highly unstable and just a first shot! I am not fully sure about all consequences yet,

Regards Jan

medini_1035403171

Hi Jan,

This works perfectly. Thanks for the fast solution.

Johannes

medini_1036016653

Dear Jan,

thank you for providing that synchronization/update functionality that updates a FMEA or FMEDA (DC worksheet) to match the represented system model.

I slightly modified the fmea.js to match the usage of factory.ex:

content of fmea.js

/*
 * Copyright (c) 2018 ANSYS medini Technologies AG
 * All rights reserved.
 * 
 * The script is provided "as is" without warranty of any kind. 
 * ANSYS medini Technologies AG disclaims all warranties, either express or implied, 
 * including the warranties of merchantability and fitness for a particular purpose.
 * 
 * v2019-04-24 - initial version
 */
if (!bind) {
	throw "This script requires extended API";
}

// bind stuff (NOT OFFICIAL API YET)
var SyncFMEAOperation = bind("de.ikv.analyze.fmea.editor", "de.ikv.analyze.fmea.sysmlFMEA.SyncSysmlArchitectureEntriesOperation", false);
var SyncDCOperation = bind("de.ikv.analyze.editor.dc", "de.ikv.analyze.editor.dc.operations.SyncDCEntriesWithSysMLOperation", false);


function synchronizeWorksheet(worksheet) {
/**
 * Synchronize the given worksheet with its connected system model.
 */

	var op = undefined;
	if (worksheet instanceof Metamodel.dc.DCWorksheet) {
		op = new SyncDCOperation(worksheet, "Sync");
	} else if (worksheet instanceof Metamodel.FMEA.FMEAWorksheet) {
		op = new SyncFMEAOperation(worksheet, "Sync");
	} else {
		throw "bad parameter";
	}

	op.execute(null, null);
}

load("/.lib/fmea.js"); // synchronize system model and FMEDA (DC worksheet)

usage

synchronizeWorksheet(dc);

This came very handy for a script I'm currently working on.

Best regards

Peter

medini_1024169437

Good! Peter, remember that the sync is executed in the same transaction as the script.

Undoing the script execution also undoes the sync.

Happy Scripting

Jan

medini_1036016653

Hi Jan,

actually this doesn't seem to always work (as expected). I need to find some time to debug the situation in more detail and possibly to create a minimal (not) working example.

Within the script I'm first creating a part and a failure mode in the system model. Then I command the synchronization and then I'm navigating to the according FMEDA entry (getMediniOpposite()) to fill in some values (custom profile attributes). While the script runs without errors and debugging hints me to believe that everything is done correctly, the DC worksheet does not reflect my entered values (the DC worksheet simply shows me empty cells for the "comment" column).

During diff&merge I observed that there seems to be a difference between empty (as empty string "" - white cell) and not defined (as "undefined"? -- greyed out cell). Thus I'm wondering whether the DCFailureModeEntry for some reason is not yet able to actually take/accept a value that is assigned to one of its attributes?

My understanding of the inner-working is still limited. May be this textual description gives you an idea where I'm missing a crucial step?

I think I already tried a second "synchronization" step after filling in the attributes, but that didn't help.

Thank you again.

Peter

medini_1024169437

Hi Peter,

that sounds strange, the example you described is supposed to work actually.

Maybe I can try to replay that on my end.

Jan

medini_1036016653

Hi Jan,

I retested the unmodified script and it works now. May be a restart solved the glicht. Thank you in any case.

Peter

medini_1024169437

OK, good to hear that. Thanks for the feedback.

Happy Scripting

Jan

medini_1046241056

Hello everyone,

Currently, I have the same situation, but the above solution does not work for me.

My script updates System Design with factory.js, then based on the changes made, I want to update the DC sheet. Unfortunately, this is not possible when executing a single script - the DC sheet does not update at the runtime.

I implemented your synchronization solution as an intermediate step, after system design updates and before DC worksheet updates and it does not cause any changes.

Has anyone had a similar problem?

medini_1024169437

Hi Łukasz,

do you get any exception or error when executing "FMEATool.synchronizeWorksheet(fmea);"?

Which version of medini are you actually using, maybe the above posted fmea.js

is outdated.

Jan

medini_1046241056

Hello Jan,

Thank you for quick response. My current Medini version: medini analyze 2020 R2.1

Build: 20.2.1.200820171047-c46591d

There is no error, but also no effect of the fmea.js usage.

I will try to be more specific, maybe my use of this library is not correct. I have created relation (Metamodel.safetyModel.CausalityRelation) and for the places where those particular relations have arisen, I want to update some values in the DC worksheet, but it is not visible in the same runtime.

Thank you in advance.

medini_1024169437

Hi Łukasz,

hm, the specific call to "FMEATool.synchronizeWorksheet(fmea);" is AFAIK only required if you do structural changes to the underlying sysml model, not if you change the failure net. Maybe you can try to do the change first manually having the DC open and second do it with the script, having the same DC open (without the above call) and see whether there is really a change. Maybe you script does not correctly create the links?

Jan

medini_1046241056

The problem that I'm trying to describe exists only during first run of the script. Simplified sequence:

1) Create relation (Metamodel.safetyModel.CausalityRelation) if certain condition is true.

2) If relation has been created then update DC worksheet, user_string_virable (Metamodel.dc.DCFailureModeEntry).

The second step 2) can not notice changes that come from the first step 1).

However, if I run the same script second time and the first step 1) was accomplished previously, the second step 2) works fine - the changes done by first iteration are updated, so second step 2) is feasible.

I assumed the solution might be the sync done by "fmea.js" called between 1) and 2), but that doesn't help.

medini_1024169437

Ah, okay that may explain it. You want to see changes in your own derived property correct? Its not about that teh DC does not show any elements or something like that.

Well, the synchronize Worksheet doe snot help here, the update sof any change in the project are "published" at the end of the transaction so editors etc should recogbize that once the sript is through.

Strangely that your property is not calculated again... do you hve more details?

Jan

medini_1046241056

My script is not very extensive, so to share more of the details I'll just throw it here. I've added some comments, so I hope it's readable. Please let me know if you find the root cause.

medini_1023909254

Hi Lukasz,

I had a quick look into your script - actually it should work without any need for explicit synchronization. See my example below. I actually made a few assumptions/modifications:

The script assumes that for the SysML model already a DC Sheet is existing - and exactly one
I used a couple of more conveneient functions from finderEx.jks library - just check that library out
I only tried it with simple DC sheets (i.e. no individual evaluation for multiple safety goals and no variants)

//$EXPERIMENTAL$ 
//$DEBUG$ <- move to first line to enable debugging

load(".lib/factory.js");
load(".lib/finderEx.js");
//var FMEATool = load(".lib/fmea.js");

function main() {
 var check = check_relation(); //check if any effect is assigned to each Failure Mode
 var create = create_no_effect(); // create effect by factory.js "No effect"
 var effects = relation(check,create); // assign created "no effect" to each Failure Mode that has not relation
 var fmeda_sheet = DC_trace(check); // update FMEDA worksheet for previously updated places <- does not see changes in first script runtime 

}

function check_relation(){ 
 var scope = Global.getFinder(selection[0]); // context sensitive -> select on BOM lvl
 var searchType = Metamodel.safetyModel.FailureMode;
 var children = scope.findByType(searchType, true).asList();
 var empty = []; 
 for (var i = 0; i < children.size(); i++){ 
 if(children.get(i).effects.size()==0){ 
 empty.push(children.get(i)); 
 } 
 }
 return empty;
}

function create_no_effect(){
 //EH: Using more convenient create functions from finderEx
 var scope2 = findOrCreatePart(selection[0],"Created by script");
 var effect1 = findOrCreateFailureMode(scope2, "No effect by script");
 return effect1;
}

function relation(fm,no_effect){
 for (var j = 0; j <fm.length; j++){ 
 if(fm[j] != no_effect )
 {
 Factory.createRelation(fm[j], no_effect, Metamodel.safetyModel.CausalityRelation);
 }
 }

}

function DC_trace(fm){ 
 for (var j = 0; j <fm.length; j++){ 
 //EH: Look-up all DCFailureModeEntries related to fm[j]
 var fm_s = fm[j].mediniGetOpposites("element").toArray().filter(function (e) {return e instanceof Metamodel.dc.DCFailureModeEntry});
 //EH: In case multiple DC Sheets exist, the next line should again iterate over the list instead of acessing fm_s[0]
 fm_s[0].spfViolation = false;
 } 
}

Best regards,

Eckhardt