(repeated from http://fold.it/portal/node/1998522)

This thread is over How to communicate when sharing.

Tips:
-you can copy from one description to the other (ctrl-c, ctrl-v)
-several information are already there: round of score, puzzle number, player's name...
-the place is limited, try to add only relevant information
-each group has it's own "language" for sharing, but i think most of them do almost the same as we do.
-this may evolve with time, players and inspiration: you are free to follow this suggested rules or not !

The title (*= recommended)

-First soloist (designer) short name (initials)
-First soloist version number (0 if not known)
-Server model number (nothing if not relevant)
-any separator like @ ) # / for the readability
-puzzle score, with decimals* (decimals help evolvers to know the cost to get evolved: 1-2 pts)
-wiggle power phase*: Low, Medium, High, Auto (the highest wiggle power ever used on this solution)
-latest wiggle power used. Here we might use initials: Low, Medium, High, Auto = L, M, H, A)
-F + Filter score* (good filter score have long term best potential)
-"solo" or "evo" (solo for your own solo, evo including if you evolve an evolution of your initial solo)
-any other free information
-"(="+indicative score in high or middle power + ")"

Examples for a first share by Pauldunn. If pauldunn shares his 3th test on model 2 of a multistart puzzle that ran only on Low wiggle power:

PD3-2) 8978.897 Low solo (= 9610 H)

or short:
2) 8978.897 Low = 9610

or at least:
2) 8978 Low

or

8978 Low (structure 2)

(in case of urgency: simple share of the "best credited soloist solution 10" etc. is of course also good)

Example for an evo of this solution:

2PD3) 9620.889 High evo

or short:
2PD3) 9620 evo

or at least:
2) 9620 evo

The description

The description contains the full range of recipes, number of loops and big point achieved. If there is no place, acronyms for known recipes could be implemented (after copy-passing the full range elsewhere, like in the forum or in the notes - this is done automatically for many group recipes - if one find it useful for later evaluation).

Example long:

struct2+Hand=7909+V2_Find Starting Point Low x30=9200/ Medium/ Blue Fuse= 9580+Acid Tweeker 2.4.5=9585

Short:
2 H+fsp L+bf M+AT and any other useful indication

Minimum:
8978 share+ Medium + bf + Low + AT

Very short:
2PD3 8978+ bf M + AT L

Note that whriting the score of the share we are evolving is usefull to identify the previous steps (and recipes used)

(Sat, 01/14/2017 - 22:20  |  18 comments)


Joined: 09/24/2012
Groups: Go Science
Some recipe acronyms (please add - I can edit this list)

The version of the recipe can be added shortly, like at234= Acid tweaker 2.3.4

at = acid tweaker
baca= banded all contacts adaptative
bf=blue fuze
bt= band and twist
bw= bridge wiggle
bwpi= banded worm pairs infinite
bwpif= banded worm pairs infinite filters
cc= contact cement
cgaba= contact gaba
cw= cut and wiggle
cwr= cut and wiggle random
di= deep idealize
dm= design models
drw = drw (deep rebuild worst)
eb= ebola (the new one)
edrw= tvdl_enhanced DRW
edrwa = tvdl_enhanced DRWa (the "a" means that it is the Go Science version)
er= ebola rebuild
ev= evaluator
fr= fracture
fsf= find starting filter
fsp= Find Starting points
fuc= fuze using cuts
gab = rav_npl GAB
gbf = gab bis (band in space)
gfc = gab filter cut
gmf= gary minima finder
grw= gary rebuild worst
H= High = at high wiggle power (in the title, it measn that we ever still went to high wiggle power)
hbnm= hydrogen bond network mutate
hf= hand fold
hp= hydro puller
hr= helix rebuild
hrc= helix rebuild cuts
ht= helix twister
htc= helix twister cuts
jet = jet (joint evolver team)
jo = jolter
krs= kuwaga repeat settle
L = Low (at low wiggle power)
l2h=Low2High
llws= lucky lws
lr= loop rebuild
lwp= low wiggle power (in the title, it means that did everything at low wiggle power)
lws= local wiggle strategy (familly of recipes)
M = mwp = med = at medium wiggle power
m= mutate (hand fold)
maaa= maaa (mutate autorized aminoacid)
mc= mutate combo
mi= microidealize
mnw= mutate no wiggle
mt= mutate and tug
nblh = nbl_hinge
qf= quickfix
qr= quaking rebuild
QR = QuakeR
qrmx= quaking remix
qrri=quaking rebuild random idealize
rbf= repeat blue fuse
rf = red fuse
ri = random idealize
s= shake
sdmwf= sd_multiwalk forever
sn=snake=the snake
tlws= total lws
trmx= tvdl_DremixC
vc= tvdl_void crusher
w= wiggle
wo = worm

Other suffixes or options:
bpc = (including) blueprint constraints
bpf = blueprint free (contraints removed)
recipe+ recipe - bpc + recipe : "-bpc" = removed blueprint constraints

Combined recipes:
bw&edrw = banding with bridge wiggle then running edrw

NinjaGreg's picture
User offline. Last seen 1 day 4 hours ago. Offline
Joined: 05/21/2010
Groups: Go Science
Additional script notations for scripts I use a lot

grw = gary rebuild worst
ht = helix twister
krs = Kuwaga Repeat Settle
QR = QuakeR

Joined: 09/24/2012
Groups: Go Science
Added

Thanks I added in the list above

puxatudo's picture
User offline. Last seen 15 weeks 12 hours ago. Offline
Joined: 04/07/2014
Groups: Go Science
Nomenclature in Wiki

This should be in a Wiki.
We could make a collection of acronyms from the top cookers and post it on a Wiki.
What do you guys think?

w1seguy's picture
User offline. Last seen 43 weeks 5 days ago. Offline
Joined: 03/05/2020
Groups: Go Science
Seconded - I refer to this

Seconded - I refer to this page a lot now... Probably good idea to open up to the whole community IMO

Joined: 09/24/2012
Groups: Go Science
Good idea

Many of them are used in other teams as well (including beta Folder which is a child of this team and where I was on "learning stay" during 6 Months).

I'll wait a bit other reactions then I start a Wiki page on this. Anybody will be able to edit the Wiki.

It's usefull for the chats as well.

Joined: 09/24/2012
Groups: Go Science
Good idea

Many of them are used in other teams as well (including beta Folder which is a child of this team and where I was on "learning stay" during 6 Months).

I'll wait a bit other reactions then I start a Wiki page on this. Anybody will be able to edit the Wiki.

It's usefull for the chats as well.

Joined: 09/24/2012
Groups: Go Science
other ones

htc= helix twister cut
rf = red fuze

Other suffixes or options:
bpc = (including) blueprint constraints
bpf = blueprint free (contraints removed)
recipe+ recipe - bpc + recipe : "-bpc" = removed blueprint constraints

jeff101's picture
User offline. Last seen 10 hours 37 min ago. Offline
Joined: 04/20/2012
Groups: Go Science
Some Recipes Gain, Others Don't

Some things I try gain points, other things don't.
Sometimes it is useful to know what didn't gain points.
I have started to mark things that gained points with *'s.
If most things gained points, perhaps I will just mark the
ones that didn't gain points with -'s.

w1seguy's picture
User offline. Last seen 43 weeks 5 days ago. Offline
Joined: 03/05/2020
Groups: Go Science
symbols idea

https://i.imgur.com/zZs1es0.png

[the discussion board didn't like the formatting, sorry for the mess below!]

Phyx's picture
User offline. Last seen 1 day 8 hours ago. Offline
Joined: 10/08/2011
Groups: Go Science
Addition to Fracture would be

Addition to Fracture would be good since it can be run with 6 different modes and I have found running 2 copies with different modes and one not gaining any points. Don't know if numbers is the best but:

Early 1 = 11, Early 2 = 12 Early 3 = 13
Mid 1 = 21, Mid 2 = 22, Mid 3 = 23
End 1 = 21, End 2 = 32, End 3 = 33

Or if we just say Early1...2...3, Mid1...2. Not that much space wasted perhaps.

w1seguy's picture
User offline. Last seen 43 weeks 5 days ago. Offline
Joined: 03/05/2020
Groups: Go Science
symbols

Even the ability to add custom symbols in the text such as:
✅- gained points
❌- No gain

w1seguy's picture
User offline. Last seen 43 weeks 5 days ago. Offline
Joined: 03/05/2020
Groups: Go Science
(sorry it's not letting me put my full comment)
w1seguy's picture
User offline. Last seen 43 weeks 5 days ago. Offline
Joined: 03/05/2020
Groups: Go Science
Symbols idea continued
w1seguy's picture
User offline. Last seen 43 weeks 5 days ago. Offline
Joined: 03/05/2020
Groups: Go Science
Last try.. linking to a post of the comment I meant to put above
Joined: 09/24/2012
Groups: Go Science
how to

Could you explain somwhere (it could be later on a wiki) how to include these symbols into Foldit comments (and even in recipes ?)

Joined: 09/24/2012
Groups: Go Science
added combinations

Combined recipes:
bw&edrw = banding with bridge wiggle then running edrw

Joined: 09/24/2012
Groups: Go Science
A new WIKI on Common language !

Hello,

I copied this to a new WIKI on common language here:

https://foldit.fandom.com/wiki/Common_language

Sitemap

Developed by: UW Center for Game Science, UW Institute for Protein Design, Northeastern University, Vanderbilt University Meiler Lab, UC Davis
Supported by: DARPA, NSF, NIH, HHMI, Amazon, Microsoft, Adobe, RosettaCommons