Skip to content
This repository has been archived by the owner on May 30, 2023. It is now read-only.

Downloaded file names #11

Open
pcaversaccio opened this issue Feb 1, 2022 · 1 comment
Open

Downloaded file names #11

pcaversaccio opened this issue Feb 1, 2022 · 1 comment
Labels
backend 🏭 Issues related to back-end feature 💥 New feature or request

Comments

@pcaversaccio
Copy link
Member

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.

@pcaversaccio pcaversaccio added feature 💥 New feature or request backend 🏭 Issues related to back-end labels Feb 1, 2022
@pcaversaccio pcaversaccio transferred this issue from another repository Feb 23, 2022
@pcaversaccio
Copy link
Member Author

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
backend 🏭 Issues related to back-end feature 💥 New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants