Check existence and location of table files at end of run

[[No...]]

Is there a way in PCM to find out at the end of a run

• whether a characteristic table file was generated and exported (i.e. if the table file option was activated in the start window AND if the custom path setting was set and activated)
• where (custom path and file name) it was exported to.

I think this would need a few "undocumented" commands. Does anyone happen to know some? 🙂

Edited July 28

[[Mi...]]

Hello Norbert,

all generated files are logged in the protocols.log file located in the actuals directory (directoryPath("actuals")):

baseSystem().machine.inspection.settings.protocollog
settingGet("protocollog")

remark: baseSystem().machine.inspection.settings.blabla is the "same" as settingGet("blabla")

If the table file option is activated in the start window:

baseSystem().machine.inspection.settings.resultToTableFileDialog
settingGet("resultToTableFileDialog")

settingGet("resultToTableFile") shows if table files are activated

You can check custom path settings with

baseSystem().machine.inspection.settings.protocolSettings.outputFileDefinition
settingGet("protocolSettings").outputFileDefinition

especially (returns nil if not)

baseSystem().machine.inspection.settings.protocolSettings.outputFileDefinition.tableFileHdr
baseSystem().machine.inspection.protocol.protocolSettings.outputFileDefinition.tableFileChr
baseSystem().machine.inspection.protocol.protocolSettings.outputFileDefinition.tableFileFet

 

[[Mi...]]

Please sign in to view this quote.

Edit: Missing files are labeled with MISSING in the protocols.log file:

C:\Users\Public\Documents\Zeiss\CALYPSO\workarea\results\somtehing_2026_07_28_pwr.pdf     MISSING

By the way: Why can't I edit my posts anymore?

[[No...]]

Insane!  Thanks a lot!

I didn't expect it to be that easy. Never payed attention to that log file before.

Does the log grow or does it always mirror the state of the last run? Because if it doesn't grow and missing files are marked, I probably won't need all the other check functions. 👍

[[No...]]

Please sign in to view this quote.

One more question:

Can we also access other (non-inspection) settings this way? settingGet() seems to be specially deisgned for inspection settings. What about more general settings?

[[Mi...]]

Please sign in to view this quote.

Hello Norbert,

the log always mirrors the state of the last run. But the file is only updated at the end of run. Meanwhile it contains the data of the last run. To be save you may delete it at start.

[[Mi...]]

Please sign in to view this quote.

What kind of settings do you have in mind?

[[No...]]

Please sign in to view this quote.

The best time to run my code (from an external PCM file) is something I have yet to figure out. I will probably just read the protocol name from that log and hope it wil already be updated at that time. But thinking about it, the best way to do it would be to retrieve the actual string written by Calypso to the log. That would also avoid possible errors if the configuration is changed in the future.

Please sign in to view this quote.

Things from \config\env\values for example. How does one figure out all those queries in the first place? I'm clearly mssing something here although I know the basics.

[[Mi...]]

Please sign in to view this quote.

 The content of \config\env\values should be displayed using

baseSystem().machine.environment.OMConfiguration.getMastersEnvMemory
  or
baseSystem().machine.environment.OMConfiguration.classPool.Memory.env

For Instance the default actuals path:
baseSystem().machine.environment.OMConfiguration.getMastersEnvMemory.defaultPathForActuals

It is just possible to access the underlying smalltalk layer using pcm. Actually, by Zeiss this kind of pcm code isn't intended to be used. So it is not documented and not easy to to figure it out.