[Ta...] Posted Wednesday at 03:48 PM Share Posted Wednesday at 03:48 PM Greetings, We have an in-house script that automatically extracts major and minor strain data from Zeiss Inspect, generating time-dependent CSV files. Currently, we can only extract data when using the Standard computational method. I would like to develop a methodology that allows us to extract more points, as the surface quality is significantly better. If someone can help us it would be great. Best regards export_2019_BATCH_med_major_minor_minorSR_majorSR_220718.py Link to comment Share on other sites More sharing options...
[Jo...] Posted 19 hours ago Share Posted 19 hours ago Hello Tarek, i have not scripted for zeiss inspect so far and i have not checked the whole code. But just having a quick look i found the following: As this seems to be the only occurance of the word "standard" (full text search) it is highly likely that changing this to the desired setting will solve your problem. Link to comment Share on other sites More sharing options...
[Ta...] Posted 16 hours ago Author Share Posted 16 hours ago Yes, we have tried that, but unfortunately, it does not work; the script crashes with an unknown error. Link to comment Share on other sites More sharing options...
[Jo...] Posted 16 hours ago Share Posted 16 hours ago Strange Seems like it should work in theory and has worked for other people. Does the error message state which line of code was carried out, when crashing? Not sure if this info has any relevance, but anyway: When i run your script with "more_points" i seem to get to the line "gom.script.sys.close_project()", because i get no error and my project is closed. Link to comment Share on other sites More sharing options...
[Ta...] Posted 14 hours ago Author Share Posted 14 hours ago Unfortunately, the line error is 38. What type of computation method is selected? Also, I couldn't find any other computation methods besides the 'standard' one. I will try with this "more_points" and see if it works Link to comment Share on other sites More sharing options...
[Jo...] Posted 13 hours ago Share Posted 13 hours ago Sorry for pointing you in the wrong direction. You can put random stuff in for computation instead of the standard or more_points or the delete the whole line it does not produce an error. This is probably just asigning a value (text) to a keyword. Link to comment Share on other sites More sharing options...
[Na...] Posted 13 hours ago Share Posted 13 hours ago To make sure the command is working, you can record the creation of the element with the intended parameters used in the dialog. For most functions you can print the .__doc__ but for this it needs to be recorded since there is no list of parameters in the .doc print(gom.script.deformation.create_surface_component.__doc__) Link to comment Share on other sites More sharing options...
[Ta...] Posted 11 hours ago Author Share Posted 11 hours ago Thanks a lot for your help. For now, I used "more_points", and it seems that it's working. So by tomorrow i should see the results. Thanks a lot one more time. Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in