BitSpawn Lv 1
About game and new players
Could be divided into cate gories. First 100, and your ranking among 1-100,second 100-200, 200-300, and the rest. On that way new players are more motivated being their first objective to be the first of its range, and to move to the following one. It's not the same to be the second on your range that to be the 587th.
As an added incentive you can't belong to a group until you complete the first range.
About way of folding
1.- Be able to extract and match portions of different tracks. For example, you have two tracks rebuilding, and one improved one part and the other one other part: be able to mount the protein as if it were a puzzle. That could also be an important improvement for teamwork.
2.- Enable a 3D grid where you can specify the distance of the grid segments. The intersection points of the grid would be sticky. If for example you active a grid with distance 3.5, you could put cuts across the backbone and place each cutted bone on points of the grid as you want.
About bands
Three types of behavior: Normal, compression, decompression.
With added properties: maximum and minimum length from which takes effect. Example: a band compression only works when the distance is greater 7
About enable cutbands
It is usually to divide the protein into several parts and work with one part. To avoid interactions with the rest you separate the part with whom you work with cuts and getting far away.
But doing so the score is always -99999, so it is impossible to know what are you doing in the working part. Could limit the exaggerated negative score of a cutpoint?
About filters:
Disable the filters completely: both wiggle behavior as calculating score, in order to work swiftly with filtered puzzles. You could put a score of -20000 when you disable the filters. Currently it is almost impossible to move puzzles with filters on an underpowered machine.
About wiggle
Assign weights to the backbone, so you can set how hard or malleable is an area, for example to prevent warping on sheets and helix and target adaptation to loops, or otherwise become less rigid one sheet if you are not sure that its SS is correct.
About Scripts:
1.- Multithread. To launch several threads. currently we run several tracks doing the same.
They consume less machine resources (only one client/track running) if for example:
Rebuild(10)
for s=1,10 do fork(FunctionsOver(RebuildResult[s]))
WaitFor semaphore(1,10)
for s=1,10 CompareResults(result[s])
2.- Callback functions for keyboard events, like this
internally:
cb_function keyb(event)
key_pressed=(...) -- key_pressed as reserved name
return
in recipe:
function Main()
...
if key_pressed="?" then
-- break the "for"
-- change C.I.
-- run rutine
-- set variable
-- ...
end
end
In this way you modify the behavior of a script as you see the intermediate results. We can start another way of folding: scripting and handwork together.
3.- Batch mode
Feature: Foldit run without GUI. So we can run:
Foldit -solution file -recipe my_recipe -time x[s,m,h]
where 'recipe' is in all.macro, and two conditions would have to end: the return of the script, or the end of time.
we can read the standard output (from print in recipe) and program a batch to run other scripts depending on the results.
Synchronization
1.- IRC Disconnect Button
2.- Reload Cookbook from disk, Save cookbook.
3.- Cookbook sync with web: you can load/save your whole all.macro online.
Learning
Enable extended log, with name of recipes running and actions. Extended = slow,
so we could enable/disable it.
thanks if you have read until here, and sorry my english :)
