Potentially coming to a kernel near you

Neat!

@halirutan 11.1.1 is out. Are the editing annoyances fixed on Linux?

Hi

I would like to ask:

what exactly meant by "t_"?

why it plots nothing when I replace t_ by t -- > y[t]=Exp[3t] ?

#daily-fun

@Shing It's a pattern. You should skim through a tutorial. wolfram.com/language/fast-introduction-for-programmers/en

but now I am confused by another thing:

Does Dsolve work differently in Mathematica 11 ?

my mathematica behaves differently to this page:reference.wolfram.com/language/howto/…

DSolve[y'[x] == x, y[x], x]

instead of the solution

damn

never mind

I figured it out

I had already defined y[x]

@Szabolcs Not tested yet since I don't have the update.

It seems a university in Germany is not the high on the priority.

Quick question: How do you change the colour of an icon. EntityValue[Entity["Icon", "Camera"], "Image"]

@halirutan I usually get the updates later than most. This time I received no email, but it is there in the user portal.

@Edmund Colorize may be the easiest (see options)

@Szabolcs Thanks.

@Szabolcs It didn't exactly cooperate. I've posted a question. mathematica.stackexchange.com/questions/144567/…

Quit the kernel and run:

$logFile =  FileNameJoin[{$UserBaseDirectory, "ApplicationData", "file"}];
$logStreams = {(Close[#]; OpenWrite[#]) &[$logFile]};
Print[Style[$Output, Red]];

I get a log of irrelevant messages. Does this happen for anyone? The only one which is correct is about the stream not being opene.

I am working on a small paclet for UK postcodes. Sharing here, in case it is useful to others as well: github.com/arnoudbuzing/postcode

Just going to put this here because I think it's neat:

Planar embeddings Mma produces are a bit... boring. I'd appreciate some aesthetic post-processing, but maybe that's not the top priority.

@kirma @JasonB How about this for post-processing? Done with IGraph/M, with Jason's graph as a starting point.

@Szabolcs Much better aesthetics, I must say! :)

It's a layout algorithm based on simulated annealing. It takes several factors into account, such as edge lengths, node distances, edge crossings, etc.

"Continue" -> True means that it takes the existing vertex coordinates as a starting point. Most layouts in IGraph/M have this.

"EdgeCrossingWeight" -> 50 causes it to put more emphasis on avoiding edge crossings.

I had to rescale the coordinates at the beginning to make it fit more or less into the unit square. Otherwise the algorithm takes steps which are too large and shuffles up the edges so much that it cannot uncross them any more.

Characteristics of fullerene are much more obvious on the hexagonal graph, although both visualizations are obviously the same.

Some additional post processing with weighted Kamada-Kawai gives something like this:

@JasonB @kirma Here's a question: mathematica.stackexchange.com/q/144594/12 It should be a fun challenge. I'm off to bed now, good night!

@Meta didn't get replies for the post about "breaking the rules", I would have to assume that I'm not breaking SE or MmaSE policy then by "attaching" files with hidden encoded data. Any idea what could define the limit on text for a question? I wouldn't want to abuse the site by doing trial and error until it breaks.

@rhermans why not store code/data in the Wolfram Cloud?

E.g.:

data = RandomInteger[20, 100]

CloudDeploy[data, Permissions -> "Public"]

And then:

Get[ CloudObject[...] ]

(for whatever the actual CloudObject it was)

@ArnoudBuzing Data shared on the site has to be available forever. Deployments to Wolfram Cloud expire after 30 days if the user who deployed the data is using a free account. People who are currently paying to have their deployments not expire will not continue to pay forever either.