If a tie arises in the # of interaction types w Arpeggio, rinrus could print out the filtered information in node_info.dat corresponding to the tied fragments. User could then sort based first on attractive SIFs then hydrophobic/clashing SIFs. Then could manually sort the remaining fragments by contact count. How can we automate any of this?
Can the driver be updated to scan the freq_per_res files and send warnings to the log file when there are ties in interaction type or interaction count?
If a tie arises in the # of interaction types w Arpeggio, rinrus could print out the filtered information in node_info.dat corresponding to the tied fragments. User could then sort based first on attractive SIFs then hydrophobic/clashing SIFs. Then could manually sort the remaining fragments by contact count. How can we automate any of this?