search

ConesaLab / SQANTI3

Tool for the Quality Control of Long-Read Defined Transcriptomes
GNU General Public License v3.0
198 stars 49 forks source link

Option to write TSV for each report table #218

Open diekhans opened 1 year ago

diekhans commented 1 year ago

It would be beneficial for sqanti_qc to have an option to write TSV files for the tables to allow extended analysis. It seems the only choice now is to parse it out of the HTML.

aarzalluz commented 1 year ago

Hi @diekhans -is there any specific piece of information that you are missing? Everything in the report (both HTML and PDF) is calculated using either the classification or junctions files.

diekhans commented 1 year ago

I wanted to be write code to compare the results from two sqanti3 runs. Yes, I could have recalculated from the classification or junctions files, however it would be much easier to have access to the data supporting the report.

Ángeles Arzalluz-Luque @.***> writes:

Hi @diekhans -is there any specific piece of information that you are missing? Everything in the report (both HTML and PDF) is calculated using either the classification or junctions files.

-- Reply to this email directly or view it on GitHub: https://github.com/ConesaLab/SQANTI3/issues/218#issuecomment-1692014494 You are receiving this because you were mentioned.

Message ID: @.> Hi @. -is there any specific piece of information that you are missing? Everything in the report (both HTML and PDF) is calculated using either the classification or junctions files.

-- Reply to this email directly, [2]view it on GitHub, or [3]unsubscribe. You are receiving this because you were mentioned. Message ID: @.***>

References

  1. https://github.com/diekhans
  2. https://github.com/ConesaLab/SQANTI3/issues/218#issuecomment-1692014494
  3. https://github.com/notifications/unsubscribe-auth/AAA23ZP5IJXCNCN6IS6TSK3XW55JNANCNFSM6AAAAAA34KKSSU