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
It would make it a lot easier to create and manage a work stream if you added the standard ability to maximize and minimize the workflow canvas and configuration and results windows.
We extensively use the AWESOME functionality of SharePoint List Input and SharePoint List Output tools. They're great! BUT... they require valid credentials to pull back the valid list and view values. Not normally an issue until you go to share your workflow. If you strip out your credentials from Alteryx the List and view fields go blank, do it from the xml and when the person you share it with opens it up the fields go blank and you have to count on that user selecting the proper list and view.
I propose to have these tools load valid lists and views only upon pressing a button or running the macro in initial configuration state.
Found this https://community.alteryx.com/t5/Alteryx-Designer-Discussions/SharePoint-Passwords/td-p/17182
and we could use a macro tool but every implementation still requires storing a valid username and password to avoid the error and the list id which I imagine the sharepoint API requires and which is why the tool behaves the way it does is not easily obvious to most ppl.