Resolving issue #29 was accomplished by definition a community profile object hierarchy, to include the notion of a Molecule which contains Segments. This replaces the bottom-most object which was merely the sequence records.
Now, users must specify in the community profile the molecule to which each sequence belongs. This allows the use of draft genomes -- which dominate the public sequence databases.
The tab-delimited flat community profile table now included a 4th mandatory column. The keys used for molecules are not special and can be whatever the user chooses. The header column is not required and any line beginning with a # is treated as a comment.
Resolving issue #29 was accomplished by definition a community profile object hierarchy, to include the notion of a
Molecule
which containsSegments
. This replaces the bottom-most object which was merely the sequence records.Now, users must specify in the community profile the molecule to which each sequence belongs. This allows the use of draft genomes -- which dominate the public sequence databases.
The tab-delimited flat community profile table now included a 4th mandatory column. The keys used for molecules are not special and can be whatever the user chooses. The header column is not required and any line beginning with a
#
is treated as a comment.