h-docs

Search

Search IconIcon to open search

Solution Finder: Cover

Solution Finder’s Cover command outputs the probability of setting up/building a specified field (or multiple), given a specified pattern. This output is written in both the terminal and the specified log path.

1
java -jar sfinder.jar cover --tetfu <fumen> --patterns <pattern>
1
java -jar sfinder.jar cover -t <fumen> -p <pattern>
1
java -jar sfinder.jar cover -t <fumen> <fumen> -p <pattern>

Input Parameters

Specified Field(s) (--tetfu, -t): the fumen code(s) that sfinder begins working with. If not specified, the file field.txt in the input folder is used. Input multiple fumens for fields by separating the fumens with spaces.

Patterns (--patterns, -p): Determines the queues checked by sfinder. Read more about this parameter here.

OptionHarddropSoftdrop90 spins180 spinsMust also do:
harddrop-
softdrop
180
t-softdropT onlyT only-
tszAny T-spin
tsmtss/tsd/tst (and/or minis)
tsstss/tsd/tst
tsdtsd/tst
tsttst only

Mode (--mode, --M): specifying the condition by which cover will return as successful or failed.

WIP

This section can be improved by showcasing the possible modes.

Starting B2B (--starting-b2b, -sb): specifying the number of B2B clears is required for a successful output.

Kick table (--kicks, -K):

WIP

This section isn’t filled out yet.


Output Parameters

Priority (--priority, -P): Only one setup can be marked as O for all the fumens provided. This will be the first setup that is buildable in the order of the fumens given in --tetfu.

Failed Count (--failed-count, -fc): determines the number of failed queues displayed at the end of the output.


Miscellaneous Parameters

Output Base (--output-base, -o): Specify the path data file output.

Log path (--log-path, -lp): create a .txt file output from the output of the command.

Specified Field from a file (--field-path, -fp): instead of defining the fumen code using --tetfu, you can specify a .txt file that contains a fumen code instead.

Patterns from a file (--patterns-path, -pp): instead of defining patterns using --patterns, you can specify a .txt file that contains either the actual queues, or patterns.


Summary

Input Parameters
ParameterShorthandDefault
--tetfu-tnull
--patterns-pnull
--hold-Htrue
--drop-dsoftdrop
--max-clearline-mc-1
--max-softdrop-ms-1
--last-sd-l0
--mirror-mfalse
--kicks-Ksrs

Output Parameters
ParameterShorthandDefault
--priority-Pfalse
--mode-Mnormal
--output-base-ooutput/cover.csv

Miscellaneous Parameters
ParameterShorthandDefault
--starting-b2b-sb0
--log-path-lpoutput/last_output.txt
--field-path-fpinput/field.txt
--patterns-path-ppinput/patterns.txt

Example Commands and Output

An example terminal output of the cover command.

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
#Command Line Input
java -jar sfinder.jar cover -t v115@vhFRQJUGJKJJvMJTNJGBJ v115@vhFRQJPGJKJJGMJTNJ0BJ -p *p7

# Output
success:
33.33 % [1680/5040]: http://fumen.zui.jp/?v115@vhFRQJUGJKJJvMJTNJGBJ
44.44 % [2240/5040]: http://fumen.zui.jp/?v115@vhFRQJPGJKJJGMJTNJ0BJ
>>
OR  = 61.67 % [3108/5040]
AND = 16.11 % [812/5040]

Each item under success represents one fumen entered under the --tetfu parameter, in order. It contains the following:

Furthermore, it tallies up the results as:


An example CSV output of the cover command.

sequencev115@vhFRQJU...v115@vhFRQJP...
TILJSZOXO
TILJSOZXO
TILJZSOXO
TILJZOSXO
5036 more lines...

The CSV output lists the first column for the patterns used, and extra columns are allocated for every fumen in order.


Special Uses

  1. Cover’s output can be converted into an sfinder path output to be used to find custom minimals, such as Quad PC minimals or T-Spin minimals.