-
Notifications
You must be signed in to change notification settings - Fork 4
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
Test scalability of hyperparameters setting #100
Comments
Out of scope for this week's planning. Would suggest to keep it on |
Since starting Q3, this enters the current scope. However, I think this is blocked by Docker images/Docker-compose to be able to have a testing environment. I'm open to suggestions that tell other opinions but as of now I think it's: |
Might still be blocked, however the competition could prove to be such test of hyperparameters. Would require more info on what's the expected output of this task. Maybe it is enough with the competition and we just need to define the output of this task rather than the steps to complete it. Think this still needs triage by the @masa-finance/subnet team as a whole |
+1 Suggest we close this since iteration over the subnet is being done on the fly by the needs of the environment. This might be already redundant or outdated by now |
Linking this to task #77 for @5u6r054 to test at scale.
Since we currently don't know if the provided implementation can support more than 1 node, we want to scale testing of the implementation.
Action items:
The text was updated successfully, but these errors were encountered: