Skip to main content
Apr 16, 2021 8:21 AM UTC
Archived

Modelcheck allow Wildcards / Placeholders / Patterns for unwanted Layers etc.

Related products:Creo Parametric

When configuring ModelCHECK, some list values allow for wildcards / placeholders like:

* — Any number of characters
? — One character (numerical, alphabetical, or symbol)
# — One numerical character
$ — One string character

 

but these cannot be used when checking for unwanted layers:

PRT_LAYER_UNWANTED [layer]
ASM_LAYER_UNWANTED [layer]
DRW_LAYER_UNWANTED [layer]

 

Allowing to use placeholders like # in the check file would make ModelCHECK much more aligned with itself and be useful because the admin would not need to explicitly list all possible layer names that are not allowed.

This should also be allowed for other unwanted... checks and when using external list files for them.

4 replies

Community Manager
Feb 20, 2025 11:58 AM UTC
Status changed to: Clarification Needed

Thank you @SvenR for publishing your idea. However, we need more information as specified in the questions below. You may simply add a comment to your idea. The more details and context you give to document your idea, the better. Think about ways to educate and convince other Community members to support your idea and present your case to the product management team for consideration.


Please let us know within the next three weeks.

1. What version of the software are you running?.
2. What is the problem?
3. Are you using a workaround? If yes, please describe it.
4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.
5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)

Additionally, I invite you to check out this topic where PTC executives explain product managers' approach to customer ideas and input for product roadmaps.

Please see examples of well-documented ideas:

https://community.ptc.com/t5/Creo-Parametric-Ideas/Make-Shrinkwrap-quality-more-scalable-to-data-size-complexity/idi-p/810192 

https://community.ptc.com/t5/Creo-Parametric-Ideas/Option-to-Import-STEP-file-as-Inseparable-Assembly-by-Default/idi-p/812924 

https://community.ptc.com/t5/Creo-Parametric-Ideas/Eztol-Rename-action-not-synchronous-in-Eztol/idi-p/828000 

https://community.ptc.com/t5/Creo-Parametric-Ideas/Always-enable-ability-to-Add-View-Label-in-a-drawing/idi-p/837630 

Feature parameters can be input and changed togeth... - PTC Community 

SvenRAuthor
Feb 20, 2025 2:42 PM UTC

1. What version of the software are you running?

Creo Parametric 10 and testing 11


2. What is the problem?

The ModelCHECK check 'LAYER_UNWANTED' can be configured by using the start configuration file using the PRT_LAYER_UNWANTED, ASM_LAYER_UNWANTED, and DRW_LAYER_UNWANTED start configuration options.

Those options do not allow wildcards / placeholders like the following to be applied (which are widely used among other configuration options in ModelCHECK):
* — Any number of characters
? — One character (numerical, alphabetical, or symbol)
# — One numerical character
$ — One string character

This leads to the situation that in order to get a specific layer name to be recognized as 'unwanted', its name needs to be exactly included using the options PRT_LAYER_UNWANTED, ASM_LAYER_UNWANTED, and DRW_LAYER_UNWANTED.

 

So in order to get every layer according to specific schemes recognized as 'unwanted', each name of an unwanted layer must be set via those options ..., which results currently in 161865 lines. This also makes ModelCHECK a bit slower to execute.

Example:

 

Spoiler

first lines:

LIST_UNWANTEDLAYERS #
LIST_UNWANTEDLAYERS ##
LIST_UNWANTEDLAYERS ###
LIST_UNWANTEDLAYERS ####
LIST_UNWANTEDLAYERS #####
LIST_UNWANTEDLAYERS ######
LIST_UNWANTEDLAYERS #######
LIST_UNWANTEDLAYERS ########
LIST_UNWANTEDLAYERS #########
LIST_UNWANTEDLAYERS ##########
LIST_UNWANTEDLAYERS ###########
LIST_UNWANTEDLAYERS _#
LIST_UNWANTEDLAYERS _##
LIST_UNWANTEDLAYERS _###
LIST_UNWANTEDLAYERS _####
LIST_UNWANTEDLAYERS _#####
LIST_UNWANTEDLAYERS _######
LIST_UNWANTEDLAYERS _#######
LIST_UNWANTEDLAYERS _########
LIST_UNWANTEDLAYERS _#########
LIST_UNWANTEDLAYERS _##########
LIST_UNWANTEDLAYERS _###########

... last lines:

LIST_UNWANTEDLAYERS _9988
LIST_UNWANTEDLAYERS _9989
LIST_UNWANTEDLAYERS _999
LIST_UNWANTEDLAYERS _9990
LIST_UNWANTEDLAYERS _9991
LIST_UNWANTEDLAYERS _9992
LIST_UNWANTEDLAYERS _9993
LIST_UNWANTEDLAYERS _9994
LIST_UNWANTEDLAYERS _9995
LIST_UNWANTEDLAYERS _9996
LIST_UNWANTEDLAYERS _9997
LIST_UNWANTEDLAYERS _9998
LIST_UNWANTEDLAYERS _9999

 

 

 

3. Are you using a workaround? If yes, please describe it.

Our not-so-'workaround' so far is using the options PRT_LAYER_UNWANTED, ASM_LAYER_UNWANTED, and DRW_LAYER_UNWANTED to include almost every misspelled layer name which could occur, thus making the configuration files in sum bigger than 4 megabytes which also slows down executing ModelCHECK.

 

4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation.

Use cases include working with big assemblies of imported models, updating models / fixing models which use old/outdated/misspelled layer names.
And the basic use case is indeed maintaining model quality / homogenous model quality.

 

5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.)

Every time a big assembly that has a lot of layers that are not included in the config options, the user has to delete them manually, which is a time-consuming task. That often happens when using imported models from customers or suppliers. This happens to ca. 100% of our users.

Additionally: the slower execution of running ModelCHECK is a persistent 'slow-down' for all users.

Mini-Example: Running ModelCHECK interactive with and without the check LAYER_UNWANTED:

assemblyruntime, check LAYER_UNWANTED with full listruntime, check LAYER_UNWANTED list of only two names
small assembly < 20 comp.6 sec3 sec
medium assembly < 500 comp.16 sec10 sec
part < 50 features5 sec1.8 sec

 

Those differences may seem small, but since we run ModelCHECK as gatekeeper and have about 16100 iterations of PRT, ASM and DRW checked in last year, it would need to be multiplied by this number... thus resulting in quite some hours being lost.

 

On the other hand, more time gets lost due to the users manually working on deletion of unwanted layers, but I have no idea to obtain statistically correct numbers of that. It may add up to 30 minutes per model, when selecting (highlighting) the layers takes a lot of time due to the vast amount when working on imported models. People often forget to disable highlighting of geometry first, as it's normally a useful function.

 

Even more time gets used when users discover unwanted layer names that are not on the list for the check. Then we found out that it may not exceed the maximum list size (NUM_ITEMS_LONG_LIST has a limit), and we are not able to add every name of unwanted layers to the option.

This results in the option being only half-useful because it cannot catch all unwanted layers.

To sum it up: being able to use wildcards for this option as it's already the case for most other options would facilitate configuring and also speed-up execution of ModelCHECK 👍

 

(fun-fact: when using the function to attach the ModelCHECK report to the model in Windchill (MC_SAVE_XML_REPORT_TO_WC        YN          Y ) , then each attachment is about 5MB in size (compared to some KB without the full list of layers) which adds up to more than 80GB for just this setting (taking the number of iterations into account).

Community Manager
Feb 20, 2025 2:50 PM UTC
Status changed to: Acknowledged

Thank you @SvenR for your idea. Based on the information you provided, we are acknowledging it as the Community management team. This is not a commitment from the Product team. Other users may comment and vote your idea up.

olivierlp
Community Manager
Jul 3, 2025 3:45 PM UTC
Status changed to: Archived

Hello,

We are archiving your idea as part of a general review. This action is based on the age of your idea and the total number of votes received, as per this announcement.

You can always post a new idea with all the details required in the form.

Thank you for your participation.

Olivier