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

[Strategy Market] [Switch] Helix Composition #22

Open
vineetsk1 opened this issue Jun 29, 2015 · 1 comment
Open

[Strategy Market] [Switch] Helix Composition #22

vineetsk1 opened this issue Jun 29, 2015 · 1 comment

Comments

@vineetsk1
Copy link
Owner

Original Author: Brourd
Original Link: https://getsatisfaction.com/eternagame/topics/-strategy-market-switch-helix-composition

First, we'll define a helix with this particular strategy as being a continuous series of consecutive base pairs. For now, all loops will terminate a helix.

Second, let's separate the helices into classes.

Active helices are mobile. These are the dynamic elements of the RNA molecule, and represent those helices that unfold and transform into other helices or single stranded regions.

Passive helices are immobile. These are the static elements of the RNA molecule, and represent the helices that should be present in most of the statistical ensemble of molecules, not transforming into other structures.

Third, the strategy.

The number of G-C base pairs in active helices should ideally be set at a count of two.

There are a few penalties and conditions for helices where the count exceeds two.

If the number of G-C base pairs in an active helix is equal to two
Then reward.

If the number of G-C base pairs in an active helix exceeds a count of two,
And there are no G-U base pairs between the G-C base pairs,
Then penalize for each helix that exceeds the limit.

If the number of G-C base pairs in an active helix exceeds the count of two,
and there are G-U base pairs between the G-C base pairs in the helix,
then neither reward nor penalize up to a maximum of 3 G-C base pairs and two G-U base pairs between the G-C base pairs.

If it's not possible to code these conditions, then penalize for each helix that exceeds a count of two G-C base pairs.

The penalties and conditions for active helices with fewer G-C base pairs are different.

If an active helix has a count of 0 G-C base pairs,
Then penalize. And penalize some more.

If an active helix has a count of 1 G-C base pair,
Neither penalize or reward.
Unless the active helix has a G-U base pair as well, then penalize.

Penalize all active helices with two or fewer base pairs.

Passive Helices

Penalize all passive helices with a length of three or fewer base pairs.

Penalize all passive helices where the number of G-C base pairs is equal to or less than half of the total number of base pairs.

Penalize all passive helices where the dot plot for that helix is contains any alternative pairing probabilities.

As a visual example

The three base pair helix seen in this dotplot would be in the passive class.
There would be two penalties.
One for being less than four base pairs in length, and another for having any alternative pairing probabilities visible on the dotplot for that helix. These pairiing probabilities would be defined by the area bound within the red lines.

Addendum Once the length of a passive helix exceeds 7 base pairs, the G-C requirement penalty is no longer quite as important, so it may do well to focus solely on the dotplot condition for helices that are 7 base pairs or more in length.

All of the strategies should be coded to be scored in all models available.

@vineetsk1
Copy link
Owner Author

Implemented with 61 lines of code.

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

No branches or pull requests

1 participant