[Market strategy] Comprehensive color line ban

I would like to have an overall strategy for my earlier 4 strategies, Green line, Blue line, Red line and Yellow line with string (Last one not programmed yet). Here is why:

I can see from the general bot output, that it uses too many lines with 3 nucleotides or more of the same color.

  • 2 nucleotides of same color in line on a strand can be trouble.

  • 3 nucleotides of the same color in line is almost always trouble. Though sometimes tolerated in longer strings and in neck area, if the area around it is stable.

  • More of those colored lines together means BIG trouble. They simply rather be anywhere else, even if they can only find one or two nucleotide of another color to pair up with. Lines of 3 or more in abundance, rips the RNA structure apart.

The last part is not taken into account in my earlier strategies, which is why I made a collective strategy, to hit the problem fast and hard. It should also make the bot a bit faster, having the algorithm run one time instead of four.

I will like to have a strategy that says, no strands in a string with 3 nucleotides of the same color in line after each other. Be it green, red, blue and yellow.

Penalize this with -2.

Pr. extra line of same colored nucleotides no matter their color, penalize exponentially.

Also give -1 pr. each extra nucleotide, if the line of same colored nucleotides is longer than 3.

This is not my usual method, I’d rather send a small missile hitting when needed instead of nuking too much. But here an exception is needed. Nuke the colored lines :slight_smile:

This is an example on what happens when many lines of red and green are present. Yellow and blue lines are not as bad as green and red, but when the number of color lines is adding up, they are a big problem too.

Notice how all except one of the line pairs, finds partners elsewhere. And notice the drop in energy.

Thanks to Brourd for title inspiration and for discussing the making of the strategy.

Dear Eli,

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

Thanks for sharing your idea!

EteRNA team