-
Notifications
You must be signed in to change notification settings - Fork 10
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
Propagate mcols NormalIRanges #13
Conversation
NormalIRanges, NormalIRanges can propagate mcols of none, x, y, or both (default none) NormalIRanges, IntegerRanges can propagate mols of x or none (default none)
NormalIRanges, IntegerRanges can propagate mcols of x or none — defaults to none not working — new tests fail and I can’t figure out why — appears that the new function _does not work correctly_ as demonstrated in the new test (ie. not a problem with the test)
The current proposal with the It's important that we try to preserve as much coherence as possible to the IRanges/GenomicRanges stack. Please use this style
instead of
for consistency with the existing style. Always use double quotes ( It is usually better to use
than doing:
Finally the setops-methods.Rd man page would need to be updated (add required aliases, add the 2 new methods to Usage section, and add some examples showing the behavior of these new methods). And yes adding tests for these new methods is important. Thanks! |
Okay, will do. The reason I think it's important to allow the option not to propage the mcols is that, as you said, the mcols requires a call to Are you saying that the |
I missed the possible usefulness of |
still having problems with dispatch — some tests failing
I've made the edits you recommended. But I am having some issues with S4 method dispatch. For example, when I call
|
I can't reproduce this:
Then from R:
Please only name optional arguments (i.e. arguments with a default value) in your function calls. So for example do:
instead of:
or:
instead of:
Thanks! sessionInfo()
|
I fixed the argument naming issue. I'm still seeing the same bugs, though. I wonder if it could have to do with the fact that my BiocGenerics version is behind yours. Seems like I'd have to update to a pre-release version of R to get BiocGenerics 0.29. Could that be the problem? Typically, I wait until the release version of R to download.
And here's my 'intersect' methods and sessionInfo...
|
You have a mix of release (BioC 3.8) and devel (BioC 3.9) packages. This can only cause trouble. Make sure you always install packages with Bioconductor packages should always be developed against the current devel version of Bioconductor, which is BioC 3.9 at the moment, and is tied with R 3.6. So yes, you need a recent R 3.6 (e.g. R 3.6 beta) and BioC 3.9. Loading BiocManager will tell you what version of Bioconductor you are using:
|
Ah, I see. I've gotten R 3.6 and the devel version of Bioconductor and the errors seem the same to me. The only difference I see between your
|
Nevermind on that idea -- the only change since I forked was incrementing the version number. |
As discussed in #12
For intersect, I implemented two new signatures:
I wrote some tests for these new signatures and they pass
For setdiff, I implemented one new signature:
I wrote tests for this new signature, which currently fail. (https://github.com/rcorty/IRanges/blob/aaa83ff9fb7fcc54d2c78029839f1a45375ebcf4/inst/unitTests/test_setops-methods.R#L71-L84) I haven't been able to figure out why. When I run the individual commands in the function definition on the inputs, the right result is produced, but inside the package, it doesn't work. Can someone more experienced have a look? I wonder if it has to do with getting the call dispatched to the correct signature?