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
At sometimes, the "ref" column: “the SNP-level allele-specific read counts of the reference allele” contains the float type values, for example, DNA methylation. So, is it practical to run the ASEP software after int(float value)? or do you have any suggestions?
thank you.
The text was updated successfully, but these errors were encountered:
Hi Charles,
ASEP is an RNA-seq data-based method and only takes integer value as input for ‘ref’ and ‘total’. I am not quite familiar with DNA methylation. But as long as you think the changings in ratio of ref/total before and after the rounding is similar, then I would say rounding to integer would be a good way to handle the data.
Best,
Jiaxin
From: Charles <notifications@github.com>
Reply-To: Jiaxin-Fan/ASEP <reply@reply.github.com>
Date: Wednesday, August 5, 2020 at 3:21 AM
To: Jiaxin-Fan/ASEP <ASEP@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Subject: [External] [Jiaxin-Fan/ASEP] How to process the float values (#1)
At sometimes, the "ref" column: “the SNP-level allele-specific read counts of the reference allele” contains the float type values, for example, DNA methylation. So, is it practical to run the ASEP software after int(float value)? or do you have any suggestions?
thank you.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#1>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ANIYGOHKMTNNJ3LTP2JAPCTR7ECAJANCNFSM4PVFPOMA>.
At sometimes, the "ref" column: “the SNP-level allele-specific read counts of the reference allele” contains the float type values, for example, DNA methylation. So, is it practical to run the ASEP software after int(float value)? or do you have any suggestions?
thank you.
The text was updated successfully, but these errors were encountered: