Closed sklages closed 3 years ago
We have to be careful with Reads
. In some versions of InterOp is scaled by the number of reads in the run (generally 2x the cluster count). We fixed this issue in recent versions of InterOp, but if you got back far enough, then you will see that extra scaling.
Also, the summary logic is summing all the tiles a lane. The S1 flowcell has 312 tiles per lane.
If your Cluster Count above comes from a single row in the imaging table, then it corresponds to a single tile and it should be 312*Cluster Count = Reads
ha, okay. Thanks for the info, now the numbers make sense :-)
@ezralanglois .. just to avoid confusion:
If your Cluster Count above comes from a single row in the imaging table
it is the result of summary(run_metrics, 'Lane')
for the first read (1).
I have a question regarding:
The above snippet gives me the following values (lane 1 / read 1 as an example):
Where do the
Cluster
values come from? I thought the actual "cluster count" equals to "raw reads count"? So I'd expectCluster Count Pf == Reads Pf
. Where am I wrong?