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
90% of the time when dragging in an input tool I need to drag in a select tool to pick only the fields that you want. Best practice suggests this should be 100% of the time for efficiency. Embeding this functionality within the input tool itself would save a step.
This is something small and silly, but having a comma in the number of records shown on the output window would be very helpful!
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.
Possibility to deselect fields directly in the input (shape, csv, tab, etc).
I have several modules that need to run in sequence. Can a ksh or some other program be used to string the modules together?
So that if I have Step1.yxmd, Step2.yxmd and Step3.yxmd. 2 is dependent on 1, 3 is dependent on 2. I want to tell it the jobs to run and then to wait until that module completes, then run the next.
run Step1.yxmd
Wait
run Step2.yxmd
Wait
run Step3.yxmd
Wait
Or, if I have a group of modules that can run concurrently but subsequent jobs are dependent on all of them to finish, i can let all those jobs run and have the next step wait for those to complete to begin.
run Step1A.yxmd
run Step1B.yxmd
run Step1C.yxmd
run Step1D.yxmd
Wait
run Step2.yxmd
Wait
run Step3.yxmd
Wait
I know this is very simplistic, but hoping it shows the need. Also, we do have the scheduler set up to use, so if there is a way to set dependencies between modules within Scheduler, that might be helpful. Just haven't found anything.
Thanks!
Currently, the map input for an application defaults either to a global view of the United States or to a fixed boundary. Usng a chained application, it would be an extremely useful option to be able to specifiy spatial objects (points, lines, polygons) in the first application and then allow the second application to zoom in appropriately to those spatial objects. This could be done by either specifying a custom zoom level and using those spatial objects as a center through a reference layer, or by allowing the zoom's boundary to contain all the spatial objects (similar to the map reporting tools).
The bak file that is automatically created (and re-created if deleted) really clutters up our folders.
Please allow us to either turn it off, or specify a different location to hold our back up files.
Thanks
User | Likes Count |
---|---|
25 | |
8 | |
5 | |
5 | |
5 |