Re: [galaxy-user] all FPKMs are 0 in the tmap files produced by cuffcompare

2014-01-14 Thread Jennifer Jackson
Hi Yang, I am going to give you a method to do this - in short you'll be splitting the dataset into three parts, altering two of them, then merging the three final results datasets together. A workflow could be extracted from the history once you have completed this method, saved for future u

Re: [galaxy-user] all FPKMs are 0 in the tmap files produced by cuffcompare

2014-01-14 Thread Yang Bi
r the initial letters and not the entire words? Thanks Yang - 原始邮件 - 发件人: "Jennifer Jackson" 收件人: "Yang Bi" 抄送: galaxy-user@lists.bx.psu.edu 发送时间: 星期一, 2014年 1 月 13日 下午 6:54:53 主题: Re: [galaxy-user] all FPKMs are 0 in the tmap files produced by cuffcompare

Re: [galaxy-user] all FPKMs are 0 in the tmap files produced by cuffcompare

2014-01-13 Thread Jennifer Jackson
Hello Yang, Glad the problem was isolated - the mismatched chromosomes is definitely something to be fixed. The tools in 'Text Manipulation" can help. The tool "Change Case of selected columns" can change the case for you. Click on the pencil icon after running the tool to reassign the datat

Re: [galaxy-user] all FPKMs are 0 in the tmap files produced by cuffcompare

2014-01-13 Thread Yang Bi
t;4.076844"; I checked the chromosome names and I realized that the BAM outputs use lower cases for "RNAME", eg. "chr1" while my gff3 file uses initial capital letters for "seqId", eg "Chr1". Could this be the problem? What is the fastest way to convert

Re: [galaxy-user] all FPKMs are 0 in the tmap files produced by cuffcompare

2014-01-13 Thread Jennifer Jackson
Hello, It looks like the data is mapping as novel - not linked with the reference annotation. There can be a few factors that can cause this to occur for part of a dataset (often desirable) but when it occurs for an entire dataset, there is often a data mismatch or parameter issue. The first