hpc-carpentry / hpc-chapel Goto Github PK

We've received the following feedback by email, so I'm passing it along. I let the OP know so they can chime in or follow the conversation here. Thanks!

Hello,

I have been working through your tutorial and was having some issues on the "Domains and single-locale data parallelism" section. When I use the code for the Distributed Domains, it gives me errors regarding the line:

a = "%i".format(a.locale.id) + '-' + here.name + '-' + here.maxTaskPar + ' ';

I believe something may have changed with how strings work with formatting?

No rush or pressure about this. I just wanted to let you know in case you weren't aware. It is also possible something is wrong on my end.

Thank you,

The first lesson, Intro, has as its objective "Write and execute our first chapel program." As written, this requires either a local installation of Chapel or access to a remote resource that has Chapel installed. Neither of these prereqs is covered in the Setup, or in the lesson itself.

Recommend pointing learners to Chapel Releases and the Quickstart Instructions.

The last section of the first lesson is confusing -- written almost as an exercise, but it's probably a "teaser" for what the course might accomplish. In doing so, it introduces a bevy of new concepts, which is not great from a pedagogical standpoint.

Recommend removing the "Case Study" section (line 98 on) from 01-intro.md.

The --fast compiler flag is introduced in the very first episode - it should be moved to a later lesson where performance is talked about.

It would be good to update the examples to make sure they work with the latest Chapel release. One way to ensure that they keep working is to add the examples to Chapel's tests.

We should add something for these sections (Why are we teaching Chapel?/Some considerations when installing Chapel/etc.)

Chapel syntax highlighting should work in Jekyll using pygments, as described here.

We should be able to enable syntax highlighting with:

{% highlight chapel %}
// chapel code here
{% endhighlight %}

A lot of the examples create executables with a .o at the end of the file names, e.g.,

chpl --fast hello.chpl -o hello.o

Having an executable file with an extension .o defies the typical convention of .o files (an object file: compiled but unlinked code, which can't be executed on its own).

I would recommend (and am willing to do the work) to change the examples, for example replacing the above example with:

chpl --fast hello.chpl -o hello