I have found strange behaviour of TrainTrack when we resume training from a checkpoint. Let's say we have two projects: GNNStudy and DNNStudy and we ran our pipeline once for each project. So we will have GNNStudy/version_0 and DNNStudy/version_0 for checkpoints in artifact_library: lightning_models/lightning_checkpoints.
If I resume my training for GNNStudy with resume_id: version_0 then TrainTrack sometimes jumps to DNNStudy/version_0 rather than GNNStudy/version_0. Seems like laod_config() uses os.walk from artifact_library as root and it finds version_0 that it encounters first. Maybe one should add a path like this artifact_library/project to search for a specific run where project: GNNStudy/DNNStudy comes from model_config.
I have found strange behaviour of TrainTrack when we resume training from a checkpoint. Let's say we have two projects: GNNStudy and DNNStudy and we ran our pipeline once for each project. So we will have
GNNStudy/version_0andDNNStudy/version_0for checkpoints inartifact_library: lightning_models/lightning_checkpoints.If I resume my training for GNNStudy with
resume_id: version_0then TrainTrack sometimes jumps toDNNStudy/version_0rather thanGNNStudy/version_0. Seems likelaod_config()usesos.walkfromartifact_libraryas root and it findsversion_0that it encounters first. Maybe one should add a path like thisartifact_library/projectto search for a specific run whereproject: GNNStudy/DNNStudycomes frommodel_config.