I want to temporarily disable anything going to the trace file. To incorporate our methods with our LIMS systems, our software department requires an output JSON file that incorporates several pieces of information for each well. I have created a way to do this, but it uses the JSON Hamilton library and adds different information to each well. This is a 384-well plate and each one is taking different volumes from two different wells, so that means 768 JSON entries at the end of the method, which completely floods the trace log and is substantial enough to create a delay in the method.
None of this information is something that really needs to be in the trace log. Does anyone know of a command I can put in BEFORE the JSON file stuff that will turn off trace messages, and another command I can put in AFTER the JSON file creation that will turn it back on? If anyone has other ideas as well, I’m all ears!
There is a SetTraceLevel function in the JSON library where you can set it to none to prevent the JSON library from generating trace files. This can be set any time in the method and only affects the JSON library.
As a followup to this, does anyone know if it is possible to suppress Trace logging of single-step (e.g. Aspirate) errors?
My situation is that we have some walk-away (i.e. automatic) handling of some pipetting errors (which works fine); but we also have an external application that is monitoring the trace log, and it sees an error and reports is, even though it is automatically handled a moment later. (The external application is not in our control, so can’t easily modify it’s behavior.)
