Foldit@Foldit
We're taking on SARS-CoV-2 with a series of new design puzzles. Can you help stop the viral helicase? 🧬
Learn more in this month's Lab Report: 📽️
#CacheChallenge #CitizenScience
0912
Posts with #CacheChallenge
Public posts on X that use #CacheChallenge.
Structural Genomics Consortium (SGC) @thesgconlineThe new #CACHEChallenge has officially been released. Computational chemists, #AI-savvy scientists from academia, biotech, and pharma take advantage of this chance and apply today if you think you can predict novel antagonists for MCHR1!
Matthieu Schapira @mattschapAnnouncing the 5th CACHE challenge. Predict novel antagonists for MCHR1, a GPCR with no structure in the PDB but hundreds of known ligands... Compounds will be tested in Bryan Roth @zenbrainest lab at UNC and results published. Apply by Feb 14th. #compchem
Structural Genomics Consortium (SGC) @thesgconlineThe first CACHE Challenge ends Jan. 31, 2022! Let's do this, the target is #LRRK2. Download & submit your application before it's too late! #CacheChallenge #DrugDiscovery #Target2035 #OpenScience #ParkinsonsDisease
Olexandr Isayev 🇺🇦🇺🇸 @olexandrLittle write-up for our CMU-UBC team competing (and winning 🏆 ) for CACHE #1 challenge! Finding small molecule hits with #compchem methods for a challenging LRRK2 WDR domain. #drugdiscovery
Sergei Yakneen @SergeiIakhninI started a new adventure, as CTO of @IsomorphicLabs, working with @demishassabis and an all-star team! Building on breakthroughs like AlphaFold from @DeepMind, we will reimagine drug discovery from first principles with AI. I am hiring top talent in ML, product, and engineering!
Matthieu Schapira @mattschapExperimental testing of 1739 compounds predicted by 23 CACHE #3 participants to bind the Macro domain of SARS-CoV-2 NSP3 is out. 28 compounds selected by 9 participants were confirmed and advanced to the hit-expansion round. #compchem @thesgconline
Bob the Grumpy Med Chemist @med_chemistThe differences in what I thought my neural intelligence machine (brain) was doing and the real world performance are well demonstrated by the damn awful grammar below... "benchmark" not "benchmarking"