You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 30, 2023. It is now read-only.
In terms of new files' names; the augmented images have some random sequence added to their name. I would avoid that and at least do it like the preprocessing files where they have 'preprocessed' added to the filename. But even then, since the files are downloaded to their specific parent folders (ORIGINAL, PREPROCES, and AUGMENT), there is technically no need to rename the files at all, which allows for consistency when reading them off the path.
The text was updated successfully, but these errors were encountered:
We need to think about the consistency of file names. These filenames should be future-proof, i.e. if new applications will be part of the DAITA service (e.g. data annotation) we can adapt that structure. The ultimate goal of this issue is to find a canonical definition of how to save files.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In terms of new files' names; the augmented images have some random sequence added to their name. I would avoid that and at least do it like the preprocessing files where they have 'preprocessed' added to the filename. But even then, since the files are downloaded to their specific parent folders (ORIGINAL, PREPROCES, and AUGMENT), there is technically no need to rename the files at all, which allows for consistency when reading them off the path.
The text was updated successfully, but these errors were encountered: