I have finally managed to get it working thanks to the help from support and users in the forum.

The solution is as mentioned before by packing the code as a workbook package, and upload it to Maple Cloud as a package.

There was one more obstacle when trying to use the package - one cannot install packages from Maple Cloud via Google Chrome or a different webbrowser. Instead it is necessary to use the link from within Maple - Tools - Maple Cloud.

After the installation of the package, it is no longer necessary to refer to a library in the startup code anymore.

I have received a reply from Maplesoft Support which I would like to post here uncommented.

Re_24912_Maple_-_How_are_you_.pdf

cloud_pack.zip

In Mathcad percent are handled as an algebraic operator, but that would be a problem because Maple already has a function associated with that. Mathcad does not have anything for "per thousand" (promille).

In my opinion this should be handled as a predefined unit in Maple.

On the wishlist to the developers?

@acer 

Ok, thanks for the reply anyway. I'll wait and see what Maple support comes up with.

But if we put the workbook solution aside first, is there a solution where I can upload the .mla file to Maple cloud as a package, and use that from there?

Here's one example that uses a special package.

https://maple.cloud/#group=packages

https://maple.cloud/app/6554607883386880/AISC+Shapes+Database+v14.1_0210_Jocelyn_Old+Maple+%282017%29+qa+test+

@acer 

I have attached the example as a zip file, probably you can make something out of that. In addition I have also opened a formal support case on that issue yesterday, so I guess someone from Maplesoft will have a look at that in the near future.

Did a quick search on Maple Cloud also, and tried to find a public example including a workbook. Didn't find anything - though I have to admit that I skipped the ones with asian (chinese ?) characters in titles...

@acer 

Thanks, here's the upload once again in a zip file.

Tre_Materialegenskaper.zip

Here's the Maple Workbook in question.

Tre_Materialegenskaper.maple

I think the answer might be to save the file as a Maple Workbook.

At least I am getting the same errors as in the Maple Cloud when working with the workbook format.

The question is - how do I use an attached Maple repository file (.mla) in the workbook?

The repository path is "this:///NODETre.mla" - so how I attach that?

libname := "this://", libname

gives a Maple Error regarding Kernel connection

@tomleslie 

Try to read once again what I have written.

The differences in rounding of halv integers - and that is really the only thing where implementations are different - are more or less known.

When I wrote that one can't always trust the last digit, that doesn't mean I don't trust the implementation of the rounding in the different software packages. It means that I don't actually know which kind of rounding (up or down) the different software packages use.

I could even extend that further to human languages. In German we have two words for that - "aufrunden" (round up) and "abrunden" (round down). In Norwegian we usually just use "avrunde" which doesn't give any indications about which way it is done.

So in my personal point of view we still stand where we started.

• Maple does at the moment not have any function to round numbers to a specific number of digits.
• It should have one. There are situations where simply defining how many digits are shown in a result is not enough (see using numbers for indexing of tables, or output to Math Containers, etc.)

@acer

Apparently it is possible if the code is run during startup or through "Execute entire worksheet".

Startupcode.mw

@acer 

No, not that I am aware of.

Tre_Materialegenskaper.mw

@acer 

Thanks a lot, that was very helpful.

@tomleslie 

Yes, the rnd2 function seems to work as I would expect from a rounding function, and like it is implemented in the software I named previously.

@tomleslie 

The question regarding halv-integers is indeed a bit strange, and the rounding behaviour of Python is indeed a bit unexpected I have to admit.

But that is common knowledge, the last digit is the one you can't always trust.

As my teacher in steel at university said.

In steel you calculate 3 digits and hope that 2 are correct. In concrete you calculate 2 digits and hope that 1 is correct. And in soil mechanics you calculate 1 digit and hope that the sign is correct.

@Christopher2222 

Well, I've filed that as a product suggestion - and it would be nice if Maplesoft took it on their list for future implementation.

For the time being we'll go around the issue somehow.