https://community.wolfram.com RSS Feed for Wolfram Community showing any discussions tagged with Product Set Up sorted by active. https://community.wolfram.com/groups/-/m/t/3694230 Has anyone installed Mathematica on the new MacBook Neo? The machine uses the A18 phone processor and has only 8 GB memory, but online reviews claim it has surprisingly good performance. I'm considering buying one for travel, but wondering how well Mathematica performs on it. John Shonder 2026-04-17T13:35:21Z https://community.wolfram.com/groups/-/m/t/3685386 Dear All, I bought a new Apple iPad Air 2026 - 11 inch - 128GB, can I use the Wolfram software online on it? In advance, thanks for your answer! Jos Klaps 2026-04-13T12:46:48Z https://community.wolfram.com/groups/-/m/t/3444192 Team, I am very rusty on this one. I have been about 4 years away and returning to a new RB Pi 5.o. The problem is that I do not know how to get started with installation of Mathematica. I downloaded an Installation script. But from here I am lost. I click the file, but only opens a text file with a code. Can not get to go any further. Jose Calderon 2025-04-14T23:29:40Z https://community.wolfram.com/groups/-/m/t/3558367 Hello I tried using the shell script from wolfram website to install 14.2 on Trixie Didn’t work due to failed dependencies… So I downloaded these two pkgs manually from ftp.debian.org libprec3_8.39-13_arm64.deb; libwayland-egl1-mesa-22.3.6-1+deb12u1_arm64.deb And after installing them, I can proceed with the installation… Any suggestions if there is a better way? Ed Wong 2025-10-09T02:29:04Z https://community.wolfram.com/groups/-/m/t/3552254 Are there any compatibility problems with Ryzen CPUs? Mark Harder 2025-09-28T13:34:25Z https://community.wolfram.com/groups/-/m/t/339315 Hello I have been using MathTensor for a long time and I always received helpful information from the web-site of the authors (Christensen, Parker). When trying to approach this web-site to seek information how to use this package with Mathematica 10 I was surprised to learn that this web-site obviously does not exitst any longer. Each attempt to open this site was in vain. Does anybody know what happened? Surely, M 10 offers a lot of tensor facilities but I believe that MathThensor could still offer a lot beyond that what Mathematica 10 offers. Does anybody know how to install MathTensor on Mathematica 10 on a Win7 PC? Thanks in advance Andre Andre Hertkorn 2014-09-09T14:07:31Z https://community.wolfram.com/groups/-/m/t/3488555 This must be a bug of some kind. It's not even consistent, but when it's occurring, no matter what input I give a cloud chat notebook cell, using Wolfram as the LLM service, OpenAI as the LLM service, or even Gemini as the LLM service, there will be long periods when the evaluation of the chat notebook cell either returns an errored-out empty cell, or it briefly displays an empty cell and then deletes that in-progress empty output. If you mouse over the red cell (when it does show up), you see an error: "An unknown box name (ToBoxes) was sent as the BoxForm for the expression. Check the format rules for the expression.". Here's an example where I evaluated a blank chat notebook input, with just that red inner cell showing up: ![empty cell with ToBoxes error][1] The TLDR is that there might be an errant backtick after `UpdateInterval` breaking everything somehow: Cell[ BoxData[ DynamicBox[ ToBoxes[ Refresh[ CompoundExpression[ Increment[Wolfram`Chatbook`SendChat`Private`x$82600], If[ MatchQ[Wolfram`Chatbook`SendChat`Private`$reformattedCell, _Cell], CompoundExpression[ Pause[1], NotebookWrite[ Wolfram`Chatbook`SendChat`Private`cellObject$81846, Wolfram`Chatbook`SendChat`Private`$reformattedCell ], Remove[ Wolfram`Chatbook`SendChat`Private`x$82600, Wolfram`Chatbook`SendChat`Private`cellObject$81846 ], Null ], Wolfram`Chatbook`Common`catchTop[ Wolfram`Chatbook`SendChat`Private`dynamicTextDisplay[ Wolfram`Chatbook`SendChat`Private`container$81846, Function[ CompoundExpression[ Set[ Wolfram`Chatbook`$ChatHandlerData["EventName"], "FormatChatOutput" ], Wolfram`Chatbook`FormatChatOutput[SlotSequence[1]] ] ], True ] ] ] ], TrackedSymbols :> {Wolfram`Chatbook`SendChat`Private`x$82600}, UpdateInterval -> 0.4` ], StandardForm ], Deinitialization :> Quiet[TaskRemove[Wolfram`Chatbook`SendChat`Private`task$81846]], Initialization :> If[ UnsameQ[$SessionID, 35126011282740619268], NotebookDelete[EvaluationCell[]] ] ] ], Can you spot it? ---------- Ok, now what made this extremely difficult is that I believe somehow the parsing diagnostic reports an issue with the `form` argument to `ToBoxes`, even though it looks like it's correct (`StandardForm`). Indeed, tweaking and playing around with it gives a clue: ToBoxes[ Refresh[ CompoundExpression[Null]` ], StandardForm ] yields: Syntax::sntxf: "Refresh[" cannot be followed by "CompoundExpression[Null]`]". Removing the errant backtick gives a result that's almost reasonably renderable. Now here's where things get a tiny bit deep. Because the issue is sometimes invisible, I had to start off my debugging session by tracking down the code that draws the tooltip. I was curious, so I spent several hours digging into the cloud chat notebook javascript implementation - thankfully I'm familiar with react and modern react buildsystems. If you ever need to debug the wolfram cloud notebook interface, this information may be useful. They've not obfuscated the code, so if you're running in `PRD` instead of `LOCAL`, `LOCAL8080`, or `DEVEL`, the logging functions are there, just nopped out. To turn it all on, look for the debug logger class, you can search for `debug()` in `dist/dyn/layoutWithNotebook.modern[some hash string].modern.js` and you'll see where the shims are nopped out: warn() {} info() {} debug() {} trace() { this.enabled && f >= _("trace") && console.trace() } Then, if you set a breakpoint either after the class is finished defining, or at debug `itself` (will fire on any invocation of debug), you can monkey patch them back into functionality quite easily with the console as such: (this.__proto__.warn = console.warn) | (this.__proto__.info = console.info) | (this.__proto__.debug = console.debug) | (this.__proto__.trace = console.trace) If you do this you will quickly end up with thousands and thousands of log entries - they were quite thorough when building a full clone of the Mathematica environment in the browser. You'll probably enjoy chrome devtools crashing frequently from the memory usage. This logging indicated there are a surprising number of unimplemented functions being sent to the browser client to evaluate, including symbols that look like they might be important to the functionality I'm using (e.g. `Unsupported symbol Wolfram`Chatbook`UI`MakeChatCloudDockedCellContents`). I can't tell if I'm just experiencing two separate issues (blank output due to models spitting out unsupported symbols, separate from the backtick issue?) or something deeper. Given I don't have access to mathematica desktop these days, I've been playing around with the cloud notebooks instead, so I'll have to fuss with this more. For completeness, here's the notebook: &[Wolfram Notebook][2] https://community.wolfram.com/groups/-/m/t/3336417 [1]: https://community.wolfram.com//c/portal/getImageAttachment?filename=Screenshot2025-06-29at7.43.08%E2%80%AFPM.png&userId=3488519 [2]: https://www.wolframcloud.com/obj/256e20f0-3ee2-47ea-b633-94f02e98104c Alexander Riccio 2025-06-30T03:38:50Z https://community.wolfram.com/groups/-/m/t/3465203 I'm a newbie. I installed Mathematica on my Raspberry Pi 5, running Linux (version 6.12.25+rpt-rpi-2712). When I access it via RealVNC with a screen size of 1280 x 1024, the loading whirlpool appears, but after 20 seconds, nothing happens. Where are the error logs? Any suggesion? Mathematica problem or should blame Vnc? Thanks in advance Emine Simsek 2025-05-21T09:16:17Z https://community.wolfram.com/groups/-/m/t/3417144 If I get help on how to use and download Mathematica it would be greatly appreciated! Mark Raygorodsky 2025-03-15T17:56:31Z https://community.wolfram.com/groups/-/m/t/3326673 Hello all :) I just bought a one year subscription plan for WANE. But when I download Wolfram 14.1 I only get Mathematica 14.1 not WANE 14.1. I have tried this 3 times with no success. I sent this question to Support @Wolfram and I was told...again.."it's the same product" that is Wolfram 14.1. If someone could help me I will be very grateful.. Kind regards to all. Jean-Michel Jean-Michel Collard 2024-11-21T19:51:16Z https://community.wolfram.com/groups/-/m/t/3201543 ![Setup local AI with Ollama and Wolfram: A step-by-step guide for configuring on Windows systems][1] # Ollama setup (post-it note instructions) Set a Windows User Environment Variable OLLAMA_ORIGINS with a value of * (Start -> Settings -> System -> About -> Advanced System Settings (on the right) -> Advanced (tab) -> Environment Variables -> Add a new one on top) Here's your HTTP request. The "ExportString" is the magic: ollamaHttpRequest[model_, contextSize_, context_, seed_, streaming_, prompt_] := HTTPRequest["http://127.0.0.1:11434/api/generate", <|"Method" -> "POST", "Headers" -> <|"Content-Type" -> "application/json"|>, "Body" -> ExportString[ <|"model" -> model, "prompt" -> prompt, "context" -> context, "stream" -> streaming, "options" -> <|"seed" -> seed, "num_ctx" -> contextSize|>|>, "JSON"]|>]; Do a URLRead on that to send it to Ollama and you get an object from Ollama you can parse (should give you a '200' status server code). Here's how you parse a non-streaming response: ollamaReadSingle[ollamaHttpResponse_] := Association[ImportString[ollamaHttpResponse["Body"], "JSON"]]; And here's how you parse a streaming one: ollamaReadStreaming[ollamaHttpResponse_] := Association[#] &@ImportString[#, "JSON"] & /@ StringSplit[ollamaHttpResponse["Body"], "\n"]; Confirming this doesn't to async responses yet (so you will wait even if you put in "streaming" unless you figure that part out). Didn't see this anywhere else. As much fun as it is being the only person in the world with a barely-working prototype... # Streaming Chat Setup I am under the impression there is more interest in using Ollama with Mathematica. I've got quite a few features working, and would like to share. The idea with this is if you're a grad student or armchair researcher, you can get up and running with Ollama and start experimenting today. If you're not using Ollama, it is available at [ollama.com][2]. It is a free and runs AIs locally on your computer (with extensive use of your graphics card to generate responses). Attached is a notebook with an extensible framework that I hope will permit further experimentation with GPTs. Some features are included already. It's tested, but not extensively. **Instructions are for Windows**, however there are parallel functions and features for Mac and Linux (and these instructions are also much more extensively covered online). All this model does is stream chat requests - it does not pull additional models, list what models you have, or run any other commands besides sending a streaming chat request (though it should be relatively easy to extend these features). **Crash Course** If you're already using Ollama, the crash course is to run the commands to load the model names, variables, and functions in the "Run Once" section, then scroll down to the bottom and enjoy. You may need to add an "OLLAMA_ORIGINS" environment variable (detailed below). If this is your first time using Ollama, you will want to use Powershell to download at least one model file (this contains all the weights [the "brains"] of the AI). You should also attempt to start a Powershell chat session with the model to make sure it is returning responses, and there is no issue with Ollama failing to run. If you are having issues running Ollama commands from Powershell, see if you can navigate to the installation folder, typically %AppData%\Local\Programs\Ollama, and attempt to run the commands there. If commands work from the Ollama installation folder, then the Ollama path is likely missing from your "Path" environment variable. **Ollama Environment Variables** Unless you do application configuration for a living, this is probably your first time hearing about environment variables. There are a few that you'll want to set / unset / know what they do. To get into these (on Windows 10), go to Start -> Settings -> System -> About, and click "Advanced system settings" on the right. On the "System Properties" window, go to the "Advanced" tab and click "Environment Variables". You should get the following window: ![enter image description here][3] (I removed my system irrelevant variables for obvious security reasons, but you should have a lot.) You may click "New" to add further variables. You will need to add "OLLAMA_ORIGINS" and set the value to "*://localhost" as in the example so that Ollama is allowed to receive connections from your own computer. If you click on "Path" and click "Edit", you may have the path to the Ollama install directory in here. This allows Powershell, the Run dialog, and other things to run Ollama without needing to reference the entire folder path in the command line. "OLLAMA_MODELS" will let you specify a different directory to download models into. Lastly, please confirm that Mathematica is allowed to access the Internet (on version 12, this option is under Edit -> Preferences -> Internet & Mail). **Building Ollama HTTP Requests** Most of the HTTP request is built using Mathematica association datatypes - this is mostly just a list where values are assigned to a named "key" as well as maintaining an array position, and can be called by the name of the key. Same as I've mentioned in an earlier post, the secret to getting the HTTP requests to work is to export *just the body* of the HTTP request association to JSON: ollamaHttpRequest[bodyAssociation_] := HTTPRequest["http://127.0.0.1:11434/api/generate", <|"Method" -> "POST", "Headers" -> <|"Content-Type" -> "application/json"|>, "Body" -> ExportString[bodyAssociation, "JSON"]|>]; This portion works for streaming responses as well as single-body responses. The notebook attached builds the request in phases using a temporary association variable, beginning with a basic request saved to a temporary variable, and **appending** further body tags to that temporary variable before returning it as the result of the function: ollamaHttpRequestBody[ollamaOptions_] := ( ollamaTempHttpRequestBody = <|"model" -> ollamaInputModelString, "prompt" -> ollamaInputFuncUserPromptString, "stream" -> True, "keep_alive" -> ollamaInputKeepAliveString, "options" -> ollamaOptions|>; (* Context - Included if not empty *) If[ollamaUseContext && (ollamaVarCurrentConversationList != {}), ollamaTempHttpRequestBody = Append[ollamaTempHttpRequestBody, "context" -> ollamaInputFuncSelectedContext]]; (* Template *) If[ollamaUseTemplate, ollamaTempHttpRequestBody = Append[ollamaTempHttpRequestBody, "template" -> ollamaInputTemplateString]]; (* System Prompt *) If[ollamaUseSystem, ollamaTempHttpRequestBody = Append[ollamaTempHttpRequestBody, "system" -> ollamaInputSystemPromptString]]; (* Image - Included if this model is a vision model *) If[ollamaUseImage && ollamaFuncIsBoolVision[ollamaInputModelString], ollamaTempHttpRequestBody = Append[ollamaTempHttpRequestBody, "images" -> ollamaInputFuncImageList]]; (* Include further body tags in here *) (* This returns just the temporary HTTP request body association \ variable as the result of the function *) ollamaTempHttpRequestBody ); The "Options" portion of the request is built much the same way, as are the image and prompt parsing functions. This is done to allow easy extensibility - simply include an additional Boolean flag and pass the prompt or image to a manipulation function. **Saving Information** The notebook will save the contents of each query, and can be further extended to save further information by passing variables to Current Query Association variable (such as image sizes and CRC32 file hashes), as demonstrated below in the image builder. This function will take an input of a list of paths of images, and first import the files so the files can have information saved (such as the size and hash), and then are converted into raw images so they can be manipulated, resized and the like, and then re-exported into JPG format for use as input into Ollama: ollamaInputFuncImageList := ( (* Appends the image paths to the query *) ollamaVarCurrentQueryAssociation = Append[ollamaVarCurrentQueryAssociation, "imagePaths" -> ollamaVarImagePathsString]; (* Splits the single string list of files up at the semicolons \ into a list of file paths *) ollamaTempFilePathsList = ollamaFuncGetImagePathsStringList[ollamaVarImagePathsString]; (* Entire image files are imported as binary objects *) ollamaTempImageFileList = ByteArray /@ (Import[#, "Byte"] & /@ ollamaTempFilePathsList); (* Appends the size of the images to the current query association \ *) ollamaVarCurrentQueryAssociation = Append[ollamaVarCurrentQueryAssociation, "imageFileSizes" -> (Length[#] & /@ ollamaTempImageFileList)]; (* Also appends a list of file hashes *) ollamaVarCurrentQueryAssociation = Append[ollamaVarCurrentQueryAssociation, "imageHashesCRC32" -> (ollamaFuncImageFileHashString[#, "CRC32"] & /@ ollamaTempImageFileList)]; (* The binary object image files are imported again in the image \ format, so it is now editable by image functions *) ollamaTempImagesList = ImportByteArray[#] & /@ ollamaTempImageFileList; (* This runs all the edits we want to apply to our images *) ollamaTempImagesList = ollamaFuncAlterImage[#] & /@ ollamaTempImagesList; (* Returns the list of images for inclusion in the HTTP request *) ToCharacterCode[ExportString[#, "JPG"]] & /@ ollamaTempImagesList); **Receiving Streaming Responses** On URL submission, the Ollama server will begin returning responses. HTTP requests can be manually submitted via the use of the URL Submit function (however this notebook will call the URL Submit function with a number of other helper functions): ollamaVarResponseTask = URLSubmit[ ollamaHttpRequest[ollamaTempHttpRequestBody], HandlerFunctions -> <| "HeadersReceived" -> (ollamaFuncHandlerHeaders[#Headers] &), "BodyChunkReceived" -> (ollamaFuncHandlerBodyChunks[#BodyChunk] \ &), "ConnectionFailed" -> (Print[ "Connection Failed: Ollama is probably not running."] &), "TaskFinished" -> (ollamaFuncHandlerTaskFinished &), "TaskStatusChanged" -> (ollamaFuncHandlerTaskInterrupt[#Task, \ #TaskStatus] &) |>, HandlerFunctionsKeys -> {"BodyChunk", "Headers", "Task", "TaskStatus"}]; When setting up the URL Submit, you will *want* to save the URLSubmit command to a variable to keep track of the "task". This task variable may be used later to interrupt the query by the use of the "TaskRemove" function. For a streaming response, URL Submit will need to be provided with "handler functions", and "handler function keys". Handler functions are called when certain HTTP events take place, such as a body chunk is received (usually containing a single token), when the response is finished, interrupted, when headers are received, etc.. Handler function keys are values passed with the event. A simple example is the headers handler, which just saves the returned headers into the current query association under the "headers" key: ollamaFuncHandlerHeaders[ headers_] := (ollamaVarCurrentQueryAssociation = Append[ollamaVarCurrentQueryAssociation, "headers" -> headers];); It is okay to receive responses just as a string without attempting to import them from JSON into an association, especially when debugging. **Issues & Future Work** There may be some issues with the body chunks received. Some may be sent back empty, and some may be sent back incomplete (with the completed portions sent in subsequent body chunk responses). The notebook attached will parse some of these issues, but it seems like some new models can introduce new issues. There are further notes within the notebook detailing how to tell if it's running, how to handle crashes and the like. Mostly you'll want to check your graphics usage, specifically the "Cuda" usage, but there are other signs things are working or not. Please feel free to extend & upload the attached notebook at will. I won't be adding features, but if there are errors or bugs I may fix them & reupload (it's a lot of code, I'm sure I've missed some things, but I feel like this is good enough to publish at present). # Setup and usage details &[Wolfram Notebook][4] [1]: https://community.wolfram.com//c/portal/getImageAttachment?filename=Image20241018183644.jpg&userId=20103 [2]: http://ollama.com [3]: https://community.wolfram.com//c/portal/getImageAttachment?filename=EnvironmentVariables.png&userId=2392475 [4]: https://www.wolframcloud.com/obj/68e4cc4b-ea49-495f-8540-215467295fc6 Cameron Kosina 2024-06-29T06:07:36Z https://community.wolfram.com/groups/-/m/t/3282353 Hello. At my college, Mathematica 14.0 is installed on a server. I asked our computer center why there are no *local* help pages, and instead it jumps to a web browser (none too successfully, by the way). They told me that with Mathematica 14.0 and newer, the help pages need to be installed on a user-by-user bases. This makes no sense to me. (What a waste!) Can someone tell me if this is true? If so, why? If not, how can I explain to the computer center how to do this? TYVM. Aaron Naiman 2024-09-24T20:39:20Z https://community.wolfram.com/groups/-/m/t/3254456 **Wolfram Prerelease** is open to new beta testers! Your feedback will be very useful and will improve future releases of Wolfram products. If you're interested in participating in this program and receive the latest builds, please apply by sending an email to prerelease@wolfram.com with a self-intro and license number if you're an existing customer. Jay Yao 2024-08-23T19:30:12Z https://community.wolfram.com/groups/-/m/t/3250945 I recently installed Mathematica 14 (Wolfram). While the notebook directory for version 13 was ~/Documents/Mathematica, the new version neither uses the old or the new ~/Documents/Wolfram. How do I set the directory under the new version 14? jules.aronson 2024-08-19T14:17:58Z https://community.wolfram.com/groups/-/m/t/2929768 I am unable to install the local documentation to a drive other than the c: drive. The installer for the documentation does not expose the option to redirect the installation. I have successfully installed Mathmatica to the D: drive, but the documentation still shows up on the c: drive. It's 8GB so it puts a big dent in my c: drive and I need to move it. Any suggestions? Gregg Revak 2023-06-02T16:18:28Z https://community.wolfram.com/groups/-/m/t/3248036 The upgrade to v14.1 changed the Eclipse->Window->Preferences->Wolfram Engine Installations to v14.0 with the path C:\Program Files\Wolfram Research\Mathematica\14.0. However, when I launch Mathematica, it uses v14.1. Should I reconfigure Eclipse to point to v14.1? If so, how can I do it? Thanks, George George Clapp 2024-08-13T20:57:32Z https://community.wolfram.com/groups/-/m/t/3066592 Withe the apple silicon and the new snapdragon elite X it seems that the trend is to move towards arm based chips. I know that mathematica does support apple silicon, but are there any plans to support other arm chips? I mean, like a general version of mathematica for the arm chips in linux and windows machines. Felipe Barbosa 2023-11-17T11:51:23Z https://community.wolfram.com/groups/-/m/t/1266184 Thought I'd post something I was struggling with in order to get Mathematica (and any sub-menus it might launch) to display correctly on high resolution monitors in Linux. The default ScreenResolution is 72dpi in a newly installed Mathematica. My monitor (and almost all modern monitors) use a higher resolution. In my case 96dpi. This means that everything rendered is tiny (it renders to 72/96 of what it was intended to run at). Controlling some fonts fails to control sizes in menus, icons, and tool bars in general. Bits and pieces of Mathematica can be enlarged through font or ScreenResolution changes, but it is difficult at best to get even part of what is too small back to a normal size. So here is how to fix this with a single step... Setting environment variables like this will fix the issue...note that 96/72, the dpi of actual monitor versus what seems to sometimes be hard coded into Mathematica, is about 1.33. This will correct the issue if starting on command line: QT_AUTO_SCREEN_SCALE_FACTOR=1 QT_SCALE_FACTOR=1.33 Mathematica & Starting Mathematica like this will allow the palettes, icons, buttons, and window frames to enlarge uniformly. Dan Stimits 2018-01-16T02:04:25Z https://community.wolfram.com/groups/-/m/t/3155725 Great having Mathematica 14 now also available for the Raspberry Pi, thank you very much! The only problem is that when starting an upgraded install (from 13.3.1). it stops with a series of errors, the first shown in the screenshot (I'm not using walynd but the old X/VNC combo). ![Mathematica 14 startup error][1] Thanks for your help, Michael [1]: https://community.wolfram.com//c/portal/getImageAttachment?filename=Mathematica14_error.jpg&userId=1664744 Michael Byczkowski 2024-04-09T18:24:27Z https://community.wolfram.com/groups/-/m/t/3132414 I recently switched to Mathematica version 14. I was using Chat Notebooks and LLMs in version 13.3.1. So, to set up my settings in v 13.3.1, I head to AI settings and select the model I wanted to use (GPT4) and also some tabs to choose and install Personas and check to connect and disconnect for API connection, but now I am getting a single tab for version 14. Was the previous setting page changed? I cannot find anything in the options or documentation or the Stephen Wolfram writings blog. AI settings version 13.3.1: ![enter image description here][1] Also this one v 13.3.1: ![enter image description here][2] Now on version 14 I only get: ![enter image description here][3] [1]: https://community.wolfram.com//c/portal/getImageAttachment?filename=v_13.3.1.png&userId=1624766 [2]: https://community.wolfram.com//c/portal/getImageAttachment?filename=v_13.3.1_2.png&userId=1624766 [3]: https://community.wolfram.com//c/portal/getImageAttachment?filename=v_14.png&userId=1624766 J V. Alva 2024-02-29T00:56:54Z