Istvan, thank you for your reply.
The specification for the file format can be found in the CASAVA user guide (http://biowulf.nih.gov/apps/CASAVAUG15011196B.pdf)
The relevant first few columns of an ELAND _export.txt file are as follows: Machine, Run Number, Lane, Tile, X Coordinate of cluster, Y Coordinate of cluster, Index sequence, Read number (1 for single reads; 1 or 2 for paired ends or multiplexed single reads)
A couple (paired) example lines are:
from file s61:
HWI-ST776 151 6 2309 1083 28970 .TGTCA 1
from file s62:
HWI-ST776 151 6 2309 1083 28970 .TGTCA 2
Paired reads should have the same cluster coordinates as I understand it.
I wrote a quick little python script to parse the files, make a set of tuples from all the (x,y) coordinates and then compare the two sets. It's not an elegant solution as it eats 21gb ram, but it works in less than half an hour, so I have time for coffee.
The log is as follows:
File 1 rows 67003423
File 2 rows 67003279
Length orginal set 1 65903883
Length orginal set 2 65903741
Length symetric Diff 142
pickled left overs from file 1.
pickled left overs from file 2.
Program End prog duration 1630.02
I'm going to investigate the differences and see about handling the coordinate duplicates in each file and the symmetric differences between the files. From what I've read, the _export.txt was meant as an internal format. I'm less than pleased that I've gotten it returned to me as a copy of the "source data" for an analysis we contracted to a company.
--Colin