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
Hi,
I am testing mirdeep2.pl on two reference bovine reference genomes (UMD3.1 and ARS-UCD1.2).
ARS-UCD1.2 is the most recently published bovine reference genome.
I get almost the same expressed mirRNAs with both references, however, with UMD3.1 some of the expressed mirRNAs have significant (yes) randfold p-values and some not significant (no). Surprisingly all expressed mirRNAs with ARS-UCD1.2 have thier randfold p-values not significant and non with a significant p-value.
Is this something you have observed before? Could it be something inherently related to the difference in the two genomes?
Thank you,
Robert
The text was updated successfully, but these errors were encountered:
Hi Robert,
I have not seen this before but since this is randfold related it may be simply a normal result.
To check this I would compare the precursor sequences where you get different results and see if has todo with that. Otherwise I would run randfold a few times on one of the significant candidates and see what the pvalue is.
Hi Marcel, I didnt manage to resolve this but I decided to use the results from UMD3.1 (the older reference) as the counts for the miRNAs were generally concordant
Hi,
I am testing mirdeep2.pl on two reference bovine reference genomes (UMD3.1 and ARS-UCD1.2).
ARS-UCD1.2 is the most recently published bovine reference genome.
I get almost the same expressed mirRNAs with both references, however, with UMD3.1 some of the expressed mirRNAs have significant (yes) randfold p-values and some not significant (no). Surprisingly all expressed mirRNAs with ARS-UCD1.2 have thier randfold p-values not significant and non with a significant p-value.
Is this something you have observed before? Could it be something inherently related to the difference in the two genomes?
Thank you,
Robert
The text was updated successfully, but these errors were encountered: