join slack. I invited everybody who submitted assignment 0 to Slack
workspace Parallel and Distributed Programming 2026; visit UTokyo Slack top page and find the workspace
find and join your team’s channel
(pd-2026-team-xx)
discuss decide where to work (classroom or Zoom) and what to work on
; see the bullet below (Things to do after the class Nov
09.) and do them before/during the class
(Posted: Nov. 16, 2026) Irregular schedules
in coming weeks
Nov 23 (Mon): no class (holiday)
Nov 25 (Wed): we do have class
Nov 30 (Mon): no class (reserved for mid-term exam, which we don’t
have)
Dec 07 (Mon): team presentations
(Posted: Nov. 16, 2026) Bonus notebook
pd10_debug : how to know what went wrong (how to debug
your program)
(Posted: Nov. 16, 2026) Format of team
presentation on Dec 07 (Mon)
all teams must prepare for presentations about the projects
code and presentation materials must be submitted by that day and
shared with everybody in the class (protocol details later)
due to time limit, randomly selected six
teams present them in the class
everybody must ask questions via sli.do (details later)
presentations must be 10 minutes and must include
problem statement
brief algorithm description
a demo showing some meaningful results (graphics, texts, etc.); can
be AI-generated serial code; can be video-recording to save time
prospect and/or progress about parallelization and
optimizations
(Posted: Nov. 10, 2026) Things to do
after the class Nov 09.
Most of you decided on your teams quickly during the class
yesterday. Thank you. Here are a few to-dos.
[1] On my side, I am trying to set up a Slack workspace so that you
can communicate easily. I have been waiting for the apparent system
issue between UTOL and Slack to be fixed, but it has been taking
forever, so I am now taking a different route.
[2] If you didn’t attend the class on Nov 9 (and intend to continue
engaging), please open the Google spreadsheet and open the “Teams” tab
to see the teams already formed. Try to join one that matches your
interest. To do so, contact members of a team you are interested in
(many of them have written their email on the sheet, and I believe and
hope they are OK with being contacted), get approval to join, and write
your team number in the sheet.
[3] If you are already in a team, here are a few more things to do.
I have renumbered teams to reflect discussion yesterday. Please
confirm them.
I hope you are OK with being contacted by those who didn’t attend on
Nov 9; please leave your email address on the sheet if you haven’t done
so.
Decide where to work (classroom or
Zoom):
Open the Google spreadsheet again and see the “Teams” tab. (The tab
you worked on yesterday has been protected to prevent accidental edits.)
Please decide where your team will work in later weeks. The idea is to
avoid, or at least minimize, teams split between the classroom and Zoom,
since it is difficult to have many such teams in one classroom. For
teams whose members were all in the classroom on Nov 9, I suggested “r”;
for teams in the opposite situation (everybody was on Zoom), I suggested
“z”. Please feel free to overwrite them in case they are not what you
intend.
For mixed teams, please discuss among members and decide either way.
I wrote “r?” for such teams, mildly suggesting you work in the
classroom, because I don’t want to prevent anyone who wants to work in
the classroom from doing so. In the original grouping I made, I never
mixed those who prefer the classroom with those who prefer Zoom. Many of
you said you are “flexible (do what other members do),” which I
appreciate, so I hope many such teams will end up attending in
person.
It is fine for teams to be split occasionally for good reasons
(e.g., a conference trip or international study). I believe we can also
use other empty classrooms nearby for group work, for both purely
in-person teams and split teams.