2019_GDB/results/qc/lr/S3_Gtube/no_barcode/no_barcodeNanoStats.txt2019_GDB/results/qc/lr/S1_SizeSelected/no_barcode/no_barcodeNanoStats.txt2019_GDB/results/qc/lr/merged/no_barcode/no_barcodeNanoStats.txt# not sure if want the "merged" though
Feel free to comment. I am not sure where the focus should be: comparing the selection methods or methylation/non-methylation aware approach approaches.
I think the merged is the only one of real concern, since we used that for downstream analyses. The other two options were Rashi trying something out. Ideally, this will not be the case.
Maybe (to be confirmed by @cedric.laczny) we will not even need to show the size_selected or gtube selection. This can introduce unnecessary scrutiny. In the methods, we can lay out that we used both methods to capture the variability (or some hand-waving), but my opinion is that it doesn't need to be in the figure itself. What say?
I think that this is something we could definitively report.
Yes, it might open us up for questions, but, then again, we could immediately try to argue over that by saying that we tested both approaches and used them together to have "longer" and "shorter" reads in the assembly.
Then again, one might question if this has added any benefit