As our plan is to split off certain pieces of code into their own repositories and then reintegrate them as submodules in meta-sweeper, we have to decide how shared python modules will be organised.
Currently, io_utils.py and abundance.py are used in sim3C and meta-sweeper. It is a poor situation to duplicate this code between repositories, however these elements do not represent a single concern and it would be odd to throw them into a catch-all.
Beyond these two, there are other pieces of code which are shared and I would actually say there is an unacceptable amount of duplication of trivial functions across all my bioinformatics modules on Github. Some of these have not made it across from Aaron's pipeline repo.
As our plan is to split off certain pieces of code into their own repositories and then reintegrate them as submodules in meta-sweeper, we have to decide how shared python modules will be organised.
Currently, io_utils.py and abundance.py are used in sim3C and meta-sweeper. It is a poor situation to duplicate this code between repositories, however these elements do not represent a single concern and it would be odd to throw them into a catch-all.
Beyond these two, there are other pieces of code which are shared and I would actually say there is an unacceptable amount of duplication of trivial functions across all my bioinformatics modules on Github. Some of these have not made it across from Aaron's pipeline repo.