ilian

yes, e.g. through LinearOptimization

@kirkus not at the moment, but it is planned for 12.3.1

(yes, databases are being used actually)

blog.wolfram.com/2020/03/18/…

@kickert The cloud is running V12 now (the push was today, so I think any previous hiccups were unrelated)

@Nasser That's not really the right conclusion, the incompatible fontconfig update arrived in Arch / Manjaro only after Mathematica 11.3 was released.

@gwr I find the "unfortunate odor" comment a little offensive. People are welcome to scrutinize my activity on this site for the last 6 years as they see fit, but sorry, there are no hidden agendas or axes to grind.

@bobthechemist Some of the functionality works, e.g. RegionDifference[Disk[], Disk[{0, 0}, 0.5]] // Area should be fine. However, boolean operations on meshes are not supported on the Raspberry Pi at present.

By the way, it is documented that RegionIntersection is not implemented for mesh regions in 3D.

@Szabolcs We will look into this further, but my initial feeling is that CreateDirectory has not changed. What may have changed is the way OS X sets the umask for various processes (this question is vaguely related).

@OleksandrR. The trouble in that particular example came from "NelderMead". But implementing other mutators for "DifferentialEvolution" seems a good idea and I've put a formal suggestion on the books.

@kirma The RegionBounds bug is on my radar. The poor result comes from a numerical optimization method where NMaximize is getting stuck at a local maximum. Developers are looking into it and hopefully will make improvements, but in general always finding the global maximum is not guaranteed.

@halirutan definitely something to be fixed (the documentation, that is)

Maybe Head[General::stop] === $Off ?

@halirutan fixed in the development version

@MartinJohnHadley seems like an incorrect version requirement in the paclet, until it's fixed, perhaps try using 10.1.0

@JimB I had voted originally to close. Then the question got voluntarily deleted by the author. Then it was undeleted and substantially revised. Now there is even a thoughtful answer, so I retracted my close vote. Sorry, but the "Inc" does not participate here. Just people in private and unofficial capacity, on our own time. Yesterday's chat accusations of an evil cover-up conspiracy were just false and unnecessary.

It sounds more like a bug report to me. Also, unless there really is a common cause (which I have some doubts about), it might be better to not stick all examples in a single “question”.

+1 from me, this answer gives additional context that is useful. By the way, 275./6.*1.03692775514337 is a valid C expression so I simply assumed that's what OP computed. But I understand the point of view that it could have been any other code too.

You may also need to adjust the values of SystemOptions["ParallelOptions" -> "ParallelThreadNumber"] and SystemOptions["ParallelOptions" -> "MKLThreadNumber"] since by default they are based on $ProcessorCount which is likely incorrectly detected in your case. This can be done on the subkernels by using ParallelEvaluate[SetSystemOptions[...]].

have a good night/evening/day depending on your time zone

thanks for the kind words, we are all passionate about Mathematica

yes, until the next version is installed

restoring it later would avoid losing the activation

if you ever need to clear your $UserBaseDirectory, I'd suggest backing up the Licensing/mathpass file

and I am sorry for the inconvenience, this paclet was an unfortunate oversight

happy to hear it worked!

does the FE start now?

no, that's what the result should look like

and PacletUpdate["CloudObject"]

try the standalone kernel

ok, but now that you are activated

okay, this is good

hmm, this reminds me of a bug, is it possible you are using version 10.0.0?

hopefully you have the licensing information handy

that's some progress

and then try starting the FE again/

could you delete the Paclets directory

both locations are writable by Mathematica? do they contain anything?

you deleted both /usr/share/Mathematica and ~/.Mathematica ?

I do suspect the paclet issue I linked to, but there probably is something in addition to that

and the startup hang appeared just recently?

what version are you using?

sure, hopefully we can figure something out

Thank you! I try to contribute to the site a bit when I have time, but there are so many experts here who've provided thousands of great answers. I hope you find it useful and enjoyable.

yes, absolutely

feedback is always appreciated, and support can file suggestions to our development team

by the way, please feel free to send any functionality wishes or examples that could be improved to [email protected]

yes, DSolve is under active development