<p>Regarding your comment:</p>

<blockquote>
  <p>This GFF file does not have the same key nomenclature as seen in
  ENSEMBL or USCS</p>
</blockquote>

<p>The link you have provided corresponds to an entry in <code>Genbank</code> format and not to <code>GFF</code> format. I believe you need a file in <code>GTF</code> format in particular.</p>

<p>Nevertheless, given the fact that you have manually added the corresponding entries to the reference <code>fasta</code> and <code>gtf</code> files prior to <code>mkref</code>, you should have seen your gene of interest in the output. I would double check one of the original fasta headers and original gtf entries in the reference file and match these for the new entry.</p>

CC BY-SA 4.0
2020-03-03T14:07:03.130Z
Thank you for the response. I figured out what the problem was, I was given an incorrect accession number! However, after finding & reading through this: https://support.10xgenomics.com/single-cell-gene-expression/software/pipelines/latest/using/tutorial_mr, I can see how my approach may have been problematic anyway because of the NCBI keys. Fixed it & I'm creating the custom reference. FYI, the link does go to a genbank file, but when downloading the information, you have the option of choosing the format (fasta, genbank, gff), but you are absolutely correct about the GTF vs GFF. Danke!
cer
CC BY-SA 4.0
2020-03-02T18:52:17.277Z
2020-03-02T18:58:16.967Z
2020-03-02T18:58:16.967Z
haci
<p>I am using several cellranger tools/pipelines to analyze some data, specifically, mkgtf, mkref, count, and aggr. I am using mkgtf and mkref to include a PI-synthesized protein to my reference. I have finished the analysis but am not seeing the protein in my output, so I am going back to the start to verify the process. </p>

<p>Unlike the documentation (<a href="https://support.10xgenomics.com/single-cell-gene-expression/software/pipelines/latest/advanced/references" rel="nofollow noreferrer">https://support.10xgenomics.com/single-cell-gene-expression/software/pipelines/latest/advanced/references</a>), my GTF file was not downloaded from ENSEMBL or UCSC, but NCBI (<a href="https://www.ncbi.nlm.nih.gov/nuccore/AY678269.1?report=genbank" rel="nofollow noreferrer">https://www.ncbi.nlm.nih.gov/nuccore/AY678269.1?report=genbank</a>). This GFF file does not have the same key nomenclature as seen in ENSEMBL or USCS.</p>

<p>I did use the mkgtf tool, but the created file is identical to the input. </p>

<pre><code>cellranger mkgtf custom_ref/AY678269_genes.gtf reference_data/AY678269_mkgtf_genes.gtf
</code></pre>

<p>I went ahead and used cat to add the fasta and gtf file from the synthesized protein to the respective reference fasta and gene files, then ran mkref. </p>

<p>The s.protein is in the fasta file: </p>

<pre><code>&gt;lcl|AY678269.1_cds_AAV52169.1_1 [protein=tandem-dimer red fluorescent protein] [protein_id=AAV52169.1] [location=1..1431] [gbkey=CDS] 
</code></pre>

<p>as well as the gene list </p>

<pre><code>##sequence-region AY678269.1 1 1431
##species https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi?id=32630
AY678269.1      Genbank region  1       1431    .       +       .
AY678269.1      Genbank CDS     1       1431    .       +       0
</code></pre>

<p>However this protein is not found in the output...surely I must have made an error. Does anyone have any ideas about what I could be doing incorrectly?</p>

<p>Do I need to change the entire nomenclature of the GFF keys to match what I see from ENSEMBL (e.g., gene_id ""; gene_version ""; transcript_id, etc...)?</p>

<p>Any assistance is greatly appreciated.</p>

<cellranger>
Using cellranger mkgtf w/ NCBI GFF3 files
# Using cellranger mkgtf w/ NCBI GFF3 files

(Asked by: username_0 on 2020-03-02)

I am using several cellranger tools/pipelines to analyze some data, specifically, mkgtf, mkref, count, and aggr. I am using mkgtf and mkref to include a PI-synthesized protein to my reference. I have finished the analysis but am not seeing the protein in my output, so I am going back to the start to verify the process. 
Unlike the documentation (https://support.10xgenomics.com/single-cell-gene-expression/software/pipelines/latest/advanced/references), my GTF file was not downloaded from ENSEMBL or UCSC, but NCBI (https://www.ncbi.nlm.nih.gov/nuccore/AY678269.1?report=genbank). This GFF file does not have the same key nomenclature as seen in ENSEMBL or USCS.
I did use the mkgtf tool, but the created file is identical to the input. 
cellranger mkgtf custom_ref/AY678269_genes.gtf reference_data/AY678269_mkgtf_genes.gtf

I went ahead and used cat to add the fasta and gtf file from the synthesized protein to the respective reference fasta and gene files, then ran mkref. 
The s.protein is in the fasta file: 
>lcl|AY678269.1_cds_AAV52169.1_1 [protein=tandem-dimer red fluorescent protein] [protein_id=AAV52169.1] [location=1..1431] [gbkey=CDS] 

as well as the gene list 
##sequence-region AY678269.1 1 1431
##species https://www.ncbi.nlm.nih.gov/Taxonomy/Browser/wwwtax.cgi?id=32630
AY678269.1      Genbank region  1       1431    .       +       .
AY678269.1      Genbank CDS     1       1431    .       +       0

However this protein is not found in the output...surely I must have made an error. Does anyone have any ideas about what I could be doing incorrectly?
Do I need to change the entire nomenclature of the GFF keys to match what I see from ENSEMBL (e.g., gene_id ""; gene_version ""; transcript_id, etc...)?
Any assistance is greatly appreciated.

**Tags:** cellranger

---

## 1 answers

### Answer by username_1 on 2020-03-02. Score: 1 | Accepted answer

Regarding your comment:

> This GFF file does not have the same key nomenclature as seen in
> ENSEMBL or USCS

The link you have provided corresponds to an entry in `Genbank` format and not to `GFF` format. I believe you need a file in `GTF` format in particular.

Nevertheless, given the fact that you have manually added the corresponding entries to the reference `fasta` and `gtf` files prior to `mkref`, you should have seen your gene of interest in the output. I would double check one of the original fasta headers and original gtf entries in the reference file and match these for the new entry.

> **Comments:**
> **username_0**: Thank you for the response. I figured out what the problem was, I was given an incorrect accession number! However, after finding & reading through this: https://support.10xgenomics.com/single-cell-gene-expression/software/pipelines/latest/using/tutorial_mr, I can see how my approach may have been problematic anyway because of the NCBI keys. Fixed it & I'm creating the custom reference. FYI, the link does go to a genbank file, but when downloading the information, you have the option of choosing the format (fasta, genbank, gff), but you are absolutely correct about the GTF vs GFF. Danke!  

---

