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
At present, Alteryx allows for users to run 2 versions of Alteryx at once - one installed using the "Admin Installer" and one via the "non-admin installer"
However, in corporate environments, only the Admin Installer can be used (all installers are repackaged for corporate environment / endpoint management)
This leads to a situation were we cannot run two or more different versions of Alteryx on one machine (like you can with Visual Studio or other platforms). This also prevents us from participating in the BETA program because the BETA version would overwrite the users's current version. Finally - this also makes version upgrades more risky since we cannot run the new version in parallel for a period to evaluate and identify any issues.
Request: Please can you change the installer for Alteryx to default to parallel install per version - so that a user can run 2019.1; 2019.2; and 2019.2 BETA on one machine in a way that is fully isolated (i.e. no shared components - have to be able to uninstall one instance cleanly and leave the others in a fully functional state).
Many thanks
Sean
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
When saving an alteryx module (yxmd, yxmc, yxwz, yxzp), can we have a simple "SAVE AS" function that allows us to choose the version number? Conversely, could we open a newer version module with a warning message rather than an error?
In either case there would be the logical CAVEAT that certain functions or features may not be compatible with the save/open function.
Thanks,
Mark
I would like the ablity to view the processing order of tools within module prior to processing and if needed reprioratize which tool processes first/last. It would also be great to have the ablity to disable a subset of tools within a module prior to processing.
User | Likes Count |
---|---|
41 | |
31 | |
20 | |
10 | |
7 |