Howdy folks,
Running into a recurring (but infrequent) issue where Venus methods are throwing a “Type Mismatch” error during the initialization step:
This happens maybe once in every 15-20 runs, and it happens across a few different methods. I’ve done a little digging through the method file for the error from this specific screenshot, which shows that the flagged line of the .med file is the initialization step. For this step, we’re just using the standard initialization step, so there shouldn’t be any variables passed that would have an incorrect type:
My current shot-in-the-dark is that there’s a line of hsl that’s causing the error message to display the incorrect line number, and that the type mismatch is elsewhere in the file or SMT (I’ve seen something similar where a block of hsl with an issues causes the line above to be flagged as erroneous). The issue is infrequent enough that I haven’t figured out a reliable way to trigger it on my own.
Nearly every time this happens, the issue is resolved by just re-running the method. It’s not a show-stopper, but unfortunately the methods are structured so that the user has to re-input information, re-do the deck loading, labware scanning, etc., so it’s a real bummer for them to have to start that process over.
Was wondering if anyone had encountered this problem before and if they had any success in finding the cause and/or resolving the issue.
If that doesn’t work, it might be another clue that the error is not actually being thrown by Initialize