Contraint calculation issue in OpenKnot Sprint lab?

[Merida]

Not actually sure if the issue is the calculation, or my understanding of the constraint. Please do correct me if this is not in fact a bug.

When trying to design pseudoknots for the current Sprint lab, I noticed what seems to me to be strange behavior with the “50% of pairs part of a pknot” constraint. I grabbed a few screen shots to illustrate.

You can see here that there are only 5 pknot pairs, but the 50% shows as met. There are far more than 10 pairs in the puzzle, so what is being counted in the calculation?

This one says pknot pairs are at 11% (3 or 4 pairs?), but then I make a mutation and…

I get one more pknot pair, and my score jumps all the way from 11% up to 51%. Again, what is being measured if 4 or 5 pairs equal 51%?

Whereas in this sequence, I think I have about 10 pknot pairs, and only get to 43%.

But in this one, two pknot pairs meets the constraint. Am I missing something obvious?

[DigitalEmbrace]

Hi Merida! Several players have had this question so I will clarify. If you hover over the constraint box, the text reads “At least 50% of pairs must be crossed (involved in a pseudoknot).” The requirement is that 50% of the pairs must cross each other, not that the design have 50% banjo strings.

Here is the dot-bracket from Eli’s fantastic round 7a design Crossing Multiloops that is featured in the new paper. I have bolded the crossing pairs. The crossing pairs are a little tough to track visually, so Rhiju and Jonathan wrote the handy metric in the constraint box to help out.

[Merida]

Oh, I see. That makes much more sense. Thank you for the explanation!