You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,6 +21,10 @@ Coverage report is available [here](https://learning-process.github.io/parallel_
21
21
*`oneAPI Threading Building Blocks (oneTBB)`
22
22
*`Multithreading in C++ (std::thread)`
23
23
24
+
## Quickstart
25
+
26
+
See the full user guide for build, tests, docs, and tooling instructions: [documentation en](https://learning-process.github.io/parallel_programming_course/en/), [documentation ru](https://learning-process.github.io/parallel_programming_course/ru/).
27
+
24
28
### Rules for submissions:
25
29
1. You are not supposed to trigger CI jobs by frequent updates of your pull request. First you should test you work locally with all the scripts (code style).
26
30
* Respect others time and don't slow down the job queue
Copy file name to clipboardExpand all lines: docs/common_information/introduction.rst
+14-20Lines changed: 14 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,31 +12,25 @@ Practice
12
12
- Test verification
13
13
14
14
- Task distribution is random for each student.
15
-
- An example for each technology can be found in the corresponding directory: ``tasks/<all/omp/tbb/seq/stl/mpi>/example``.
16
-
- In each repository, the README.md contains a link to the course documentation (**read it fully!!!**).
17
-
- Additionally, each repository includes an example of a properly formatted PULL REQUEST.
15
+
- Full automation of quality and performance checks; plagiarism checks are applied.
16
+
- Deadlines are set per task. See the penalties and grading rules in ``Points``.
17
+
- Examples are provided in ``tasks/example_threads`` and ``tasks/example_processes`` (and extended variations ``tasks/example_processes_2`` / ``tasks/example_processes_3``).
18
+
- In each repository, the README.md contains a link to the course documentation.
19
+
- Each repository includes an example of a properly formatted PULL REQUEST.
18
20
- Submission of all tasks is mandatory to pass the course.
19
21
- A task that has been merged into the master branch continues to be monitored.
20
22
If a task fails in the master, it is disabled, and a record of this is added to the score table.
21
23
All disabled tasks will result in a zero points result for those tasks at the end of the semester.
22
24
It can be seen that your task is disabled due to the following reason: the directory of your task has been renamed
23
25
from ``seq/nesterov_a_vector_sum`` to ``seq/nesterov_a_vector_sum_disabled``
24
-
- All resources for using the repository will be provided here:
25
26
26
-
- `Git for half an hour: A Beginner’s Guide <https://proglib.io/p/git-for-half-an-hour>`__
27
-
- `Getting Started with Git and GitHub: A Beginner’s Guide <https://medium.com/nuances-of-programming/%D0%B7%D0%BD%D0%B0%D0%BA%D0%BE%D0%BC%D1%81%D1%82%D0%B2%D0%BE-%D1%81-git-%D0%B8-github-%D1%80%D1%83%D0%BA%D0%BE%D0%B2%D0%BE%D0%B4%D1%81%D1%82%D0%B2%D0%BE-%D0%B4%D0%BB%D1%8F-%D0%BD%D0%B0%D1%87%D0%B8%D0%BD%D0%B0%D1%8E%D1%89%D0%B8%D1%85-54ea2567d76c>`__
28
-
- `Git: A Quick Start Guide to Using Core Operations with Explanations <https://tproger.ru/translations/git-quick-start/>`__
29
-
- `Conflicts resolving in Git <https://githowto.com/ru/resolving_conflicts>`__
- `Writing Multithreaded Applications in C++ <https://eax.me/cpp-multithreading/>`__
39
-
- `Multithreading: New Features of the C++11 Standard <https://web.archive.org/web/20200608173050/http://www.quizful.net/post/multithreading-cpp11>`__
40
-
- `Introduction to Parallel Computing <http://ikt.muctr.ru/images/info/2Lecture_3.pdf>`__
27
+
Communication
28
+
~~~~~~~~~~~~~
41
29
42
-
\* *All instructions, repositories, and tables may be updated during the learning process for better usability. Be prepared for changes, check and update them periodically!!!*
30
+
- Telegram channel — announcements and quick updates
31
+
- GitHub Issues — repository problems and bug reports
32
+
- Lessons — Q&A
33
+
- Feedback form — critical issues
34
+
- Email — non‑urgent matters
35
+
36
+
\* *All instructions, repositories, and tables may be updated during the learning process for better usability. Be prepared for changes and check updates periodically.*
0 commit comments