-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Permission errors with docker while launching higlass-manage #84
Comments
You probably need to allow docker run as a non-root user. Have you tried this? https://docs.docker.com/engine/install/linux-postinstall/#manage-docker-as-a-non-root-user |
Ok thanks, it seems to work better but I had an other issue that seemed to come from cython:
So I updated cython as suggested here Toblerity/Fiona#1043, which may be incompatible with cooler but it allows me to open an higlass instance and visualise the sample.cool.
However, higlass-manage browse command does not seem to exist. Also, can you confirm higlass is the right tool for a fast and smooth exploration Hi-C data in .cool or .mcool format on the fly, like IGV is for other -seq ? I was used to work with .hic file from Juicer tools, and visualisation with Juicebox is actually quite fast, even at high res while higlass seems lagging a lot. Thanks for your support, |
HiGlass requires a multi-res cooler file. To go from single resolution to multires is easy: Hard to say if higlass is the right tool. It's a tool that some people like and others don't. As you said, Juicer works well as well. The main factor that affects higlass performance is the resolutions that are present in your mcool file. If you use |
Dear higlass team,
I followed instructions to install higlass-manage:
Prerequisites:
Docker installed following https://docs.docker.com/desktop/install/ubuntu/ and I can launch Docker desktop
Higlass is installed with pip install higlass-manage
But when I try to launch higlass, I hav the following errors:
Could you help me and tell me what did I miss ?
Thanks!
David
The text was updated successfully, but these errors were encountered: