Skip to main content
L
lgreene7-Bedrock
7-Bedrock
December 30, 2022
Solved

ModelCHECK, ACCURACY_INFO does not update absolute accuracy values. It does update relative values

  • December 30, 2022
  • 2 replies
  • 2991 views

I am using Creo Parametric Release 8.0 and Datecode8.0.5.0

In ModelCHECK, ACCURACY_INFO does not update absolute accuracy values. It does update relative values

Best answer by lgreene

I did . . . resulting in SPR 14464196.

Development team has fixed the issue and the fix will be available in Creo Parametric 8.0.9.0. and 9.0.5.0.

2 replies

K
KenFarley21-Topaz II
21-Topaz II
December 30, 2022

Perhaps the setup of your ModelCHECK is not taking into account that the limits are defined by different parameters depending on whether the accuracy is absolute or relative. A quick online search using "creo modelcheck accuracy_info" yields the following:

 

ModelCHECK Accuracy 

 

In brief, it calls for:

ACCURACY_LOW and ACCURACY_UPP for relative accuracy
MIN_ABS_ACCURACY and MAX_ABS_ACCURACY for absolute accuracy
L
lgreene7-BedrockAuthor
7-Bedrock
December 30, 2022

Thanks for the reply. Yes I did consider the limits for both Relative and Absolute

I can change the accuracy to the absolute value in the regular, manual way just not with MC

H
hadardor17-Peridot
17-Peridot
January 2, 2023

Hello,

By ModelUPDATE mode, Creo ModelCHECK automatically changes the accuracy to this value if the accuracy is not within the acceptable limits.

Use this syntax in the start configuration file:

MU_ACCURACY ABSOLUTE 0.001

L
lgreene7-BedrockAuthor
7-Bedrock
January 2, 2023

Thank you for providing your comment.

ModelUPDATE mode is a bit too aggressive for me.

I want ModelCHECK to warn of unacceptable accuracy value and provide the option to change it then.

M
ML_81261196-Contributor
6-Contributor
April 12, 2023

Did you get any support for your ticket?  I am experiencing the same issue where updates can be made thru the model properties but changes are not applied if changed in the ModelCheck interface.

Terms & ConditionsCookie settingsAccessibility statement