Skip to content

address (nil), cause 'memory not mapped' #1

@aanderson54

Description

@aanderson54

Hi,

Thank you for the package. I was trying to run through the workflow with my own data and ran into an error when running sc-compreg. The same error occurs when I try the sample data, and it appears to be caused by the loadPeakNameIntersectFile function. When I run through the example code, I get this error:

 *** caught segfault ***
address (nil), cause 'memory not mapped'

Traceback:
 1: loadPeakNameIntersectFile(file.dir, token)
 2: load_pn_intersect_file(peak.name.intersect.dir, token)
 3: comp_reg_preprocess.default(peak.name.intersect.dir, token = sep.char)
 4: comp_reg_preprocess(peak.name.intersect.dir, token = sep.char)
 5: sc_compreg.default(sample1$O1, sample1$E1, sample1$O1.idx, sample1$E1.idx,     sample1$symbol1, sample1$peak.name1, sample2$O2, sample2$E2,     sample2$O2.idx, sample2$E2.idx, sample2$symbol2, sample2$peak.name2,     motif$motif.name, motif$motif.weight, motif$match2, motif.file,     peak.name.intersect.dir, peak.gene.prior.dir, sep.char = " ")
 6: sc_compreg(sample1$O1, sample1$E1, sample1$O1.idx, sample1$E1.idx,     sample1$symbol1, sample1$peak.name1, sample2$O2, sample2$E2,     sample2$O2.idx, sample2$E2.idx, sample2$symbol2, sample2$peak.name2,     motif$motif.name, motif$motif.weight, motif$match2, motif.file,     peak.name.intersect.dir, peak.gene.prior.dir, sep.char = " ")

I am wondering if you might know what could be causing this issue. Is there a way to load and format the peak name intersect file without using the cpp script?

Thank you!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions