Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Example input files? (error: "bv is not a valid literal-keeper implementation") #5

Open
agnieszkadanek opened this issue Oct 5, 2022 · 0 comments

Comments

@agnieszkadanek
Copy link

Hi,

Could you provide a toy example of input files that work with rlzap_build or fix the link to your dataset (as mentioned here: #3)

I tried FASTA files (as in the example below) and also text files with DNA sequences, but I always get an error: "bv is not a valid literal-keeper implementation".

$ cat r
>r
ATGCAACTGATCG
$ cat i
>i
TGCTAAAACGTA
$ ./rlzap_build -i i -r r -o o 
bv is not a valid literal-keeper implementation.
Command-line options:
  -i [ --input-file ] arg             Input file, that is, file to be indexed.
  -r [ --reference-file ] arg         Reference file.
  -A [ --alphabet ] arg (=lcp32)      Alphabet. Choices: lcp32 
  -o [ --output-file ] arg            Output file.
  -k [ --parser ] arg (=parametric)   Select a parsing strategy. Choices: 
                                      classic, automatic, parametric, 
  -L [ --look-ahead ] arg (=30)       Amount of look-ahead symbols.
  -E [ --explicit-len ] arg (=15)     Minimum length of an explicit phrase, in 
                                      symbols.
  -l [ --literal-strategy ] arg (=bv) Literal lengths datastructure 
                                      implementation. Choices: sampling .
  -M [ --max-lit ] arg (=4)           Length of end-of-phrase literal length, 
                                      in bits. Choices: 2 4 8 .
  -S [ --sample-int ] arg (=32)       Literal sampling interval size, in 
                                      elements. Choices: 16 32 48 .
  -d [ --delta-bits ] arg (=8)        Adaptive pointer length, in bits. 
                                      Choices: 2 4 8 .
  -e [ --explicit-bits ] arg (=32)    Explicit pointer length, in bits. 
                                      Choices: 32 .
  -a [ --accelerate ] arg             File containing matching stats (optional)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant