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

DIG-1533: cancer_type->primary_site & DIG-1583: Implement censoring on aggregate count threshold #40

Merged
merged 4 commits into from
Jun 10, 2024

Conversation

OrdiNeu
Copy link
Collaborator

@OrdiNeu OrdiNeu commented May 24, 2024

Best tested from CanDIGv2's feature/censoring-and-rename-cancer-type branch

Description

Includes #37 because it is required to handle the new version of Katsu

This both handles data censoring on discovery queries for low counts, and renaming cancer_type to primary_site.

To test:

  • curl candig.docker.internal:5080/query/discovery/programs -H "Authorization: Bearer $TOKEN"
  • curl candig.docker.internal:5080/query/genomic_completeness -H "Authorization: Bearer $TOKEN"
  • curl candig.docker.internal:5080/query/discovery/query -H "Authorization: Bearer $TOKEN"

Copy link
Contributor

@SonQBChau SonQBChau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

tested and it worked. LGTM

@OrdiNeu OrdiNeu force-pushed the feature/censoring branch from 31cd6ba to 6a1236c Compare May 28, 2024 18:00
@mshadbolt mshadbolt changed the title Feature/censoring DIG-1533: cancer_type->primary_site & DIG-1583: Implement censoring on aggregate count threshold May 28, 2024
@OrdiNeu OrdiNeu merged commit e079eb7 into develop Jun 10, 2024
@OrdiNeu OrdiNeu deleted the feature/censoring branch June 10, 2024 14:18
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

Successfully merging this pull request may close these issues.

2 participants