In the current conda-env.yml the pysam version corresponds to one that incorrectly pulls the wrong libssl from conda. This causes an error when training indicating libcrypto0.1.0 does not exist. The issue can be fixed by using a later version. pysam==0.15.3 seems to do the trick.
In the current
conda-env.yml
the pysam version corresponds to one that incorrectly pulls the wrong libssl from conda. This causes an error when training indicatinglibcrypto0.1.0
does not exist. The issue can be fixed by using a later version.pysam==0.15.3
seems to do the trick.