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 developing a module, I generally BROWSE the final data until I'm ultimately ready to generate output. Then I need to add or replace a browse tool with an output tool. Perhaps a general purpose output tool could save time for developers where the output tool functions as a browse tool until the output is actually checked on the tool configuration.
Taking this a step further, if an output is defined and the module is executed one could have a row limit on the read of data into the browse function of an output tool and see the first N records within a browse/output tool.
Sneak Peek.
m
In my environment, creating tables with fields in a particular order is a requirement.
The Select tool (and others) let me manually change sort orders. The Select tool will also allow me to sort on Field Name in Ascending or Descending order.
I can add a sort order prefix to my input data with the Dynamic Rename tool, connect a Select tool and then go into the Select tool properties to sort by Field Name. But this requires that I first run the module so that the Select tool knows what the incoming fields are called, then set up the Select tool properties, and then rerun the module. If I change the prefixes or the list of incoming variables, the Select tool has to be reconfigured.
It would be really nice if there was a Field Sort tool that only had Ascending or Descending as properties that would 'dynamically' do what the Sort on Field Name option in the Select tool does.
In the Browse window:
Thanks!
Our team works with a lot of in-house transaction data sets that have been put into a calgary database. It would be much easier to build apps that use the calgary input tool without having to configure html code.
Currently when I open and run an app in designer mode im unable to access any other modules while it runs. It would be nice to be able to work on other modules while an app runs without opening a debug.
Add an option to read directly from a zip file.
It would be nice to have the ability to double click the top area of a container to either show or hide the container's objects. Only being able to show or hide containers using the arrow icon in the top right is quite cumbersome for large containers because it requires a lot of horizontal scrolling in order to change the desired view of the modules workflow.
For example, in the Properties tool (I say that generally because it could be in more than one place in that tool) all the user to enable to visibly see the path of the variable in the flow on the canvas. As shown in the mock-up image below (as crude as it is, I think you get the idea). This would allow you to trace the path forward and backwards in the flow, seeing where the variable entered and when it exited. This could be something you can turn on and off like the grid option.
Instead of being a module setting, showing counts should/could be a user setting.
When building an expression (e.g. [Store Type] in ("Supermarket", "C-Store", "Gas Station") ) when the user selects the field variable, provide all the unique values in that field so user can double-click and add them to the expression, without having to look and see what values are in the table, what data type (shows quotes if string) and manually type the values, which can lead to errors.
This functionality is currently available in GIS programs such as ArcGIS and Quantum GIS (QGIS).
Currently on the input tool I can only specify if the first row contains data. It would be great if I could simply specify which row the data starts on, ie. row 4 or row 500, and then specify which row, if at all, contains the headers.