Link to this post | posted 19 Nov, 2015 04:29

cdshaffer

Maybe Steve or Dan can confirm but I believe the database has grown too large for the tasks you want. Looking at Actino_draft there are over 1100 phage and almost 12,000 phams. I don't think I have been able to get a pham circle since the phage count went above about 200. I can't image how small the font would need to be to have the names of 1100 phage around a circle. There are other ways of looking at pham data [but it won't be pretty pictures]. Its fairly easy to generate a list of all genes in a pham using either the mysql command line or extracting the data out of the pham table. What pham are you interested in? Would a list of the gene members for a particular pham be helpful?

Link to this post | posted 02 Nov, 2015 16:37

cdshaffer

OK I will look into it. Sorry for being late; I am at peak teaching, things should calm considerably. I will try to post updates to this posting as I track down the issue. OK figured out that the 117th pham is pham 14107. This corresponds to gene 1 on the phamerator map. It looks like this is the same (or at least related to) the issue with Dori 94. I have now precisely mapped that gene by running auto-annotation in DNA Master. Turns out the problem gene is a wrap-around gene called by glimmer that goes from base 444 down to base 1, then end of phage down to 68540. Starterator is not able to handle these right now due to the way that they are handled by Phamerator when importing genes like this. Working on a solution…. Ok I did the quick and dirty fix, added code to skip any genes that look problematic. In this case if the length of the gene in the database does not equal the distance between the given start and stop codons then something is awry, so skip the gene. This fix is not yet submitted to the main Starterator branch so your version does not have it, only my local copy. I want to do more testing before I submit. In the mean time I did try my patch on Yara and it went all the way through without crashing. I have posted the final pdf report here. Thanks for the report, another bug squashed! Now if I can just find the time to do all the testing so I can submit all these bug fixes I have found. Edited 03 Nov, 2015 02:10

Link to this post | posted 21 Oct, 2015 03:07
cdshaffer	Ok I tweeked the entry for missing phage.

Link to this post | posted 19 Oct, 2015 16:23
cdshaffer	Dan, Is there anyway to make this post sticky so it stays on top of the list. Might be helpful to new faculty to read this post first and try solutions before posting a question. Could we even change the title to add something like READ THIS FIRST or START HERE. Chris

Link to this post | posted 15 Oct, 2015 21:16
cdshaffer	Ok good to know. I will add this issue to the starterator troubleshooting thread.

Link to this post | posted 12 Oct, 2015 18:57

cdshaffer

It looks like (based on the new 2016SEAVM) that the default database for Starterator is Mycobactriophage_Draft so even if phamerator has Actino_Draft, Starterator may not be using it. To check your instance, open starterator, go to the top magically appearing menu items and select edit-> preferences. In the dialog box, check that the database name in there also set to Actino_draft. It may still be set to Mycobactriophage_Draft. If so, edit that entry to Actino_Draft and hit OK. Once I had done that with my 2016SEAVM I was able to completely process Bipper (great phage name by the way). Also, since I ran the whole phage to check that everything was working with Bipper, I posted the whole phage starterator analysis report as a PDF here. Feel free to download and use if you want. I will figure out how to update the default database for starterator. I don't have direct access to the code for Starterator but I can post a pull request which should fix the issue once it is accepted. That should fix things for future users. Thanks for being the first and discovering the issue of the old default setting for the starterator database. Edited 12 Oct, 2015 21:45

Link to this post | posted 08 Oct, 2015 17:28

cdshaffer

I would be happy to look into this. It is pretty unlikely that you are doing something wrong. To start I need to make sure I have the same database to see if I can replicate the problem. If you open up Phamerator and select Edit -> Preferences. You should see something like the picture I attached. Do you see the same Actino_Draft for the Database, or something else? If you do see Actino_Draft, can you check that your Ubuntu machine is able to get to the internet to download the most recent version of the database? To do that just open up a web browser in the ubuntu machine and see if you can get to sites on the internet like seaphages.org. Edited 08 Oct, 2015 17:33 36Kb

Link to this post | posted 24 Sep, 2015 19:59

cdshaffer

The fasta file from either source will work as input for another program but it can be a hassle if you want to see the sequences yourself. In that case you will probably want to reformat. On the web I use the EMBOSS tool called seqret to do that. Do a google search on "emboss seqret ebi" and pick the seqret server at www.ebi.ac.uk You can upload your fasta file and select "FASTA format" as the output format and all the sequences will be formatted so you can see the entire protein sequence without having to do so much horizontal scrolling.

Link to this post | posted 24 Sep, 2015 19:52
cdshaffer	In DNA Master: 1. DNA Menu, bottom item is "Save ORF's…" which will bring up the tool window 2. You will see a list of all the features in your phage 3. Select one or more by clicking, or use the "Select all genes" button 4. Go to the "Specify Export Files" tab 5. Use the checkboxes as appropriate to control what will be saved (e.g. "Peptide Sequences" 6. Click the "Save" button

Link to this post | posted 18 Sep, 2015 18:03
cdshaffer	Dan, Can you create a page that students can get to that has all the instructions for installing the machine just like on the protected /software/virtualmachine/ page? I would like to be able to point students to all those well written instruction on how to go about installing virtual machines once I give them the virtual disk I want them to use. thanks