search

sate-dev / sate-core

3 stars 3 forks source link

start_tree_search_from_current does not impact final raxml run #16

Closed smirarab closed 12 years ago

smirarab commented 12 years ago

Final raxml run continues to use starting trees even if start_tree_search_from_current = False.

The following code in mainsate.py needs to change to check for start_tree_search_from_current

                post_job = rte.create_job(job.multilocus_dataset,
                                    starting_tree=job.tree,
                                    num_cpus=sate_config.num_cpus,
                                    context_str="postraxtree",
                                    tmp_dir_par=post_tree_dir,
                                    delete_temps=delete_tree_temps,
                                    sate_products=sate_products,
                                    step_num="postraxtree")
joaks1 commented 12 years ago

Commit 4077ba0d68e3d4e7e55f259dab1c7a6e3989a985 modifies the behavior of the post-processing raxml search to co-opt the sate-algorithm boolean start_tree_search_from_current to determine whether to use the tree produced by the sate algorithm as a starting tree.