How vardhan1607/academics works
1. Repository purpose
- This is a structured academic archive, not an application codebase.
- The main organizing principle is semester → subject/course → artifact type.
- It stores study materials, assignment submissions, lab reports, project work, and a small amount of executable code.
2. Top-level boundary: semester folders
- The repository is split into Sem-1 through Sem-6.
- Each semester acts as a coarse boundary for a set of related courses.
- An architecture diagram should show semesters as the primary container, with no shared runtime or cross-semester dependency graph.
3. Primary content types
- Most files are static documents: PDFs, PPT/PPTX, DOCX.
- Some folders contain interactive notebooks (.ipynb) and a few scripts (.py, .cpp).
- There are also data files (.csv, .xlsx) and CAD files from SolidWorks (.SLDPRT, .SLDASM, .SLDDRW).
4. Semester 1–4: mostly course notes and lab/report artifacts
- These semesters are largely collections of lecture notes, reference material, and submitted assignments.
- Examples include Mechanics, Physics, Chemistry, Linear Algebra, Numerical Analysis, Vector Calculus, Basic Electronics, Fluid Mechanics, Economics, Heat Transfer, Probability and Statistics, and Thermodynamics.
- The structure here is document-centric: course folder → lecture notes / class materials / tests / lab reports.
5. Semester 3–4: first appearance of structured lab/report workflows
- Lab-oriented folders such as BE Lab and Fluid Flow and Design Lab contain experiment reports.
- These are isolated deliverables rather than a program pipeline.
- The only “flow” is from experiment work to a finalized PDF report.
6. Semester 5: strongest project and computation boundary
- This semester contains the richest mix of documents, notebooks, code, and design files.
- Major subsystems:
- Mass Transfer: lecture slides and assignment PDFs under two professor-specific branches.
- NLP: notebooks, a Python script, raw corpus text, output CSV, and report PDFs.
- PED-1 / Shell and Tube Heat Exchanger: design calculations, notebooks, Python code, regression working files, spreadsheets, and CAD design assets.
- Reaction Engineering: lecture notes and tests.
- Mech Ops and Heat Transfer Lab: lab reports for multiple experiments.
- This is the closest the repo gets to a data-processing architecture.
7. Computational workflow in the engineering project folders
- The Shell and Tube Heat Exchanger area shows a clear artifact pipeline:
- reference data in CSV/XLSX files,
- exploratory/regression work in notebooks,
- a Python implementation (G29.py),
- generated PDFs with sample output,
- and SolidWorks design files for the physical component.
- Similarly, the Heat Exchanger Network folder uses a notebook (Pinch.ipynb) to support design analysis and a final PDF report.
- In architecture terms, these are “analysis + design” pipelines feeding final documentation, not long-running services.
8. NLP workspace: data-to-output flow
- The NLP section has a more explicit computational structure:
- raw corpus text input,
- notebook-based analysis,
- a Python lexing script,
- generated results archive and output CSV,
- final report PDFs.
- This indicates a classic offline processing flow: input text → preprocessing/analysis → saved outputs → report.
- The repository keeps both intermediate and final artifacts, which is important for diagramming data lineage.
9. Semester 6: algorithm implementation and control-lab reports
- Algorithms contains a C++ implementation (mineSolver.cpp) plus a presentation and readme.
- This is the main compiled-code node in the repo and should be shown separately from notebook-driven work.
- IPC Lab and MT Lab are again report-centric, with experiment PDFs rather than reusable code.
10. Cross-cutting technology profile
- The repo spans several working modes:
- academic notes and course packets,
- notebook-based scientific computing,
- Python scripting,
- one C++ algorithm project,
- spreadsheets for design calculations,
- CAD for mechanical design.
- There is no shared build system, package manager, or application runtime tying these together.
11. Important boundaries for an architecture diagram
- Keep documentation-heavy folders separate from computational/workflow folders.
- Treat notebooks/scripts/data files as local analysis pipelines, not as services.
- Treat SolidWorks files as design artifacts connected to engineering projects, not code assets.
- The dominant dependency direction is from source material / experimental data / reference tables toward reports, outputs, and project deliverables.
12. Overall shape
- This repo is best diagrammed as a hierarchical knowledge-and-project archive:
- semesters at the top,
- courses underneath,
- then artifact subtypes such as notes, labs, assignments, notebooks, code, data, and design files.
- The most important “system-level” story is how academic inputs are preserved, processed, and turned into final submissions within each course boundary.
Main entry points: Curve_fitting_for_50degree.ipynb PED Analysis · Lecture_1_06.01.2020.pdf Math & Chem · Basic Electronics.pdf Core Eng · JC HT-1.pdf Process Core
Components 19
Sem-1
Foundational study materials and notes
- Foundations · Mechanics and physics note collections.
Sem-1/Mechanics/Mech notes for end sem.pdf
Sem-2
Math and chemistry coursework
- Math & Chem · Linear algebra, numerical analysis, vector calculus, and chemistry notes.
Sem-2/Maths-2/Linear Algebra/Lecture_1_06.01.2020.pdf
Sem-3
Core engineering subjects and lab reports
- Core Eng · Basic electronics, fluid mechanics, machine learning materials, and lab reports.
Sem-3/Basic Electronics/Basic Electronics.pdf
Sem-4
Theory-heavy courses plus design and lab submissions
- Process Core · Economics, heat transfer, probability, thermodynamics, and fluid-flow design labs.
Sem-4/Heat Transfer/Conduction, Radiation/JC HT-1.pdf
Sem-5
Largest mix of documents, notebooks, code, data, and design artifacts
- Mass Transfer · Professor-specific lecture decks and assignment PDFs.
Sem-5/Mass Transfer/Prof NKP/MT NKP-1.pdf - Raw Corpus · Source text for NLP assignments.
Sem-5/NLP/19CH30018__Assn1_NLP_A21/19CH30018_Assn1_rawCorpus.txt - NLP Analysis · Notebook-driven processing and lexing work.
Sem-5/NLP/NLP_Group 10/NLP_lexing_G10.ipynb - NLP Outputs · Generated CSV and packaged results from offline analysis.
Sem-5/NLP/19CH30018_NLP_Assignment-3/19CH30018_NLP_Assignment3_Output.csv - NLP Report · Submission PDFs documenting the NLP work.
Sem-5/NLP/NLP_Group 10/NLP Report.pdf - Design Data · Reference datasets and spreadsheets for exchanger design regression.
Sem-5/PED-1/Shell and Tube Heat Exchanger/Regression Working Files/K_c Factor/Book1.xlsx - PED Analysis · Curve fitting and pinch-analysis notebooks.
Sem-5/PED-1/Shell and Tube Heat Exchanger/Regression Working Files/K_c Factor/Curve_fitting_for_50degree.ipynb - PED Code · Executable design logic for the shell-and-tube exchanger.
Sem-5/PED-1/Shell and Tube Heat Exchanger/G29.py - CAD Design · Mechanical part and assembly files for the exchanger and assignment design.
Sem-5/PED-1/Shell and Tube Heat Exchanger/Solid Work Design/Shell with Nozzles.SLDPRT - PED Report · Generated PDFs and sample outputs for the exchanger project.
Sem-5/PED-1/Shell and Tube Heat Exchanger/G29.pdf - Reaction Eng · Reaction engineering notes and test PDFs.
Sem-5/Reaction Engineering/Prof JKB/RE JKB-1 .pdf - Mech/HT Labs · Mechanical operations and heat transfer lab submissions.
Sem-5/Mech Ops and Heat Transfer Lab/Heat Transfer Lab/19CH30018_Heat Transfer.pdf
Sem-6
Algorithm implementation and control lab reports
- Minesweeper Solver · Compiled-code algorithm project with presentation and readme.
Sem-6/Algorithms/mineSolver.cpp - IPC Lab · Instrumentation and process-control experiment reports.
Sem-6/IPC Lab/IPC Lab Pressure Control Trainer.pdf - MT Lab · Mass transfer lab experiment reports.
Sem-6/MT Lab/19CH30018_Mass Transfer Lab 1.pdf
Connections 15
- Foundations → Math & Chem: progression · Course archive continues into later semesters.
- Math & Chem → Core Eng: progression · Later semesters add more engineering and lab work.
- Core Eng → Process Core: progression · Process and design subjects become more prominent.
- Process Core → Mass Transfer: focus shift · Semester 5 concentrates the richest subject-specific archive.
- Mass Transfer → Raw Corpus: source · Raw text corpus used as analysis input.
- Raw Corpus → NLP Analysis: process · Notebook-based preprocessing and lexing.
- NLP Analysis → NLP Outputs: generate · Analysis produces result files and CSV output.
- NLP Outputs → NLP Report: document · Outputs are captured in final report PDFs.
- Design Data → PED Analysis: analyze · Tables and spreadsheets feed notebook-based regression work.
- PED Analysis → PED Code: implement · Notebook exploration informs the Python design implementation.
- PED Code → PED Report: produce · Code execution produces sample output and supporting PDFs.
- PED Analysis → CAD Design: design · Analysis supports the SolidWorks component files.
- CAD Design → PED Report: document · CAD artifacts are finalized through project reporting.
- Reaction Eng → Mech/HT Labs: paired work · Reaction engineering and lab-report work coexist as semester deliverables.
- Minesweeper Solver → IPC Lab: semester boundary · Semester 6 combines implementation with control-lab documentation.