Skip to content
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

Segmentation fault on hg38 #7

Open
millerh1 opened this issue May 1, 2022 · 8 comments
Open

Segmentation fault on hg38 #7

millerh1 opened this issue May 1, 2022 · 8 comments

Comments

@millerh1
Copy link

millerh1 commented May 1, 2022

Hello -- I am having trouble using G4Hunter on the hg38 FASTA from UCSC.

It starts fine, but after about ~10 minutes, it crashes with a Segmentation fault:

~$ python2 G4Hunter.py -i ~/.rlpipes_genomes/hg38/hg38.fa -o "../" -w 25 -s "1.2"
true Results_hg38

         Re-evaluation of G-quadruplex propensity with G4Hunter

#####################################
#    New Results directory Created  #
#####################################


 Input file: hg38
Segmentation fault (core dumped)
@AnimaTardeb
Copy link
Owner

AnimaTardeb commented May 1, 2022 via email

@millerh1
Copy link
Author

millerh1 commented May 1, 2022

I am not running out of RAM if that is what you are implying. I'm on a machine with 256GB and running G4Hunter doesn't add more than 10GB from baseline.

I also do not experience Segmentation faults with any other python programs.

@AnimaTardeb
Copy link
Owner

Hello,

im not implying anything. it't the first time i see the segmentation fault on python i usually see it on c++
i did run the hg19 not the problem ...

1: -s "1.2"=> why " "

2: have you tied to run first the test? do you have segmentation fealt with a test file

3: why the "" in -o "../"?
4: why are you using python2 ? i code it on 2.7

@millerh1
Copy link
Author

millerh1 commented May 1, 2022

Thank you for looking into this! Here are my responses to your questions:

  1. Just a personal preference -- I will remove them.
  2. I just ran it and it worked fine:
~$ python2 G4Hunter.py -i Mitochondria_NC_012920_1.fasta -o ../ -w 25 -s 1.2
true Results_Mitochondria_NC_012920_1

         Re-evaluation of G-quadruplex propensity with G4Hunter

#####################################
#    New Results directory Created  #
#####################################


 Input file: Mitochondria_NC_012920_1

 Results files and Score Figure are created in:
../ / Results_Mitochondria_NC_012920_1 /
  1. Same as (1)
  2. I am using python 2.7.18 which is aliased as python2 on my machine.

@AnimaTardeb
Copy link
Owner

it better if you create a folder inside your ../ and send the results there
could you please run the hg38 without the "" ?
if not try to do just 1 chromosome and see because 10 min still on the 1 chr

try another genome from your collection
I know a lot of ppl + me have run the hg19 and succeeded
beside this i really don't see where the problem cam from !!

@millerh1
Copy link
Author

millerh1 commented May 2, 2022

It worked when applied to just Chr1 from UCSC hg38:

~$ python2 G4Hunter.py -i chr1.fa -o ../ -w 25 -s 1.2                      
########################################################################
#                            Results directory Created                 #
########################################################################


 Input file: chr1

 Results files and Score Figure are created in:
../ / Results_chr1 /

Unsure of why it would fail on the whole genome then.

@millerh1
Copy link
Author

millerh1 commented May 2, 2022

After working with this for a bit, I am still getting intermittent segfaults -- still unsure of why though.

@AnimaTardeb
Copy link
Owner

sorry for the delay.
I might have an idea but I really don't have a time to go back to my scripts.it been 6 years
did you try each chromosome separately? I know it's long sorry for that

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants