Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHello,
After used the new "Image Recognition Tool" a few days, I think you could improve it :
> by adding the dimensional constraints in front of each of the pre-trained models,
> by adding a true tool to divide the training data correctly (in order to have an equivalent number of images for each of the labels)
> at least, allow the tool to use black & white images (I wanted to test it on the MNIST, but the tool tells me that it necessarily needs RGB images) ?
Question : do you in the future allow the user to choose between CPU or GPU usage ?
In any case, thank you again for this new tool, it is certainly perfectible, but very simple to use, and I sincerely think that it will allow a greater number of people to understand the many use cases made possible thanks to image recognition.
Thank you again
Kévin VANCAPPEL (France ;-))
Thank you again.
Kévin VANCAPPEL
Hi,
Here is an idea I think it would help with documenting any process using the container tool. Currently, with each of the tool, user can use the default annotation or add his or her own annotation to help explaining each step in a process. The annotation on each tool can be set to be hidden (never show) when there are high number of tools are present. This is when the container tool can be used to organized tools. This idea is similar in scope with the two ideas below but I want to push it a little further beyond the current available features described in https://help.alteryx.com/2019.3/ToolContainer.htm
The idea is to have the container tool summarize all the annotations from tools within a container as its own. This way, you will have the full documentation of the combined process within the container, and container of containers. This feature can either be the option to view or to export from the pop up window.
Give the option in the tags properties to place the tag to the right of the tool.
Have this be the default setting for Browse and Output tools or others that would normally be found at the end of a workflow. This allows the detail to remain and a cleaner view of the module.
User | Likes Count |
---|---|
5 | |
5 | |
3 | |
2 | |
2 |