fishtest
fishtest copied to clipboard
Add a system of filters to find tests
https://github.com/official-stockfish/Stockfish/issues/1865
Quoting the text from the linked issue here for convenience.
FauziAkram said:
Can we implement a system of filters in the main page of fishtest, so we can play around with the filters, and find exactly the tests that we need.
Criteria that might be used for the filters: -Type of test (Sprt/Spsa/Num of games) -Color (White, Red, Yellow, Green) -Time Control (Stc/Ltc/Other) -SPRT bounds ( [-3,1]/[0,4]/[0,5]/other) -Number of games (from: X / to: Y)
Vizvezdenec said:
This will be useful to surf for for example "good" parameter tweaks to make big combo patches of them. Once in 2/3 months there is always some combo patch passing but it requires quite a lot of deep digging into fishtest and a lot of effort. With this functionality it will get 50 times easier. Also if we will soon have SPRT bounds changes it will be really useful for searching for "almost passed" patches to see if they will pass new SPRT (see discussion there basically approved by both maintainers #1859 ).
some discussion in fischcooking on the usefulness of search also there https://groups.google.com/d/msg/fishcooking/rQGALpXDZew/boJ2UPQVAQAJ
So, some ideas about searching, not yet very organized or firm.
Ideally we can use the search to answer questions like 'what are all LTC evaluation patches by Viz he ran last month, changed something about pawns and finished yellow'
certain aspects seem 'easy'
- restrict date to a range
- find the author (github and fishtest handles might be different), maybe fuzzy search (have Viz match Vizvezdenec)
- test type (sprt), outcome (yellow, green, or Elo range), parameters (ltc, stc, smp, ...)
- state (running, pending, ....)
the most tricky, but most valuable questions are trying to infer the topic. This could be things we have in the database
- branch name (fuzzy match e.g. pawns match PawnTweak12)
- info field
others might require additional interaction with github
- commit messages
- files changed (e.g. evaluate.cpp hints at and eval patch)
- actual diff content ?
- github comments
Sometimes the test note is not the same as the github commit message. Being able to search the notes and the name of the test branch using keyword partial match would be really helpful.