strange help listings about tudocomp HOT 2 OPEN

Issuing ./tdc --list=bi gives

There is more than algorithm named 'bi'. Please specify using one of the following canonical IDs:
bi:lzss_bidirectional_coder
bi:lzss_bidirectional_coder

Do you have it declared twice in the registry?

Can we push default parameters into the coder bi such that we do not have to write bi(binary,binary,binary),
and use as default strategy the best one, i.e., plcpcomp?

This can be set up in the meta functions.

Binary is likely never the best choice for coding, and "best choice" depends very much on the input.
As for plcpcomp being the default, has it been fully implemented in-memory? Is the PLCPPeaksStrategy obsolete?

from tudocomp.

Do you have it declared twice in the registry?

I am using /etc/registries/lcpcomp.py of the master branch, but could not find a duplicate.

Binary is likely never the best choice for coding, and "best choice" depends very much on the input.

It would be nice for newcomers to just issue any compressor without parameters.
Currently, invoking lcpcomp is meddlesome.
It would also be a good idea to have a core registry with standard implementations a user would expect.

As for plcpcomp being the default, has it been fully implemented in-memory?

It has already been fully implemented before the work on the EM algorithm started.

Is the PLCPPeaksStrategy obsolete?

Yes, kind of. It works, but I would favor its sibling LexParseStrategy instead, as I expect new research results on lex-parse.

from tudocomp.