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

Error in glm.fit: object fit not found #17

Open
skanwal opened this issue Mar 5, 2024 · 5 comments
Open

Error in glm.fit: object fit not found #17

skanwal opened this issue Mar 5, 2024 · 5 comments

Comments

@skanwal
Copy link

skanwal commented Mar 5, 2024

Hi @reimand0 ,

I am getting an error, when trying to run ActiveDriveWGS using following command:

ActiveDriverWGS.res[[i]] = ActiveDriverWGS(mutations = ActiveDriverWGSInfo[[i]], elements = elements, sites = NULL, window_size = 50000, recovery.dir = paste(outDir, "ActiveDriverWGS_recovery", sep="/"), mc.cores = 4, ref_genome = paste0("hg", params$ucsc_genome_assembly)) 

The error is:

0 remove hypermut, n= 0 ,  0 %
hypermuted samples:   

reversing 0 positions
Removing  0  invalid SNVs & indels

Number of Elements with 0 Mutations:  14 
Tests to do:  1195 
Tests recovered:  928 
100  elements completed
200  elements completed
300  elements completed
400  elements completed
500  elements completed
600  elements completed
700  elements completed
800  elements completed
900  elements completed
.Error in glm.fit(x = numeric(0), y = numeric(0), weights = NULL, start = NULL,  : 
  object 'fit' not found

Data

>  head(ActiveDriverWGSInfo)
$pdac
         chr      pos1      pos2 ref alt                            patient
     1: chr3 120002137 120002137   T   C p010_tumor-52fccd-somatic.pcgr.vcf
     2: chr4 125450687 125450687   G   T p010_tumor-52fccd-somatic.pcgr.vcf
     3: chr5  38502681  38502681   C   A p010_tumor-52fccd-somatic.pcgr.vcf
     4: chr6  89951675  89951675   C   T p010_tumor-52fccd-somatic.pcgr.vcf
     5: chr7  82822603  82822603   G   T p010_tumor-52fccd-somatic.pcgr.vcf
    ---                                                                    
196698: chrX  15795073  15795073   A   C                  SA533811_SP125786
196699: chrX  15800132  15800132   T   A                  SA569276_SP133702
196700: chrX  15803607  15803607   G   T                  SA558660_SP125807
196701: chr9  14398633  14398633   C   G                            CGPA229
196702: chr1 186680291 186680291   C   T                            CGPA234

> str(ActiveDriverWGSInfo)
List of 1
 $ pdac:Classes 'data.table' and 'data.frame':	196702 obs. of  6 variables:
  ..$ chr    : chr [1:196702] "chr3" "chr4" "chr5" "chr6" ...
  ..$ pos1   : num [1:196702] 1.20e+08 1.25e+08 3.85e+07 9.00e+07 8.28e+07 ...
  ..$ pos2   : num [1:196702] 1.20e+08 1.25e+08 3.85e+07 9.00e+07 8.28e+07 ...
  ..$ ref    : chr [1:196702] "T" "G" "C" "C" ...
  ..$ alt    : chr [1:196702] "C" "T" "A" "T" ...
  ..$ patient: chr [1:196702] "p010_tumor-52fccd-somatic.pcgr.vcf" "p010_tumor-52fccd-somatic.pcgr.vcf" "p010_tumor-52fccd-somatic.pcgr.vcf" "p010_tumor-52fccd-somatic.pcgr.vcf" ...
  ..- attr(*, ".internal.selfref")=<externalptr>
  
  > head(elements)
     chr    start      end       id          GENEID
20 chr12   912077   990053    RAD52 ENSG00000002016
30 chr17 38869859 38921770    LASP1 ENSG00000002834
56 chr12 21468911 21501669    RECQL ENSG00000004700
66  chr7 96120220 96322147 SLC25A13 ENSG00000004864
74 chr19 18831938 18868236     UPF1 ENSG00000005007
78  chr7 27181510 27185223   HOXA11 ENSG00000005073

I have also done some sanity checking on both mutation and elements data and found no issues with having NA's or empty values.

Can you please help figure out why this might be producing an error?
Many thanks.

@reimand0
Copy link
Contributor

reimand0 commented Mar 7, 2024 via email

@skanwal
Copy link
Author

skanwal commented Mar 12, 2024

@reimand0 - I have emailed the data to your utoronto.ca id. Hopefully you have received it?

@reimand0
Copy link
Contributor

reimand0 commented Mar 13, 2024 via email

@skanwal
Copy link
Author

skanwal commented Mar 13, 2024 via email

@skanwal
Copy link
Author

skanwal commented Apr 9, 2024 via email

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