[WSG21] Daily Study Group: Notebook-Based Workflows for Data Exploration

A new study group for Notebook-Based Workflows for Data Exploration begins Monday, Jan 11, 2021! A list of daily topics can be found on our Daily Study Groups page.

We will look at various “Workflows” from the Wolfram Documentation Center and see how they can be used to build our own notebook-based workflows for exploring data.

Sign up here: https://wolfr.am/StSdgBS9

2 Likes

Good session today!
Do you want us to write questions here (as a reply) or in the general forum?

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.

1 Like

Here are the links to some of the workflows we looked at today:

3 Likes

Here is a link to some of the workflows we will be looking at today:

Our topic for today is “Visualizing Data”. Here are some useful resources from the Wolfram Documentation Center:

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
1 Like

Thanks @Rohit Namjoshi - very helpful.

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. :wink: The old function navigator was a good start but was removed.

Thank you!

We do have this: Alphabetical Listing—Wolfram Documentation

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.

Where can we find ExampleData/cities.xlsx?

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.

FindFile[“ExampleData/cities.xlsx”]

“/Applications/Mathematica.app/Contents/Documentation/English/System/ExampleData/cities.xlsx”

1 Like

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”]

Hi Stephen,

Replace the file path with the object’s URL, e.g.

Import["https://www.wolframcloud.com/obj/5cee1f52-2173-49f6-80bc-17a532607753"]

Or if you know the path on the Wolfram Cloud

CloudImport["https://www.wolframcloud.com/obj/rohit.namjoshi/test.xlsx"]

Thanks, I got the hang of it now.

Just a question on the link to the Multiparadigm course ( https://www.wolfram.com/wolfram-u/multiparadigm-data-science/dealing-with-messy-data.html )

The link refers to a page with the Wolfram U logo and then after 1-2 s, the browser moves on the URL

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

1 Like

Seems to be an issue with “third party cookies”