@acer 

Thanks, will try this and see if it works on my main setup.

@acer 

You are right. I had export there instead of local of the module variables. What I did only works if the variables have export on them.

I see now you used kernelopts(opaquemodules=false):  but this requires one to pass each individual variable name to be accessed if I want to keep the module variables local. I will try it and see.

the debugger ofcourse.

If Maple did not have a debugger, I would not even use Maple.

Even though the debugger is hard to use (line mode, no nice grapical interface like Matlab's debugger) it is for me indispensable. 

Too bad Maplesoft seems to have abandoned making any improvements to it any more.

Trace shows that `is/solve` fail, but could not find why.

Here is another strange result from coulditbe (cousin of is ?)

coulditbe(cos(x)=sqrt(1-sin(x)^2));

   #true

coulditbe(cos(x)=sqrt(1-sin(x)^2)) assuming x::real;

   #FAIL

@mmcdara 

I tend to use patmatch more. Main uses for me is to check if an ode has certain form to find what type it is.

I find pattern matching easier to use and more intuitive. After all, alot of math is about recognizing patterns and transformation.  But in Maple, pattern matching is somewhat more limited than it could be. But still, one can do alot with it.

@janhardo 

But the way you used `Or` is the same as using alternatives {  }

type(1+"s",`Or`(`&+`(integer,string),`&+`(string,integer) ) )

is same as

type(1+"s",{ `&+`(integer,string),`&+`(string,integer) } )

I was trying to use `Or` to tell type something like

type(1+"s", `&+`( `Or`(integer,string)))

Which ofcourse does not work. i.e. a way to avoid having to tell it the order.

So your `Or` at top level or using {} is same thing. One is forced to enumerate all possibles cases. 

With Pattern matching this is not needed.

@mmcdara 

          "stuff but it seems impossible to go further."

You could always step through the code in the debugger. You could open a text file on the side and using the debugger get the listing of each step or proc from the debugger, and stitch it into the text file you have open as you step through. Eventually, you can get all the code this way.

A := Statistics:-Sample('Beta'(3, 5), 10^5):
stopat(Statistics:-Mean);
Statistics:-Mean(A);

Here is some of the code processing the above

Statistics:-Mean:-ModuleApply:
   1*  try
       catch :
           ...
       end try

DBG> showstat

Statistics:-Mean:-ModuleApply := proc(X::{algebraic, {array, list, rtable, DataFrame, DataSeries}})
   1*! try
   2       return Quantities:-Dispatch('Statistics:-Mean',X,[NULL],_rest)
       catch :
   3       error
       end try
end proc

Statistics:-Quantities:-Dispatch := proc(qname::name, X::{algebraic, {array, list, rtable, DataFrame, DataSeries}}, parms::list)
   1 ! if type(X,'{array, list, rtable, DataFrame, DataSeries}') then
   2       return GetValueTab[':-DescriptiveStatistics'](qname,X,parms,_rest)
       else
   3       return GetValueTab[':-RandomVariables'](qname,X,parms,_rest)
       end if
end proc

Statistics:-Quantities:-Dispatch:
   2       return GetValueTab[':-DescriptiveStatistics'](qname,X,parms,_rest)

Statistics:-Quantities:-GetValueTab[DescriptiveStatistics] := proc(qname::name, X::{array, list, rtable, DataFrame, DataSeries}, parms::list, {matrixbycolumn::truefalse := true, weights::{array, list, rtable, DataFrame, DataSeries} := NULL})
local x, xx, w, ww, mbc_marker, answ;
   1   answ := Statistics:-DescriptiveStatistics:-CreateOutputRecord();
   2 ! if matrixbycolumn then
   3       mbc_marker := NULL
       else
   4       mbc_marker := 1
       end if;
   5   x, xx := PreProcessData(X,mbc_marker,':-reconstruct' = ':-summarize');
   6   if weights = NULL then
   7       Statistics:-DescriptiveStatistics:-GetValue(qname,[x, op(parms)],
             answ,_options['matrixbycolumn'],_rest)
       else
   8       w, ww := PreProcessData(weights,mbc_marker,':-reconstruct' = [':-
             summarize', xx]);
   9       Statistics:-DescriptiveStatistics:-GetValue(qname,[x, op(parms)],
             answ,_options['matrixbycolumn'],':-weights' = w,_rest)
       end if;
  10   return Statistics:-DescriptiveStatistics:-BuildOutput(answ,':-
         reconstruct' = xx)
end proc


Statistics:-Quantities:-GetValueTab[DescriptiveStatistics]:
   7       Statistics:-DescriptiveStatistics:-GetValue(qname,[x, op(parms)],
             answ,_options['matrixbycolumn'],_rest)



Statistics:-DescriptiveStatistics:-GetValue := proc(quantity::name, plist::list, answ::record, {matrixbycolumn::truefalse := true, weights::{array, list, rtable, DataFrame, DataSeries} := Vector(0)})
local columns, dtype, i, m, parms, rest, rows, weightsset, V;
   1 ! if type(weights,{array, list}) then
   2       weightsset := Vector(weights)
       else
   3       weightsset := weights
       end if;
   4   if type(plist[1],':-list'(':-Vector')) then
   5       parms := plist
       elif type(plist[1],{'array', 'list'}) then
   6       parms := subsop(1 = Array(plist[1]),plist)
       elif type(plist[1],':-rtable') and rtable_num_dims(plist[1]) = 2
         and matrixbycolumn then
   7       m := plist[1];
   8       rows := upperbound(m,1)-lowerbound(m,1)+1;
   9       columns := upperbound(m,2)-lowerbound(m,2)+1;
  10       rest := op(2 .. (NULL),plist), _rest, ':-weights' = weightsset;
  11       if convert(quantity,':-`global`') = ':-Mode' then
  12           dtype := NULL
           else
  13           dtype := ':-datatype = :-float'
           end if;
  14       answ:-value := Vector[':-row'](columns,dtype);
  15       if [rtable_options(m,':-storage',':-order')] = [':-rectangular
             ', ':-Fortran_order'] then
  16           for i to columns do
  17               V := ArrayTools:-Alias(m,(i-1)*rows,[rows]);
  18               answ:-value[i] := GetValueWorker(quantity,V,rest)
               end do
           else
  19           for i to columns do
  20               V := m[(NULL) .. (NULL),i-lowerbound(m,2)+1];
  21               answ:-value[i] := GetValueWorker(quantity,V,rest)
               end do
           end if;
  22       return
       else
  23       parms := plist
       end if;
  24   answ:-value := GetValueWorker(quantity,op(parms),_rest,':-weights' = 
         weightsset)
end proc

And so on...

It seems Statistics:-Mean is routed via some dispatch mechanism called Quantities:-Dispatch to the actual code of the implementation. Hard to see how to access and see that dispatch code.

Download mean_print.mw

You can not integrate    z(x)*y'(x)  or z(x)*y''(x) if z(x) is not known.

How would you do this by hand? Even if you use integration by parts, since z'(x) is not known.

If you know what z(x) is, then it should be possible.

Download int_feb_4_2025.mw

You could check these maybe they will help

Make-Real-And-Imaginary-Part-Separate

Get-The-Real-And-Imaginary-Part-Of-A

How-I-Do-To-Obtain-The-Real-Part-And

How-To-Extract-Real-And-Imaginary-Using

Your 2D code does not seem to be valid Maple code.

I convert it to 1D input and this is what Maple gave me

0 < solve(%, Cv)*Assuming*d, 0 < Am, 0 < R0er, 0 < Clm, 0 < s1, 0 < Ce, 0 < s2, 0 < Clr, 0 < l, 0 < g1, 0 < g2, 0 < Aer, 0 < Rer;

This is your last line

First of all, it is assuming and not Assuming. You also have multiplication signs in wrong places.

Use 1D Maple language instead of the 2D one.

Did not look at your work, but try moving eveything to one side first and then call simplify. Like this

Download one_side.mw

@salim-barzani 

               i didn't delete it i don't know why they do that

Maybe then forum manager deleted it. Any way, here is my answer I was going to post. I was going to delete the worksheet. I do not if this is what you wanted. I assumed you wanted each b[i,j] be replaced by (k[i] - k[j] + (k[i] - k[j])^2)/(k[i] - k[j])
 

Download fix_b.mw

@salim-barzani 

Why your questions gets deleted after posting? You posted this question not long ago and I was about to give you an answer but it is gone. Do you delete them or the forum manager deletes them? It seems it was a good question.

@mmcdara 

Sure. After the fact, it seems to make sense that Set() should be used only after Setup().

But one would think help will say that. Looking at the help page for Set() there is no mention at all of this.

It will also be nice if calling Set() before calling Setup() would issue a warning to the user to alert them. This would have saved me 2 days of work trying to find what is wrong and why I was not seeing output on the screen.

A simple warning message is all what was needed.

If I was the programmer who wrote Grid, that is what I would have done. I am sure inside the Grid package, it knows if Setup() was called or not before. A simple flag internal and private to the package would do the job.

#somewhere inside Grid package

....
local SETUP_WAS_CALLED::truefalse:=false: #this flag will be set to true by Setup()
.....
export Set:=proc(....)

      if  not SETUP_WAS_CALLED then
           print("WARNING: You are calling Set() before Setup().");
     fi;
....
end proc;

Update 1/29/2025

An important note for those who might read this later:  Set() works if no Setup() is called after it. i.e. using the default numnodes, which for my pc is

Grid:-NumNodes()

           24

Set() does not work if called before doing explicit Setup("local",numnodes=24).  So to be safe, do not call Setup() at all, unless you want for some reason to change numnodes from default value.

So in summary

# OK
Set(....)   


#BAD
Set(...)
Setup(....)   

#OK
Setup(....)   
Set(...)

Using Maple 2024.2 on windows. The above could change in future versions of Maple.