-
Notifications
You must be signed in to change notification settings - Fork 978
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
Timeline / interest for not yet implemented foverlaps() functionality #3002
Comments
Related: #3007 foverlaps error message could be more informative |
@sritchie73 thanks for this. I wrote |
Some potentially helpful other references: bedops, bedtools, tidygenomics. |
Hi, just wondering if maxgap, minoverlap is likely to be implemented soon? I think it would be a brilliant addition to avoid the conversion to GRanges object. |
Hey @Al-Murphy that's definitely in "contributions welcome" status... happy to support however I can if you wanted to take up the gauntlet 😃 cc @arunsrinivasan who would be most familiar with that part of the code base & maybe better able to offer "mentor" support (not sure availability) |
For those looking for not yet implemented functionality in foverlaps, please go to #528 (comment) and provide example code |
There are a number of arguments in the
foverlaps()
function that are not yet implemented:type = "equal"
- [FR] foverlaps type="equal" implementation #3416maxgap
minoverlap
Along with a few requested features:
minoverlap
foverlaps()
should work withoutsetkey()
beforehandfoverlaps()
could work with factor levelsThere will be a lesson on the
foverlaps()
function in the DataCamp course on joins, so I'm wanting to gauge whether its worth trying to implement these features before the course is released. Are there obvious technical barriers that have prevented these features from being implemented? Or has there been a lack of interest from the community and developers, e.g. given the availability ofGenomicRanges
?The text was updated successfully, but these errors were encountered: