Joe Riel

9470 Reputation

23 Badges

18 years, 64 days

MaplePrimes Activity

These are answers submitted by Joe Riel

Before calling A:-main(), issue the maple command

stoperror(traperror["numeric exception"]);

When you then execute A:-main(0, the debugger will stop at the location of the error (1/n) in foo.

The string in the traperror index should match the start of the error message; here you could reduce it to "numeric".  You can also use


which will cause the debugger to stop at every trapped error.  Usually you don't want that, since some Maple procedures use try/catch to handle special cases and you end up stopping at too many locations before arriving at the place of interest.

I don't believe there is a way to do precisely what you want.  There are, however, a few alternatives that may or may not be acceptable.  The simplest might be to just create a local module, say funcs, which has exports of the local functions you want to use throughout the main module.  Then you could access them with funcs:-foo. For example

parent := module()
    funcs := module()
        foo := proc() ... end proc;
        bar := proc() ... end proc;
   end func;
      foo := proc()
      end proc;
end module:

Another possibility, if you are planning on making parent a package, is to make foo an export of it, but don't allow it to be given a short name if the parent is with'ed, i.e. a user calls with(parent).  That doesn't prevent it from being called externally, or from appearing in the output of exports(parent), but it does make it slightly less accessible.  To do this, make _pexports an export of parent and assign it a procedure that returns a list of the exports you want to be withed.  For example,

parent := module()
option package;
export foo, bar, _pexports;
    _pexports := () -> [ ':-bar' ];   # only bar will show up in the output of with(parent)
end module:


Later A third alternative is to make foo a local, but call it with thismodule:-foo.  That, however, can only be used if thismodule refers to parent, that is, it won't work inside a procedure in a submodule of parent. 

Here's a somewhat crude solution using the Syrup package (available on the MapleCloud):

Solve := proc(m::posint, n::posint, p::posint)
local R, ckt, i, j, k, sbuf, sol;

    sbuf := StringTools:-StringBuffer();
    sbuf:-append("* Grid Circuit\n");

    # insert resistances forming grid
    for i from 0 to m do
        for j from 0 to n do
            for k from 0 to p do
                if 0 < i then sbuf:-appendf("Rx%d%d%d n%d%d%d n%d%d%d 1\n", i,j,k, i-1,j,k, i,j,k) end if;
                if 0 < j then sbuf:-appendf("Ry%d%d%d n%d%d%d n%d%d%d 1\n", i,j,k, i,j-1,k, i,j,k) end if;
                if 0 < k then sbuf:-appendf("Rz%d%d%d n%d%d%d n%d%d%d 1\n", i,j,k, i,j,k-1, i,j,k) end if;
            end do;
        end do;
    end do;

    # ground node n000 and connect 1A source to n[m,n,p]
    sbuf:-append("V0 n000 0 0\n");
    sbuf:-appendf("I1 0 n%d%d%d 1\n", m,n,p);

    ckt := sbuf:-value();

    sol := Syrup:-Solve(ckt, 'dc');
    # extract the voltage at node n[m,n,p],
    # which corresponds to the desired resistance.

    R := subs(sol, 'v'[nprintf("n%d%d%d",m,n,p)]);
    return R;
end proc:


The rational returned is 4913373981117039232145573771/4056979859824989677919819480, which is 1.21109...

They can be connected, however, the input is vectorized, which requires an additional step to select which slot of the vector to connect to.  I generally start from the output gate and draw the connection to the input gate, hovering over its input section (left side) until I see the green highlight, then click. That should make a connection, typically (maybe always) to the first slot. Then select the signal (click on the line) and you should see, in the upper right pane a display like A2.y <--> N1.x[1].  That means the output (A2.y) is connected to the first slot of the N1.x.  Use the drop-down menu that appears in that pane to change this to, say N1.x[2]. 

Here is the updated model.


DEtools is rather old and is not a Maple module, but rather a table-based package.  As such, I'm surprised DEtools:-kovavicsols even works, though maybe there is now a mechanism to handle that (use of the member operator, :-, with a table-based package). Try

    proc() `DEtools/kovacicsols`(_passed) end proc

Based on that, I'd modify your code to use either DEtools['kovacicsols'] or `DEtools/kovacicsols`, which is the procedure that is eventually called.

As the help page for edge with init part states, the output will only ever be true for an instant, so on a plot will appear to be always false (0). The output should drive a block that that responds to an edge.  In the attached model it is driving a triggered sampler; you can see the output of the sampler change.


The immediate issue is the assignment L*i(0) := 2000.  The lhs of an assignment should typically be a name, hence the error message.  Admittedly, error message is a bit obtuse; that appears to be a consequence of using 2D math for the input.  Using 1D math gives the more useful message

L*i(0) := 2000;
Error, invalid left hand side of assignment


By way of example



A necessary condition for the two lists of vectors to be equal under a permutation of the vectors is for the two lists to be equal as sets with each vector converted to a set.  This should be cheaper to test and allow the expensive test to be run less often.  Whether it is useful depends how frequently the mismatch occurs. So

Cheap := proc(L1, L2)
local S1, S2;
   S1 := convert(map(convert, L1, 'set'), 'set');
   S2 := convert(map(convert, L2, 'set'), 'set');
   evalb(S1 = S2);
end proc:


I've seen that more than a few times. Am not sure the origin (it's a kernel thing).

The emacs maple debugger (mdcs) doesn't resolve that issue.  Am working on updating the github site for mdcs, will post a message to MaplePrimes when it is ready.

Followup Got a response from the kernel group. Some Maple procedure do, in fact, change in place, which causes issues with the debugger.  I had submitted SCRs for this years ago and was kindly pointed to them. One case where a procedure can change in place is if it modifies itself to add a remember table. I think that now can be done in an alternative way that avoid the change in place, but the example was in some rather old library code.

To use the debugger to step through code, the code has to be in a procedure.  However, you did say that the code was crashing. Am not sure what that means, but if it is raising an error, than you can use that to launch the debugger. For example,

(**) stoperror('all'):
(**) for i to 10 do 1/(i-3); end do:

Executing that will launch the debugger when the error is raised and display the expression raising the error.  Inside the debugger you can inspect the variable i. Maybe this will suffice for your problem.

Is this what you have in mind

(**) with(DynamicSystems):
(**) tf1 := TransferFunction(z/(z^2+z+1),'discrete'):
(**) de1 := DiffEquation(tf1):
(**) de1:-de;
           [x1(q + 1) = -x2(q), x2(q + 1) = x1(q) - x2(q) - u1(q), y1(q) = -x2(q)]

This is consistent with your other issue.  Apparently the Maple version launched by emacs is not reading the .mapleinit file.  Am investigating [it works for me].  Will contact you separately but report any results here. 

Note that it is generally best if the initialization file produces no printable output.  So it is better to terminate the assignment with a colon (vs a semicolon).  That won't matter here.

Rather than use the maplev-mode on git (which I haven't updated in a while, if memory serves), use the one available on the Maple Cloud.  That is, in Maple Standard, click the icon in the upper left that opens the cloud interface.  Search for maplev, then follow the instructions. 

An alternative is to use

s := "   string with   various    spaces    ":
StringTools:-RegSplit(" +", StringTools:-TrimLeft(s));
                        "string", "with", "various", "spaces"

TrimLeft is used to remove a prefix of white space, which would otherwise be returned as an empty string in the sequence.

4 5 6 7 8 9 10 Last Page 6 of 113