CD Making Guidelines
People coming after you should benefit from our work. The guideline below applies to all students: BTP, MTP and PHD
The CD you should make before leaving should contain
IMP:
A. The CD should be marked by your name, roll no., year and the topic of your research; There should be a readme file in EVERY directory and subdirectory describing what the directory contains.
B. The top level readme file should contain your name, roll no., title of your thesis and the abstract.
C. Naming convention for files- venue-researcher-topic e.g., mtp1-bhavani-speech-mt
Content Description for the folders above:
- System directory: your source and executable codes
- code directory
- dataset directory
- your own created dataset
- others' dataset used
- Documents directory with
- report directory
- pdf
- all source files (doc/tex)
- manual directory
- user manual (how to install and run the system)
- programmer manual (for a person who can change the code; JavaDocs/Oxygen etc.)
- slides directory
- first stage
- second stage
- seminar
- published conference
- weekly updates
- any other talks
(PPTS and PDF)
- papers directory
- your own papers (tex, fig)
- your own survey paper
- others' papers read (pdf, ps, doc etc.)
After all this is done, Your report shall be signed.
Additional rules to follow:
- All the folders should contains their individual readme.txt files containing a single line about the files contained in that folder.
- Sub-folders inside the source code folder are an exception to this.
- Comments inside the code would do it.
- Reports should be available in both PDF and editable format.
- Please include your PPT's as well in the reports folder in a subfolder.
- README should be in .txt format.
- For Latex source files create two sub folders- tex_files & images
- Work update directory should contain all work update slides in ppt format under slides
directory.
- The philosophy behind the manual directory is as follows: USER manual- anybody should be able to install and run your system, your user manual should facilitate this.
- PROGRAMMER manual- anybody should be able to take your code and be able to modify it.
- Your programmer manual should facilitate this.
- Source files should be present- ppts for slides and latex files for report
- NO zip files (latext files in text format)
- Slides directory will have 4 subdirectories- MTP1, MTP2, Seminar, Work-update (DDPs map
accordingly)
- Put down the reviews recieved after submissions to any of the conferences in the Papers
directory for the CD.