SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Biotech / Medical : Trickle Portfolio

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: tuck who wrote (317)1/2/2001 7:38:49 PM
From: Pseudo Biologist  Read Replies (1) of 1784
 
Tuck, if I understand this, we are talking of a very fundamental limitation, one that people have known about for many years and unlikely to be "fixed" one of these days. The original article on FRET by a man named Forster was published in 1948; BRET, of course, is a slight twist on the basic FRET concept. The fundamental limitation is in the physics of (F/B)RET whereby donor/acceptor partners need to be within some critical distance for the measurement to be possible. For particular proteins one could, I guess, tweak the system to make it work. This would not be possible in general protein-protein mapping proteomics projects, but may be doable for small molecule screening and a *given* pair of interacting proteins. If you really, really want to use the BRET system and your pair does not appear to interact by BRET even though you know it does, then tweaking at the molecular biology level may allow you to "fix" the problem for the particular case. An interesting survey may be found in ncbi.nlm.nih.gov (admittedly full-text would be a lot more informative here, but I think you get a flavor from the abstract on the main issues at hand: this is where I would start with the "tweaking")

Turns out a very tricklish, formerly very active, SI contributor, Richard Haugland of Molecular Probes, would know this area hands down. If anyone is willing to "resurrect" him ...

PB
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext