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

ask about the “AD.hIGH" NOT FOUND #32

Open
lnqiao opened this issue Jun 11, 2020 · 7 comments
Open

ask about the “AD.hIGH" NOT FOUND #32

lnqiao opened this issue Jun 11, 2020 · 7 comments

Comments

@lnqiao
Copy link

lnqiao commented Jun 11, 2020

No description provided.

@bmansfeld
Copy link
Owner

Sorry please try to better state the issue and bug.
I hope I can help you

@lnqiao
Copy link
Author

lnqiao commented Jun 11, 2020

when I conduct the inport form gatk, it was failed and said that "> df <-

  • importFromGATK(
  • file = file,
    
  • highBulk = Mut,
    
  • lowBulk = WT,
    
  • #chr=c('chr01')
    
  • )
    Error in eval_tidy(enquo(var), var_env) : object 'AD.HIGH' not found"

1 similar comment
@lnqiao
Copy link
Author

lnqiao commented Jun 11, 2020

when I conduct the inport form gatk, it was failed and said that "> df <-

  • importFromGATK(
  • file = file,
    
  • highBulk = Mut,
    
  • lowBulk = WT,
    
  • #chr=c('chr01')
    
  • )
    Error in eval_tidy(enquo(var), var_env) : object 'AD.HIGH' not found"

@lnqiao
Copy link
Author

lnqiao commented Jun 11, 2020 via email

@bmansfeld
Copy link
Owner

Thanks.
Please supply the head of your table file as well as the commands you used prior to importFromGATK
This will help me understand why the import function is unable to parse your data correctly and identify the column names.
Ben

@lnqiao
Copy link
Author

lnqiao commented Jun 11, 2020 via email

@bmansfeld
Copy link
Owner

Nanqiao,
I figured out what the issue is. As I suspected the problem is with the names of your columns "W" and "G". It is an end case in the column renaming step I perform after importing.
I can make a fix for this soon but it's not my top priority at the moment.
The good news is that if you change the column names to longer more informative names even to "Mut" and "WT" in the actual table file.
This will make it work for you in the mean time and you can continue the analysis.
Good luck,
Ben

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

No branches or pull requests

2 participants