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
Today the Autofield tool transforms the fields into byte by default when it considers that the content is suitable while we expect text in it and that it can simply be a field not filled in in the context current but which may be later.
The idea would be to be able to choose which type by default to implement on text or empty fields and not the default byte because a byte field is not recognized on a formula using an IN for example which can produce errors in the following workflows.
Hello,
My idea is that the current Download tool does not handle errors and continues its path even if it does not find for example a file in the transmitted URL or if it does not find the hostname it crashes.
In the case of a user with several URLs in a row, this is penalizing.
In the case of downloading files with recording, it still writes a file (thus overwriting the existing file) but which is not openable and is not in the correct format. (BLOCKED file!) Which then causes problems in workflows reading these files.
The idea would be to put a second output to this tool for all the URLs where there was a problem (non-existent hostname, file not found, HTTP KO) and one where it received the expected elements so as not to prejudice the processing. and allow better management of error cases.
Regards,
Bruno
When using Dynamic Input with databases, the Database may be returning errors or other information that the tool cannot parse into a dataset.
It would be great if we could see the 'raw' response from the database somehow, as this might provide insight into why we are not getting the expected results.
If the tool could output an optional error column that has the unparsed response from the database server, it might allow us to debug the problem ourselves.
If the returned data is actually a string response from the database, but one that is flawed in some way, we might still be able to parse data out of it to 'ride over' the error.
Configuration window - Add feature to zoom in or out of the configuration window similar to the canvas. There is alot going on in the Configuration window and it would be helpful (especially for those of us with eyesight challenges) to be able to zoom in/out similar to the Canvas.
Migrate old R based charts and create new statistical charts in the interactive chart tool to provide enhanced statistical charting and visual data exploration capabilities.
This includes:
This these URLs for more examples:
For heavy workflows (e.g. reading massive amount of data, processing it and storing large datasets through in db tools in Cloudera), a random error is sometime generated: 'General error: Unexpected exception has been caught'
This seems due to Kerberos ticket expiration and the related setting may not be modifiable by the Alteryx developer 'especially when GPO). Suggestion is to enhance the indb tools in such a way that they are able to automatically renew the Kerberos ticket like other applications do.
Br, Lookman
User | Likes Count |
---|---|
4 | |
3 | |
3 | |
2 | |
2 |