Archive bug.

[GeoffreyChen777]

Thanks for your awesome product!

I found that archived runs reappear after a while.

I'm using the latest version (2.1.5).

Is there any debug log that I can provide to you? How to find these logs?

[SGevorg]

Hi @GeoffreyChen777 do they appear back on the experiments page or the dashboard?

[GeoffreyChen777]

@SGevorg Both.

[GeoffreyChen777]

After reading the code about archive function,

aim/aim/engine/repo/repo.py

Line 895 in ac13388

with open(config_file_path, 'r') as config_file:

I think I know what's going on.

Actually, there is no bug of archive function.

Archive state is saved in the config.json, but this file is overwrite by my sync scripts.

Because I run my experiments on a cluster, I cannot start the aim UI on this cluster (no docker and no permission to install). So I need to run a sync script on my own machine to fetch the .aim folder on the cluster and start the aim ui on my local machine.

It would be better to support remote storage (mentioned here #315 ). I believe many researchers run experiments on clusters.

Anyway, thanks for your awesome product! 😃

I think this issue can be closed if no further discussion.

[gorarakelyan]

Hi @GeoffreyChen777 ,

Thanks for the details. I will keep you updated on progress of remote server feature development.
We also consider removing docker dependency to make Aim easier to install and to avoid overhead.

[gorarakelyan]

@GeoffreyChen777 would love to invite you to join Aim community to stay up to date with changes.