so-sc / vtu-lab-material Goto Github PK

This is a collection of resources that intend to cover from lab programs to viva questions and all everything in between.

License: GNU General Public License v3.0

Python 1.05% Jupyter Notebook 80.18% PHP 1.13% HTML 1.14% CSS 0.11% C 7.04% Java 5.92% C++ 2.11% Assembly 1.32%

educational-project education open-source community-project teaching-materials labs

vtu-lab-material's Introduction

VTU Lab Material

Collection of VTU laboratory easy solutions and related educational material maintained by the students, for the students, to the students. 💪🏻

Motivation

Ever had trouble getting the right VTU lab material to study from? Well, look no further! here's a collection of all resources required, gathered and verified with by the respective laboratory incharge, by the students over at Sahyadri Open Source Community

Getting started

The folder structure is arranged according to semester/branch/subject_code+subject_name/file_name

.
├── sem-7
│   ├── computer_science
│   │   ├── 15CSL76_MACHINE_LEARNING_LABORATORY
│   │   │   ├── 01. Find-S Algorithm.ipynb
│   │   │   ├── 01. Find-S Algorithm.py
.   .   .   .
.   .   .   .

If the Lab experiments contain more than one file, create a separate sub directory for each experiment. eg /semester/branch/subject_code_subject_name/experiment_no_experiment_name/filename

.
├── sem-7
│   ├── computer_science
│   │   ├── 15CSL77_WEB_PROGRAMMING_LABORATORY
│   │   │   ├── 01 Calculator
│   │   │   |   ├── index.html
│   │   │   |   ├── style.css
.   .   .   .   .
.   .   .   .   .

Contributing

Please read CONTRIBUTING.md for details on our code of conduct and the process for submitting pull requests.

License

This project is licensed under the GNU General Public License v3.0 - see the LICENSE file for more details.

vtu-lab-material's People

Contributors

Stargazers

Watchers

vtu-lab-material's Issues

Algorithms, flowcharts and viva-questions

⭐ Along with existing programs and outputs, we should include 😉 :

Algorithms
Flow-charts
Expected viva-questions 📙 from each programs
Concept applied ☺️

Refactor Suggestion 😉

How about having the programs (directory structure) sectioned as:

-> SEM-01
    -> PCD LAB
    -> SOME NEW LAB
-> SEM-02
...

because in some semesters based on the Branch they might have different labs. (ex: IS 6th sem didn't have CG)

Or having different git branches for different branches (engineering) 🤡 since the repo is named VTU-Lab-Material.😃

No program

There was no code written for dfs and bfs program in c program in 3rd sem Ds lab program

Program complexities and intensions

The programs as in 15CSL77 are far too complex as people won't need material that's really easy to remember and digest like little chunks. Just the first program required them to remember three files where people don't really know the difference between JS and PHP two days prior to external. So lets keep it simple and not too fancy.
Keep in mind that it need to be developer standards just easy learning material. @haxzie Let's have a review before any merging code.

program is missing.

There are no programs in the files mentioned below

VTU-Lab-Material/sem-1-2/18CPL17-27_COMPUTER_PROGRAMMING_LABORATORY/Program-02/program-01.c
VTU-Lab-Material/sem-1-2/18CPL17-27_COMPUTER_PROGRAMMING_LABORATORY/Program-02/program-02.c
VTU-Lab-Material/sem-1-2/18CPL17-27_COMPUTER_PROGRAMMING_LABORATORY/Program-02/program-03.c
VTU-Lab-Material/sem-1-2/18CPL17-27_COMPUTER_PROGRAMMING_LABORATORY/Program-02/program-04.c

Creating a PDF of completly finalised VTU lab materials

Refactor sem 3 lab Programs

It'd be great to have the directory structure refactored for the 3rd semester DS LAB programs.

Create a folder inside sem 3 with the name of your branch. eg. Computer Science
Create another folder inside Computer Science with name of the subject along with the VTU subject code. Eg. 15CSL77-DATA-STRUCTURES-LAB
Create a separate folder inside for each lab program with the folder name as program_number. Program name eg. 1. Stacks and Queues make sure the programs inside have proper file extension and name, a good practice would be to give a name like program1.c
Additionally add a README.md file inside each folder containing the program with instructions regarding how to execute the program, output of the program and any explaination/links to learn/understand the program.

PLEASE NOTE

Donot directly push the code to this repository, always fork and make a copy of this and work on a new brach. Once done, submit a Pull Request to the repository. Donot merge the pull request without having someone review it .

Cheers ✌️