track motif genealogy in MoVRs_MotifSetReduce.pl #13
Description
We probably should create a good logfile that traces the consensus motif generation in this script. This would include untangling the final names - the current suffixes were meant for a bit of tracing during development, but this is inadequate for code distribution.
We also need to think about some edge cases of motif merging. In principle, it could be that, for example, we have two 8-mer motifs that overlap by a 6-mer, with 2-mer overhangs on each end: do we report the 6-mer as a consensus motif (which may be found everywhere) or the 10-mer (which may not be found anywhere) or else? The code is flexible enough to go any direction, but we need to review what it is doing currently and document choices.
Coding assigned to me, but issue formulation and example collection is an issue for the team.