Skip to content

Conversation

@markmcdowall
Copy link
Member

Code refactoring to avoid namespace collisions when there are multiple repos that have used the same template

@markmcdowall markmcdowall self-assigned this Jul 6, 2018
docs/adr.rst Outdated
2018-06-27 - Remove reads marked as duplicate by BioBamBam
----------------------------------------------------------

BioBamBam only marks reads as duplicate, but does not remove the after. The Tool has been updated to remove the flagged duplicates using samtools with the parameter `-F 1024`. This matches the pipeline used within the `Blueprints project <http://dcc.blueprint-epigenome.eu/#/md/chip_seq_grch37>`_.
Copy link
Contributor

Choose a reason for hiding this comment

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

does not remove theM ?

docs/adr.rst Outdated
2018-07-05 - Refactoring of repo to avoid naming collisions
-----------------------------------------------------------

The original repo had the tools and tests in a directory that was in the root of the repo. This is problematic when there is sharing of the code as there are collisions in teh name space. This has meant that all of the code needs to be moved into a new subdirectory (mg_process_fastq).
Copy link
Contributor

Choose a reason for hiding this comment

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

the* name

[pytest]
#testpaths = tests
#testpaths = mg_process_fastq/tests
norecursedirs = data tmp* env docs apps basic_modules *.egg_info TADbit-master
Copy link
Contributor

Choose a reason for hiding this comment

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

no new line sign

Copy link
Member Author

Choose a reason for hiding this comment

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

That's fine

…tools to allow for easy importing into other pipelines.
…ce code duplication and allow for this script to be used as a single as part of the mg-tool-api
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