Difference between revisions of "Course schedule"
From m1p.org
m |
m |
||
| Line 1: | Line 1: | ||
This course introduces the technologies of scientific research. It teaches students how to present their results in the anticipated format. It results in a research paper that should be submitted to a reputable peer-reviewed journal. | This course introduces the technologies of scientific research. It teaches students how to present their results in the anticipated format. It results in a research paper that should be submitted to a reputable peer-reviewed journal. | ||
| − | |||
==Goals== | ==Goals== | ||
* General: to learn how to convey the author's message to the reader in a clear way. | * General: to learn how to convey the author's message to the reader in a clear way. | ||
| Line 7: | Line 6: | ||
# Research paper in a peer-reviewed scientific journal | # Research paper in a peer-reviewed scientific journal | ||
# Computational experiment with analysis and code to reproduce it | # Computational experiment with analysis and code to reproduce it | ||
| − | # Slides with | + | # Slides with brief comprehensive results |
# Video of the presentation speech | # Video of the presentation speech | ||
| Line 30: | Line 29: | ||
|16 | |16 | ||
|1 | |1 | ||
| − | |[[Week 1|Set the workflow, schedule, tools.]] | + | |[[Week 1|Set the workflow, schedule, and tools.]] |
| − | |Tools are ready to use. The project initial status is set. | + | |Tools are ready to use. The project's initial status is set. |
|Set the record | |Set the record | ||
--> | --> | ||
| Line 45: | Line 44: | ||
|23 | |23 | ||
|3 | |3 | ||
| − | |[[Week 3|State your problem]], generally in Introduction | + | |[[Week 3|State your problem]], generally in Introduction and formally |
| − | |Write the problem statement, write the basic algorithm description. | + | |Write the problem statement, and write the basic algorithm description. |
|'''I'''ntroduction with References, '''P'''roblem statement | |'''I'''ntroduction with References, '''P'''roblem statement | ||
|- | |- | ||
| Line 52: | Line 51: | ||
|4 | |4 | ||
|4 | |4 | ||
| − | |Set goals and [[Week 4|plan report of your computational experiment]]. <!-- write a description of your basic algorithm, prepare your computational experiment. -->Run basic code. Write down results. | + | |Set goals and [[Week 4|plan report of your computational experiment]]. <!-- write a description of your basic algorithm, and prepare your computational experiment. -->Run basic code. Write down the results. |
| − | |Goals of the experiment. Basic code, draft report on the basic algorithm. Ready | + | |Goals of the experiment. Basic code, a draft report on the basic algorithm. Ready for the first checkpoint. |
|e'''X'''periment palning, '''B'''asic code, '''R'''eport, c'''H'''eck-1 | |e'''X'''periment palning, '''B'''asic code, '''R'''eport, c'''H'''eck-1 | ||
|- | |- | ||
| Line 59: | Line 58: | ||
|9 | |9 | ||
|5 | |5 | ||
| − | |Run your computational experiment and [[Week 5| | + | |Run your computational experiment and [[Week 5| visualize its results]]. |
|Code, visual presentation of results. Create a draft of your presentation for 1'30". | |Code, visual presentation of results. Create a draft of your presentation for 1'30". | ||
|'''C'''ode, '''V'''isualization, '''O*'''ne slide-talk | |'''C'''ode, '''V'''isualization, '''O*'''ne slide-talk | ||
| Line 73: | Line 72: | ||
|23 | |23 | ||
|7 | |7 | ||
| − | |Make the [[Week 7|error and quality analysis]]. | + | |Make the [[Week 7|error and quality analysis]]. Finalize the computational experiment. |
|The experiment description with error analysis. | |The experiment description with error analysis. | ||
|'''E'''rror | |'''E'''rror | ||
| Line 80: | Line 79: | ||
|2 | |2 | ||
|8 | |8 | ||
| − | |Prepare for the reader the theoretical part and computational experiment. Explain the figures, write conclusions. [[Week 8|Ready to the second checkpoint]]. | + | |Prepare for the reader the theoretical part and computational experiment. Explain the figures, and write conclusions. [[Week 8|Ready to the second checkpoint]]. |
|The paper draft with the sections Computational experiment and Conclusions. Checkpoint. | |The paper draft with the sections Computational experiment and Conclusions. Checkpoint. | ||
|'''D'''ocument, c'''H'''eck-2, '''M*'''edium-talk | |'''D'''ocument, c'''H'''eck-2, '''M*'''edium-talk | ||
| Line 88: | Line 87: | ||
|9 | |9 | ||
|Your paper is ready to [[Week 9|the peer-review]]. | |Your paper is ready to [[Week 9|the peer-review]]. | ||
| − | |You published your peer | + | |You published your peer review of your colleague's paper. |
|Revie'''W''' | |Revie'''W''' | ||
|- | |- | ||
| Line 94: | Line 93: | ||
|16 | |16 | ||
|10 | |10 | ||
| − | |Finalization. Collect all necessary documents: author's affiliations, | + | |Finalization. Collect all necessary documents: author's affiliations, review, response, [[Week 10|English abstract]], references for catalogs, and letter to the editor. |
|The paper and slides are subjects to submit. | |The paper and slides are subjects to submit. | ||
|'''J'''ournal, '''S'''lide-check | |'''J'''ournal, '''S'''lide-check | ||
| Line 110: | Line 109: | ||
# 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. | ||
| − | # Deadline | + | # Deadline for the last version is Wednesday 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. | ||
| − | <!--# (To be clarified) Motivated delay. (Non-motivated delay interferes peer | + | <!--# (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 MIPT Intelligent Systems Department group is 74-128 hours |
#* The group of the MIPT Faculty of Innovation and Technologies is 200 hours (expended software system and deployment part). --> | #* The group of the MIPT Faculty of Innovation and Technologies is 200 hours (expended software system and deployment part). --> | ||
| − | # A '''consultant''' is expected to make one-hour | + | # 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 | + | # 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== | ||
Revision as of 04:19, 7 October 2022
This course introduces the technologies of scientific research. It teaches students how to present their results in the anticipated format. It results in a research paper that should be submitted to a reputable peer-reviewed journal.
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 2023
| Date | N | To be done | Result to discuss | Symbol | |
| February | 9 | 1 | Introduction and subscription. | List of participants. | Subscribed to the schedule |
| 16 | 2 | Select your project and tell about it. List references, write Abstract, LinkReview. | Abstract, Introduction, References in bib-file. | Abstract, LinkReview, B*egin-talk | |
| 23 | 3 | State your problem, generally in Introduction and formally | Write the problem statement, and write the basic algorithm description. | Introduction with References, Problem statement | |
| March | 4 | 4 | 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 |
| 9 | 5 | 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 | |
| 16 | 6 | Describe the algorithm. | The theory and algorithms are in the paper. | Theory | |
| 23 | 7 | Make the error and quality analysis. Finalize the computational experiment. | The experiment description with error analysis. | Error | |
| April | 2 | 8 | 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 |
| 9 | 9 | Your paper is ready to the peer-review. | You published your peer review of your colleague's paper. | RevieW | |
| 16 | 10 | 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 | |
| 23 | 11 | 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.
- Deadline for the last version is Wednesday 6:00 am. The review goes on Wednesday's working day.
- Each symbol A gives +1 according the system (А-, А, А+). No symbol gives A0.
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 2022
- Playlist 2021
- Playlist 2020, 2019 link hidden
- Tests, link hidden