I will open one

Yes

But that's not the case

in the file's name

Of course you can edit which parameters you like

Obviously I am working with my trains-server, as I can see the new pipeline task under the new project 😮

in /tmp/.trainsagent_5031_f4iwisna.tmp
For example

great, will try this

But it still doesn't answer one thing, why when I cloned a previously successful experiment, it failed on git diff?

I'll do as Jake says. Thanks :)

Sure, but before that, it seems that the script path parameter (which I think you refer to as entry_point) is not relative to the base of the repo, as I expected it to be, could that interfere?

I'm confused. Why would that matter what my local code is when trying to replicate an already ran experiment?
Also, between which files is the git diff performed? (I've seen the line
diff --git a/.../run.py b/.../run.pybut I'm not sure what's a and what's b in this context)

I will try that.
In addition, I've seen that the file location of a task is saved, does it mean that when rerunning said task (for example clone it and enqueue it) trains will search for the file in the stored location? Or will it clone the repo with the given commit id and use the relative path to find this file?

I am not sure what you mean by verifying the API.

you could do something like 'tags':{'AND':['pipe','training']}
And the user could decide if he wants AND or OR logic

Since my servers have a shared file system, the init process tells me that the configuration file already exists. Can I tell it to place it in another location? GrumpyPenguin23

or do you mean it tries to apply the already ran experiment's uncommitted changes? If that's the case, why did the new experiment fail if the previous experiment ran successfully?

This is the path:
/Remote/moshe/Experiments/trains_bs_pipe_new/ypi/OKAY/Try_That/baseline/evaluation_validation/results/images/bottom_scores/0.0_slot02_extracted_23_01__1035__1.png

(The one that was created with initial task)

Hmm
AttributeError: 'Task' object has no attribute 'tags'

Something else, If I want to designate only some of the GPUs of a worker, how can I do that?

Hmm, that's quite an uncomfortable syntax. How does this work with wanting to apply an "AND" logic only to tags, in the task_filter?

Nevermind, you can find it in the apiserver.conf

Sure

Will try, thanks

Hmm, is there a way to do this via code? I wish to do that before running the Pipeline so each task it contains would be updated to latest branch

I see haha