Hmm... I just typed this in a documentation page and completely froze Mathematica:

Piecewise[{{x^2, x<0}, {x, x>0}}, x]

very weird

@Kuba you're famous: wolfram.com/broadcast/video.php?v=2499

@Kuba @b3m2a1 I would like to evaluate a notebook the same way as if I did it through the menu. I use FontEndTokenExecute[nb, "EvaluationNotebook"]. But it pops up a window asking if I want to evaluate initialization cells. How can I avoid this or programmaitcally respond "no" to it?

Why not NotebookEvaluate[nb, InsertResults -> True]? Because I have a custom kernel set for that notebook and NotebookEvaluate does not respect it.

@Szabolcs before you evaluate set InitializationCellEvaluation->False

Easiest way to my mind.

And just be sure to reset it afterwards

Yes, this works for me. Thank you!

@b3m2a1 Do you know how to programmatically quit a specific kernel?

Very odd that NotebookEvaluate doesn't respect your kernel, as it calls into the FE version of that, but ah well.

@b3m2a1 oh god. That video only proves that only my wife loves me, because she told me a long time ago to go to a speach therapist O_O I am sorry for that, focus on content though. :) Anyway, the key of the talk is around 18min mark or later.

@Szabolcs I've done this in the past. Let me dig a bit.

@Szabolcs FrontEnd`EvaluatorQuit will do it but it asks you if you want to quit...

I thought I'd done it without that but maybe not.

I've definitely started them without it but maybe not quit them without it.

@b3m2a1 @Szabolcs @b3m2a1 mathematica.stackexchange.com/a/120963/5478

Here's the full list of Evaluator FE packets:

{FrontEnd`AddEvaluatorNames, FrontEnd`EvaluatorAbort, \
FrontEnd`EvaluatorHalt, FrontEnd`EvaluatorInterrupt, \
FrontEnd`EvaluatorQuit, FrontEnd`EvaluatorStart}

Create a new notebook, set the evaluator on it, evaluate it, close it. What a hack! :(

Sounds like the FE

One cute thing you can do, if you didn't know, is to use CurrentValue to add a new custom kernel.

CurrentValue[EvaluationNotebook[], {EvaluatorNames, "Second"}]

{"AutoStartOnLaunch" -> False}

And you can use Set in the standard way with that

When I read in .czi images using BioFormatsLink, my output of MemoryInUse[] goes up massively, and quickly goes above my actual 16Gb limit. Which I assume means it is trying to use virtual memory...

If I read a particularly large .czi file with multiple individual images in, then it crashes my mac every time, even if I edit the code to only keep one image.

@Kuba Really enjoying your talk, lots of useful stuff I didn't know about there. Well done!

Beyond excited about this particular feature from the SPARQL stuff hopefully landing in 12 youtu.be/fyiNHpb_CX4?t=769

In my opinion the Entity framework should really have been a triple store all along, so this is a cool step in the right direction

@CarlLange How would you imagine an entity as a triple store?

@chuy I imagine EntityStores as a triple store

Wikidata is far bigger than the wolfram knowledgebase can ever really be, and it has 80% the same data.

I know that the cool thing about the entity framework is computed properties, but that's something they could have added on top of a triple store IMO

I have a huge list that's supposed to represent a picture. I want to partition that list the way ImagePartition would partition a picture. I tried Partition for a while but I failed.

@psimeson there's an example for you.

@C.E. Thanks. I was being a fool and trying to apply this thing to a nested list of dimension about 3000... so I was getting a level error ... I am trying to fix it by reshaping the list

@CarlLange thanks for kind words!

Neat stuff comming in v12 for graphics, if you know how to write it ;)

@Kuba Kind of strange not to have seen anything about this in the livestreams! Very interesting stuff

Would love to see SW's reaction to bare GL shader code in MMA :D

Also great to see that Metal will be a graphics engine on OSX, OpenGL is ancient on OSX :(

@CarlLange Maybe they didn't tell him, those features are not plug-and-play enough.

@Kuba Yes, maybe. Or perhaps it will be left undocumented forever :(

We will see, it was advertised, altough in a much more primitive form, on wtc2016. So yes they did something but will they release it?

@Kuba That's very cool