@Carl Love Thanks Carl. I didn't mean it exactly that way, but I can use your ideas for other purposes. I m actually quite satisfied with how I have got now.

Erik

@Kitonum Thank you! Nice zip-function to combine the two lists into one and then manipulate this using a map command. I guess this is the most straightforward way to do it without having to use procedures, right? I did rewrite it a bit for my own situation to make it s bit more readable, though:

restart;
with(Gym);
R := [163, 163, 163, 107, 107, 107, 51];
V := [15, 45, 75, 15, 45, 75, 45];
W := zip((x, y) -> [x, y], R, V);
X := map(t -> t[1]*Cos(t[2]), W);
Y := map(t -> t[1]*Sin(t[2]), W);

NB! That way I can easily access X and Y. I have used a custom package to deal with cosine and sine when angles given in degrees.

Regards,

Erik

@Carl Love 

Yes something like that, but the name quotes behaves in a very strange way in my opinion. I was not able to mix it with the rest of the line - to get what is inside the red rectangle. Apparently Maple can't make an output like in a typical programming language, where you can mix text and symbols with values of variables... Anyway, I am pretty happy I got the right side.

@Markiyan Hirnyk 

Not entirely satisfying. How do I write something without having it interpreted in the same line? Quotes around it doesn't work ...

Erik

Great! I like the latter way. Then the part on the right side of the equality sign is fixed. How do I write f₀ ' in front of it, without having Maple evaluate it as d/dxf₀(x) ? (Probably basic again, sorry)

Thanks,

Erik

Great! Thanks to both of you.

Regards,

Erik

@Carl Love Thank you for the reminder. Maybe it is a bug that the cursor doesn't stop at the line, where the error occurs - as it did in Maple 16, you say?

Interesting with the Modules. I haven't been working with modules earlier. I understand it as a kind of collection of procedures created for a special purpose, so it makes a whole and easier to work with.

Erik

@Carl Love Thank you for the reminder. Maybe it is a bug that the cursor doesn't stop at the line, where the error occurs - as it did in Maple 16, you say?

Interesting with the Modules. I haven't been working with modules earlier. I understand it as a kind of collection of procedures created for a special purpose, so it makes a whole and easier to work with.

Erik

Thanks a lot, Carl. I will look at it soon. So far I have been looking at other corners of my program ...

Thanks a lot, Carl. I will look at it soon. So far I have been looking at other corners of my program ...

@Alejandro Jakubi I agreee with you. Firstly one need to realize of course that whatever Maplesoft provide of documentation it will never be possible to fully grasp and fully master all the functionality of such a big program. When that's said, Maplesoft should try to make the program as easy as possible to use for both advanced users as well as people who are new to it. Many of the list commands are what I will regard as being on an intermediate or advanced level. You will probably not be able to mix all those clever tricks in one line to accomplish what you want, if you are new to Maple. Then you will be looking for simpler commands. It's here I am missing some commands in the ListTools package.

It would be great if Maplesoft would make some pages in the documentation, where they are focusing on some important key issues. I remember for at long time being confused on the differences between rtables, arrays, lists, vectors, sets, ... A focus on the differences would be great. As you mention: The evaluation contexts. There are a whole Zoo of those commands evalf, eval, evalb, evalhf, evalc, ... What is the overall idea of those commands and the context in which they are being used. In the Help menu under Table of Contents tab, I found a folder names "Tasks > Lists", but it had little content. The same with "Tasks < Evaluating.

When I get stuck in the Help menu trying to figure out something, I quite often write the command and a few other words in Google to seach for it on the Web. Often I end up in Mapleprimes or in the Online help menu for Maple, which is great. But I am missing pages, where Maple are handling key issues or handling similar commands 'under one hat'. I think many beginners in Maple are looking for the logic behind the concepts. When that is understood, much is accomplished. 

Alejandro, great with the list in Maple 401, as you mention: Commands and more you should know as an advanced user.

Erik   

Thanks a lot Markiyan! Actually I succeded myself doing it too in another way. I am proud of myself now ... finally, hehe. Here it is:

Here is the worksheet: Grouped_data_in_Hist.mw

Erik

Thanks a lot Markiyan! Actually I succeded myself doing it too in another way. I am proud of myself now ... finally, hehe. Here it is:

Here is the worksheet: Grouped_data_in_Hist.mw

Erik

@Alejandro Jakubi Right. It could be a suggestion to implement 'not in' to make it easier and making it more idiomatic. I think I remember that I got confused by the fact that say '2 in A' is not a boolean value but just an expression. One need to put it inside an evalb or is command to decide the boolean value of this expression. Then I thought it would give no meaning to put a parenthesis around and negate ... anyway I need to learn the syntax and overall logic better. Anyway more ways to do the same will definitely help the user ...

I actually use the Help menu a lot and find it quite usable. Usually I run down to the examples to figure things out. Then if I need more, I go to the description higher on the page. The 'Sets and List' page is however inadequate in my view - for such an important technique of handling lists. There are some useful eamples for sure, but also some perculiar examples, which you will never use. Many important and often used examples are not presented. The many different commands from several areas makes it difficult to get to grips with.

I think all the new possibilities with special signs `, ', op, $, ~, etc. are great, because it makes it possible to write something very compact. Sometimes you can write something in one line, which would take maybe 10 lines with ordinary programming technique. Especially the `if`operator is great. One can branch out in several possibilities without having to write an ordinary if sentence. But when something is very compact it is also harder to grasp in the beginning. That's why I request a few more basic commands in the ListTools package, besides a better documentation for lists!

Erik 

Thanks for the new ways to do the same. However I was actually placing this as a Post rather than a Question, since I hoped for a discussion about new commands in the ListTools package and a discussion if the ways to manipulate lists are sufficiently well-documented for new users in the Help menu. Since I get no response on these issues, I guess you think it is fine already.

I regard the handling of lists - as well as vectors and tables - a key issue to really get into Maple and how it works.

Erik