ModelCheck Gatekeeper allowing different configurations

[mschulze]

By setting the "ModelCHECK Configuration" one can configure multiple configurations for different Lifecycles (Lifecycle Names! not Lifecycle States)  

<Lifecycle_1>:<mch_file1>,<mcs_file1> <Lifecycle2>:<mch_file2>,<mcs_file2>...​

This is well documented in the PTC Help chapter: Configuring ModelCHECK in Windchill

But this is not a realistic example. 

I am looking for a way to configure the “ModelCHECK configuration” so that different configurations can be used regardless of the lifecycle name (we only have one). This is because there is usually only one lifecycle for Creo data.
e.g.:

<Lifecycle_1>:<mch_file1>,<mcs_file1> < Lifecycle_1>:<mch_file2>,<mcs_file2>...

Does on have a hint for me? 

[Catalina]

Hi @mschulze 

Thank you for your question. 

Your post appears well documented but has not yet received any response. I am replying to raise awareness. Hopefully, another community member will be able to help.

Also, feel free to add any additional information you think might be relevant.

Best regards,

[joe_morton]

ModelCheck is very complicated...! I did a bunch of investigation previously, here's an except from my notes:

ModelCheck settings are spread across several different files

The config.pro setting modelcheck_dir defines the root directory for Creo to use for all ModelCheck files. The path defined should contain a folder called “config” default and the subfolders as shown below.

• config

  • check

  • constant

  • groups

  • start

  • status

  • text

These files are stored in the root (config) directory:

• config_init.mc - initialization file. This is only read on Creo startup. See: http://support.ptc.com/help/creo/creo_pma/r6.0/usascii/index.html#page/model_analysis%2Fmodelcheck%2FAbout_the_config_init_mc_File.html%23

• condition.mcc - this file lets you set logic for the model (based on parameters) for which files should be used. See: https://support.ptc.com/help/creo/creo_pma/r7.0/usascii/index.html#page/model_analysis/modelcheck/About_the_condition_mcc_File.html# 

• config.gmc - seems to have values for geometry checks, such as tiny element

• setconf.mcc - used for manual selection of which configuration file to use. CNFG_SELECT_AUTO configuration option must be set to N or A in the config_init.mc file for it to be used. See: https://support.ptc.com/help/creo/creo_pma/r7.0/usascii/index.html#page/model_analysis/modelcheck/About_the_setconf_mcc_File.html#

For your question, I think you can accomplish what you're looking for via the condition.mcc file. You should be able to set different rules based on the parameters in the models.

[mschulze]

Sorry Joe, yes I know the configuration of model check. and using the condition.mcc will lead into the usage of different configuration files, which need to be configured in the gatekeeper.  This is what this idea is about. as you cannot configure different configuration files for one lifecycle (name). 

[joe_morton]

I guess I misunderstood. What are you trying to achieve? 

Condition.mcc lets you run different configuration files, based on some parameter in the model. There are 2 parameters (at least in Windchill 13) that get automatically populated into Creo models:

• PTC_WM_LIFECYCLE - this is the lifecycle template name
• PTC_WM_LIFECYCLE_STATE - this is the current state name

I agree with you that there is usually 1 lifecycle template name for CAD models, but I would think you would have several lifecycle states. If you want different checks based on the state, that should be achievable.

You could configure different rules based on any model parameter, or use the setconf.mcc if you want to allow manual selection.

[mschulze]

Yes, but as you yourself say, that would lead to the use of different configuration files.

Imagine a Condition.mcc that responds to different lifecycle states (e.g., lc_state_1, lc_state_2, lc_state_3).

Then the gatekeeper would have to be configured to something like this (#Operation #CheckIn Operation #ModelCHECK Configuration

Basic:check/lc_state_1_checks.mch,start/lc_state_1_nostart.mcs,constant/lc_state_1_inch.mcn

Basic:check/lc_state_2_checks.mch,start/lc_state_1_nostart.mcs,constant/lc_state_2_inch.mcn

Basic:check/lc_state_3_checks.mch,start/lc_state_3_nostart.mcs,constant/lc_state_3_inch.mcn

Unfortunately, this is not possible.