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

feat: Deliver MultiQC intermediate files #1388

Merged
merged 13 commits into from
Feb 10, 2024
Merged

Conversation

ivadym
Copy link
Contributor

@ivadym ivadym commented Feb 5, 2024

Description

Add MultiQC intermediates files to the deliverables .hk file.

Added

  • MultiQC intermediate files to deliverables

Changed

  • delivery.py, removing unused arguments

Documentation

  • N/A
  • Updated Balsamic documentation to reflect the changes as needed for this PR.
    • [Document Name]

Tests

Feature Tests

  • N/A
  • Test generation of the .hk file
    Screenshot 2024-02-05 at 14 51 31
  • Test MultiQC files included in the deliverables .hk file with unique tags
    Screenshot 2024-02-05 at 14 52 54
  • Test that different workflow generate the intermediate MultiQC expected files

Pipeline Integrity Tests

  • Report deliver (generation of the .hk file)
    • N/A
    • Verified
  • TGA T/O Workflow
    • N/A
    • Verified
  • TGA T/N Workflow
    • N/A
    • Verified
  • UMI T/O Workflow
    • N/A
    • Verified
  • UMI T/N Workflow
    • N/A
    • Verified
  • WGS T/O Workflow
    • N/A
    • Verified
  • WGS T/N Workflow
    • N/A
    • Verified
  • QC Workflow
    • N/A
    • Verified
  • PON Workflow
    • N/A
    • Verified

Clinical Genomics Stockholm

Documentation

  • Atlas documentation
    • N/A
    • Updated: [Link]
  • Web portal for Clinical Genomics
    • N/A
    • Updated: [Link]

User Changes

  • N/A
  • This PR affects the output files or results.
    • User feedback is considered unnecessary because [Justification].
    • Affected users have been included in the development process and given a chance to provide feedback.

Infrastructure Changes

Integration Tests

Checklist

Important

Ensure that all checkboxes below are ticked before merging.

For Developers

  • PR Description
    • Provided a comprehensive description of the PR.
    • Linked relevant user stories or issues to the PR.
  • Documentation
    • Verified and updated documentation if necessary.
  • Tests
    • Described and tested the functionality addressed in the PR.
    • Ensured integration of the new code with existing workflows.
    • Confirmed that meaningful unit tests were added for the changes introduced.
    • Checked that the PR has successfully passed all relevant code smells and coverage checks.
  • Review
    • Addressed and resolved all the feedback provided during the code review process.
    • Obtained final approval from designated reviewers.

For Reviewers

  • Code
    • Code implements the intended features or fixes the reported issue.
    • Code follows the project's coding standards and style guide.
  • Documentation
    • Pipeline changes are well-documented in the CHANGELOG and relevant documentation.
  • Tests
    • The author provided a description of their manual testing, including consideration of edge cases and boundary
      conditions where applicable, with satisfactory results.
  • Review
    • Confirmed that the developer has addressed all the comments during the code review.

@ivadym ivadym self-assigned this Feb 5, 2024
@ivadym ivadym requested a review from a team as a code owner February 5, 2024 13:23
@ivadym ivadym linked an issue Feb 5, 2024 that may be closed by this pull request
5 tasks
@ivadym ivadym changed the base branch from master to develop February 5, 2024 13:26
Copy link

codecov bot commented Feb 5, 2024

Codecov Report

Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (790ad8a) 99.42% compared to head (fe40771) 99.44%.
Report is 88 commits behind head on develop.

Files Patch % Lines
BALSAMIC/models/validators.py 85.71% 2 Missing ⚠️
Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #1388      +/-   ##
===========================================
+ Coverage    99.42%   99.44%   +0.01%     
===========================================
  Files           41       40       -1     
  Lines         1916     1983      +67     
===========================================
+ Hits          1905     1972      +67     
  Misses          11       11              
Flag Coverage Δ
unittests 99.44% <99.74%> (+0.01%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Copy link
Collaborator

@mathiasbio mathiasbio left a comment

Choose a reason for hiding this comment

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

This looks great 🌟 Looks like you also took the opportunity to do some refactoring. Feels like this deliver.py is easier to read now! I just added a question, but even if you haven't tested it explicitly I trust in the logic of your code. Just wanted to make sure that it has been considered : )

Copy link

Quality Gate Passed Quality Gate passed

Issues
0 New issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

@ivadym ivadym merged commit 2745116 into develop Feb 10, 2024
8 checks passed
@ivadym ivadym deleted the deliver-multiqc-files branch February 10, 2024 17:48
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.

[User Story] Start Storing Intermediate MultiQC Files
2 participants