Open PriceJon opened 5 years ago
Hi Jon,
We have run into similar issues in the past: some constraints never made it into the final structure. This could be some sort of issue with the hybrid-ss-min program, but we don't know exactly what causes it, except that it usually affects very short structure elements.
To check if the issue stands with comradesFold or hybrid-ss-min, I suggest you run hybrid-ss-min with a constraint file containing your single constraint and see what happens.
You should also double-check if positions 3998-4002 can in fact basepair with 5055-5059.
Please let me know once you've done these tests...
best, Greg
On Tue, Aug 27, 2019 at 3:27 PM PriceJon notifications@github.com wrote:
Hello,
I am hoping you can give some insight into an issue I am experiencing with comradesFold. I will try and give a minimal example. I have run comradesMakeContraints on a sequence that I wish to know the structure of. My .hyb files are sound and when plotting the chimeras there is evidence for a secondary structure. After running comradesMakeConstraints this structure is identified in the *ranked_interactions.txt file:
646 . 6556 RNA . . 5055 5059 . RNA . . 3998 4002 . count_total=5;count_last_clustering=5;two_way_merged=0;
This is then converted correctly into the *folding_constraints.txt file:
F 3998 5059 5
Then if I run comradesFold just with this 1 constraint it does not get included in the .accepted file and therefore it is not included in the final structure. But there are other contraints that have been identified by comradesMakeConstraints that are included. Have you noticed this behaviour before of some constraints not being included in any accepted files even though evidence has been found for them?
Any help / advice would be greatly appreciated.
Many thanks,
Jon
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/gkudla/comrades/issues/2?email_source=notifications&email_token=ABM3FBX5W47NFRDYMNMBMB3QGU2WNA5CNFSM4IQFFKBKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HHVNGWA, or mute the thread https://github.com/notifications/unsubscribe-auth/ABM3FBXSKRAF5QP5KT5NF4TQGU2WNANCNFSM4IQFFKBA .
Test 1: Can the position base pair:
3998-4002 GAAAT
5055-5059 ATTTC
Test2: hybrid-ss-min with constraints:
Does not produce a structure with the above contraints base paired.
These structures are the ones with the most evidence (and the most interesting), any suggestions for how I can include them? I have manually set --maxbp to a larger value but this still does not include them. I have checked a few of the constraints and it seems like hybrid-ss-min does not like to include things more than 300bp apart. Any advice appreciated.
Thanks,
Jon
Hi Jon,
So this seems to be a problem with hybrid-ss-min, though it is specific to your sequence. In general, hybrid-ss-min does allow constraints more than 300 nt apart.
The only things that occur to me are setting --maxbp manually (but you've done that already), setting --force on the command line (rather than through a constraint file), or trying to run mfold/hybrid-ss-min with constraints through their website. I know this sounds a bit desperate, but I vaguely remember that this worked for us at some point.
If this doesn't work, try contacting the developers of hybrid-ss-min, or use the ViennaRNA package instead.
best, Greg
On Tue, Aug 27, 2019 at 4:48 PM PriceJon notifications@github.com wrote:
Test 1: Can the position base pair:
3998-4002 GAAAT
5055-5059 ATTTC
Test2: hybrid-ss-min with constraints:
Does not produce a structure with the above contraints base paired.
These structures are the ones with the most evidence (and the most interesting), any suggestions for how I can include them? I have manually set --maxbp to a larger value but this still does not include them. I have checked a few of the constraints and it seems like hybrid-ss-min does not like to include things more than 300bp apart. Any advice appreciated.
Thanks,
Jon
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/gkudla/comrades/issues/2?email_source=notifications&email_token=ABM3FBUOP53ESMOJLBM3DATQGVEEZA5CNFSM4IQFFKBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5IGQYI#issuecomment-525363297, or mute the thread https://github.com/notifications/unsubscribe-auth/ABM3FBV2ISUA4VCW4YQODX3QGVEEZANCNFSM4IQFFKBA .
Thank for your replies, it has been really helpful.
I have tried to use force with no luck and I cannot use the online website as I need to run this ~1000 times which may get very tedious.
I will contact the hybrid-ss-min developers and also test the ViennaRNA package. Would you lie to inform you of the process?
Thanks again,
Jon
Yes, please keep me informed!
Greg
On Wed, Aug 28, 2019 at 11:35 AM PriceJon notifications@github.com wrote:
Thank for your replies, it has been really helpful.
I have tried to use force with no luck and I cannot use the online website as I need to run this ~1000 times which may get very tedious.
I will contact the hybrid-ss-min developers and also test the ViennaRNA package. Would you lie to inform you of the process?
Thanks again,
Jon
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/gkudla/comrades/issues/2?email_source=notifications&email_token=ABM3FBV4FNRVOKTFOLMTAGDQGZIHJA5CNFSM4IQFFKBKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5KVJEY#issuecomment-525685907, or mute the thread https://github.com/notifications/unsubscribe-auth/ABM3FBWBB6UYN5433DRKJ2TQGZIHJANCNFSM4IQFFKBA .
O.K no problem, I won't close this issue just yet.
Hello,
I am hoping you can give some insight into an issue I am experiencing with comradesFold. I will try and give a minimal example. I have run comradesMakeContraints on a sequence that I wish to know the structure of. My .hyb files are sound and when plotting the chimeras there is evidence for a secondary structure. After running comradesMakeConstraints this structure is identified in the *ranked_interactions.txt file:
646 . 6556 RNA . . 5055 5059 . RNA . . 3998 4002 . count_total=5;count_last_clustering=5;two_way_merged=0;
This is then converted correctly into the *folding_constraints.txt file:
F 3998 5059 5
Then if I run comradesFold just with this 1 constraint it does not get included in the .accepted file and therefore it is not included in the final structure. But there are other contraints that have been identified by comradesMakeConstraints that are included. Have you noticed this behaviour before of some constraints not being included in any accepted files even though evidence has been found for them?
Any help / advice would be greatly appreciated.
Many thanks,
Jon