bug: Protocol Analysis Failure when accessing a CSV and also not fetching existing labware offset data

[MSMDG]

bug: Protocol Analysis Failure when accessing a CSV and also not fetching existing labware offset data

[ClaireLee22]

I recently encountered a similar issue. While researching the problem on this webpage (https://support.opentrons.com/s/article/Protocol-analysis), I discovered that "Protocols that used to run perfectly on a previous software version might have a "File not found error" because the file is on the OT-2 and not on the Protocol Analysis engine in the app. ".

It appears that the Protocol Analysis engine doesn't recognize the path in the OT-2 machine when you import the Python script. To address this, I've implemented a workaround using a try-except block. This allows me to handle the "File not found error" gracefully, ensuring that the previous offset data is automatically reloaded. However, there is a drawback to this approach – even if your file or path is incorrect, no error message will be displayed.

[MSMDG]

Hello @ClaireLee22 I've taken a similar approach with you (see below "Code to reproduce"). You are right no error message will be displayed for the protocol analysis step, it will show an error after pressing start setup.

[wolfrickw]

Try to reimport your protocol after some modification in your csv.... You'll see no modification compared to you first import, the "external" csv is cached and it is not read anymore..... or at least untill you change the csv name and modify your protocol