-
Notifications
You must be signed in to change notification settings - Fork 0
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
Adding arm-level CNA data #332
Comments
Second this - We end up loading it as sample data for all the arms which is perhaps less than ideal from a ui point of view. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
unstale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Unstale |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
1 similar comment
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Modified description:
CC: @jjgao |
@dippindots I removed the items related to query arm-level cna data. I think the benefit may not justify the cost to implement that. |
@jjgao Thanks! |
Just wanted to capture the idea - this is not a priority.
future tasks:
create another profile typesArm-level copy number alteration
in query interfaceallow user to type1p
or1p:gain
or1p:hetloss
in gene box for queryingoql, faq,data formatadd to Cancer Types Summary tab when it's possible to queryadd to Mutual Exclusivity tab when it's possible to query@cBioPortal/product
The text was updated successfully, but these errors were encountered: