Hi acer


The presence of the in the main scope is normal: I want the program to be executed for increasing values of the constant M_tot.

If I understand you are suggesting that I should put all the procedure body outside the for ... end do, and let only the calling inside? This sounds bright! I'm going to change it.


For the number of global variables... I have a lot of numerical parameter, what else could I do (the idea of passing each global parameter to each procedure seemed to cumbersome).
Actually, most of my procedures don't change the global variables value, but what happened is that without explicitly use global ... inside the procedures' bodies , the procedures made their own version of the variables (symbolic), put it in the formulae, so that I wasn't able to simplify them in the main scope. This is why I explicitly pass all the global variables.

If you have remarks I'll pay attention to them

Thanks

S.
 

Hi acer


The presence of the in the main scope is normal: I want the program to be executed for increasing values of the constant M_tot.

If I understand you are suggesting that I should put all the procedure body outside the for ... end do, and let only the calling inside? This sounds bright! I'm going to change it.


For the number of global variables... I have a lot of numerical parameter, what else could I do (the idea of passing each global parameter to each procedure seemed to cumbersome).
Actually, most of my procedures don't change the global variables value, but what happened is that without explicitly use global ... inside the procedures' bodies , the procedures made their own version of the variables (symbolic), put it in the formulae, so that I wasn't able to simplify them in the main scope. This is why I explicitly pass all the global variables.

If you have remarks I'll pay attention to them

Thanks

S.
 

Thanks Acer, this was exactly the problem, a local M in a procedure... when you have dozens of them is easy to forget a global declaration..!

S.

Thanks Acer, this was exactly the problem, a local M in a procedure... when you have dozens of them is easy to forget a global declaration..!

S.

Hi acer

the 2nd of yours rows:

eval(expr,M=1);

is exactly what I did in my 3rd line, and for you eval does work even if the Int is inert. But not for me

Hi acer

the 2nd of yours rows:

eval(expr,M=1);

is exactly what I did in my 3rd line, and for you eval does work even if the Int is inert. But not for me

Hi Robert

thanks for your reply. But this imply that I'd change the values on the list v you introduced for each plot ( = a lot of time expensive work)

Hi Robert

thanks for your reply. But this imply that I'd change the values on the list v you introduced for each plot ( = a lot of time expensive work)

Hi

The code is very long.

Isn't there a way to tell to maple what kind of numerical format it should use for the axis, whatever the input could be?

Thanks

S.