HI QuizzicalDove0
I guess the reason is that the idea is integration is literally 2 lines, and it will take less time to execute the code on a system with working env (we assume there is one) then to configure all the git , python packages, arguments etc...
All that said you can create an experiment from code , using Task.import_task https://allegro.ai/docs/task.html#trains.task.Task.import_task
Great, thanks for confirming! Is there any reason why it's not possible to define the experiment in the UI directly?
You can always clone a “template” task and change everything (it will be on draft mode), what is you use case? maybe we already have a solution for it
Hi QuizzicalDove0 ,
Yes, you need to create the definition of the experiment, but you can add to your code the following linetask.execute_remotely(queue_name=<queue name>)This will stop running you code and enqueue the task to a specific queue (which the agent will run).