Thank you Fredrik. Please post any questions from the study group sessions here.

For generic questions on various Wolfram Language topics and other interests, please feel free to post in the related groups in the Community.

Here is a link to some of the workflows we will be looking at today: https://reference.wolfram.com/language/workflowguide/ImportingAndAnalyzingData.html

For a hyperlinked list of all Workflow Guides

workflowGuides = {$InstallationDirectory, "Documentation", $Language, "System", "WorkflowGuides"} //
  FileNameJoin // FileNames["*.nb", #] &;

workflowGuides // 
  Map[<|"Workflow Guide" -> Hyperlink[#, "paclet:workflowguide/" ~~ #] &@FileBaseName[#]|> &] //
  Sort // Dataset

For Workflows

workflows = {$InstallationDirectory, "Documentation", $Language, "System", "Workflows"} // 
  FileNameJoin // FileNames["*.nb", #] &;

workflows // 
  Map[<|"Workflow" -> Hyperlink[#, "paclet:workflow/" ~~ #] &@FileBaseName[#]|> &] //
  Sort // Dataset

Bless you for sharing this code; very very helpful.

Can you provide a listing all the functions as links? I don't like the current presentation as requiring more effort to use when one is disabled. I have my own ideas. ;-) The old function navigator was a good start but was removed.

Thank you!

Already have that (and thats tied directly to your servers not local to my harddrive); what I want to the full path of each function (the semantic context) a la the hyperlinks as data (as shown for the workflows) so I can reorganize the functions so a better GUI be made. I hate typing (not easy for me or for many other disabled folk) and want the least amount of mousing needed.

Ps. the website I see now finally provides the Info for each function if you hover over it, cool; vastly more useful.

Hi Andrew,

We are going a bit off-topic, but you can do the same thing for symbols

symbols = {$InstallationDirectory, "Documentation", $Language, "System", "ReferencePages", "Symbols"} //
  FileNameJoin // FileNames["*.nb", #] &;

symbols // Map[<|"Workflow" -> Hyperlink[#, "paclet:ref/" ~~ #] &@FileBaseName[#]|> &] //
  Sort // Dataset

You can use that to build a nicer interface than Dataset, maybe using autocompletion to filter from the long list.

Hi, How can I import the file from the cloud into a cloud notebook instead of from my machine?

For example How do I change this line?

Import["/Users/arbenk/Documents/Data Visualization Workflow Sample.m"]

Thanks, I got the hang of it now.

Great example with the meteorites. Here is the timing with and without the Interpreter function for the final Manipulate

Could you try this link from the Wolfram U site? https://www.wolfram.com/wolfram-u/multiparadigm-data-science/

Here are some of the links (from Stephen Wolfram's blog) I shared today about using notebooks for your data exploration workflow:

• What is a Computational Essay?
• Launching the Wolfram Data Repository: Data Publishing that Really Works
• The New World of Notebook Publishing

The added notebook above behaves differently than the same notebook running in Mathematica. The notebook in Mathematica produces a menu outline pull down menu with the chapters, sections, and subsections shown but the numbers are all zero. The added notebook above produces the transpose error. Would should some explain what's happening there?

When you are using FeatureSpacePlot you can use options like FeatureExtractor and Method to customize the type of features being extracted from the data. However FeaatureSpacePlot does not immediately make available the extracted features.

To look at the extracted features, you could use FeatureExtract (https://reference.wolfram.com/language/ref/FeatureExtract.html) and DimesnionReduce (https://reference.wolfram.com/language/ref/DimensionReduce.html).

What FeatureSpacePlot provides is a quick and easy alternative to using FeatureExtract on your data followed by DimensionReduce (to reduce number of dimensions to 2) and then use ListPlot.

You can try the following code:

imgs = Rasterize /@ Alphabet[];
FeatureSpacePlot[imgs]
ListPlot[Thread[DimensionReduce[FeatureExtract[imgs], 2] -> imgs]]

The two visualizations may be different because we are not specifying any options in the code above and the methods picked during the two sets of operations may be different with defaults settings. You could possibly get similar results by fine tuning options (Method, FeatureExtractor, etc.) for both sets of functions.

Thank you.

Hi Yeu Wen,

Sorry for the delay in getting back to you. Here is the answer key: 1. B, 2. D, 3. B, 4. D, 5. C, 6. A, 7. D, 8. A, 9. D, 10. B