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

FMEDA: Push hardware parts into correct design block

medini_1062733402

Hello together,

after creating a hardware part library I imported a BOM.

Before deriving a FMEDA as a intermediate step I created 'Elements' within the 'System/ Function Model illustrating the schematic blocks.

The problem:

I had to select the components reference designator by reference designator and push that components into the right 'Element'. Time intense.

I'd like to have a function that selects all components in that BOM and optionally push that components into an 'Element'.

I think it is necessary to tell that function where the RefDes information is stored. I used the 'Name' property.

My requirement to that functions are:

* Possibility to enter the number range,e.g. 500 - 550

* Function selects all components within that number range, means R, L, C, IC, ...

* Enter the target element, where the components shall be pushed into

Best Regards

Benedikt Wilhelm

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024169437

Hello Benedict,

interesting use case and feasible solution. Shouldn't be too difficult.

Meanwhile you may have a look at the scripts inside our "Best Practices" example that you can find in our welcome page:

In there you can find the script "Restructure HW Model". The script uses an attribute "circuit_block" to find the parent element, no user interaction. I know, its not what you are seeking for but maybe a start for you or others who have similar problems.

Jan

All comments

medini_1024169437

Hello Benedict,

interesting use case and feasible solution. Shouldn't be too difficult.

Meanwhile you may have a look at the scripts inside our "Best Practices" example that you can find in our welcome page:

Jan

medini_1024169437

Well, I started to script the support and recognized that with a little more options it can help on a broader scope, so to also support other use cases that have been asked here and elsewhere.

So, I managed to quickly script a first draft. It supports the following use cases:

- move an arbitrary number of selected parts into a different scope inside the same model (this was asked by users that have a huge BOM imported and drag & drop is not feasible)

- the same as above but just those who match a certain pattern (as asked by Benedikt)

- selecting just a scope (model or package) and search for parts that match a certain pattern. The pattern is given as "<attribute>=<regex>" so an attribute name (as "name" or "partNumber") and a regular expression it must match. This is exactly the use case Benedikt was asking for I think

The script does the following steps:

1. checking for single or multi selection

2. if multiple elements are selected, the user can choose between just proceed with the selection or to run pattern matching against the selected, if just one element is selected, it runs pattern matching against the complete sub-tree

3. the user is asked for a pattern as described above

4. one the number of elements (selection or pattern matching or a mixture) is clear, the user is asked for a destination. The destination must be inside the same model

5. all elements are moved

Here is the script, its written with the 2019 R2 RC but should work with 2019 R1 or even 19.2. You of course need the libraries posted in the Solutions:

// $EXPERIMENTAL$ $STRICT_MODE$ $WARNING_AS_ERROR$ $ENHANCED_CONTAINMENT_ACCESS$
/*
 * Copyright (c) 2019 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-15 - initial version
 */

load(".lib/factory.js");
load(".lib/finderEx.js");
load(".lib/ui.js");
load(".lib/helper.js");

// validator
function validPattern(text) {
	if (!text) {
		return "Please enter a valid pattern";
	}
	var index = text.indexOf("=");
	if (index <= 1) {
		return "Assignment is missing (=)";
	}

	return null;
}

// ask the user for the method
function main() {
	if (!selection || !selection.length) {
		return "This script requires a selection, either a single scope to search or a set of elements to move.";
	}
	var multiSelection = selection.length > 1;
	var kind = multiSelection ? selectOption("Make Your Choice", "Use selection or match by pattern?", [ "Selection", "Pattern"]) : 1;
	if (kind == undefined || kind < 0) {
		return undefined;
	}

	var elements = selection;
	if (kind == 1) {
		var pattern = inputText("Pattern", "Give me a pattern (<attribute>=<regex>)", "partNumber=5[0-5][0-9]", validPattern);
		if (!pattern) {
			return undefined;
		}

		var index = pattern.indexOf("=");
		var attribute = pattern.substring(0, index);
		var regex = pattern.substring(index + 1);

		console.log("Searching for {0}={1}", attribute, regex);

		// use our own scoped finder
		var scopeFinder = Global.getFinder(multiSelection ? selection : selection[0]);
		var found = scopeFinder.findByType(Metamodel.sysml.SysMLPart).and(attribute, java.util.regex.Pattern.compile(regex));
		if (found.isEmpty()) {
			return "No elements were matching in the selected scope, nothing to do";
		}

		elements = found.asArray();
	}

	// paranoia
	if (!elements || !elements.length) {
		return "No elements were selected or matched or anything, nothing to do";
	}

	// we want to select a new root but ONLY inside the common ancestor
	var root = undefined;
	for (var i = 0; i < elements.length; i++) {
		var elementRoot = getModelRoot(elements[i]);
		if (!root) {
			root = elementRoot;
		} else if (root != elementRoot) {
			return "The selected or matched elements do NOT have a common model root but MUST. Aborting.";
		}
	}

	// ask for destination
	var target = selectElement("Select target model or package", Metamodel.sysml.SysMLContainerPackage, false, root);

	// now move
	for (i = 0; i < elements.length; i++) {
		elements[i].the_owner = target;
	}

	return elements;
}


main();

Note that I did just some basic tests. Use the script on your own risk. There is for example just limited checks that the selected target is valid. Moving elements to their children should be prevented, but other things may be wrong (moving into types, moving out of types etc.)

Feedback is highly appreciated. I'll attach the script as well. And maybe a sample project to play later if someone is asking for it.

Happy Scripting

Jan

medini_1062733402

Hello Jan,

I like that script, but I have a question.

The reference designator always has letter(s) in front of the numbers,e.g. R500, IC1600. How to use a wildcard here?

medini_1024169437

Hi Benedikt,

the script uses the Java class java.util.regex.Pattern that supports a variety of options (for details see the Java doc) . If you have just a single character your use for example \D for "non digit" or simply . for any character or use [a-zA-Z] so all in all:

partNumber=\D5[0-5][0-9]

Jan

medini_1024169437

I forgot to mention: if there might be multiple characters, use the + symbol, so \D+

Jan