Open rcasero opened 4 years ago
Hi @rcasero,
Yes, this change was made to enable users to define a /data/projects
directory with JSON files that prescribe the required image and annotation file. Some people found this an easier way of managing the relationships between images and annotations, particularly when there were multiple annotation files associated with a single image.
A project .json looks something like this:
{
"projectName": "Example project name",
"images": [
{
"name": "Mount Whilhelm",
"path": "mountains/Mount_Wilhelm.jpg" // Relative to data/images
}
],
"annotation": "Mount_Wilhelm.json" // Relative to data/annotation
}
It's a bit unforgiving at the moment. The file has to be proper JSON or it throws errors.
A side effect of all this, as you note, was the switch to the Vuetify treeview component. This results in the whole directory structure being shown on the dashboard. I spent some time attempting to enable a filter for only AIDA applicable files (hiding the _files directories for example) but the Vuetify component is a little inflexible here and doesn't support doing this in a robust way just now.
I'll keep an eye on it though. I think you're right in that it would be nice to toggle a view where only AIDA applicable files were shown. Perhaps this should even be the default.
Just pulled ab5148d, same data directory structure in
~/Software/AIDA/dist/data
, but removingimages.json
that doesn't seem to be necessary anymore.Interface with file browser in
http://localhost:3000/dashboard
shows both theannotations
andimages
directories, and withinimages
, both the.dzi
file and its directory of auxiliary files.