Skip to main content

compile - How to execute an existing notebook with Wolfram Engine?


[My related question: mwe-for-compiling-functions-into-standalone-dll-and-calling-them-in-python - here I am exploring an alternative]


I have downloaded, installed and activated the wolfram engine (12.0) on Windows, and I have installed the WolframClient in my Python environment.


In python I execute


from wolframclient.language import wl
from wolframclient.evaluation import WolframLanguageSession

kernelLoc = 'C:\\Program Files\\Wolfram Research\\Wolfram Engine\\12.0\\WolframKernel.exe'
session = WolframLanguageSession(kernelLoc)
session.evaluate(wl.StringReverse('abc'))

and the result is 'cba' proving that the integration is working.


I have a workbook that contains all my (valid) compilable functions.


Question: how do I load & evaluate that notebook and call the compiled functions? (I could use a package file instead if that would help)


I have not (yet) found the answer by reference to the Wolfram Client documentation


Side issue: I recall that setting up my MMA 11.0.1.0 to work with Visual Studio 2017 for C compilation was... tricky. Does the Wolfram Engine have independent setup and if so how do I apply the working config for compilation from MMA to WE? Of course, if I can load the required notebook and it just works then this becomes redundant, but... expect the not-to-be-unexpected is my motto for development.


Update



Loading a Notebook requires FrontEnd, which is not available; I tried to import using NotebookImport, passing a filename and using "Input" as the style filter but also to no avail


using


nbPath = 'A:\\My Documents\\...\\ctXi_WolframEngine.nb'
mynb = session.evaluate(wl.NotebookImport(nbPath,'Input'))
mynb

I got this, which is clearly not helpful


(HoldComplete[None],
 HoldComplete[None],
 HoldComplete[None],

 HoldComplete[None],
 Failure['InterpretationFailure', {'CellStyle': 'Input', 'ContentData': BoxData, 'Cell': RawBoxes[Cell[BoxData['~'], 'Input', Rule[CellChangeTimes, (3771391298.009615,)]]]}],
 HoldComplete[None],
...

Note that the notebook works perfectly well in Mathematica itself.



Answer



Provided that $Path contains an appropriate path to a package CTMisc.m the following works


session.evaluate(wlexpr('Needs["CTMisc`"]'))


Then I was able to successfully call a function yyyymmddhhmmssmsDateString[milliseconds_] defined in that package


t = session.evaluate(wlexpr('yyyymmddhhmmssmsDateString[3407800000]'))
print(t)

1900-02-09 10:36:40.000

One must be careful with the expression of strings: contexts as strings are usually written as "MyContext`" in Mathematica. I had a problem when I was trying to be too literal and declared


pkgName = '"MyContext`"'

Specified correctly one can also write e.g.



session.evaluate(wl.Get("MyContext`"))

The following function was defined in the package:


compiledTestFunction = 
Compile[{{n, _Real}, {m, _Real}},
    Module[{},
        Return[n * m]
    ];
    CompilationTarget->"C", "RuntimeOptions"->"Speed"];


After Get-ting the package we define the Python function and then execute


compiledTestFunctionPython = session.function('compiledTestFunction')
compiledTestFunctionPython(2.0, 7.0)

and the result is as expected, 14.0


Conclusion: Wolfram Engine on Windows 10 with Visual Studio 2017 worked out of the box for C compilation on this MWE.


Comments

Post a Comment

Popular posts from this blog

mathematical optimization - Minimizing using indices, error: Part::pkspec1: The expression cannot be used as a part specification

I want to use Minimize where the variables to minimize are indices pointing into an array. Here a MWE that hopefully shows what my problem is. vars = u@# & /@ Range[3]; cons = Flatten@ { Table[(u[j] != #) & /@ vars[[j + 1 ;; -1]], {j, 1, 3 - 1}], 1 vec1 = {1, 2, 3}; vec2 = {1, 2, 3}; Minimize[{Total@((vec1[[#]] - vec2[[u[#]]])^2 & /@ Range[1, 3]), cons}, vars, Integers] The error I get: Part::pkspec1: The expression u[1] cannot be used as a part specification. >> Answer Ok, it seems that one can get around Mathematica trying to evaluate vec2[[u[1]]] too early by using the function Indexed[vec2,u[1]] . The working MWE would then look like the following: vars = u@# & /@ Range[3]; cons = Flatten@{ Table[(u[j] != #) & /@ vars[[j + 1 ;; -1]], {j, 1, 3 - 1}], 1 vec1 = {1, 2, 3}; vec2 = {1, 2, 3}; NMinimize[ {Total@((vec1[[#]] - Indexed[vec2, u[#]])^2 & /@ R...
Post a Comment
Read more

functions - Get leading series expansion term?

Given a function f[x] , I would like to have a function leadingSeries that returns just the leading term in the series around x=0 . For example: leadingSeries[(1/x + 2)/(4 + 1/x^2 + x)] x and leadingSeries[(1/x + 2 + (1 - 1/x^3)/4)/(4 + x)] -(1/(16 x^3)) Is there such a function in Mathematica? Or maybe one can implement it efficiently? EDIT I finally went with the following implementation, based on Carl Woll 's answer: lds[ex_,x_]:=( (ex/.x->(x+O[x]^2))/.SeriesData[U_,Z_,L_List,Mi_,Ma_,De_]:>SeriesData[U,Z,{L[[1]]},Mi,Mi+1,De]//Quiet//Normal) The advantage is, that this one also properly works with functions whose leading term is a constant: lds[Exp[x],x] 1 Answer Update 1 Updated to eliminate SeriesData and to not return additional terms Perhaps you could use: leadingSeries[expr_, x_] := Normal[expr /. x->(x+O[x]^2) /. a_List :> Take[a, 1]] Then for your examples: leadingSeries[(1/x + 2)/(4 + 1/x^2 + x), x] leadingSeries[Exp[x], x] leadingSeries[(1/x + 2 + (1 - 1/x...
Post a Comment
Read more

What is and isn't a valid variable specification for Manipulate?

I have an expression whose terms have arguments (representing subscripts), like this: myExpr = A[0] + V[1,T] I would like to put it inside a Manipulate to see its value as I move around the parameters. (The goal is eventually to plot it wrt one of the variables inside.) However, Mathematica complains when I set V[1,T] as a manipulated variable: Manipulate[Evaluate[myExpr], {A[0], 0, 1}, {V[1, T], 0, 1}] (*Manipulate::vsform: Manipulate argument {V[1,T],0,1} does not have the correct form for a variable specification. >> *) As a workaround, if I get rid of the symbol T inside the argument, it works fine: Manipulate[ Evaluate[myExpr /. T -> 15], {A[0], 0, 1}, {V[1, 15], 0, 1}] Why this behavior? Can anyone point me to the documentation that says what counts as a valid variable? And is there a way to get Manpiulate to accept an expression with a symbolic argument as a variable? Investigations I've done so far: I tried using variableQ from this answer , but it says V[1...
Post a Comment
Read more