-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improves and fixes the web-client UI #668
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
wow, a fresher and clearer interface, great work! ✨
as usual, nothing blocking, only a few comments
- good idea to remove i18n, it's was barely used anyway
- and rm useles tests on Landing is a nice too
- for the geotags & skin_mnist task, nothing to salvage?
@@ -17,7 +17,8 @@ export const cifar10: TaskProvider = { | |||
tradeoffs: 'Training success strongly depends on label distribution', | |||
dataFormatInformation: 'Images should be of .png format and of size 32x32. <br> The label file should be .csv, where each row contains a file_name, class. <br> <br> e.g. if you have images: 0.png (of a frog) and 1.png (of a car) <br> labels.csv contains: (Note that no header is needed)<br> 0.png, frog <br> 1.png, car', | |||
dataExampleText: 'Below you can find 10 random examples from each of the 10 classes in the dataset.', | |||
dataExampleImage: 'https://storage.googleapis.com/deai-313515.appspot.com/example_training_data/cifar10-example.png' | |||
dataExampleImage: 'https://storage.googleapis.com/deai-313515.appspot.com/example_training_data/cifar10-example.png', | |||
sampleDatasetLink: 'https://www.kaggle.com/competitions/cifar-10/data' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
consider adding that to datasets/populate
instead of pulling from our own archive
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Would it work when the webapp is deployed? I think datasets/populate can only be used in local isn't it?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
correct, do keep it in cifar10's Task
and add it to datasets/populate
so that we ensure that we also train our tests with the sample dataset.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah so some cifar10 data is already included in the example_training_data
(which requires manipulation to used in the webapp...) but I wanted to provide a public facing link too.
Co-authored-by: Valérian Rousset <[email protected]>
Co-authored-by: Valérian Rousset <[email protected]>
Co-authored-by: Valérian Rousset <[email protected]>
Co-authored-by: Valérian Rousset <[email protected]>
Co-authored-by: Valérian Rousset <[email protected]>
Co-authored-by: Valérian Rousset <[email protected]>
Co-authored-by: Valérian Rousset <[email protected]>
There is a map modal implemented in Tester.vue for the geotag task which can be interesting but it relies on https://disco-polygon.web.app/ which doesn't exist anymore. I couldn't find what was the training data and with the base map missing I'm going to remove the task. It would be interesting to keep it in mind and go back to it if we ever want to implement another location based task |
@tharvik It looks like the npm deployment broke the build-server-docker action? |
Addresses parts of #627 #628, #662, #665 and various things noted while working on the LUS COVID demo
Addresses #627
Addresses #628
Addresses #662
Addresses #665