-
Notifications
You must be signed in to change notification settings - Fork 2
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
can't unzip file #2
Comments
It should work. I just tried it. Try to download allt he maps and unzip it if you still have the issue. cheers |
Hi, strangely this bed file does not contain any regions with state 3. |
@simonelsasser Use the chromatin state names instead of the numbers. |
thanks, got it. state 3 runs under "9_Txn_Transition" (this is in
mESC_cStates_HMM
<https://github.com/gireeshkbogu/chromatin_states_chromHMM_mm9/blob/master/mESC_cStates_HMM.zip>,
I haven't checked any other)
…On Wed, May 16, 2018 at 7:37 PM, Gireesh Bogu ***@***.***> wrote:
@simonelsasser <https://github.com/simonelsasser> Use the chromatin state
names instead of the numbers.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AREwOIoCqkUA2HVz0jZY_Fe1HIYTbmUfks5tzGPNgaJpZM4HiFHT>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi there,
I can't unzip the file. Please help.
Thanks,
Clayton
1.
[ckc620@qhimem0001 Kai]$ ls
mESC_cStates_HMM.zip
[ckc620@qhimem0001 Kai]$ unzip mESC_cStates_HMM.zip
Archive: mESC_cStates_HMM.zip
End-of-central-directory signature not found. Either this file is not
a zipfile, or it constitutes one disk of a multi-part archive. In the
latter case the central directory and zipfile comment will be found on
the last disk(s) of this archive.
unzip: cannot find zipfile directory in one of mESC_cStates_HMM.zip or
mESC_cStates_HMM.zip.zip, and cannot find mESC_cStates_HMM.zip.ZIP, period.
The text was updated successfully, but these errors were encountered: