Closed shappiron closed 1 year ago
Can you check which version of numpy you got in the conda environment for that wrapper? I've seen this problem because of https://github.com/numba/numba/issues/8615, but the version of numpy is pinned in the cooltools bioconda recipe to avoid it...
numpy='1.24.2'
Interestingly, on local machine I have numpy='1.23.5'. Apparently I can downgrade it by putting the actual version into the .yaml
file. But is there better option?
I don't know how it is possible for you to get that version, since it's pinned <1.2... So just try downgrading like that I guess.
I noted the difference between two yaml files:
Working case:
channels:
- conda-forge
- defaults
- bioconda
dependencies:
- ucsc-bedgraphtobigwig
- cooltools =0.5.2
Case returning error
channels:
- conda-forge
- defaults
- bioconda
dependencies:
- cooltools =0.5.1
Are these yaml files depend on the version of wrapper?
Wait, why do you have different yaml files? I assumed you were using latest versions in both cases...
As I mentioned previously I forked your repository some time ago. But my fork still depends on snakemake-wrappers which I fetch from here (I guess). I can't understand how to control versions of wrappers I fetch.
Just fetch the latest wrappers, or at least the version that is mentioned in the rules in the master branch here. E.g.
wrapper:
"v1.21.2/bio/cooltools/expected_cis"
This is the core of my problem. I put v1.19.1
in both cases (working and not working) and it doesn't affect yaml file. Moreover, when I put 1.21.2 - nothing changes.
Idk perhaps delete the .snakemake folder?.. I've never had this problem.
Do I correctly get that "...it's pinned <1.2..." means that numpy should have the corresponding version restriction in this file. If yes, it doesn't have actually.
Finally, I found a problem. I forgot to enter the command conda config --set channel_priority strict
as workflow recommends at the start. I propose to add this small line to the README in the future.
Thank you for your advice!
I see! Great that you solved it, thanks for letting me know what helped!
Hi! I faced a problem after installing the workflow with mamba (but probably it is not the problem). And after running the pipeline got the following error on
make_expected_cis
step:I must note that this problem is not in the actual version of the repository, but in my fork. Meanwhile, I decided to write the issue here because I didn't make any changes in the actual cooltools wrapper which does perform this rule. Moreover, when I run my fork locally everything is well but after reinstallation, on the remote machine, the error above appears.
Could you help me with any advice, please?