You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are contacting you regarding an issue we are facing when training a base-analog classifier on a particular plasmid-like DNA fragment (mitochondrial DNA to be specific). We reached out to you at an event a week ago and you indicated us to contact you directly through GitHub.
We generated the following training dataset:
A control, without base analog, covering around 75% of the sequence from our plasmid (fragments of size 3000bp).
A set of pure BrdU-labelled reads, around 3000bp each, spanning the exact same sequences as the control.
This training data was generated with pore10 and pore09, and we have trained one classifier for each version, employing the following steps:
Base-call all reads using the relevant “sup” base-caller (Dorado).
Down-sample regions to insure a limited difference in coverage across the different regions of the contig.
Generate training chunks using ‘remora dataset prepare’. We crop the reads at 40bp at each end by providing a bed file, we use the k-mer-level table provided by Nanopore, and focus on the motif T (‘--motif T 0’). Finally, we played with the chunk-context, using 50, 100 and 200 (repeated twice).
We create a config file using ‘remora dataset make_config’ and put a weight of 2 for the control samples, to avoid false positives.
We train the model using ‘remora model train’, using the ConvLSTM model. We played with some hyper-parameters (batch-size and learning rate mostly, but these did not make much difference).
We then use this classifier on real data, but observed stark differences depending on the chunk-size. Specifically, a whole region of the plasmid, of size 600-700bp, harbors the following predictions for a large number of reads:
BrdU-labelled when chunk-context is 100 or 200.
Unlabelled when chunk-context is 50.
On the rest of our sequence (16kb), the performances are very similar. Maybe of importance: this sequence falls within the regions covered by the training data.
Would you have any material that could help us shed some light on this phenomenon? We are unsure which results to trust, although an external tool on pore09 yields predictions similar to the chunk-size 50.
Thank you in advance for your help.
Best regards,
Chih-Yao (@chihyaochung) and Soufiane
The text was updated successfully, but these errors were encountered:
saroudant
changed the title
Sensitivity on chunk-size parameter
Sensitivity on chunk-context parameter
Oct 19, 2024
Dear Remora development,
We are contacting you regarding an issue we are facing when training a base-analog classifier on a particular plasmid-like DNA fragment (mitochondrial DNA to be specific). We reached out to you at an event a week ago and you indicated us to contact you directly through GitHub.
We generated the following training dataset:
This training data was generated with pore10 and pore09, and we have trained one classifier for each version, employing the following steps:
We then use this classifier on real data, but observed stark differences depending on the chunk-size. Specifically, a whole region of the plasmid, of size 600-700bp, harbors the following predictions for a large number of reads:
On the rest of our sequence (16kb), the performances are very similar. Maybe of importance: this sequence falls within the regions covered by the training data.
Would you have any material that could help us shed some light on this phenomenon? We are unsure which results to trust, although an external tool on pore09 yields predictions similar to the chunk-size 50.
Thank you in advance for your help.
Best regards,
Chih-Yao (@chihyaochung) and Soufiane
The text was updated successfully, but these errors were encountered: