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

specifying chromosome does not map aliases if gene is correct on another chromosome #11

Open
lwaldron opened this issue Jan 12, 2021 · 7 comments
Assignees

Comments

@lwaldron
Copy link
Member

Here is an example. @Aggarwal-Ayush would you see if you can fix this?

library(HGNChelper)
#> Please cite our software :) 
#>  
#>  Sehyun Oh et al. HGNChelper: identification and correction of invalid gene symbols for human and mouse. F1000Research 2020, 9:1493. DOI: https://doi.org/10.12688/f1000research.28033.1 
#>  
#>  Type `citation('HGNChelper')` for a BibTeX entry.
hgnc.table[hgnc.table$Symbol == "TKT" | hgnc.table$Approved.Symbol == "TKT", ]
#>    Symbol Approved.Symbol chromosome
#> 1:    TKT            DDR2          1
#> 2:    TKT             TKT          3
checkGeneSymbols(c("TKT", "TKT"), chromosome = c(1, 3))
#> Maps last updated on: Mon Sep 28 18:31:21 2020
#>     x Approved Suggested.Symbol Input.chromosome Correct.chromosome
#> 1 TKT     TRUE              TKT                1                  1
#> 2 TKT     TRUE              TKT                3                  3

The desired behavior for a unit test would be:

library(testthat)
library(HGNChelper)
res <- checkGeneSymbols(c("TKT", "TKT"), chromosome = c(1L, 3L))
expect_identical(res$Approved, c(FALSE, TRUE))
expect_identical(res$Suggested.Symbol, c("DDR2", "TKT"))
expect_identical(res$Input.chromosome, c(1L, 3L))
expect_identical(res$Correct.chromosome, c(1L, 3L))
@Aggarwal-Ayush
Copy link
Contributor

Sure. I'll fix it.

lwaldron added a commit that referenced this issue Jan 20, 2021
Rectified Issue #11: specifying chromosome does not map aliases if gene is correct on another chromosome
@lwaldron
Copy link
Member Author

@Aggarwal-Ayush just checking if this is still on your radar?

@Aggarwal-Ayush
Copy link
Contributor

@lwaldron This issue was resolved in my last PR.

@lwaldron
Copy link
Member Author

lwaldron commented Jan 28, 2021 via email

@Aggarwal-Ayush
Copy link
Contributor

Yes, that I'm looking into but so far I've not been able to find the cause of that error. I'll check again.

@lwaldron
Copy link
Member Author

Hi @Aggarwal-Ayush I just did some other minor updates and am getting ready to update CRAN in advance of posting the response to reviewers. Any luck?

@Aggarwal-Ayush
Copy link
Contributor

Hi @lwaldron All the checks were passed in my last PR. This issue can be closed now.

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