# What is the meaning of Reference Gene Model in FPKM Tools in Galaxy?

**URL:** https://help.galaxyproject.org/t/what-is-the-meaning-of-reference-gene-model-in-fpkm-tools-in-galaxy/13141
**Category:** Uncategorized
**Tags:** bed, reference-annotation, rseqc\_fpkm\_count
**Created:** [August 6, 2024, 11:48am UTC](https://help.galaxyproject.org/t/what-is-the-meaning-of-reference-gene-model-in-fpkm-tools-in-galaxy/13141 "2024-08-06T11:48:48Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Dr.Lida](https://avatars.discourse-cdn.com/v4/letter/d/da6949/32.png) [@Dr.Lida](https://help.galaxyproject.org/u/Dr.Lida)
#### Post date: [August 6, 2024, 11:48am UTC](https://help.galaxyproject.org/t/what-is-the-meaning-of-reference-gene-model-in-fpkm-tools-in-galaxy/13141/1 "2024-08-06T11:48:48Z")

</div>

Hi everyone, i have 3 question:

1. in “FPKM Counts” Tools, (that give us FPKM for each Gene), there is one Parameter as: “Reference Gene Model in BED format”, what is the meaning of that? It means the annotation file (GTF)?
2. If the answer is the annotation file(GTF) in the BED format, why does the downloaded annotation file from NCBI not have the ability to be converted to the BED format in Galaxy, while the annotation file(GTF) obtained from the Ensembl Plant is converted?
3. I did all Analysis using GTF file from NCBI, but now galaxy can not convert this GTF file to BED format, can i use GTF from Ensembl for this section? are the GTF files from different source the same?

---

<div class="post-metadata">

### Author: ![jennaj](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/jennaj/32/27_2.png) [@jennaj](https://help.galaxyproject.org/u/jennaj)
#### Post date: [August 6, 2024, 5:36pm UTC](https://help.galaxyproject.org/t/what-is-the-meaning-of-reference-gene-model-in-fpkm-tools-in-galaxy/13141/2 "2024-08-06T17:36:08Z")

</div>

Hi @Dr.Lida

These are good questions! 🙂 Reference annotation can vary quite a bit between data providers. Some tools expect the content in a variation of BED format and other tools expect a variation of GFF/GTF/GFF3 formats. The good news is that converting between these formats is usually possible.

Let’s break this down using the tool form and resources linked from it for context, then I’ll explain the steps to transform your data.

* * *

**Tool Form → RSeQC**

The top section where you input the gene model specifies that it is expecting a **BED12** input (toggle _accepted formats_). That means a BED dataset with 12 columns. UCSC originally designed the specification and has [a good description here](https://genome.ucsc.edu/FAQ/FAQformat.html#format1).

_Screenshot of the **Input** area_

![accepted-formats](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/6/6f95b5c67dbf862ab47a770e3b423fcf2448bc0f.png)

Next, further down on the tool form is the **Help** section. (scroll down)

_Quote from tool form_

> ### About RSeQC
> 
> The [RSeQC](http://rseqc.sourceforge.net/) package provides a number of useful modules that can comprehensively evaluate high throughput sequence data especially RNA-seq data. “Basic modules” quickly inspect sequence quality, nucleotide composition bias, PCR bias and GC bias, while “RNA-seq specific modules” investigate sequencing saturation status of both splicing junction detection and expression estimation, mapped reads clipping profile, mapped reads distribution, coverage uniformity over gene body, reproducibility, strand specificity and splice junction annotation.

Following the link to the author’s website at [RSeQC](http://rseqc.sourceforge.net/) finds this:

_Screenshot of RSeQC homepage_

![rseqc-homepage](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/f/fc8af2d6d164b51230fde91224961b30e617627f.png)

And at that page ([RSeQC: An RNA-seq Quality Control Package — RSeQC documentation](https://rseqc.sourceforge.net/#download-gene-models-update-on-12-14-2021)) more help is provided.

_Screenshot of RSeQC Gene Model page_

 ![rseqc-gene-model](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/d/d9636effd7cb98d9474ca654794dfee11cfc4174.png)

* * *

**What to do**

UCSC’s reference genomes are the version that the public Galaxy servers pre-index for tools. That means if you used a native index for other steps (like mapping) you can also source the bed12 from UCSC.

If you are using a reference genome that is not supported by UCSC, you can convert to BED12 from a standardized GFT format. UCSC has [another useful guide here for](https://genome.ucsc.edu/FAQ/FAQformat.html#format3) GFF/GTF/GFF3 formats.

If you have GTF now, first make sure the format is standardized. This usually means removing any extra headers that may have been added by the data provider, or you may need to transformation from GFF3 to GTF first, then convert to BED12.

_Screenshot of a search in the tool panel with the keyword **bed12** _

![search-bed12](https://us1.discourse-cdn.com/flex020/uploads/galaxy/original/2X/c/c799cd65169d8eacbdf3a24e896ce666fcd391c9.png)

I ran a test using a GTF input with the tool **Convert GTF to BED12** and it produced what I expected (match to the UCSC specification). **RSeQC** should be able to consume it fine. You can do the same for your reference annotation once in a standardized GTF format.

Shared history → [https://usegalaxy.eu/u/jenj/h/help-gtf-to-bed12](https://usegalaxy.eu/u/jenj/h/help-gtf-to-bed12)

A tool might be able to do the conversion automatically if the data is in a standardized GTF format. If a tool cannot do the transformation, double check the format, or consider doing the transformation yourself. We have a guide here about standardizing formats → [FAQ: Working with GFF GFT GTF2 GFF3 reference annotation](https://training.galaxyproject.org/training-material/faqs/galaxy/datasets_working_with_reference_annotation.html)

And these tutorials include examples of using **RSeQC** → [Galaxy Training!](https://training.galaxyproject.org/training-material/by-tool/iuc/gtftobed12.html)

* * *

So, that’s a lot of information! Please review and let us know if you need more help. You can share a history back with what you did, or at least the starting annotation file, and we can troubleshoot what to do next. 🧑‍🔬
