# Pygenometracks: Changing bed style from flybase to UCSC

**URL:** https://help.galaxyproject.org/t/pygenometracks-changing-bed-style-from-flybase-to-ucsc/4588
**Category:** Uncategorized
**Created:** [October 9, 2020, 7:06pm UTC](https://help.galaxyproject.org/t/pygenometracks-changing-bed-style-from-flybase-to-ucsc/4588 "2020-10-09T19:06:19Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![MzwaneleN](https://sea2.discourse-cdn.com/flex020/user_avatar/help.galaxyproject.org/mzwanelen/32/1859_2.png) [@MzwaneleN](https://help.galaxyproject.org/u/MzwaneleN)
#### Post date: [October 9, 2020, 7:06pm UTC](https://help.galaxyproject.org/t/pygenometracks-changing-bed-style-from-flybase-to-ucsc/4588/1 "2020-10-09T19:06:19Z")

</div>

Hi. I want to change the bed style of my genes from flybase to UCSC format in galaxy using pygenometracks. Even though I try to set it to UCSC bed style the output is always flybase. I would appreciate any help. Thanks.

---

<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: [October 12, 2020, 11:48pm UTC](https://help.galaxyproject.org/t/pygenometracks-changing-bed-style-from-flybase-to-ucsc/4588/2 "2020-10-12T23:48:18Z")

</div>

Hi @MzwaneleN

This could be an input content problem, a tool option problem, or a previously undetected tool bug.

First, make sure you are using the most current version of the tool. Right now that is: `pyGenomeTracks plot genomic data tracks (Galaxy Version 3.5)`  
. If using a different version, try this one and see if that resolves the issue.

If the problem persists, a few more details would help. Where are you running the tool? A public Galaxy server? Which URL? Or explain if somewhere else – and maybe try at a public Galaxy server to see what happens as a comparison – if it works at a usegalaxy.\* server but not your own server, that narrows down what may be going wrong.

Let’s follow up from there.
