Course schedule

From Research management course
Revision as of 16:52, 19 February 2024 by Vs (talk | contribs)
Jump to: navigation, search

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 2024

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=1481’