Buried Unsats (max +500)
Penalizes polar atoms that cannot make hydrogen bonds, -200 points per atom (not including symmetric copies).
Core Existence: Monomer (max +1600)
Ensures that at least 16 residues are buried in the core of the monomer unit.
Core: Complex (max +0)
Awards no bonuses or penalties. Click Show to see which residues count as "Core" for the H-bond Network objective.
Interaction Energy (max +500)
Monitors that all large PHE, TYR, and TRP residues are scoring well.
H-bond Network (max +2400)
Rewards networks that comprise at least 2 H-bonds involving core residues.
Between 1 and 12 H-bonds should cross the interface between symmetric units.
Networks must be at least 75% satisfied (i.e. 75% of all bondable atoms in a network must make a H-bond).
SS Design (max +500)
Penalizes all CYS residues. Penalizes GLY, ALA residues in sheets. Penalizes GLY, ALA in helices.
Ideal Loops (max +500)
Penalizes any loop region that does not match one of the Building Blocks in the Blueprint tool. Use "Auto Structures" to see which regions of your protein count as loops.
Description say use no more thatn 50% helices but there is no penalty in the filter menu.
That was an error in the puzzle description; this puzzle should permit as much alpha helix as you want! I've corrected the puzzle description.
My initial reaction was: Wow, another D2 Symmetry puzzle. Nice!
But then I thought, before I spend a lot of work on a new design, let me have a look at the way bands between the chains work now. As I pointed out in a feedback item last June, this was a bug in the previous D2 symmetry puzzles.
This quick test was a bitter disappointment: the bug has not been resolved. :-(
I would like to hear from Foldit Staff what has been done in the past three and a half months to address this (as milkshake announced in this comment), and also: when can we expect a fix?
For now, all we can do is avoid any bands to chain 1 (purple) and chain 3 (brown), or, if you need a band to one of these chains, use this workaround.
I had thought this bug was fixed when we addressed the HBNetwork issues with D2 symmetry. We'll have to dig back into it, but it looks like a potentially hairy bug, so may be difficult to track down.