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
When jobs have run successfully in scheduler, retain a baseline average so when items are in the queue much longer than normal, an alert can be sent.
This will allow us to kill stuck jobs and free up resources.
I know y'all are working on data lineage for some future offering and it is very much needed. For highest quality results, please make logs a primary source of lineage information. Being able to use dynamic naming with some tools and macros makes the names in the workflows simple foobar placeholders and do not reflect what actually happened. Today Connect doesn't use logs and leaves many lineage gaps because of this
Please move this to a more appropriate category if needed. This future feature work is not part of Connect.
I pull data from APIs frequently in my workflow, which has some potential for error if the API is unavailable. I would love to be able to develop the workflow without having to add in some text box place holders or record count feature to allow the remainder of the workflow to run without error and potentially be able to try the API again so if "Invalid authentication" route to a section that will regenerate an authentication and retry the data call. I have currently worked out some hacks to be able to work through the issue but it makes the workflow very messy. A tool like the Detour tour that goes if value contains 400 go this way. If value contains 200 then close off this container and continue on the other one. Maybe the request is to allow the detour tool to be set to a specific value and maybe have multiple route options if A then do connection one, if B then do connection two or If C then do connection three.
Github support. push/pull your workflow code directly to/from a repo. I posit this is the single biggest feature misisng form Alteryx -and I'm be happy to blab on and on to the product team about how not having this is a huge miss.
User | Likes Count |
---|---|
17 | |
6 | |
5 | |
4 | |
3 |