We’ve been seeing an issue where sample tubes that are misscanned during the autoload step and manually entered are placed at the beginning of the array regardless of their physical position on the deck, which is written incorrectly to our output file.
Our current sample tracking method works by loading the sample carrier on the autoload, retrieving the scanned barcodes from the step return data, putting the barcodes into an array and then writing that array to a file.
Why do error samples appear out of order and how can I adjust our method to fix this corner-case issue?
Hi @Not-So-EasyBlood ,
This is a common issue that can happen when parsing through the step return value. The reason why the entries are out of order is due to the time the actions happened. The barcode scanning takes place, and then the manual barcode recovery takes place. This puts the barcodes that were manually recovered on top of the list because they happened later in the steps.
Luckily there is a simple solution for your issue. There is a function called GetPositionFromNum. Essentially, this will get the new index based on the position you actually want to query. Use its return value for the num params on each of the Get functions to correct this issue.
1 Like
Oh wow what a simple solution, thanks for this! Super helpful as always!
2 Likes
