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
I personally think it would work better to tab from 'Select Column' to 'Enter Expression Here' and not the 'Functions' List as probably people who are tabbing would immediately like to start typing the formula rather than going through functions, fields, etc.
Currently when you add an event to notify you of workflow failure / success - you have to enter the SMTP settings every time. It would be more efficient to set this up as a user setting which can be used for the default across all canvasses that this user creates.
Frequently with more complicated tool configurations I end up having to setup certain elements over and over again. Would be great to have a one click "use this as the default" configuration that would follow my profile and apply to all future drags of that tool onto the workflow. Configuration elements that depend on the input fields would not be impacted.
Also an apply all feature to apply the similar configuration elements to all tools of the same tool type.
Example Configuration Elements
Comment Tool - Shape, Font, text Color, Background Color, Alignment...
Tool Container - Text Color, fill color , border color, transparency, margin
Table Tool - Default Table Settings
Union Tool - "Auto config by name", Actions when fields differ
Data Clensing - all configuration elements
Sample - all configuration elements
I'm really liking the new assisted modelling capabilities released in 2020.2, but it should not error if the data contains: spatial, blob, date, datetime, or datetime types.
This is essentially telling the user to add an extra step of adding a select before the assisted modelling tool and then a join after the models. I think the tool should be able to read in and through these field types (especially dates) and just not use them in any of the modelling.
An even better enhancement would be to transform date as part of the assisted modelling into something usable for the modelling (season, month, day of week, etc.)
It would be great if you could create default settings for the Tool Containers. As workflows become larger, I use containers a lot. But once I have 10-15 containers, I have to set all of them to have a Transparency of 1 and a margin of None. While the changes don't take long to make, it would be nice if they could be preset.
Could you please assess the idea of reverse engineering existing SQL code (in special inside DataWarehouse's code, thousands of LOCs filled with SELECT and JOINS) and replace it with Alteryx widgets?
Doing this will accelerate penetration rate of Alteryx products in large companies and dismantle IBM Cognos and their cousins.
Sort by file size based on first digit in file size (should be based on all digits).