When do we expect to receive an email on final exam of the daily study group: Getting Started with Mathematica and Wolfram Language?

THANK YOU for responding to me, Arben! :) You always make time to respond to me: I know that you do that to all of your students. And I am very grateful to you and Wolfram that I could be one of your students.

I am deeply sorry that I sent you emails. And I appreciate you telling me why there has been no response from them. It's great to learn about it because I always regret sending you emails to take your valuable time.

I wish you all the best for successful Data Science Boot Camp that meets your expectations.

Attachments:

rainbow+heart+thum up.jpg

Awesome presentations this week.

Do you find yourself creating copies of notebooks or templates for each instance of a problem type? How do you manage gradual refinements of notebook templates? Are diff-ing and merging notebooks commonly done? Do you commonly create "hyperlinks" between notebooks? When do you recommend version control via Mathematica or Git?

Somebody asked about useful resources about things like Histogram in today's session—here's a short list that has statistics-related materials which they may find relevant:

• Elementary Introduction to the Wolfram Language (see Ch. 24)
• Introduction to Statistics
• Modeling with Statistical Distributions
• Statistical Analysis with Wolfram Language
• Statistical Distributions

Subtle thing going on with NotebookDirectory[]—if the notebook exists at all as a file which was ever saved, then NotebookDirectory[] will return the save location, but it doesn't have anything to say about the "current state" of the notebook vs. its "saved state".

You can get something kind of related via NotebookInformation[]—namely, you can get a "saved" time and a "modified in memory" time. I thought that maybe taking their difference could be instructive, but I think that just running the code itself counts as "modified in memory", so you wind up getting the time in seconds since your last save with this:

Subtract @@ 
 Lookup[Association[NotebookInformation[]], {"MemoryModificationTime",
    "FileModificationTime"}]

As for the greyed out icon, maybe I can tell you another new thing re: macOS—the reason that that icon gets greyed out is that it's a fully-functional "link" to the file in question! When you have unsaved changes, the saved file and the "working file" no longer match up, so it greys out to indicate that the "link" is no longer active. But if you've got an up-to-date file open, you can drag that icon around and it will act like the file itself—that is, you could drag it onto this page to embed it in a post, or drag it over to an email to attach it, and so on.

In any case, I'm glad you're having fun with the code!

EDIT: However, if you're in another notebook, you can point to the Notebook of Interest as follows and this will work:

Subtract @@ 
 Lookup[Association[
   NotebookInformation[
    NotebookOpen[
     "path/to/NotebookOfInterest.nb"]]], {"MemoryModificationTime", "FileModificationTime"}]

Hey Ray! You should have gotten that notebook both in the recording email for that office hours session and in a follow-up to your latest email to us. As for seeing whether the notebook is currently saved to disk, the only relevant thing that comes to mind is the default OS-wise behavior in macOS that shows a little dot in the red "close" button to indicate that you have unsaved changes to the contents of the corresponding window. If you're okay with evaluating a line of code, NotebookDirectory[] will tell you where the notebook it's evaluated in is saved, or produce a failure message specifying that it isn't saved in the case that it isn't.