Difference between revisions of "Course schedule"

From Research management course
Jump to: navigation, search
m
 
(13 intermediate revisions by 2 users not shown)
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.
+
{{#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 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==
 
==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 15:
 
# 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 a brief comprehensive results
+
# Slides with brief comprehensive results
 
# Video of the presentation speech  
 
# Video of the presentation speech  
  
−
==Schedule 2023==
+
==Schedule 2025==
 +
This is a preliminary version
 +
 
 +
On Thursdays 17:50-19:20
 
{|class="wikitable"         
 
{|class="wikitable"         
 
|-
 
|-
Line 21: Line 32:
 
|-   
 
|-   
 
|February
 
|February
−
|9
+
|8
−
|1
+
|0
−
|[[Week 1|Introduction and subscription.]]
+
|[[Week 0|Introduction and subscription]]
−
|List of participants.
+
|The course schedule
 
|Subscribed to the schedule
 
|Subscribed to the schedule
 
|-   
 
|-   
−
<!--|
+
|
−
|16
+
|15
 
|1
 
|1
−
|[[Week 1|Set the workflow, schedule, tools.]]
+
|[[Week 1|Catch up]]
−
|Tools are ready to use. The project initial status is set.
+
|List of participants
−
|Set the record
+
|Catch up the necessary skills
−
-->
 
 
|-
 
|-
 
|
 
|
−
|16
+
|22
 
|2
 
|2
−
|[[Week 2|Select your project and tell about it.]] List references, write Abstract, LinkReview.
+
|[[Week 1|Set the workflow, schedule, and tools]]
−
|Abstract, Introduction, References in bib-file.
+
|Select your project
−
|'''A'''bstract, '''L'''inkReview,  '''B*'''egin-talk
+
|The project's initial status is set
 
|-
 
|-
 
|
 
|
−
|23
+
|29
 
|3
 
|3
−
|[[Week 3|State your problem]], generally in Introduction, and formally
+
|[[Week 2|Tell about your project.]] List references, write Abstract, LinkReview.
−
|Write the problem statement, write the basic algorithm description.  
+
|Abstract, Introduction, References in bib-file.
−
|'''I'''ntroduction with References, '''P'''roblem statement
+
|'''A'''bstract, '''L'''inkReview, '''B*'''egin-talk
 
|-
 
|-
 
|March
 
|March
 +
|7
 
|4
 
|4
−
|4
+
|[[Week 3|State your problem]],  generally in Introduction and formally
−
|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.  
+
|Write the problem statement, and write the basic algorithm description.
−
|Goals of the experiment. Basic code, draft report on the basic algorithm. Ready to the first checkpoint.
+
|'''I'''ntroduction with References, '''P'''roblem statement
 +
|-
 +
|
 +
|14
 +
|5
 +
|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, 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  
 
|-
 
|-
 
|
 
|
−
|9
+
|21
−
|5
+
|6
−
|Run your computational experiment and [[Week 5|visualise its results]].
+
|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
 
|-
 
|-
 
|
 
|
−
|16
+
|28
−
|6
+
|7
 
|[[Week 6|Describe the algorithm]].
 
|[[Week 6|Describe the algorithm]].
 
|The theory and algorithms are in the paper.
 
|The theory and algorithms are in the paper.
 
|'''T'''heory
 
|'''T'''heory
 
|-
 
|-
−
|
+
|April
−
|23
+
|4
−
|7
+
|8
−
|Make the [[Week 7|error and quality analysis]]. Finalise the computational experiment.
+
|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
 
|-
 
|-
−
|April
+
|
−
|2
+
|11
−
|8
+
|9
−
|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
 
|-
 
|-
 
|
 
|
−
|9
+
|18
−
|9
+
|10
 
|Your paper is ready to [[Week 9|the peer-review]].  
 
|Your paper is ready to [[Week 9|the peer-review]].  
−
|You published your peer-review of your colleague's paper.
+
|You published your peer review of your colleague's paper.
 
|Revie'''W'''
 
|Revie'''W'''
 
|-
 
|-
 
|
 
|
−
|16
+
|25
−
|10
+
|11
−
|Finalization. Collect all necessary documents: author's affiliations, revew, response, [[Week 10|English abstract]], references for catalogs, and letter to the editor.
+
|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
 
|-
 
|-
−
|
+
|May
−
|23
+
|2
−
|11
+
|12
 
|[[Week 11|Prepare your presentation]].
 
|[[Week 11|Prepare your presentation]].
 
|Presentation day.  
 
|Presentation day.  
Line 110: 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.  
−
# Deadline of the last version is: Wednesday 6:00am. The review goes on Wednesday working day.  
+
# 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.  
−
<!--# (To be clarified) Motivated delay. (Non-motivated delay interferes peer-review).-->
+
# 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).-->
  
 
==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 group of the MIPT Intelligent Systems Department is 74-128 hours
+
<!--#* The 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 Faculty of Innovation and Technologies is 200 hours (expended software system and deployment part). -->
−
# A '''consultant''' is expected to make one-hour meeting weekly and promptly to student's questions. So it makes 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 hour maximum. And we guess any researcher is ready to discuss the favourite problem. In fact, it makes the 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.
+
# 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 154: Line 173:
 
Streamed live on Apr 16, 2020
 
Streamed live on Apr 16, 2020
  
−
My first scientific paper: Modelling and Error analysis
+
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

  1. Research paper in a peer-reviewed scientific journal
  2. Computational experiment with analysis and code to reproduce it
  3. Slides with brief comprehensive results
  4. 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

  1. The workflow goes around each week, namely, week 0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11.
  2. The iterative consultations and delivery of results are highly welcome! Start during the weekends.
  3. The deadline for the last version is Wednesday at 6:00 am. The review goes on Wednesday's working day.
  4. Each symbol A gives +1 according the system (А-, А, А+). No symbol gives A0.
  5. The scoring comes from the geometric mean of the sum of symbols and the final assessment.

Workload

  1. Student's workload depends on the group and can vary from 54 hours and up.
  2. A consultant is expected to make one-hour meetings weekly and promptly to student's questions. So it takes 12 to 16 hours.
  3. 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

Retrieved from ‘https://m1p.org/index.php?title=Course_schedule&oldid=1586’