In the same screen that asks the user to provide the URL of the PyGrid, adding a field where the user can provide the model version he wants to use, this is because when hosting the training and averaging plan on the {yGrid using a specific version,
the KotlinSyft worker needs to request the same version, but what if I need to change the plans? I have to change the version from the notebook and then host the new plans using a new version number.
Is your feature request related to a problem?
What alternatives have you considered?
What is currently happening is each time I want to host a new plan on the grid I have to change the code inside the app, build it for each worker I have (because each worker has his own raw pixels and labels) then I have to export the 3 apks, then install them on 3 different devices, which is frustrating if I want to experiment with different plans.
Hey @AbdulRahmandata That's a nice idea. Can you add a PR for the same? You would need to modify the login activity to another field for model name and pass it along just like we pass pygrid URL.
Feature Description
In the same screen that asks the user to provide the URL of the PyGrid, adding a field where the user can provide the model version he wants to use, this is because when hosting the training and averaging plan on the {yGrid using a specific version, the KotlinSyft worker needs to request the same version, but what if I need to change the plans? I have to change the version from the notebook and then host the new plans using a new version number.
Is your feature request related to a problem?
What alternatives have you considered?
What is currently happening is each time I want to host a new plan on the grid I have to change the code inside the app, build it for each worker I have (because each worker has his own raw pixels and labels) then I have to export the 3 apks, then install them on 3 different devices, which is frustrating if I want to experiment with different plans.