You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looks like there is some code to check for y.field being length > 1 in "initialize". Should we maintain this? Looks like it just re-creates length(y.field) .Objects
The text was updated successfully, but these errors were encountered:
This is also the case for a lot of arguments that allow for scalar or vector inputs (but not all). Propose to leave all the multi-track details to "c" and not support vector formatting inputs in the gTrack constructor, to avoid ambiguity and make more robust / simple.
a vector y.field does replicate an object - this is tremendously useful syntax for quickly plotting many fields (eg covariates) from a single gRanges object.
aside from this feature I'm happy with restricting all the args to be scalar --> i.e. unless y.field is a vector. In all other cases use of c() is best
Looks like there is some code to check for y.field being length > 1 in "initialize". Should we maintain this? Looks like it just re-creates length(y.field) .Objects
The text was updated successfully, but these errors were encountered: