-
Notifications
You must be signed in to change notification settings - Fork 344
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
Update munge_sumstats.py #391
Open
evlim
wants to merge
1
commit into
bulik:master
Choose a base branch
from
evlim:patch-1
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Fixed the inconsistent use of tabs and spaces in indentation
Did you get some help. munge_sumstats.py is also taking forever on my end. |
You can try add a chunksize setting in the command. It will help.
----------
该邮件从移动设备发送
…--------------原始邮件--------------
发件人:"Vivien Chebii ***@***.***>;
发送时间:2024年3月6日(星期三) 下午5:56
收件人:"bulik/ldsc" ***@***.***>;
抄送:"leoarrow1 ***@***.***>;"Comment ***@***.***>;
主题:Re: [bulik/ldsc] Update munge_sumstats.py (PR #391)
-----------------------------------
Did you get some help. munge_sumstats.py is also taking forever on my end.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
For the chunk size do you provide size or chromosomes? I can not find more
information on the READMe
…On Wed, Mar 6, 2024 at 11:57 AM leoarrow1 ***@***.***> wrote:
You can try add a chunksize setting in the command. It will help.
----------
该邮件从移动设备发送
--------------原始邮件--------------
发件人:"Vivien Chebii ***@***.***>;
发送时间:2024年3月6日(星期三) 下午5:56
收件人:"bulik/ldsc" ***@***.***>;
抄送:"leoarrow1 ***@***.***>;"Comment ***@***.***>;
主题:Re: [bulik/ldsc] Update munge_sumstats.py (PR #391)
-----------------------------------
Did you get some help. munge_sumstats.py is also taking forever on my end.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#391 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZTQ2V23GBQEXYJYRQMYZTYW3SCPAVCNFSM6AAAAAAZHHRM5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBQGQ4TGNBZGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Vivien Chebii, Ph.D.
Post doctoral Scientist (Bioinformatics)
Sydney Brenner Institute for Molecular Biosciences,
Wits University, South Africa
Email: ***@***.*** ***@***.***>*;
***@***.***
Mobile: +254 722 712 248
Linkedin: www.linkedin.com/in/viviennechebii/
|
It depends on the device you use for computing. Try read the original code of munge_sumstats.py in github. There are things that are not clarified enough in README file---thats bad.
***@***.***
From: Vivien Chebii
Date: 2024-03-07 22:14
To: bulik/ldsc
CC: leoarrow1; Comment
Subject: Re: [bulik/ldsc] Update munge_sumstats.py (PR #391)
For the chunk size do you provide size or chromosomes? I can not find more
information on the READMe
…On Wed, Mar 6, 2024 at 11:57 AM leoarrow1 ***@***.***> wrote:
You can try add a chunksize setting in the command. It will help.
----------
该邮件从移动设备发送
--------------原始邮件--------------
发件人:"Vivien Chebii ***@***.***>;
发送时间:2024年3月6日(星期三) 下午5:56
收件人:"bulik/ldsc" ***@***.***>;
抄送:"leoarrow1 ***@***.***>;"Comment ***@***.***>;
主题:Re: [bulik/ldsc] Update munge_sumstats.py (PR #391)
-----------------------------------
Did you get some help. munge_sumstats.py is also taking forever on my end.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
—
Reply to this email directly, view it on GitHub
<#391 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAZTQ2V23GBQEXYJYRQMYZTYW3SCPAVCNFSM6AAAAAAZHHRM5SVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBQGQ4TGNBZGQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
--
Vivien Chebii, Ph.D.
Post doctoral Scientist (Bioinformatics)
Sydney Brenner Institute for Molecular Biosciences,
Wits University, South Africa
Email: ***@***.*** ***@***.***>*;
***@***.***
Mobile: +254 722 712 248
Linkedin: www.linkedin.com/in/viviennechebii/
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: ***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixed the inconsistent use of tabs and spaces in indentation