Jump to content

GOM Inspect 2022 - Possible Bug - Crash when updating stage comparison script via "Update Script) tool


---
 Share

Recommended Posts

Hello! I am currently in the process of updating various scripts from ATOS V8 SR1 to GOM Inspect 2022 and am using the built-in "Update Script" tool to handle most of the syntax changes. I've used it successfully on all but one script, which happens to be the only script we use that deals with stages. When using the "Update Script" tool on this script, GOM goes unresponsive and crashes. By checking the script one command at a time, I believe I've isolated the command causing the crash to the "create surface comparison on actual stage" command pasted below. I have yet to re-record this command in 2022, but I'm assuming something in its syntax has indeed changed? I will be putting together a test project to try and re-record the command for myself but thought I should also share here in case this is a bug causing crashes for other users...

MCAD_ELEMENT=gom.script.comparison.create_surface_comparison_on_actual_stage (
	compute_maximum_deviation=True, 
	deviation_calculation_type='shortest_distance', 
	max_angle_between_normals=1.57079633e+00, 
	max_opening_angle=5.23598776e-01, 
	name=gom.app.project.get ('user_Spec_Abbreviation') + ' ' + gom.app.project.get ('user_Spec_Number') + ' to Stage', 
	properties=gom.Binary ('eAHNWFtsFFUY/lcUSrEUqKKi4qSUWq1Lb4h1W2CpUKuxRKFB4m3T7m7bjXtjdirdKrL4ojH44INR3rzGBwiVJ+KTJoYEo5YnjTHxSdMnopEXEkxYv++cPZ3Z7nTtakzcyXTOnPnP99///5yOZFLBQw9um5ahfXv27jsgI/ZowsmFQvuS8VQ87TxpZ7Jx20nEc6J/AVkhDfVSLw1S34CpT1879twknod6rYMHuqyhjDOemLZ2lKjdx9zpVfIQXgO4Pztz7ZnH8Mw+q58u1eLRapLfjfvRmbnTAbkLo5tFCnFJSlxSEpGoZPBM4S0tjnwSnjt9g6wD1UpQ5TBjSwJfJqTtR66/EV/wK0iAbxsxXF2GlpNJ4B2VX94lDjhxRWEMcxlwfOEsV1GiQOENDlswBLNCUkZlDCIkIdAYxlF5ESxtLJoC85icDxJuP6i3gnoE8ykJ4RqEcBPSrcZPLGAMYJQDGik4Xoz2iBImA/wTFyhFG3ApCXnU4Vn6FSYXz4Ay/rFZsaFCbiLGwNcumTUJPrYMXyKuMdWEkn2buDJ0HSYi0GQtbo5hMv6Ku098dC/fW/Gyviq3FFDJ+fhu8rod9PWgH1D8tUTDJYpGxWETKCgR0Y2T0qBIAyNy5dXPOe/nGwZLWlFFERoJ9XZpwE+/Q0CKSg+kOtJudGgucaR88z/XTb95tfvLP3qben7tOhm+48P2jYN96fAr5we3kr4XNJCyLDLKudO2EUQMwxNSI+gS4OYgAGdWUiILCLBogZZ2Zeaqpxcov79KXkwKysQxfXATVuUQYaNAT8rF53/fzi/Gqt5YHVfYjlx/nxxvwVrET8H4eLD09e13uH4IX/eWuITwvHWBMoJozeN2oAdT0o8DFiz8zl5uvIeInZiBFwteepM1WWWXCaAxsZldTPiYXPmCkhqfL5mYjwN6y99C55CmCcniInQEpo+DlUkB45qcHPnBy3RKiebI4XNUohTsElYVxc/IpqZcz3tRKkWXQh0BLYhOv3utoi2bVZbl+FwHoZYuc8Y++6EOS2PkJyL7CUe0aXiueK064gbU01UrpNAPIznATMou4VgbjGPyccDPUiWZxViX5J3SLF24LeVHUnHmCOI4AUqiaQmapUNhMo7yytuWGtE5XGHoOrAqh6sZ1PUo35a6svIAnnSZJS/jPgrkhFoTBG0WckWBE8KXLDjHJQgKG7NZ6cPcsQWkfkjhSkC9Osq0pNtikM/yUFE6k0nEjYPzhNIsJNsR5Z2Kh0vh4odgE2a0ztU+pVM/pDbxbiHu+V2HpGtJF4FzXpqgsr6u3CGkQBTczU1Ny2ldnBD0YYtjDSIdJbKhBatTEBJlYKkQsLKIlsrvRHUUFfvaUlTM4HFQLU3BmDCWMyiMnDHMsnpqvajzFiC5F2noX9Y7+jqGS7d90nbidr+baHC/B1V80tfcLuhnDCtc6xDlJeDboGDUsrIG1V/Km4ZGKcyTK3WkfcqlCKp5rft23+/lmvshuD7w+7rYAyaWtLbpCm2WG40tSl92IOwd4HvWIEak3iUwU5mfEdiC+xx2AkYvc/U+dGCdTbRFWtm1A19i/wML+/vgv7JweUXYgXisrSK0qOqiq4QDT7bBmrqus+Y1S7uKX45Nq4mofSfr306sZbRyP1ndI/SNjn6OTAXSFZDRxapn6qHpABewNwzIZnQsnAQK3o6lsyWH6GHsRHd4W19lAw0AIbyeWPdj1ASsLCTWWjDvU4iyKUil27RbCVrniVvr3nR2dra45qlvmsiPe7pG8MsB34at3P27PlroaI9t/id8hk+dKq7t+nONVy8vH3M6YKXNg7Or11uqG9eqF1RZ2HNbeOEuwuUXA5dRdCdXw94er1foY99DDo8XPCz4Q5Ur0YfjxTK2Z5VWd6Ubh5yMGUcO7loWWDVVud1gUjx8uTpUae9lzgx+qmYhFXuGA8Cvi/8ajht0Gpwb/uM7q8OVTpuVVjPqeWMn/xvBao+dYlH2fHWbf064urPCJ2QGZv0W5yJ3DxqDKlPo0+x/740QxT2J1oVD6mxicpt1lidl9mhqkFaY9DnPDjx+s7tcTiwXn6cfb45Vw59CJWHHsuVMslZ8Ex0anxjsa9x30CrU31ZvH9xJZOOtEaWtl/qgh7a120jOUzLH5l8c3BlGEB60lXf1xXWvf+elY9WmHLrTszNTprzMb6pFv78ATT6DCwG3og=='), 
	search_distance=1.00000000e+01)

Thanks,

Michael Henson

Link to comment
Share on other sites

  • 2 weeks later...

Hello!

I had more time to dig into updating this script manually this week, and believe I found the syntax change upon re-recording the command. I thought I'd post my findings in case anyone else runs into a similar issue. Manually changing the command from:

gom.script.comparison.create_surface_comparison_on_actual_stage 

to:

gom.script.comparison.create_multiple_surface_comparison_on_actual_stage 

seems to have fixed the problem, as now the "Update Script" tool is able to analyze the rest of the script without crashing the GOM instance.

Regards,
Michael Henson

Link to comment
Share on other sites

 Share

×
×
  • Create New...