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.

Sign up for GitHub

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

Jump to bottom

Establish naming convention for latent features #86

Open
gwaybio opened this issue Oct 6, 2017 · 0 comments
Open

Establish naming convention for latent features #86

gwaybio opened this issue Oct 6, 2017 · 0 comments
Labels
enhancement
Projects
Tybalt Evaluation

Comments

@gwaybio
Copy link
Collaborator

gwaybio commented Oct 6, 2017

This has caused issues in the past (see #63) and was again brought up in greenelab/pancancer#59

I will need to revisit how features are named. This could be as simple as node_algorithm format. For example, ADAGE feature 17 would be 17_adage but could ease frustration and prevent breakage in the future.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
Tybalt Evaluation
To Do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@gwaybio