Link to this post | posted 19 Aug, 2020 20:00
DanRussell	Hey Steve, Seems to be working fine for me at the moment. –Dan

Link to this post | posted 09 May, 2020 20:35
DanRussell	Hi Fernando, No, "None" just means we haven't made a determination for that cluster yet, so it could be either. Some of the clusters are very well known at this point, while others are fairly new and we haven't taken a close look. –Dan

Link to this post | posted 09 Apr, 2020 00:23

DanRussell

Hi Susanne, The length disparity is almost certainly because of the terminal repeat. When I assembled your genome, it looked clear to me that your it had direct terminal repeats; there was an area of approximately double coverage (compared to the rest of the genome) and flanking reads that started on the same base. That's classic terminal repeat. In those cases, we generally report the genome with the terminal repeat on each end, as the DNA would actually appear in the phage capsid. The Metroid terminal repeat is around 10kb, which almost certainly accounts for the difference between your assembly and the final file. My initial assembly was also only ~140 kb, but once I added the second copy of the repeat, it went to ~150kb. Hope that makes sense, –Dan

Link to this post | posted 05 Apr, 2020 15:39
DanRussell	Hi Kyle, Here are a couple options: Sherwood Casjens' paper about using terminases to determine end types, but it also sort of explains what the ends types might be: https://www.ncbi.nlm.nih.gov/pmc/articles/PMC3082370/ A more recent paper about the program PhageTerm, which tries to predict end type from sequencing reads: https://www.nature.com/articles/s41598-017-07910-5 Take care, –Dan

Link to this post | posted 20 Mar, 2020 01:20
DanRussell	Hi Dan and D'Andrew, Interesting. I can tell you (as the person who programmed the button on PhagesDB) that the same exact request is sent to GeneMark in both the Mayweather and Kenosha cases. So it must be GeneMark itself that is making a decision about which model/method to use. From the PhagesDB perspective, we don't distinguish based on length or anything. –Dan

Link to this post | posted 06 Feb, 2020 17:48

DanRussell

Hi Roy, I think you've caught things between versions of the Phamerator database. If you go to phamerator.org and click on the little dropdown database menu in the top left, it'll show you what version of the database you're currently viewing. As of now, I see Actino_Draft version 338. Meanwhile, Chris has recently made a link where you can check the version of the database Starterator is using. http://phages.wustl.edu/starterator/database.version Earlier today, it showed 337, but I just checked again and now it's showing 338, so hopefully things are back in sync now. –Dan

Link to this post | posted 06 Feb, 2020 16:16
DanRussell	Hi guys, For the record, here's a link to the Genome Announcement we wrote after sequencing that host. https://www.ncbi.nlm.nih.gov/pubmed/27013048 –Dan

Link to this post | posted 05 Feb, 2020 19:15
DanRussell	Hi Amy, You don't need to directly address it during your annotation, but it can be interesting to work with the students and see how that might affect the protein(s) in question. We also add those sequencing notes as sometimes they can help explain an odd phenotype (turbid AND clear plaques, e.g.). –Dan

Link to this post | posted 24 Jan, 2020 15:20
DanRussell	I think Chromebooks are a non-starter as far as DNA Master is concerned, but you can always pair a Chromebook user (who can still access Phamerator, GeneMark, PECAAN, etc.) with another student who has functional DNA Master. I've been successfully using DNA Master on a Windows 10 virtual machine for a while now, following the instructions here. –Dan

Link to this post | posted 21 Jan, 2020 15:48
DanRussell	Hi Fernando, Are you on a University/computer lab computer? Could it be that the system is somehow doing a regular cleanup operation to remove "unwanted" stuff and somehow DNA Master is getting caught in that? If so, it'd probably be easiest for your local IT to sort out. I have DNA Master installed on a Windows 10 virtual machine, and it's been stable for months. –Dan