Skip to content

Feature/check contamination#47

Merged
sawibo merged 26 commits intodevelopfrom
feature/check_contamination
Apr 30, 2021
Merged

Feature/check contamination#47
sawibo merged 26 commits intodevelopfrom
feature/check_contamination

Conversation

@ellendejong
Copy link
Contributor

@ellendejong ellendejong commented Feb 17, 2021

What has changed?

A process is implemented to estimate DNA contamination.

Additional information

Azure backlog item: https://dev.azure.com/umcu/LAB-Bioinformatics-Genetics/_workitems/edit/63171
https://dev.azure.com/umcu/LAB-Bioinformatics-Genetics/_workitems/edit/66906

DxNextflowWes UMCUGenetics/DxNextflowWES#28

I keep track of to-do's in Azure and pull-request DxNextflowWes.

rernst and others added 2 commits July 10, 2020 10:10
…oadInstitute. The process runs verifyBamID to retrieve estimation table and calculate contamination float.
@ellendejong ellendejong marked this pull request as draft February 17, 2021 09:34
@ellendejong ellendejong marked this pull request as ready for review February 23, 2021 08:24
@ellendejong ellendejong requested a review from rernst February 23, 2021 08:41
Copy link
Member

@rernst rernst left a comment

Choose a reason for hiding this comment

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

Could you add this parameter and let nextflow set the number of threads based on the process cpus config.

--NumThread      [Int] Set number of threads in likelihood calculation[default:4]

@ellendejong
Copy link
Contributor Author

Could you add this parameter and let nextflow set the number of threads based on the process cpus config.

--NumThread      [Int] Set number of threads in likelihood calculation[default:4]

@rernst Ratio threads:cpu is not 1:1 on the HPC, i believe. Do we use a scaling factor somewhere?

@rernst
Copy link
Member

rernst commented Apr 29, 2021

Could you add this parameter and let nextflow set the number of threads based on the process cpus config.

--NumThread      [Int] Set number of threads in likelihood calculation[default:4]

@rernst Ratio threads:cpu is not 1:1 on the HPC, i believe. Do we use a scaling factor somewhere?

No we don't correct / adjust for hyperthreading, we just use ${task.cpus}.

@rernst rernst self-requested a review April 30, 2021 07:14
@rernst rernst requested a review from sawibo April 30, 2021 07:15
Copy link
Member

@sawibo sawibo left a comment

Choose a reason for hiding this comment

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

Dikke prima

@sawibo sawibo merged commit eeda3b7 into develop Apr 30, 2021
@ellendejong ellendejong deleted the feature/check_contamination branch April 30, 2021 08:00
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.

3 participants