-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Where to Put the Potency/Clearance Data for this Series #1
Comments
@mattodd |
@mattodd Main spreadsheet should be used for registration, to get a unique ID, and generate InChiKey etc. Biological results can go in a separate sheet, but using the unique ID molecule identifier as key. Does this make sense? |
@drc007 Yep, I think this is the best system. Does it make sense to add SB-044868 and the ALM-DAI focused array compounds to the spreadsheet now? I'm just thinking maybe it's best to consistently refer to them by OSA numbers from the beginning. Happy to add them now if you also think that's a good idea! |
@danaklug If you are willing to do that it would be great. |
@drc007 No problem! |
Okay, this is done - I've just filled in SMILES, InCHIKey, name, and MW. @fidiris @rhanson1046 FYI: All ALM compounds now have OSA IDs. |
Excellent!! |
Just to summarise and close this issue. New compounds will be assigned an OSA ID and added to the master sheet. Once we get biological data back, this will go in a separate tab using the OSA ID as the molecule identifier. Link to the sheet can be found here |
The inherited data for this series, and the data we're likely to acquire soon, will consist of whole cell potency vs MRSA and in vitro clearance rates. These are different from the typical data we'll be acquiring for the fragments in Series 1, in the mur ligase project.
Yet we really ought to try to reduce fragmentation and keep data in one place.
Shall we upload the inherited data to the current OSA spreadsheet, in a separate tab? Danger: if we use one numbering system for both series (we should), we may become confused as to where we're up to.
Ping @drc007 for opinion, as well as anyone else.
The text was updated successfully, but these errors were encountered: