Rather than only procedurally generated trees, we should reintroduce the ability to have defined trees. Either as a file reference or string in YAML config. Concern that the YAML string may prove problematic when creating filesystem instance -- due to illegal character use. For file references, we must either impose absolute paths or add logic for relative ones when in working directories.
Trees defined as such then have ntaxa defined also. Therefore this detail should move into tree parameter of Clade. A tree is then either a set of grouped parameters
For future utility with multiple algorithms, this would be more complete
Rather than only procedurally generated trees, we should reintroduce the ability to have defined trees. Either as a file reference or string in YAML config. Concern that the YAML string may prove problematic when creating filesystem instance -- due to illegal character use. For file references, we must either impose absolute paths or add logic for relative ones when in working directories.
Trees defined as such then have
ntaxa
defined also. Therefore this detail should move intotree
parameter of Clade. A tree is then either a set of grouped parametersFor future utility with multiple algorithms, this would be more complete
OR explict definitions either as file or string
OR