Hi @InnerKK,
What you’re experiencing here is similar to the total volume that gets printed in the mapping report (see this thread). Tracking data in the Vector Database is stored based on Labware ID, not sequence name. As such, when a mapping report is generated for a target sequence, it is actually pulling all data related to the Labware ID, not just the given sequence name. This leads to the duplicates that you’re seeing in your output file, as you are using different sequences for pipetting, but all referencing the same Labware ID and positions. Like the linked thread suggests, a way to work around this is by using the Remove Labware function between rounds of pipetting to clear the Database of the previous pipetting data. If your labware has a barcode, then you’ll also want to use a Set Labware Barcode function after the remove to reassign the corresponding barcode.
Thank you,
Dan