[Strategy Market] Severn strategies to try and fail at least once

  • 1
  • Idea
  • Updated 8 years ago
[Strategy Market]
this includes some 'bad' strategies - hoping to do badly enough that the bots can learn that it's no good

1) any one base not being used at all

2) any two bases not being used at all

3) melting point not 67 (every degree away counts against) - or some other 'optimal' temperature

4) 50% of base pairs are GC

5) half the bases (paired or unpaired) are G (or any other percentage - or any other base)

6) R (number of repeated sequence of 3 base pairs) x (L+N) (number of loops+number of necks)

7) one half of the chain has all of the CU the other half has all of the AG
Photo of Edward Lane

Edward Lane

  • 139 Posts
  • 8 Reply Likes

Posted 8 years ago

  • 1
Photo of Edward Lane

Edward Lane

  • 139 Posts
  • 8 Reply Likes
Just had a thought - when you get around to coding them, if they are getting a negative score can you optimise them to be as 'bad as possible' and if they are getting a positive score can you optimise them to be as good as possible. Cheers

Those that get really bad scores might be more useful (as something to eliminate) compared to those that are just a little bit bad :)
Photo of Edward Lane

Edward Lane

  • 139 Posts
  • 8 Reply Likes
wanted to edit 5) into 4 seperate tests - but having commented looks like that's locked now,

5) a) half the bases (paired or unpaired) are G (or any other percentage)
b) half the bases (paired or unpaired) are U (or any other percentage)
c) half the bases (paired or unpaired) are A (or any other percentage)
d) half the bases (paired or unpaired) are C (or any other percentage)

:)
Photo of Edward Lane

Edward Lane

  • 139 Posts
  • 8 Reply Likes
So just wanted to clarify that would make it 10 distinct strategy market ideas - not all combined into one.
Photo of Jeehyung Lee

Jeehyung Lee, Alum

  • 708 Posts
  • 94 Reply Likes
Dear Edward,

Your strategy has been added to our implementation queue with task id 84~93. You can check the schedule of the implementation here.

Thanks for sharing your idea!

EteRNA team
Photo of Edward Lane

Edward Lane

  • 139 Posts
  • 8 Reply Likes
small clarification for strategy 6

I said N = number of necks, I meant to say number of stacks/necks,
and L the number of loops should also include bulges
Photo of Edward Lane

Edward Lane

  • 139 Posts
  • 8 Reply Likes
clarification for 1 and 2 it might be that you just rank them by lowest base count - probably still needs to include the hook despite it having some bases that are immutable - sone of those bases can be changed - meaning you could reduce the proportion of a particular base.