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

Interactions insty fixes #1974

Merged
merged 7 commits into from
Nov 14, 2024
Merged

Conversation

karolamik13
Copy link
Contributor

I did the following things:
(1) added getInteractors() to obtain interactions for a particular residue

interactions.getInteractors('LEU1322A')
@> hb:VAL1335A-LEU1322A
@> hp:LEU1322A-PHE1304A
@> hp:TRP1389A-LEU1322A
@> hp:ILE1374A-LEU1322A
@> hp:VAL1335A-LEU1322A

(2) fixed getFrequentInteractors()
Before, we were overwriting one type of interaction if we had two for the same pair, and we didn't include reverse pairs.

It means that when we had such interactions for LEU1322A:
'hb:VAL1335A-LEU1322A',
'hp:LEU1322A-PHE1304A',
'hp:TRP1389A-LEU1322A',
'hp:ILE1374A-LEU1322A',
'hp:VAL1335A-LEU1322A'

We were obtaining only:
'hp:TRP1389A-LEU1322A',
'hp:ILE1374A-LEU1322A',
'hp:VAL1335A-LEU1322A'
because 'hb:VAL1335A-LEU1322A' was overwritten by 'hp:VAL1335A-LEU1322A', and 'hp:LEU1322A-PHE1304A' was ignored because counts were done by the second element (''hp:TRP1389A-LEU1322A') so PHE1304A was different. Now I included all of that.

I have changed some cutoffs, too.

@jamesmkrieger
Copy link
Contributor

(2) is a weird bug. Why did it overwrite things with different residues? Glad you fixed it anyhow

(1) sounds good

@karolamik13
Copy link
Contributor Author

Regarding (2):
It was because of this:
for ii in i:
m1 = resIDs_with_resChIDs.index((int(ii[0][3:]),ii[2]))
m2 = resIDs_with_resChIDs.index((int(ii[3][3:]),ii[5]))
InteractionsMap[m1][m2] = interaction_type[nr]+':'+ii[0]+ii[2]+'-'+ii[3]+ii[5]

When m1 and m2 were the same for two pairs of interactions, the first one was overwritten. I noticed that when the hydrogen bond pair disappeared and was replaced by hydrophobic interactions for the same residues. I was looking at what was wrong for 3 days (those two problems). I noticed that now because of the example I was testing. Before, I didn't have such a case.

@jamesmkrieger
Copy link
Contributor

Regarding (2): It was because of this: for ii in i: m1 = resIDs_with_resChIDs.index((int(ii[0][3:]),ii[2])) m2 = resIDs_with_resChIDs.index((int(ii[3][3:]),ii[5])) InteractionsMap[m1][m2] = interaction_type[nr]+':'+ii[0]+ii[2]+'-'+ii[3]+ii[5]

When m1 and m2 were the same for two pairs of interactions, the first one was overwritten. I noticed that when the hydrogen bond pair disappeared and was replaced by hydrophobic interactions for the same residues. I was looking at what was wrong for 3 days (those two problems). I noticed that now because of the example I was testing. Before, I didn't have such a case.

Ok

@karolamik13
Copy link
Contributor Author

Can we merge it James if you don't have other comments?

@jamesmkrieger
Copy link
Contributor

Can we merge it James if you don't have other comments?

I was going to look more and test parts and I think Anthony is going to too

@jamesmkrieger
Copy link
Contributor

Oh, I mixed up the PRs. Yes, this one we can merge

@karolamik13
Copy link
Contributor Author

Ok. Thank you :)

@karolamik13 karolamik13 merged commit 94bc3e9 into prody:main Nov 14, 2024
6 checks passed
@karolamik13
Copy link
Contributor Author

I was thinking of updating SignInt branch with those fixes and also hbp.so updates for Py3.11 and Py3.12 (#1982). Checks were not completed because of an FTP problem, which you fixed, and it was merged with SignInt, right? Those are all InSty fixes. What do you think?

@jamesmkrieger
Copy link
Contributor

Yes, merging the hpb ones into signInt makes sense

@jamesmkrieger
Copy link
Contributor

Or we could just merge the ftp changes first and then all the other PRs should be fine

@jamesmkrieger
Copy link
Contributor

Or we could just merge the ftp changes first and then all the other PRs should be fine

I just opened it again and it’s at #1988 so please can you approve it so we can merge it

@karolamik13
Copy link
Contributor Author

Ok. I will do it.

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

Successfully merging this pull request may close these issues.

2 participants