Dear All,

I'm wondering if there is a simple way to define, given a "module" that protects "e" as a global, to allow the user to write e[0], e[1], e[2], e[3], e[inf] such that I calculate with e[4] but I display e[inf]. And if I type in e[inf], it translates behind the curtain of the module e[inf] into e[4] such that I keep my indexes 0-4 for the handling of my entities.

I hope I made myself understood ;)

I was woundering if there is some way with the standard "TypeSetting Module" ?

Sincerely

Ivar 

Derar All

I'm trying ot adapt some old Maple V code to a new Maple 2022 Module/Package and have an issue understanding if the "ModuleLoad" process does really run automatically with the "> with(TST); " command ?
the "> restart;" runs the ModuleUnload though, but for me the ModuleLoad does not seem to run when I expect it to !?

Sincerely

Ivar

Any comment appreciated ?
the test code :

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

Tst := module()
  local ModuleLoad, ModuleUnload;
  export MyProc;
  global AAA;
  option package;
  ModuleLoad := proc()
      global AAA;
      AAA := 1;
      print("Hello Module");
  end proc;
  ModuleUnload := proc()
      print("Bye Module");
  end proc;
  MyProc := proc()
      print("Hello from Core");
  end proc;
end module ;

Dear All

I wanted to use the ColorTools of Maple to study the conversions between color spaces and different color definitions, but I find the tool very limited and rather confusing.

My main issue is to understand really which "RGB" definition is used ?
I assume it's a "RGB" = sRGB from Adobe(r) that is then translate to CIE 1931 values XYZ, xyz, Lab and more recent Luv values, all based on D65 illumination ? This must be really better defined in the help !!!

This is really not clearly stated as today "RGB" means mostly Adobe 1998 RGB, the larger gamut color space from Adobe and not the older and more reduces sRGB.

Color Space and Color understanding is subtile and require really a clear differentiation about illumination, color mappings, input, and output devices, and more ...

This issue applies to the "HSV" and "CMYK" these are all HW associated devices, and at least the standard illumination considered here must be defined, from my undersanding (and within the CIE definitions there are at least half a dozen of illumination standards, the most common, for me, are the D50, & D65).

It would be great if the ColorTables allowed us to really study colors in a correct way and following more the appraoch of i.e. "Digital Color Management, ENCODING SOLUTIONS" by Edward J. Giorgianni and Thomas E. Madden, Wiley (2.Ed, 2008) or some of the other serious book on color management.

Thanks in advance for your replies

Sincerely

Ivar

Hi MaplePrimes Web managers

I suspect you have forgotten to update the lists for MapleSim "2017" you seem to stop at "MapleSim 2016", while I hear from your local office that MapleSim 2018 is "just around the corner" ...
It would make it easier to sort the issues for the last version, no ?

Thanks for your support
Sincerely
Ivar

Dear All

I seldom need support, Maple/MapleSim usually runs OK, but here I'm stuck with MapleSim 2017 I'm modelling some thermal fluid properties and each time I make a sub-system I get two errors:

1) the entries (and exit variables) "rho, Cp, Cv, lambda, and nu" of my models are set to default "1" instead of my expected value the names of my fluid-parameter items. I must rename them by hand to be able to solve my model, why not a link to the fluid parameter node ?

2) I get a pressure p (or is it a "rho"?) issue: "Cannot resolve `Main.Block1.p`; there is no `p` in variable `Main.Block1`" when I create a sub-system I call here Block1 and my model does not solve if I make any "sub-systems", and I cannot find out what to do, is this an initial value issue ? the error message could be more helpful ;)

Any clues how to get around this ?

Thnaks in avance

Sincerely

Ivar