MoseleyBioinformaticsLab / manuscript.peakCharacterization

0 stars 1 forks source link

qcqa via scan level metrics #19

Closed rmflight closed 2 years ago

rmflight commented 2 years ago

Would be great to have examples of this. The ones I can think of that we've seen are:

rmflight commented 2 years ago

Another way to check for scans being dropped for any reason would be to open the zip, do the raw_ms filtering, and then compare the normalization factor scans from the final zip to the scans in the raw_ms filtering. Or even what is listed in raw_ms$scan_range and what is in the normalization factor data.frame.

rmflight commented 2 years ago

Scans being dropped due to bad R^2 (can check if this happens I think)

Based on the logs for re-running the entire set again, we don't see this come up. So we can mention it, but we don't see it happen.

Scans being dropped b/c their sqrt terms are outliers.

We missed this one above, but it does happen. Many, many samples lose one or two scans due to having outlier sqrt terms coefficients in the frequency model. What is really nice, is we can see how many samples and how many scans were lost due to this, and plot a sina_plot with the outlier terms. I've got the data for this.

Two sets of different start - stops on range of convertable frequency differences.

I need to pull this data in and make the graph, and note how many samples this happened to and how we got around it.