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

Report ccv score/temperature on case report #5173

Open
wants to merge 7 commits into
base: main
Choose a base branch
from

Conversation

molucorner
Copy link
Collaborator

This PR adds a functionality or fixes a bug.

Closes issue #5143

Testing on cg-vm1 server (Clinical Genomics Stockholm)

Prepare for testing

  1. Make sure the PR is pushed and available on Docker Hub
  2. Fist book your testing time using the Pax software available at https://pax.scilifelab.se/. The resource you are going to call dibs on is scout-stage and the server is cg-vm1.
  3. ssh <USER.NAME>@cg-vm1.scilifelab.se
  4. sudo -iu hiseq.clinical
  5. ssh localhost
  6. (optional) Find out which scout branch is currently deployed on cg-vm1: podman ps
  7. Stop the service with current deployed branch: systemctl --user stop scout.target
  8. Start the scout service with the branch to test: systemctl --user start scout@<this_branch>
  9. Make sure the branch is deployed: systemctl --user status scout.target
  10. After testing is done, repeat procedure at https://pax.scilifelab.se/, which will release the allocated resource (scout-stage) to be used for testing by other users.
Testing on hasta server (Clinical Genomics Stockholm)

Prepare for testing

  1. ssh <USER.NAME>@hasta.scilifelab.se
  2. Book your testing time using the Pax software. us; paxa -u <user> -s hasta -r scout-stage. You can also use the WSGI Pax app available at https://pax.scilifelab.se/.
  3. (optional) Find out which scout branch is currently deployed on cg-vm1: conda activate S_scout; pip freeze | grep scout-browser
  4. Deploy the branch to test: bash /home/proj/production/servers/resources/hasta.scilifelab.se/update-tool-stage.sh -e S_scout -t scout -b <this_branch>
  5. Make sure the branch is deployed: us; scout --version
  6. After testing is done, repeat the paxa procedure, which will release the allocated resource (scout-stage) to be used for testing by other users.

How to test:

  1. how to test it, possibly with real cases/data

Expected outcome:
The functionality should be working
Take a screenshot and attach or copy/paste the output.

Review:

  • code approved by
  • tests executed by

Copy link

codecov bot commented Jan 13, 2025

Codecov Report

Attention: Patch coverage is 42.85714% with 8 lines in your changes missing coverage. Please review.

Project coverage is 84.46%. Comparing base (188e871) to head (0d28b14).

Files with missing lines Patch % Lines
scout/server/blueprints/cases/controllers.py 38.46% 8 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #5173      +/-   ##
==========================================
- Coverage   84.50%   84.46%   -0.04%     
==========================================
  Files         327      327              
  Lines       19789    19800      +11     
==========================================
+ Hits        16722    16725       +3     
- Misses       3067     3075       +8     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@dnil dnil self-assigned this Jan 14, 2025
Copy link
Collaborator

@dnil dnil left a comment

Choose a reason for hiding this comment

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

Thank you @molucorner! As you like with the alignment - the report layout is messy as it is - but if you don't have a specific reason, I would say leave the centering out.

@@ -674,7 +674,7 @@ <h4>Scout case analysis report</h4> - created on:&nbsp;<strong>{{report_created_
{% endif %}
</tr>
</thead>
<tbody>
<tbody style="text-align:center;">
Copy link
Collaborator

Choose a reason for hiding this comment

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

Hm, the alignment in general isn't super consistent on the report, but to me a couple of table lines in the bulk there with suddenly centered numbers stands out a bit, where it would look quite good on its own. If you had good reason, keep it - it seems to align somewhat with some other columns in the same card - but otherwise seems easier to keep them all defaulting left.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

The only reason is that I personally think it looks better, but I don't have a problem changing it back

@@ -715,7 +715,7 @@ <h4>Scout case analysis report</h4> - created on:&nbsp;<strong>{{report_created_
{% endif %}
<td>
{% if variant.acmg_classification %}
<span class="badge rounded-pill bg-{{variant.acmg_classification['color'] if variant.acmg_classification['color'] else 'secondary'}}" title="{{variant.acmg_classification['code']}}">{{variant.acmg_classification['code'] }}</span>
<span class="badge rounded-pill bg-{{variant.acmg_classification['color'] if variant.acmg_classification['color'] else 'secondary'}}" title="{{variant.acmg_classification['label']}}">{{variant.acmg_classification['label'] }}</span>
Copy link
Collaborator

Choose a reason for hiding this comment

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

💯

@dnil dnil removed their assignment Jan 14, 2025
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.

CCV bayesian score classifications (Ie cold VUS etc) on general report
3 participants