@Will_iii Since I don't have Maple Flow, I can only answer by comparing to Maple itself. From what I've seen so far, Maple Flow is just a large subset of Maple commands in a completely different GUI interface.

Since log[b](x) = ln(x)/ln(b), surely this will work:

ln(1000)/ln(10)

Since your error message indicates that the Units:-Simple package is being used, there's a chance that this will work:

:-log[10](1000)

The :- is to tell it to NOT use the package version of log. It works in Maple, but I don't know whether it works in Maple Flow.

There was an Excel file containing the 3D data attached to your recently deleted duplicate Question. Please post and/or attach that file here.

@acer Thank you for the corrections, which I've incorporated into my Answer. I too was skeptical about adding whitespace. I've verified that what I currently have in my Answer works in Maple 2018.

I have no doubt that Typesetting is both easier to use and more flexible / forgiving in syntax. My decision to use nprintf was influenced by knowing that the OP's interest is graph theory and that constructions such as `1:1` are vertex labels produced by GraphTheory:-CartesianProduct and related commands, and vertex labels must be type {symbol, string, integer}. Still, as I said, if the OP only wants to use these multicolored objects for prettyprinting, then they might as well use your Typesetting-based method.

@tomleslie You wrote:

• After the point of achieving a solution, I have no idea what your subsequent code is trying to achieve.

The OP's goal is to get an approximate series solution by the Homotopy Perturbation Method. AFAIK, that's the only purpose of HPM. The well-known S-E-I-R ode system given may just be an example with a more-general HPM solver being the goal.

[Moderator's Comment]

I changed this from a Question to a Post. My reasons are

• A scientific/technical forum's formal Questions are requests for information (for example, solutions (mathematical or computational), workarounds, coding tricks; but not limited to just those). Questions on this forum can be about Maple or other Maplesoft products or third-party add-ons related to those (for brevity, I'll just call all that "the Mapleverse" for the rest of this), linking the Mapleverse with other software, classification of perceived anomalies (e.g., as bugs, misinterpretations of documentation, absence of documentation, errors in documentation, unfortunate design that nonetheless must be lived with, unfortunate design that can be worked around, misconceptions of generally accepted (but often unwritten) conventions about how mathematical software should work), and general mathematical, computational, recreational, and practical technical problems for which one can reasonably expect that the Mapleverse can make some contribution towards a solution (even if it's only a small contribution).
   
• On the other hand, formal Posts are presentations of well-reasoned opinions or arguments or requests for open-ended discussion regarding the Mapleverse and suggested improvements to it (your Post is certainly all of the that); anecdotes regarding the Mapleverse; interesting (or at least workable) Mapleverse solutions to problems for which there is not necessarily a specific Question or solutions that generalize Answers to several Questions, etc.

Of course, your Post is about an "absence of documentation", but there's no doubt that that's the correct classification of the anomaly; so, you're not requesting information about how the anomaly should be classified. 

If you understand the distinction between Questions and Posts that I've written above, then you should also understand that whether the title is grammatically a question is irrelevant. Attempts to classify contributions by that criterion are naive and superficial.

Judicious use of a grammatical question as the title for something that is not a formal Question (as I defined above) can be a powerful rhetorical device---one that I often use myself (more often for Answers and Replies since I don't write many Posts); so, I have no problem with your title. Indeed, I have no problem whatsover with what you wrote; I consider it a valuable contribution (as yours usually are), which I've upvoted; the only issue is how it was classified.

This is obviously a Question, so I just converted it from a Post to a Question.

@nm Good Answer; voted up (and I also upvoted Tom's Answer).

You wrote:

• You can also make y(x) itself a function. But I think it is better to use sol and keep y as free variable.

I strongly agree with that, but I see no problem with assigning the result of unapply to some other unused variable. If the original was y, I'd typically use Y or Y_ (but not _Y because you shouldn't assign to global variables whose names begin with underscore). 

@vs140580 You wrote:

• As my remaing codes are in 2D inputs please help in 2D inputs please kind help please

You can mix 1D and 2D in the same worksheet. Just take my procedure definitions and put them in Maple Input execution groups, and the rest of what you have can remain in 2D Input. The two will execute together seamlessly. (The part of Maple that executes the code, called the kernel, doesn't even see the 2D Input, because the other part, called the GUI, translates the 2D Input to 1D before passing it to the kernel.)

@vs140580 Your recently mentioned requirement can be handled by sorting the rows (elements) of the listlists, like this:

WhereInVS:= (A::Matrix, B::Matrix)-> 
    WhereIn((sort~)~(subs(0= (), convert~([A,B], 'listlist')))[])
:

where WhereIn is the same procedure already given in my Answer.

@vs140580 You are using 2D Input. In your worksheet, look at the first pull-down box on the lowest tool bar. It says "2D Input". To run my code, you need to use 1D input, also known as Maple Input, as I said. You can find "Maple Input" in that pull-down box.

I'm thinking about the rest of your Reply now.

I posted code for your recent Graph Theory Algorithm Question, but you haven't acknowledged my Answer.

Both in standard algebra terminology and in Maple, simplifying and solving are separate operations with distinct targets. One simplifies expressions and only expressions; one solves equations and inequalities or sets of them.

Maple relaxes those target restrictions a tiny bit:

• Simplifying an equation simplifies its two sides separately;
• Solving an expression is treated as solving the equation formed by setting it to 0.

@vs140580 If you don't care about multiplicities, then using sets would be the best way, and it's trivial to code:

evalb({L2[]} subset {L1[]})

I gave a detailed response 2 weeks ago (it's below) explaining 4 possible reasons for the slowness and 3 possible ways to speed things up. You've given no response about whether they helped or even whether you read them.

I did this without being able to see the procedures/functions that you've defined that are in the integrand.

@AHSAN Ah. The English word that you mean in place of "desire" is "resolution" (in its technical sense related to displayed graphics).

@Christian Wolinski Although your Answer "works" in a limited sense in this case, it may give the user the wrong impression that square brackets can in general be used instead of algebraic parentheses as long as one uses expand afterwards. That's not true in the vast majority of cases.