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
I have been using the outputs from Spline Regression to facillitate analysis of demographic data (specifically Department of Labor Quarterly Employment data). I have data from 1992Q1 to 2014Q1 and use Spline Regression to get fitted values for each quarter with predictors being the year/quarter, Year/quarter multiplied by a dummy variable for each of the 4 US Presidents, and a dummy variable for each president.
So I can compare results across various groupings by geographic, and other levels as well as the BLS aggregation level. I can analyze raw data or have the values to be fitted indexed to 1992Q1.
I use the default settings for Spline and it builds the best fit including where the node periods for each spline section. To help interpret the results, though, I use the output to compare the actual vs. fitted values (e.g. employment Level) and then look at the changes by quarter.
With the spline regression building the best model with optimal line segments, the results make it possible to see how employment progress or regress correletat with with presidential terms of office or specific impacts of economic recessions on employment data.
I can supply an example of the process, if anyone is interested.
I'd appreciate any comments and/or suggestions to improve the process or interpret the results.
To keep from being too specific, the "Idea" is that Alteryx Designer should do better at recognizing and handling Date/Times on input. Thoughts include:
1) Offer more choices in the Parse: DateTime tool, including am/pm.
2) Allow users to add new formats to the Parse: DateTime lists.
3) Include user-added formats in the Preparation: Auto Field tool's library.
4) Don't require zero-padding of days and hours in the DateTimeParse() function. (1/1/2014 1:23:45 AM looks enough like a date that DateTimeParse() should be able to figure it out, but it stumbles on day and hour.)
My particular difficulty is that I have incoming date/times with AM/PM components. I've gone ahead and created a macro to take care of that for now, but it certainly seems like that sort of thing would be handled automatically.
Thanks!
I have an app that contains 4 check boxes. Each check box is independent, and when checked, two other prompts open up to the user (in this case, text boxes which are also independent of the other check boxes).
I would like to be able to "Check All", so that with one click, ALL four check boxes are checked, and their prompts all open up.
Can you put a check box on the container title bar to make it easier to enable/disable containers in the process window? And can you make the minimize/maximize option for a conatiner a separate option from enable/disable?
We need the ability to pre-populate App questions with a default value. This not only gives the user an example of what type of data string the App is looking for, but also may avoid the user from having to do anything if the default folder or file is already correct.
This would also allow for quick App testing since we can just accept the defaults and not have to load up a yxwv file every single time.
ArcPy/Python, ESRI Modelbuilder, PyQGIS can all do this (heck, even MapBasic can do it!) - there's no doubt it's more convenient for the designer and end user.
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.