search

asapdiscovery / asapdiscovery.github.io

3 stars 4 forks source link

TEP blurb #87

Open LizbeK opened 1 year ago

LizbeK commented 1 year ago

2 observations that I don't have suggestions for how to solve. 1) TEPS were started in SGC as indicated, but is still part of the CMD (https://www.cmd.ox.ac.uk/resources/teps). Do we need to link to that webpage also? 2) I know this is my personal bugbear, but since a large part of my team is not officially XChem, I worry that the massive effort from the CMD get lost because we are always grouped in with them (understand me correctly, Daren and co are some of my favourite people and we are heavily relient on each other). The final TEP would also include first round follow-up designs from PostEra. Two choices, we either take out the Diamond hyperlink; or add a sentence and acknowledge that data for the TEPS are from CMD, Diamond, PostEra and multiple academic partners.

LizbeK commented 1 year ago

TEP blurb...maybe we should revert to what is in the grant:

The concept and impact of performing Target Enablement systematically was established in 2015-2021 through a £9m Wellcome Trust funded strategic grant at what was then the University of Oxford site of the Structural Genomics Consortium

jchodera commented 1 year ago

This is all great feedback! I'll propose some changes and tag you for review.

Regarding the first-round TEP follow-ups: I was under the impression that the first-round fragment progression happens in P2 with Diamond ordering from Enamine REALSpace, not in P3 at PostEra. Regardless, we want to acknowledge everyone who has contributed (both people and Projects/Cores), and can work out a way to make sure everyone gets credit!

LizbeK commented 1 year ago

Regarding first-round TEP follow-ups: it has become a grey area. In reality both Diamond and PostEra starts working on the fragment data as soon as its availible.