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

Why should the number of SAP representation protein sequence file lines and the number of Canonical compound SMILE file lines match? #9

Open
CallMeDek opened this issue Sep 22, 2022 · 2 comments

Comments

@CallMeDek
Copy link

Hi,

I am trying to get results of my own data with your model.

(1) According to the file "DeepAffinity_inference.sh", it seems that the number of lines for input protein sequences file and compound file must matches like below.
스크린샷, 2022-09-22 10-46-42
Is it mean that the number of each entity in both files have to be matched or literally the the number of lines of both files have to be matched?

(2) I got two files for my own data after following your manual.
Could you tell me if their entities' structure are correct for model input?

  • CID_Smi_Feature:
    스크린샷, 2022-09-22 11-31-44
  • protein_grouped_finalPresentation
    스크린샷, 2022-09-22 11-33-55

Thank you,
CallMeDek

@Shen-Lab
Copy link
Owner

Shen-Lab commented Sep 23, 2022

The number of the protein sequences and that of compound files are asked to be equal because we are predicting given pairs of proteins and compounds. So the k-th row of the protein file is paired to the k-th row of the compound file. If you are interested in cross prediction for all combinations of given proteins and given compounds, you can write a simple script to prepare the two files (with repeats) without having to change our scripts. Otherwise you can change the script through the for loop (use nested for loops instead).

I am not sure what exactly you are asking in the second question. Please kindly detail your question and could @AstroSign please follow up if possible?

@AstroSign
Copy link
Collaborator

AstroSign commented Sep 23, 2022 via email

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