{pear} is not likely to be ready for a public release this spring. But a good second option is to include relevant parts of the code from {pear} as internal, documented and tested functions in {pioneeR}. This should be relatively simple to achieve, and fits nicely into the restructuring of the package (i.e. moving code to the R/-folder).
{pear}is not likely to be ready for a public release this spring. But a good second option is to include relevant parts of the code from{pear}as internal, documented and tested functions in{pioneeR}. This should be relatively simple to achieve, and fits nicely into the restructuring of the package (i.e. moving code to theR/-folder).