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

y.field with multiple fields? #3

Open
walaj opened this issue Mar 20, 2016 · 3 comments
Open

y.field with multiple fields? #3

walaj opened this issue Mar 20, 2016 · 3 comments

Comments

@walaj
Copy link
Collaborator

walaj commented Mar 20, 2016

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

@walaj
Copy link
Collaborator Author

walaj commented Mar 20, 2016

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.

@mskilab
Copy link
Collaborator

mskilab commented Mar 20, 2016

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

@walaj
Copy link
Collaborator Author

walaj commented Mar 20, 2016

Ok perfect, that's what I was hoping. The y.field vector makes sense, but I was confused by the others. This is a good solution.

@walaj walaj closed this as completed Mar 20, 2016
@walaj walaj reopened this Mar 20, 2016
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