Closed lavenderca closed 7 years ago
Interesting, this is likely unrelated to the redirect but instead related to a certificate error in OSX. Did you install pyBigWig with bioconda or pip?
bioconda. I used the following:
conda install pybigwig -c bioconda
What's the output of conda list | grep curl
?
$ conda list | grep curl
curl 7.45.0 0
pycurl 7.19.5.3 py34_0
Currently trying an upgrade.
What happens if you conda install -c bioconda curl
(you might have to remove the one you currently have installed)? I made a version of curl for bioconda a year or so ago that fixed a few problems like this.
The upgrade seems to work! Thanks so much for your help.
Ran conda upgrade curl
. Now:
$ conda list | grep curl
curl 7.52.1 0
pycurl 7.43.0 py34_2
Cool, conda finally fixed their package! Glad that worked!
Hi! I came up with the same question even after I upgraded curl. How shall I solve this problem? Many thanks!
$ conda list | grep curl
curl 7.52.1 0 defaults
pycurl 7.43.0 py35_2 defaults
What version of OSX are both of you using? Maybe that's the difference? Perhaps I should add an option to libBigWig (what pyBigWig uses) to ignore certificate errors.
I download some bigwig files from ENCODE, and some of them works, but some are not. In addition, using url directly works well. For example:
pyBigWig.open('https://www.encodeproject.org/files/ENCFF555VCB/@@download/ENCFF555VCB.bigWig')
works well.
pyBigWig.open('ENCFF555VCB.bigwig')
could not work after I download the file to my server. The error message is:
[urlOpen] Couldn't open ENCFF555VCB.bigwig for reading
Sorry, this problem occurs in linux server.
Are you in the same directory as ENCFF555VCB.bigwig
?
Yes. In addition, I am wondering whether it is because the version of my installed pybigwig is too low. I installed it via bioconda, and the latest version of pybigwig is 0.2.8 in bioconda.
@kepbod: You'll get that error whenever there's an error opening a local file. This particular error will usually only happen if the file specified doesn't exist or you don't have rights to open it.
Oh, it is my fault. I figured out what is wrong that I used the wrong file name. Thanks for your assistance.
In the README, an ENCODE bigBed file is opened. On Linux, I'm able to run the command as written:
On Mac, I'm receiving the following error:
I'm still able to access the file using my browser.
Trying to fix the issue, I updated my installation of curl (now 7.52.1) but am still getting the error. I ran curl with the file, and it seems like there is a redirect:
Could this be contributing to my issue?