-
Notifications
You must be signed in to change notification settings - Fork 321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hierarchy of experiments #189
Comments
@newtonle - thanks for your interest! Can you elaborate what you mean by "grouping" in this case, and the sort of API you'd like to use for accessing this grouping? Phrased differently, what is the sort of functionality you hope to leverage this grouping for? We are actually working on a way of grouping experiments into "Projects" (where the project may have some basic metadata, such as owners, description, etc.). At the moment, this is not yet available through the ServiceAPI, but if I better understand how you want to use this abstraction, we can evaluate building that out. I'd be happy to discuss requirements you may have in more detail, as well; feel free to contact me directly. |
Essentially, imagine a directory-like structure, where an experiment is referenced by |
We will now be tracking wishlist items / feature requests in a master issue for improved visibility: #566. Of course please feel free to still open new feature requests issues; we'll take care of thinking them through and adding them to the master issue. |
I'm interested in using AxClient with a SQL backend for multiple users at Twitter. Ideally, the experiments would be grouped by users and projects. Is there any recommended way of doing this? Or is this on a roadmap? How can I be aware of future features for Ax?
The text was updated successfully, but these errors were encountered: