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
As seen in This Discussion Post, the idea here is to be able to add a link to example workflows in macro descriptions - like the ones seen in native tools.
Many thanks to @jdunkerley79 for demonstrating how this can be done by manually editing the macro's XML - specifically by adding a child element to the <MetaInfo> section, like so:
<Example> <Description>Open Example</Description> <File>\\aSERVER\aRootDir\path\to\Alteryx\Macros\Date Wizard\Date Wizard Examples.yxmd</File> </Example>
One small caveat is that it doesn't support truly relative paths. @PaulN explained in the discussion post that a relative reference here would search in the sample folders.
"Alteryx default behavior is to look for examples under .\Alteryx\Samples\02 One-Tool Examples or Alteryx\Samples\02 One-Tool Examples (or .\Alteryx\Samples\en\02 One-Tool Examples)."
Having said that, trying to reference a macro example in the same folder (using a relative reference) will throw an error given the following situation:
Package Structure:
Date Wizard.yxmc XML edits:
<Example> <Description>Open Example</Description> <!-- THIS WORKS --> <File>\\aSERVER\aRootDir\path\to\Alteryx\Macros\Date Wizard\Date Wizard Examples.yxmd</File> <!-- THIS DOESNT <File>Date Wizard Examples.yxmd</File> <File>.\Date Wizard Examples.yxmd</File> <File>./Date Wizard Examples.yxmd</File> --> </Example>
This shows a link in the Macro description but yields an error (shown below) when it is clicked.
Once again, this works fine with an absolute file path reference.
Here is ultimately what I am suggesting: Can we add an option to the Interface Designer (that updates the XML) and have it allow relative paths? Allowing relative paths would obviously be essentially to maintaining the macro's ability to be "lift-and-shift" when packaged/moved/uploaded to servers/galleries etc.
I'm assuming the option could look something like this, similar to the "Help" file -only it would show link in the macro description...
In conclusion, this would be very useful in providing links to example workflows for custom macros that may be complex and/or not self-explanatory.
Cheers,
Taylor Cox
We are starting to use Alteryx as a full ETL DW build tool (and blogging about it too..)
Compared to other tools in the market there do not seem to be the usual SCD(slowly changing dimension) and other "standard" tools or templates to start building.
It would be great to have a template/Macros/guide to starting to build a DW solution. It is rather daunting starting with a blank page!