[DIYbio] Re: I'm curious, why don't we post open source sequences more often?

The reason is that people don't really say it's "open". Sequences are just shoved it databases that you have to find. 

A good start is here http://parts.igem.org/Main_Page

A lot of times people just know what they want for a sequence then look for a plasmid that has it. For example, I could say "I want a pUC ori, AmpR, CEN/ARS, leu2 auxotrophy, and lacZ MCS." I would know exactly what I want (pRS315, http://www.snapgene.com/resources/plasmid_files/yeast_plasmids/pRS315/). Then I would ask around colleagues for it.

There's not enough DIYbiologists to make a type of git really worth it. I know what most work on and if I needed to know one of their sequences I'd pop them an email or post here. Also for the git it's important to remember that unlike computing biology is extremely *context dependent*. One ribosomal binding site will give different expression per protein (ranging hundreds times of expression). If I wanted to express something, I wouldn't go to a registry like the parts registry, I'd go find it myself from a virus or go to the RBS calculator (https://salislab.net/software/)

What do you want? If you know send me an email anytime and I bet I could find it. Sharing the physical DNA is a whole other rant though.

-Koeng

On Monday, June 15, 2015 at 12:59:12 PM UTC-5, Jarrad wrote:
Hey Guys,

I see alot mentions to do with open science but I rarely see full open source sequences? Why is that?

Would DIYBio be served borrowing some concepts from the software world in terms of their Free & Open Source Software movement? as well as using version control (git?) to document the sequence history.

AFAIK the main reason is current approach is very much a bottom-up approach, where it's easier and cheaper to use various enzymes to chop and insert various segments until you get what you want, then to provide a protocol on how to repeat this process... but an alterantive would be to provide with a complete sequence first, then allow the "compiler" (lab monkey) to generate a protocol?

That way multiple people could use the same source code sequence, adapt and fork it, but ultimately use various different techniques/protocols (such as dna printing) to get to the end result.

Or is there some other reason I've overlooked?

--
-- You received this message because you are subscribed to the Google Groups DIYbio group. To post to this group, send email to diybio@googlegroups.com. To unsubscribe from this group, send email to diybio+unsubscribe@googlegroups.com. For more options, visit this group at https://groups.google.com/d/forum/diybio?hl=en
Learn more at www.diybio.org
---
You received this message because you are subscribed to the Google Groups "DIYbio" group.
To unsubscribe from this group and stop receiving emails from it, send an email to diybio+unsubscribe@googlegroups.com.
To post to this group, send email to diybio@googlegroups.com.
Visit this group at http://groups.google.com/group/diybio.
To view this discussion on the web visit https://groups.google.com/d/msgid/diybio/4849a09e-c061-431d-87eb-a6b9780c06d2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  • Digg
  • Del.icio.us
  • StumbleUpon
  • Reddit
  • RSS

0 comments:

Post a Comment