Difference between revisions of "Course schedule"

From Research management course
Jump to: navigation, search
m
Line 1: Line 1:
This course introduces to the technologies of scientific research, to teach the students to present the results of their studies in the format that is acknowledged by other researchers from the field of Machine Learning and Data Analysis. The expected result of the course is a research paper, submitted to a peer-reviewed journal from the list of the Higher Attestation Commission.
+
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==

Revision as of 04:12, 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

  1. Research paper in a peer-reviewed scientific journal
  2. Computational experiment with analysis and code to reproduce it
  3. Slides with a brief comprehensive results
  4. 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, 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 results. Goals of the experiment. Basic code, draft report on the basic algorithm. Ready to the first checkpoint. eXperiment palning, Basic code, Report, cHeck-1
9 5 Run your computational experiment and visualise 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. Finalise 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, 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, revew, 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

  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. Deadline of the last version is: Wednesday 6:00am. The review goes on Wednesday working day.
  4. Each symbol A gives +1 according the system (А-, А, А+). No symbol gives A0.

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 meeting weekly and promptly to student's questions. So it makes 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 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.

Past years