Skip to main content

Defining a function via pattern matching with SeriesData


I want to define a function myLO that gives me the leading order of a series expansion in Mathematica (the whole term, not just the coefficent).


My idea is, given that any series expansion in Mathematica has de form SeriesData[x, x0, {a0, a1, ...}, nmin, nmax, den] I can use this structure to construct my function. I did it the following way:


myLO[SeriesData[x_,x0_,coefs_List,nmin_Integer,nmax_Integer,den_Integer]]:=First@coefs Power[(x-x0),nmin/den]

And it works OK, e.g.



serie = Series[ Exp[x-1]/Sqrt[x-1],{x,1,3}]

myLO[serie]
(* 1/Sqrt[-1 + x] *)

But in the definition it gives me an error:


SeriesData::sdatc: "Coefficient specification coefs_List in SeriesData[x_,x0_,coefs_List,nmin_Integer,nmax_Integer,den_Integer] is not a list."

I don't understand this error, I am specifying that the header of lcoefsmust be List, but the function seems to do not notice it. I can write {a__} instead, and it won't trigger (but it will complain about the integers), but I want to handle the list as a whole.


How can I avoid this? Or how can I improve this definition?




Answer



Explanation


Using the construction arg_List indeed specifies that arg should be given as a list, and this is a correct construction to match an expression of the form arg = {subexpression} when the outer head enclosing arg_List does not evaluate.


For instance, the function f defined by


f[g[arg_List]] := Total[arg]

expects an argument with head List in order to trigger the right-hand side. The difference with your situation comes from the symbol g. In the above, there is no definition associated to it; in your example, g is SeriesData and there is a definition associated to it.


What happens is that the expression


SeriesData[x_, x0_, coefs_List, nmin_Integer, nmax_Integer, den_Integer]


evaluates (even though it is written in a SetDelayed construction --- see below). Since SeriesData is expecting a list as a third argument and integers afterwards, it will complain when given arguments with other heads:


Head /@ {coefs_List, nmin_Integer, nmax_Integer, den_Integer}
(* {Pattern, Pattern, Pattern, Pattern} *)

After throwing the error message, the same expression SeriesData[...] will be returned, the definition will be constructed with this expression, and the latter will be used subsequently for the pattern-matching, which explains why an output is still generated when calling the definition.


Solution


The solution to make this work is to wrap the expression in the symbol HoldPattern, in order to prevent the evaluation of the expression.


Defining


myLO[HoldPattern@ 
SeriesData[x_, x0_, coefs_List, nmin_Integer, nmax_Integer, den_Integer]

] := First@coefs Power[(x - x0), nmin/den]

will not generate any error messages.


Additional comments


The fact that a symbol has the attribute HoldAll does not mean that it will not evaluate its arguments. It means instead that its definition is triggered before evaluating the arguments.


Evaluation of those arguments will then depend on the internal of the function. So, the arguments may not be evaluated at all, or they can be evaluated once, or several times. About SetDelayed, its first argument (left-hand side) does evaluate, as shown by the generated error message.


Comments

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...

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...

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...