To track, handle and specify custom actions for specific channels/wells that were affected in a particular ML_STAR step, you will want to use a combination of custom error handling by user and the step return data returned from your aspiration step in question.
There are a couple thorough examples already on the forum that I strongly suggest reviewing, as this will guide you to be able to get exactly the level of control you are looking for for this type of scenario:
In your case, the end goal would be to:
- Auto ‘Cancel’ channels which throw the error code of interest
- In an error handler, parse the step data of each channel to determine which (if any) channels were affected
- For parsed channels, generate a channel pattern and custom sequence corresponding only to the affected channels and wells respectively
- Use the custom sequence and channel pattern to use an additional aspirate step in the error handler, but this time using ‘bottom’ and ‘available’ step parameters
The linked posts break down this very useful technique in granular detail, highlighting two different use cases.
Hope this helps. Thanks.
-Nick