Hello Nancy,

The attribute sounds as if it is the correct place in the reference annotation file (the 9th field), but perhaps there are other format/content problems with the file. Do you have a tss_id? Do you have exons labeled?


This is the area of the manual that covers the formatting and usage of these attributes:
http://cufflinks.cbcb.umd.edu/manual.html#cuffdiff_input

I am not sure if I understand what you mean by input/writing codes. But if you need more help after reviewing the manual, please let us know,

Best,

Jen
Galaxy team

On 1/18/14 9:06 AM, Yanxiang Shi wrote:
Hi all,

I've been trying to use the cufflinks-cuffmerge-cuffdiff flow to analyze my RNAseq data. However, cuffmerge lost my p_id. My p_id was originally from changing the protein_id to p_id by myself in the gtf file. The current p_id showed up in the same attributes column as gene_id in the gtf file. Does anyone know how to make it reachable by cuff? I'm using galaxy public platform. Apparently in the history people say solving the problem by writing an extra code. But I cannot find anywhere to input codes in galaxy.

Do I have to run everything on my own computer?

Thanks a lot!!!!!

Nancy



___________________________________________________________
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using "reply all" in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

   http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

   http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:

   http://galaxyproject.org/search/mailinglists/

--
Jennifer Hillman-Jackson
http://galaxyproject.org

___________________________________________________________
The Galaxy User list should be used for the discussion of
Galaxy analysis and other features on the public server
at usegalaxy.org.  Please keep all replies on the list by
using "reply all" in your mail client.  For discussion of
local Galaxy instances and the Galaxy source code, please
use the Galaxy Development list:

  http://lists.bx.psu.edu/listinfo/galaxy-dev

To manage your subscriptions to this and other Galaxy lists,
please use the interface at:

  http://lists.bx.psu.edu/

To search Galaxy mailing lists use the unified search at:

  http://galaxyproject.org/search/mailinglists/

Reply via email to