GithubHelp home page GithubHelp logo

j-hudecek / tm2cbio Goto Github PK

View Code? Open in Web Editor NEW
1.0 1.0 2.0 352 KB

Utility to translate tranSMART export files to a directory ready for import to cBioPortal

License: GNU General Public License v3.0

Groovy 100.00%

tm2cbio's People

Stargazers

 avatar

Watchers

 avatar  avatar

Forkers

thehyve aderidder

tm2cbio's Issues

clinical meta file incorrect

I'm playing around with the newmetadataformat branch and I generated clinical files for the cluc. In the most recent cbioportal release the clinical files were split into a Sample file and a Patient file. Hence, the datatype tag should now be SAMPLE_ATTRIBUTES
Furthermore, the line in the datafile which contains "SAMPLE" is no longer allowed, since this is already defined by the datatype tag.

Patient / Sample flag in clinical data file should be customisable

Currently tm2cbio labels every attribute in the data_clinical it generated as a sample attribute, even e.g. Race. Even though it is not currently an issues, as we have only 1 sample per patient, it would be better if a user can specify whether a clinical attribute is a patient or a sample attribute.

Desired solution:
allow user to specify the type in the mapping file

clinical data header issue

I'm not 100% sure what's going on, but if my input clinical file contains:

PATIENT_ID RNAseq Illumina HiSeq2000\siNon-Targeting 1 RNAseq: Illumina HiSeq2000\siNon-targeting 1

This becomes

PATIENT_ID SAMPLE_ID siNon-Targeting_1 siNon-targeting_1

PATIENT_ID SAMPLE_ID RNAseq_Illumina_HiSeq2000/siNon-Targeting_1 RNAseq:_Illumina_HiSeq2000/siNon-targeting_1

STRING STRING STRING STRING

5 5 5 5

PATIENT_ID SAMPLE_ID siNon-Targeting_1 siNon-targeting_1

Even though I'll change the header anyway, apparently there is a bug here as the difference between:
RNAseq Illumina HiSeq2000\siNon-Targeting 1
and
RNAseq: Illumina HiSeq2000\siNon-targeting 1
is a ":" and a capital T and the difference we end up with is just the capital T. cBioPortal will not upload this, as it considers them the same.

expression file data column to datatype mismatch

The tM data contains e.g. a column LOG2E, which I would like to use as data for my cBio import. My mapping file contains:

expression file path=data_mrna.tsv

one of VALUE, LOG2E or ZSCORE

expression data column=LOG2E

In the code, the data column is used directly as datatype
datatype: ${typeConfig.data_column}
However, cBio wants CONTINUOUS as its datatype. I think we're missing a mapping from data column to datatype, as now the datafile contains the correct data, but the meta file is wrong:

datatype: LOG2E
stable_id: null

Support for segmented copy number data

Transmart can have gene, probe or region level copy number data. cBioPortal supports gene and region (segmented, perhaps it could be used also for probe level).

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.