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
This is something small and silly, but having a comma in the number of records shown on the output window would be very helpful!
You can select all fields at once, but it'd be nice to select a chunk of fields using CTL+Shift+Click
Scenario: 6 input tools, and want to add, say, a select tool after each one.
Would be nice to select all 6, and add the tool after all of them at once.
I would like to use the precreate statement as part of a app. That means if a user selects ID '12345' from an interface tool, I would like to delete recs in SQL server with that same ID through the pre create statement, then afterwards I would append new records with the same ID.
What I really miss is having the ability to send one Name & Value to an interface tool like label or readonly textbox.Then I could use Label/Textbox->Action->Output and change the precreate statement that way.
I tried the formula way but SQL think I am running a stored procedure.
It looks like I need to use a listbox or dropdown tool and do it that way but that means I am cluttering my app with unnecessary tools.
Could you give interface tools a 'hide' property or allow a field to be passed to the pre-Create SQL statement?
Unless there's another way to do all this?
With a module that contains a lot of tool containers, it would be nice to have an option (similar to Disable All Tool That Write Output in the RunTime TAB) to disable all Tool Containers and then I can go pick the one or two that I would like to enable.
I have a big need to input files created in a .sqlite format and also write out to files as .sqlite that contain spatial object fields. Currently they are not recognized as spatial objects. BlobConvert is not able to convert the spatial fields from the input correctly (it gets close) so the result is that we are unable to utilize any spatial fields from or to these files.
Hello,
I think it would be extremely useful to have a switch connector available in Alteryx. What I mean by a switch connector is a connecting line with an on/off state that will block the data stream through it when off. Something like below:
Switch Connector in an "Off" state
This would be extremely useful when you only want data to flow down some of the paths. In the example above, I might turn the switch connector to off because I want to see the Summarize results without outputting to a document.
The current methods for having a path/set of tools present but unused are insufficient for my needs. The two methods I and Alteryx support were able to find were:
We've had several requests from clients for the ability to import password protected Excel spreadsheets into Alteryx. Within Alteryx, it would be good to specify the password and inport the file without the need to create an unprotected copy for use in Alteryx.
Thanks
User | Likes Count |
---|---|
4 | |
3 | |
3 | |
2 | |
2 |