-
Notifications
You must be signed in to change notification settings - Fork 12
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
track.splice #7
Comments
would it be a good idea to include it in gTrack? and since it relies on read.bam, wouldn't bamUtils be a good place for it? |
well it relies on both, so if we include in one package then we have to add actually gTrack supports bams and ucsc formats, so it will need to depend so let's keep in gTrack On Wed, Mar 30, 2016 at 8:13 PM, Khagay Nagdimov [email protected]
|
ah okay and then I'll add read.bam to bamUtils and add the dependency of bamUtils in gTrack? |
Let’s wait to see what Jeremiah thinks On March 30, 2016 at 8:30:26 PM, Khagay Nagdimov ([email protected]:[email protected]) wrote: ah okay and then I'll add read.bam to bamUtils and add the dependency of bamUtils in gTrack? — This electronic message is intended for the use of the named recipient only, and may contain information that is confidential, privileged or protected from disclosure under applicable law. If you are not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any reading, disclosure, dissemination, distribution, copying or use of the contents of this message including any of its attachments is strictly prohibited. If you have received this message in error or are not the named recipient, please notify us immediately by contacting the sender at the electronic mail address noted above, and destroy all copies of this message. Please note, the recipient should check this email and any attachments for the presence of viruses. The organization accepts no liability for any damage caused by any virus transmitted by this email. |
What if we did it the other way around. gTrack is most exciting / closest to release, and I don't want to have to release bamUtils ahead of it just for one function. We can switch it into a later release of gTrack later (and thus the bamUtils dependency), since adding functions is not a problem for backwards compatibility.
|
Ok sounds fine in principle regarding waiting for later releases Kind of a letdown though if we can't show an example with plotting reads. Eventually I'd like to work in direct bam compatibility - i.e. let bam path On Thursday, March 31, 2016, Jeremiah Wala [email protected] wrote:
|
Yeah, I see what you mean regarding the examples. Even if it's in "suggests", it won't make it onto CRAN without having all the dependent and suggested packages on their as well... May be that we just try and release bamUtils before gUtils, even we have the bandwidth to get this ready. |
ok sounds good .. One interim option would be to use Rsamtools in the examples, i.e. using This would be uglier but would avoid having to get bamUtils ready. It Another option is add read.bam back to gUtils - which would add an On Thu, Mar 31, 2016 at 12:47 PM, Jeremiah Wala [email protected]
|
just to summarize - should we keep read.bam in BamUtils and release that package. Then, include BamUtils as a dependency in gTrack before gTrack release. |
yes I think so
…On Mon, Dec 5, 2016 at 3:00 PM, Khagay Nagdimov ***@***.***> wrote:
just to summarize - keep read.bam in BamUtils and release that package.
Then, include BamUtils as a dependency in gTrack before gTrack release.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#7 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AL-0kSPmfwdV-dr40aAUD2NZm9Bv2xRAks5rFG1dgaJpZM4H8Rrp>
.
|
where should we put this?
I like keeping it gTrack - I think it shows off gTrack very nicely, however it relies on read.bam, so we have a little dependency crisis
otherwise we should at least put into skitools
The text was updated successfully, but these errors were encountered: