Movatterモバイル変換

Categories

The recordings from Maple Conference presentations, including the workshops, are now available on theconference website.

Thank you to all those who attended or presented, you made the conference a great success!
We hope to see you all again next year.

Kaska Kowalska
Contributed Program Co-Chair

TheSchatz Mechanism should move like this

However, with the default solver settings it froze after a few seconds in a planar link configuration. To make it run, I played around with advanced solver settings. Here is one attempt that went nuts:

(More solver settings for strange behavior can be found here:Schatz_Linkage.msim)

Some people might find this amusing. Of course, it is less fun when the initial plan was to spend an hour just for fun with a simple model (an hour is a fair estimate for similar simple looking models in MapleSim). The immediate reaction when seeing such simulation results is to blame the software for being either buggy or incapable. In this case, however, this was not the case, but identifying the root cause was not obvious.

The Schatz mechanism is a so called closed-loop mechanism where the links of the mechanism form a loop (the ground in the model closes the loop). In general, building and modeling mechanisms with loops is less straight forward than thought. Without a-priory knowledge or help (either by documentation or software hints) users can quickly find themselves in a situation of desperate trial and error. What was easy with other models can become a frustrating experience with unsatisfactory outcome. This happened to me on various occasions.   

What makes closed-loop mechanisms more challenging?  After resting for a long time on my virtual pile of unanswered questions, it turned out that the model, on top of being a closed-loop mechanism, is ill-conditioned: The Schatzmechanism is anover-constrained mechanism that is only mobile for certain geometric parameters. MapleSim can simulate such over-constrained mechanisms, but this can be a balancing act for the solver.

Who could have known this? A knowledgeable expert might say that users who do not know what they are doing should not use the software. But how to become aware of over-constrained assemblies when building and running a model in MapleSim does not require to be an expert?  In this case the geometry was taken from a reference that sets the length of the ground link to Ö3. Model build, assembly and simulation instantly worked … but not for an extended time span.

In retrospect, everything is clear. Models that do not assemble do not fit together. Models that freeze in motion “jam numerically”. Linkages and joints of closed-loop mechanisms made of infinite stiff components may not fit together in all geometrical configurations. During runtime, after successful assembly, a stiff model can make a simulation sensitive to numerical errors. This does not mean that the user is dealing with a so-called numerical stiff problem that can be addressed by using stiff solvers. In this case, stiff solvers could not prevent sudden freeze or inversion of movements.

The only remedies that work for infinite stiff and over-constrained mechanisms are the ones that work also in real life. By either introducing mechanical play or elasticity in supports, joints and links, the simulation becomes robust. Numerically, for this case where none of the many advanced solver options made a difference, a simple increase of the relative error in the standard simulation settings worked.  This remedy could be described as introducing morenumerical play. Interestingly in a completely different approach of animating a Schatzmechanism @one man also needed to introduce “deformations” in hissimulation to make it work.

The Schatzmechanism is of little commercial interest and can therefore be shared. Is it a rare case of successful assembly and freeze during runtime or is it more frequent that users run into similar problems? Only MapleSoft can tell, but in the latter case it could make sense that MapleSim supports the user. I see several possibilities for that:

• A more prominent mention in the documentation that kinematic loops require caution could raise awareness.  
• Algorithmically detecting kinematic loops and informing the user that closed loops can be potentially over-constrained in certain geometric configurations.
• (If possible, analyzing the Jacobian in the frozen configuration might give better hints than solver messages during runtime can provide. The attached model gives the hint with MapleSim 2025.1 that the error tolerance might be too tight, but no indication why.)
• Implementing themobility formula, analyzing closed loops and issuing a warning when the mobility M is less than 1 (meaning no degree of freedom)

The latter option sounds appealing. However, the degree of freedom calculated by the mobility formula only provides a necessary but unfortunately not a sufficient condition for mobility.  For example, connecting a prismatic joint coaxially to another increases the mobility by one but does not add to the mobility of a mechanism. This means that an advanced algorithm must take the orientation of joints into account to determine the effective degrees of freedom. On the other hand, the Schatzmechanism and some other mechanisms have a mobility ofM=0 but can be mobile for certain geometries.

Should Maplesoft implement mobility analysis or are CAD tools that offer some sort of mobility analysis more suitable? In my opinion, from a conceptual point of view, it would be beneficial and faster to have this support already in MapleSim before going into details.

Should the user refrain from modeling infinite stiff mechanisms? I do not think so because they are useful in the context of deriving (analytical) forward and inverse kinematics. Furthermore, there are more mechanisms out there that are mathematically, according to the mobility formula, immobile but useful in daily life. Thetelescopic fork is a prominet example.

Final note for math enthusiasts:

The Schatzmechanism (invented by Paul Schatz) is a byproduct of theinversion of a cube. Recalling that the diagonal of the unit cube isÖ3 gives a hint of why the Schatz mechanism becomes mobile for this parameter. Also related to the inversion of a cube is theoloid: a solid with a developable surface that touches with its entire surface a flat surface whenrolling. The oloid and the Schatz mechanism are closely related, which can be appreciated from thisvideo.

Maplesoft continues to bring technology, collaboration, and learning together. Here’s some of the exciting industry news from the world of web converting and high-precision manufacturing lines, and what’s new withMapleSim for Web Converting Systems software.

How is MapleSim helping web converters and manufacturers?

From EV batteries to flexible packaging and medical films, industries that rely on thin web materials are advancing at remarkable speed. To keep pace, engineers need tools that let themmodel, simulate, and optimize every detail of their process with accuracy and confidence. Processes that once relied on intuition and trial-and-error are now guided by advanced modeling and simulation, such as MapleSim.

Using MapleSim simulation, engineering teams can perform process validation testing virtually -saving time and money compared to physical testing. The virtual models are used toexplore and accelerate production — and the new release of MapleSim delivers a powerful set of features to make that possible.

What’s new in the latest MapleSim release?

The new release (available today) enhances MapleSim’s ability to answer “what-if” questions about industrial systems, easily review and compare results, and find strategies to improve production.

For converters and web material manufacturers, it is now even easier to create models of roll-to-roll systems. The updates to MapleSim for web converting systems include pre-built components formodeling spansandapplying control during rewindingandmatching tension profiles with PLC settings. There is also a newUtilities section to help users to handle sensor data and perform common calculation tasks.

We have just released updates to Maple and MapleSim.

Maple 2025.2 improvements include fixes to print layout, PDF export, tooltips for keyboard shortcuts, Plot Builder, and more. We recommend that all Maple 2025 users install this update. This update is available throughTools>Check for Updates in Maple, and is also available from theMaple 2025.2 download page, where you can find more details.

At the same time, we have also released an update to MapleSim, which includes enhanced tools for comparing models and analyzing simulation data, and improved runtime performance for MapleSim connectors.You can find more information on theMapleSim 2025.2 download page.

Maplesoft Open Maple Java Programming Interface : Bug Report 1

Subject

-------------------------------------------------------------
FATAL ERROR in native method: Using JNIEnv in non-Java thread
-------------------------------------------------------------

Unexpected and apparently inconsistent threading behaviour.

Perhaps due to default callback semantics ?

Hello Maplesoft Support team,

Environment

* Maple: Maple 2024.2 (build used in our tests) Build ID #18723373
* OS: macOS (Apple Silicon / arm64) Sequoia 15.7.1 32 GB
* uname output from the failing machine: Darwin Mac-Mini.local 24.6.0 Darwin Kernel Version 24.6.0: Mon Aug 11 21:16:30 PDT 2025; root:xnu-11417.140.69.701.11~1/RELEASE_ARM64_T8132 arm64  
* JDK: openjdk 21.0.8 2025-07-15 LTS (Temurin 21.0.8+9)  
 
* Maple Java jars in use:
    * /Library/Frameworks/Maple.framework/Versions/2024/java/jopenmaple.jar
    * /Library/Frameworks/Maple.framework/Versions/2024/java/externalcall.jar
* Native libraries loaded from:
    * /Library/Frameworks/Maple.framework/Versions/2024/bin.APPLE_ARM64_MACOS

Exact java command used to run OpenMapleBug1:

java -Xcheck:jni --enable-native-access=ALL-UNNAMED -Xrs \  
  -cp .:/Library/Frameworks/Maple.framework/Versions/2024/java/jopenmaple.jar:/Library/Frameworks/Maple.framework/Versions/2024/java/externalcall.jar \  
  -Djava.library.path=/Library/Frameworks/Maple.framework/Versions/2024/bin.APPLE_ARM64_MACOS \  
  OpenMapleBug1  

Minimal Java reproducer:

import com.maplesoft.openmaple.*;
import com.maplesoft.externalcall.MapleException;
import java.util.*;

public class OpenMapleBug1
{
    public static void main(String[] args) throws Exception
    {
        String[] mapleArgs = { "java" };

        try
        {
            Engine engine = new Engine(mapleArgs, new EngineCallBacksDefault(), null, null);
            String expr1 = "diff( tan( x )/exp( x ), x );";
            String expr2 = "u_general := sum(B[n] * sin(n*Pi*x/L) * exp(-alpha*(n*Pi/L)^2*t), n=1..infinity);";
            System.out.println("Evaluating: " + expr1);
            engine.evaluate(expr1);
            System.out.println("Evaluating: " + expr2);
            engine.evaluate(expr2);
            System.out.println("Success");
        }
        catch (MapleException e)
        {
            System.out.println("Error: " + e);
            e.printStackTrace();
        }
    }
}

Observed Behaviour

Two calls are made to OpenMaple. The first succeeds:

Evaluating: diff( tan( x )/exp( x ), x );
(1+tan(x)^2)/exp(x)-tan(x)/exp(x)

The second fails (cf. OpenMapleBug2 (which is actually my main line of investigation); also submitted).

Evaluating: u_general := sum(B[n] * sin(n*Pi*x/L) * exp(-alpha*(n*Pi/L)^2*t), n=1..infinity);

FATAL ERROR in native method: Using JNIEnv in non-Java thread
zsh: abort      java -Xcheck:jni --enable-native-access=ALL-UNNAMED -Xrs -cp    OpenMapleBug1

=========================================
Suggested actions for Maplesoft engineers
=========================================

* Reproduce on macOS Apple Silicon using the provided reproducer and command line.
* Check whether this regression is present on other platforms (x86 mac, Linux) and JDK versions.
* Provide a fix for Maple 2024.2 (and Maple 2025.x if applicable).

Thank-you.

Maplesoft Open Maple Java Programming Interface : Bug Report 2

Subject

Native crash (SIGSEGV) in libmaple.dylib when evaluating symbolic sum with indexed coefficients (B[n]) — macOS Apple Silicon — Maple 2024.2

Hello Maplesoft Support team,

I’m reporting a native crash (SIGSEGV) inside libmaple.dylib that occurs when evaluating a symbolic sum containing indexed symbolic coefficients (for example B[n]) via the Maple Java Engine API (jopenmaple). The crash aborts the JVM and produces hs_err_pid34602.log. This is available: email me to receive it.. Rewriting the indexed symbol as a function (for example B(n)) avoids the crash, which suggests a native bug in Maple’s handling of indexed symbolic objects during summation/conversion/evaluation.

Please find environment, exact commands, a minimal reproducer, hs_err_pid34602.log (email), and suggested tests and actions below.

Environment

* Maple: Maple 2024.2 (build used in our tests) Build ID #18723373

* OS: macOS (Apple Silicon / arm64) Sequoia 15.7.1 32 GB
    * uname output from the failing machine: Darwin Mac-Mini.local 24.6.0 Darwin Kernel Version 24.6.0: Mon Aug 11 21:16:30 PDT 2025; root:xnu-11417.140.69.701.11~1/RELEASE_ARM64_T8132 arm64  

JDK: openjdk 21.0.8 2025-07-15 LTS
OpenJDK Runtime Environment Temurin-21.0.8+9 (build 21.0.8+9-LTS)
OpenJDK 64-Bit Server VM Temurin-21.0.8+9 (build 21.0.8+9-LTS, mixed mode, sharing)

Maple Java jars in use:
    * /Library/Frameworks/Maple.framework/Versions/2024/java/jopenmaple.jar
    * /Library/Frameworks/Maple.framework/Versions/2024/java/externalcall.jar

Native libraries loaded from:
    * /Library/Frameworks/Maple.framework/Versions/2024/bin.APPLE_ARM64_MACOS

Exact java command used to run MinimalSumTest2:

java -Xcheck:jni --enable-native-access=ALL-UNNAMED -Xrs \  
  -cp .:/Library/Frameworks/Maple.framework/Versions/2024/java/jopenmaple.jar:/Library/Frameworks/Maple.framework/Versions/2024/java/externalcall.jar \  

  -Djava.library.path=/Library/Frameworks/Maple.framework/Versions/2024/bin.APPLE_ARM64_MACOS \  
  MinimalSumTest2  

Note: Adding -Xss100M did not make any apparent difference.

Minimal Java reproducer (attach as MinimalSumTest2.java):

// MinimalSumTest2.java

public class MinimalSumTest2
{
    public static void main(String[] args)
    {
        String[] mapleArgs = new String[] { "java" }; // some versions require this
        com.maplesoft.openmaple.Engine engine = null;
        try
        {
            System.out.println("Creating Engine...");
            engine = new com.maplesoft.openmaple.Engine(
                mapleArgs,
                new com.maplesoft.openmaple.EngineCallBacksDefault(),
                null,
                null
            );

            // assign with ":" to suppress printing (should avoid large marshalled result)
            String assignSuppressed = "u_test := sum(B[n]*sin(n*Pi*x/L)*exp(-alpha*(n*Pi/L)^2*t), n=1..100):";
            System.out.println("Evaluating (suppressed): " + assignSuppressed);
            engine.evaluate(assignSuppressed);
            System.out.println("Assigned (suppressed) OK");

            System.out.println("Done.");
        } catch (Throwable t)
        {
            System.err.println("Unexpected throwable (may be native crash):");
            t.printStackTrace();
            // If a SIGSEGV occurs, JVM may abort before this runs; look for hs_err_pid*.log
        } finally
        {
            // no stop() method available
        }
    }

}

Observed Behavior

* JVM aborts with SIGSEGV in native code (libmaple.dylib). The hs_err log shows frames in:
    * libmaple.dylib : errorJmp(_ThreadLocalData*) / extIsNumeric
    * libjopenmaple.jnilib : newAlgebraic / Java_com_maplesoft_openmaple_Engine_evaluate

* Using B(n) (function form) instead of B[n] or substituting numeric coefficients avoids the crash.

Attached crash evidence

* hs_err_pid34602.log is available: email me to receive it.
* Please use the full hs_err file for diagnostics; it contains native frames, thread state and loaded libraries.

Suggested quick tests to run (please include pass/fail for each):

1. Replace indexed form with function form:
    * B := n -> b^n: u := sum(B(n)*sin(...), n=1..100): — does this crash?
2. Reduce N (small upper bound):
    * sum(B[n]*sin(...), n=1..10): — crash or not?
3. Use a table in place of indexed name: Btab := table():  
4. for k from 1 to 100 do Btab[k] := b || k od:  
5. sum(Btab[n]*sin(...), n=1..100):  
6. Pre-substitute a simple expression for B[n] before summing:
    * sum(subs(B[n]=1/n, B[n]*sin(...)), n=1..100):
7. Try same reproducer on a non-Apple-Silicon mac or Linux (if available) and with JDK 17.

Suggested cause (based on hs_err frames):

* Crash appears to occur in native routines that check numeric-ness / build algebraic objects (functions such as extIsNumeric and newAlgebraic). This indicates a bug in Maple’s native handling/conversion of indexed symbolic objects in sum/convert/evaluate code paths.

Temporary workarounds
* Use function form: B := n -> ... and B(n) in sums rather than B[n].
* Substitute definitions for B[n] before summation (client-side or via subs) so that the sum does not carry an indexed symbolic name into the conversion step.
* Build sums client-side (Java/Clojure) or use explicit truncated numeric sums when possible.

Files to attach (recommended)
* hs_err_pid*.log (full file)
* MinimalSumTest.java (the Java reproducer above)
* README_cmd.txt (contains exact javac and java commands used)
* java_version.txt (output of java --version)
* maplesoft_jars_list.txt (paths to jopenmaple.jar and externalcall.jar used)

=========================================

Suggested actions for Maplesoft engineers
=========================================

* Email me to receive the error log file produced for the crash.
* Reproduce on macOS Apple Silicon using the provided reproducer and command line.
* Inspect handling of indexed name objects inside summation/conversion code paths — particularly code interacting with extIsNumeric, newAlgebraic, and conversion routines invoked by Engine.evaluate.
* Check whether this regression is present on other platforms (x86 mac, Linux) and JDK versions.
* Provide either a patch that prevents this conversion path from dereferencing invalid memory, or return a safe Maple-level error for unsupported symbolic forms.

Thank-you.

I was honored to give a talk about the MRB constant at the INTERNATIONAL 10th USBILIM APPLIED SCIENCES.

If you're unfamiliar with the MRB constant, this is a solid introduction to it.

(28) INTRODUCING THE MRB CONSTANT: CONVERGENCE, GEOMETRY, AND OPEN PROBLEMS

[Edit: a general procedure based on these ideas is givenbelow.]

Maple'sisolve can solve some but not all of the quadratic equations in two variables describing the conic sections. Here I show that by transforming the equations, Maple can then solve these missing cases.

Download DiophantineConics2.mw

There is still time to register for Maple Conference 2025, which takes place November 5-7, 2025.

The free registration includes access to three full days of presentations from Maplesoft product directors and developers, two distinguished keynote speakers, contributed talks by Maple users, and opportunities to network with fellow users, researchers, and Maplesoft staff.

The final day of the conference will feature three in-depth workshops presented by the R&D team. You'll get hands-on experience with creating professional documents in Maple, learn how to solve various differential equations more effectively using Maple's numerical solvers, and explore the power of the Maple programming language while solving interesting puzzles.

Access to the workshops is included with the free conference registration.

We hope to see you there!

Kaska Kowalska
Contributed Program Co-chair

It's possible to carve a hole through a unit cube, without splitting it into pieces, so that another unit cube can pass through that hole.  This is know as thePrince Rupert problem and was first analyzed by John Wallis, a contemporary of Isaac Newton.  Here's what the result looks like:

If your computer can play audio, have a look at  Ruperts Cube with music!

Here is the worksheet that produced the cube and the animation: ruperts-cube.mw

Hi again everybody,

Made some easy Maple code to find some special prime numbers.

Namely, positive prmie numbers p 
such that p, p+2, and p+6 are all prime numbers

see prime_triples_p_p_and_2__p_and_6.mw

prime_triples_p_p_and_2__p_and_6.pdf

for your viewing pleasure

Have a good day.

Matthew

The concept of an ode that has a function + integration variable as its solution is similar to that of a pde.

A pde (with two variables as example here) that has a function as its solution + function integration variableIn ode, the shape of the solution curve is determined by the integration variable, and in a pde, the shape of the solution surface is determined by the function integration variable.

Download intergatie_functie_variabele_pde_onderzoek-engesle_versie.mw

Imagine standing 365 metres above Toronto on the CN Tower’s EdgeWalk and throwing a baseball. Could you actually land it on third base at Rogers Centre, about 263 metres away?

Sportsnet raised this question, and we decided to put it to the test in Maple Learn, check outthis document to see the answer.

Also take a look at the Sportsnetvideo on the problem, to see why the answer may not be obvious.

In the Maple Learn document, you can adjust the initial speed and angle at which to throw the ball and then visualize its trajectory (without having to throw as hard as Addison Barger).

I was surprised that even in the simplified projectile motion model, that neglects air resistance, AND assuming I could throw at 60mph (a questionable assumption to say the least) I wouldn’t be able to hit the base myself.

I then used Maple to build a more realistic model that would account for air resistance. The equations below model the position of the ball, where y(0) = h₀ is the initial height of 365m and v₀ is the initial speed.

local h0, m, d, rho, g:h0 := 365:m := 0.145:d := 0.072:rho := 1.225:g := 9.81:local eqns, ics:eqns := diff(x(t),t) = u(t),     diff(y(t), t) = v(t),     diff(u(t), t)= -Pi/16 * d^2 * rho/m * sqrt(u(t)^2 + v(t)^2) * u(t),     diff(v(t), t)= - g - Pi/16 * d^2 * rho/m * sqrt(u(t)^2 + v(t)^2) * v(t):ics := x(0) = 0, y(0)=h0, u(0) = v_initial*cos(theta_initial), v(0) = v_initial * sin(theta_initial):local ans, xpos, ypos:ans := dsolve([eqns, ics], numeric, output=listprocedure):xpos := subs(ans, x(t));ypos := subs(ans, y(t));

In the Maple Learn document, you can visualize the difference between the models by comparing the trajectories. The trajectory from the simple model is shown in blue, and the trajectory after accounting for air resistance is modelled in red.

Accounting for air resistance, I’m no longer convinced even Addison Barger could accomplish this challenge.

Check out the Maple Learn document to try for yourself!

Thefull program for Maple Conference 2025 is now available. 

The agenda includes two full days of keynote speakers, presentations from Maplesoft product directors and developers, and contributed talks by Maple users all around the world. There will be opportunities to network with fellow users, researchers, and Maplesoft staff.

The final day of the conference will include three in-depth workshops presented by the R&D team.
The workshops will explore how to:

• Create papers and reports in Maple
• Solve various differential equations more effectively using Maple's numerical solvers
• SolveAdvent of Code challenges using Maple

Access to the workshops is included with the free conference registration.

We hope to see you there!

Kaska Kowalska
Program Co-chair

This post presents a work I did to answer this recent question by @AHSAN.

I believe that the two procedures I developed could be of interest to Mapleprimes members. Here they are in their most recent forms. However, I think they can still be improved and completed, and I am open to your suggestions for developing them further in this direction.

BarGraph_2_Categories.mw
Illustration


BarGraph_3_Categories.mw
Illustration

 

In addition to the discussion on the desirability of having % available as a unit, I have a need to develop quantities that numerically have a unit of 1, such as per unit (pu), with pu:=1, and 1 pu = 100%. It is straightforward to define custom unit pu. However, the problem is that I end up getting numbers such as 16.60% pu (see below, should be one unit or the other, pu or %, not both):

Curiously, if I click on the pu designation at variable X__dppv , Maple Flow removes the pu duplication and somehow knows that % is the intended unit:

Percent_Ex.zip

For a document that extensively uses per unit and % quantities, it is a lot of extra work to have to evaluate the decimal quantities first, then changing to % in the context menu, and then manually correcting all of the display issues with % and pu conflicts. Maple Flow does not seem to "remember" the result of the manual unit selection described above between file editing sessions. It also does not remember several other things related to formatting, container placement and spacing, column vectors not retaining a manually adjusted width, and section layout, but those are different issues. 

I have noticed other examples of not remembering the correct units. For example, I have calculations where Maple Flow automatically returned a unit of 1/S in an initial calculation evaluation and I changed this in the context menu to ohms. Similar to the above discussion, upon re-opening the file, 1/S units appear. I cannot get that issue to consistently repeat, so it is not in the example Maple Flow document attached to this post, but the end result is the same - lots of re-formatting of the document from editing session to editing session.

It would be nice if Maple Flow could recognize units that are numerically 1 so that they can be defined for display/documentation, added as necessary, but the result computed such that it is multiplication by 1 with no extra unit added. For example, enter 0.166 pu such that it evaluates to 0.166, with the option of then displaying as a percentage or re-displaying as per unit using the context menu. It would also be nice if Maple Flow could consistently remember the last retained unit used in an editing session as well as all document formatting. 

Thanks