Closed TheLemonPig closed 1 year ago
I followed the documentation instructions for adding a package to AutoRA, which meant making the repo locally. Would it make sense to make it an AER repository?
Hi Joshua! I see what you've done – created a package with common utilities for dealing with general computation trees, and applied that to the SR, BSR and BMS approaches. I like it!
Before we merge it, I think you'll need to think about how best to use it. The current approach for AutoRA is that each model has its own repository, and BMS/BSR follow that. What you could do is make the current theorist-toolkit with the models into a more specific computation-tree-library without the models, and then import that as a dependency in each of the BSR/BMS packages. That would mean that you wouldn't break any existing functionality, and people who were using BMS/BSR get the benefit of the updated backend.
But before you make a package like that which serves as the foundation of other packages, you'll need a couple of other bits. Things like:
sympy
to do the same thing or to get a long way there, that might reduce your maintenance load and give you additional functionality for free, and allow us to close some existing issues (https://github.com/AutoResearch/autora/issues/301).from autora.utils.computation_tree import Tree, replace_node, Temperature
or from subpackages?
Description
Initial PR to pull the toolkit into AutoRA as a pre-release
Type of change
Features (Optional)
Remarks (Optional)