Difference between revisions of "Course schedule"
From Research management course
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{#seo: | ||
| + | |title=My first scientific paper course schedule | ||
| + | |titlemode=replace | ||
| + | |keywords=course schedule | ||
| + | |description=My first scientific paper course schedule includes classes on problem stating, finding adequate references, generating novel and significant ideas for problem-solving, and presenting research results. | ||
| + | }} | ||
| + | |||
The goal of the course is to introduce students to the technologies of scientific research. The course teaches how to plan, perform, and present research results. It provides formats acknowledged by other researchers. Each student works with an advisor and a consultant to learn how to formally state research problems, find adequate references, and generate novel and significant ideas for problem-solving. The expected outcome of the course is a research paper submitted to a peer-reviewed journal. | The goal of the course is to introduce students to the technologies of scientific research. The course teaches how to plan, perform, and present research results. It provides formats acknowledged by other researchers. Each student works with an advisor and a consultant to learn how to formally state research problems, find adequate references, and generate novel and significant ideas for problem-solving. The expected outcome of the course is a research paper submitted to a peer-reviewed journal. | ||
| Line 11: | Line 18: | ||
# Video of the presentation speech | # Video of the presentation speech | ||
| − | ==Schedule | + | ==Schedule 2025== |
| + | This is a preliminary version | ||
| + | |||
On Thursdays 17:50-19:20 | On Thursdays 17:50-19:20 | ||
{|class="wikitable" | {|class="wikitable" | ||
| Line 25: | Line 34: | ||
|8 | |8 | ||
|0 | |0 | ||
| − | |[[Week 0|Introduction and subscription | + | |[[Week 0|Introduction and subscription]] |
|The course schedule | |The course schedule | ||
|Subscribed to the schedule | |Subscribed to the schedule | ||
| Line 32: | Line 41: | ||
|15 | |15 | ||
|1 | |1 | ||
| − | |[[Week 1| | + | |[[Week 1|Catch up]] |
| − | |List of participants | + | |List of participants |
| − | | Catch up the necessary skills | + | |Catch up the necessary skills |
|- | |- | ||
| | | | ||
|22 | |22 | ||
|2 | |2 | ||
| − | |[[Week 1|Set the workflow, schedule, and tools | + | |[[Week 1|Set the workflow, schedule, and tools]] |
| − | |The project's initial status is set | + | |Select your project |
| − | + | |The project's initial status is set | |
|- | |- | ||
| | | | ||
| Line 118: | Line 127: | ||
# The workflow goes around each week, namely, week [[Week 0|0]], [[Week 1|1]], [[Week 2|2]], [[Week 3|3]], [[Week 4|4]], [[Week 5|5]], [[Week 6|6]], [[Week 7|7]], [[Week 8|8]], [[Week 9|9]], [[Week 10|10]], [[Week 11|11]]. | # The workflow goes around each week, namely, week [[Week 0|0]], [[Week 1|1]], [[Week 2|2]], [[Week 3|3]], [[Week 4|4]], [[Week 5|5]], [[Week 6|6]], [[Week 7|7]], [[Week 8|8]], [[Week 9|9]], [[Week 10|10]], [[Week 11|11]]. | ||
# The iterative consultations and delivery of results are highly welcome! Start during the weekends. | # The iterative consultations and delivery of results are highly welcome! Start during the weekends. | ||
| − | # | + | # The deadline for the last version is Wednesday at 6:00 am. The review goes on Wednesday's working day. |
# Each symbol '''A''' gives +1 according the system (А-, А, А+). No symbol gives A0. | # Each symbol '''A''' gives +1 according the system (А-, А, А+). No symbol gives A0. | ||
| + | # The scoring comes from the geometric mean of the sum of symbols and the final assessment. | ||
<!--# (To be clarified) Motivated delay. (Non-motivated delay interferes with peer review).--> | <!--# (To be clarified) Motivated delay. (Non-motivated delay interferes with peer review).--> | ||
==Workload== | ==Workload== | ||
# '''Student''''s workload depends on the group and can vary from 54 hours and up. | # '''Student''''s workload depends on the group and can vary from 54 hours and up. | ||
| − | <!--#* The | + | <!--#* The Intelligent Systems Department group is 74-128 hours |
| − | #* The group of the | + | #* The group of the Faculty of Innovation and Technologies is 200 hours (expended software system and deployment part). --> |
# A '''consultant''' is expected to make one-hour meetings weekly and promptly to student's questions. So it takes 12 to 16 hours. | # A '''consultant''' is expected to make one-hour meetings weekly and promptly to student's questions. So it takes 12 to 16 hours. | ||
| − | # An '''expert''' is expected to state the problem and evaluate the delivery. It takes one | + | # An '''expert''' is expected to state the problem and evaluate the delivery. It takes one hour maximum. And we guess researchers are ready to discuss their favorite problems. It creates a negative workload: for a problem, the expert solves as a daily routine, some delivery appears after several months of synchronized work. The quality of the stated problem matters. |
==Past years== | ==Past years== | ||
| + | * [https://www.youtube.com/watch?v=n4rBC4-Rcms&list=PLk4h7dmY2eYGdHTyN_LP0qlplQDyH_Z5c Playlist 2024] | ||
* [https://www.youtube.com/playlist?list=PLk4h7dmY2eYE2Lp2ScMRSGDxLIbJr4vJ8 Playlist 2022] | * [https://www.youtube.com/playlist?list=PLk4h7dmY2eYE2Lp2ScMRSGDxLIbJr4vJ8 Playlist 2022] | ||
* [https://www.youtube.com/playlist?list=PLk4h7dmY2eYF2DWWi6LoByk_ZaoHWh3na Playlist 2021] | * [https://www.youtube.com/playlist?list=PLk4h7dmY2eYF2DWWi6LoByk_ZaoHWh3na Playlist 2021] | ||
| Line 162: | Line 173: | ||
Streamed live on Apr 16, 2020 | Streamed live on Apr 16, 2020 | ||
| − | My first scientific paper: Modelling and Error | + | My first scientific paper: Modelling and Error Analysis |
Streamed live on Mar 26, 2020 | Streamed live on Mar 26, 2020 | ||
https://www.youtube.com/watch?v=F_SNmGyxcZg | https://www.youtube.com/watch?v=F_SNmGyxcZg | ||
Latest revision as of 15:16, 13 August 2024
The goal of the course is to introduce students to the technologies of scientific research. The course teaches how to plan, perform, and present research results. It provides formats acknowledged by other researchers. Each student works with an advisor and a consultant to learn how to formally state research problems, find adequate references, and generate novel and significant ideas for problem-solving. The expected outcome of the course is a research paper submitted to a peer-reviewed journal.
The course has been successfully delivered during the last eight years. Each year 15-30 students perform their research projects. Each project ends with a scientific paper, a code, a presentation, and a video. The course has a repository with over 500 projects and its YouTube channel.
Goals
- General: to learn how to convey the author's message to the reader in a clear way.
- Practical: to publish a scientific paper, to be welcome in the research society.
Delivery
- Research paper in a peer-reviewed scientific journal
- Computational experiment with analysis and code to reproduce it
- Slides with brief comprehensive results
- Video of the presentation speech
Schedule 2025
This is a preliminary version
On Thursdays 17:50-19:20
| Date | N | To be done | Result to discuss | Symbol | |
| February | 8 | 0 | Introduction and subscription | The course schedule | Subscribed to the schedule |
| 15 | 1 | Catch up | List of participants | Catch up the necessary skills | |
| 22 | 2 | Set the workflow, schedule, and tools | Select your project | The project's initial status is set | |
| 29 | 3 | Tell about your project. List references, write Abstract, LinkReview. | Abstract, Introduction, References in bib-file. | Abstract, LinkReview, B*egin-talk | |
| March | 7 | 4 | State your problem, generally in Introduction and formally | Write the problem statement, and write the basic algorithm description. | Introduction with References, Problem statement |
| 14 | 5 | Set goals and plan report of your computational experiment. Run basic code. Write down the results. | Goals of the experiment. Basic code, a draft report on the basic algorithm. Ready for the first checkpoint. | eXperiment palning, Basic code, Report, cHeck-1 | |
| 21 | 6 | Run your computational experiment and visualize its results. | Code, visual presentation of results. Create a draft of your presentation for 1'30". | Code, Visualization, O*ne slide-talk | |
| 28 | 7 | Describe the algorithm. | The theory and algorithms are in the paper. | Theory | |
| April | 4 | 8 | Make the error and quality analysis. Finalize the computational experiment. | The experiment description with error analysis. | Error |
| 11 | 9 | Prepare for the reader the theoretical part and computational experiment. Explain the figures, and write conclusions. Ready to the second checkpoint. | The paper draft with the sections Computational experiment and Conclusions. Checkpoint. | Document, cHeck-2, M*edium-talk | |
| 18 | 10 | Your paper is ready to the peer-review. | You published your peer review of your colleague's paper. | RevieW | |
| 25 | 11 | Finalization. Collect all necessary documents: author's affiliations, review, response, English abstract, references for catalogs, and letter to the editor. | The paper and slides are subjects to submit. | Journal, Slide-check | |
| May | 2 | 12 | Prepare your presentation. | Presentation day. | Final show |
Consultations
- The workflow goes around each week, namely, week 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11.
- The iterative consultations and delivery of results are highly welcome! Start during the weekends.
- The deadline for the last version is Wednesday at 6:00 am. The review goes on Wednesday's working day.
- Each symbol A gives +1 according the system (А-, А, А+). No symbol gives A0.
- The scoring comes from the geometric mean of the sum of symbols and the final assessment.
Workload
- Student's workload depends on the group and can vary from 54 hours and up.
- A consultant is expected to make one-hour meetings weekly and promptly to student's questions. So it takes 12 to 16 hours.
- An expert is expected to state the problem and evaluate the delivery. It takes one hour maximum. And we guess researchers are ready to discuss their favorite problems. It creates a negative workload: for a problem, the expert solves as a daily routine, some delivery appears after several months of synchronized work. The quality of the stated problem matters.
Past years
- Playlist 2024
- Playlist 2022
- Playlist 2021
- Playlist 2020, 2019 link hidden
- Tests, link hidden