Skip to content
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

Binder/Non binder per site? #60

Closed
alejandrovr opened this issue Nov 11, 2019 · 6 comments
Closed

Binder/Non binder per site? #60

alejandrovr opened this issue Nov 11, 2019 · 6 comments

Comments

@alejandrovr
Copy link

Hello,

I was wondering if the prediction has to be made by site or globably. That is, will we be asked to predict binders and not binders for S1, for S2, ... or just binders and not binders for the whole protein?

Best regards and thanks for organizing these events,

Alejandro.

@davidlmobley
Copy link
Contributor

Do you have any input? I believe the current thinking is to release which sites the fragments bind in when we release the list of binders, and then give folks the option of what they want to do from there, but we aren't 100% decided.

cc @haroldgrosjean

@davidlmobley
Copy link
Contributor

Also @MehtapIsik and @bergazin

@haroldgrosjean
Copy link
Collaborator

Hi Alejandro,

The fragments were found to bind at these sites. Thus, it would make more sense to focus your efforts there. However, the presence of false negatives is a possibility and any information (including outside of the sites) that would enable us to identify those would be a plus!

I hope that helps,

Harold

@alejandrovr
Copy link
Author

Yes, sorry, I was not referring to the whole protein, but rather the difference between discriminating binder vs non binder at each site, OR discriminating binder vs non binder in any of the sites. So 4 lists of binder/not binder (S1,S2,S3,S4) or just one. I understand is the second option what you are looking for.

@davidlmobley
Copy link
Contributor

Yes. Sorry, I'm just submitting something to clarify this and also add the submission format.

@davidlmobley
Copy link
Contributor

Closed by #62

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants