How ofkira/tex_informes works
1. Repo purpose
This repository is a versioned LaTeX report workspace, not an application codebase. Its primary product is a set of compiled PDFs for academic reports, organized by subject and assignment moment.
2. Top-level structure
The root contains a reusable IEEE LaTeX template (IEEE-conference-template-062824.tex), a README.md with workflow guidance, and GitHub issue templates for contribution requests and compilation bugs. The rest of the repository is split into subject-specific report folders.
3. Core document-generation boundary
Each report is authored as a standalone .tex file inside its subject/moment folder and is expected to compile with pdflatex using the shared IEEE template as the base. The repo’s main boundary is therefore source LaTeX + assets in Git versus generated PDFs outside version control.
4. Subject subsystem: Automatas
automatas/ contains reports for automata coursework. It is divided by “momento”:
- momento2/ with grupo1.tex
- momento3/ with grupo12_m3.tex
These are independent report units, each with their own local supporting materials.
5. Embedded implementation artifacts in Automatas
The automata reports include code-related subfolders such as sketch_grupo1, tinkercad_grupo1, and sketch_grupo12_m3. This indicates the report is not purely narrative: it also packages Arduino/Wokwi/Tinkercad simulation code used as evidence or demonstration material in the report.
6. Simulation-centric files in Automatas moment 3
automatas/momento3/sketch_grupo12_m3/ contains:
- sketch_grupo12_m3.ino for Arduino code
- diagram.json for the circuit/topology definition
- wokwi.toml for Wokwi project configuration
- a local README.md
This folder acts as a self-contained simulation artifact set that complements the LaTeX write-up.
7. Subject subsystem: Física
fisica/ follows the same pattern, with momento2/grupo7.tex as the report root and a simulaciones/ directory holding experiment/simulation files. This keeps the report text separate from the simulation artifacts it describes.
8. Physics simulation artifact formats
The physics simulations use domain-specific file types such as .sch and .sim1, which suggests circuit or technical simulation tools rather than generic source code. These files are likely referenced as supporting evidence in the LaTeX report and are treated as first-class project artifacts.
9. Assets and visual inputs
Each report folder has an assets/ directory. This is the likely boundary for images, diagrams, figures, or exported screenshots that the .tex files include. In architecture terms, the .tex documents consume these assets to generate the final PDF.
10. Collaboration and workflow
The repository is optimized for collaborative academic editing through GitHub:
- issue templates for content requests and compilation errors
- guidance to clone, edit, diff, and propose changes via issue if needed
- local compilation verification via pdflatex under TeXLive
The workflow is: edit report source and supporting artifacts → compile locally → submit changes via Git.
11. Operational model
There is no centralized application runtime, backend, or deployment layer. The repo is a document-centric monorepo where each subject/moment folder is an isolated report package composed of LaTeX, figures/assets, and any embedded simulation/code artifacts needed to justify the report content.
12. What an architecture diagram should show
A correct diagram would have:
- a shared template layer at the root
- multiple independent report packages under automatas/ and fisica/
- per-package supporting artifact directories (assets/, simulaciones/, sketch_*, tinkercad_*)
- LaTeX compilation as the main transformation from source materials to PDF output
- GitHub issue templates as the collaboration entry point for changes and bug reports
Main entry points: grupo1.tex Grupo 1 · grupo12_m3.tex Grupo 12 · grupo7.tex Grupo 7 · IEEE-conference-template-062824.tex IEEE Template
Components 14
Root
Shared template, repo guidance, and collaboration entry points.
- README · Repository workflow and editing guidance.
README.md - IEEE Template · Shared IEEE conference LaTeX starting point.
IEEE-conference-template-062824.tex - Issue Templates · Contribution and compilation issue forms.
.github/ISSUE_TEMPLATE - PDF Build · Compiled report output produced from LaTeX sources.
Automatas
Automata report packages and their embedded simulation artifacts.
- Grupo 1 · Automatas momento 2 report source.
automatas/momento2/grupo1.tex - M2 Assets · Images and figures used by the Automatas momento 2 report.
automatas/momento2/assets - M2 Sketch · Embedded Arduino evidence for Automatas momento 2.
automatas/momento2/sketch_grupo1 - Tinkercad · Tinkercad-based simulation artifact for Automatas momento 2.
automatas/momento2/tinkercad_grupo1 - Grupo 12 · Automatas momento 3 report source.
automatas/momento3/grupo12_m3.tex - M3 Assets · Images and figures used by the Automatas momento 3 report.
automatas/momento3/assets - Wokwi Sketch · Self-contained Wokwi/Arduino simulation bundle.
automatas/momento3/sketch_grupo12_m3
Física
Physics report package and supporting simulation files.
- Grupo 7 · Física momento 2 report source.
fisica/momento2/grupo7.tex - Assets · Visual assets consumed by the Física report.
fisica/momento2/assets - Simulations · Circuit and experiment artifacts supporting the report.
fisica/momento2/simulaciones
Connections 15
- README → Issue Templates: guides · Workflow guidance points editors to issue-based collaboration.
- IEEE Template → PDF Build: compiles · Shared IEEE template is the base for final PDF generation.
- Grupo 1 → IEEE Template: uses · Automatas report is built on the shared LaTeX template.
- Grupo 1 → M2 Assets: includes · Report consumes local figures and images.
- Grupo 1 → M2 Sketch: documents · Report references embedded Arduino evidence.
- Grupo 1 → Tinkercad: documents · Report references simulation artifacts.
- Grupo 1 → PDF Build: outputs · LaTeX source is compiled into the report PDF.
- Grupo 12 → IEEE Template: uses · Automatas momento 3 report is built on the shared template.
- Grupo 12 → M3 Assets: includes · Report consumes local figures and images.
- Grupo 12 → Wokwi Sketch: documents · Report references the bundled Wokwi simulation package.
- Grupo 12 → PDF Build: outputs · LaTeX source is compiled into the report PDF.
- Grupo 7 → IEEE Template: uses · Physics report is built on the shared LaTeX template.
- Grupo 7 → Assets: includes · Report consumes local figures and images.
- Grupo 7 → Simulations: references · Report depends on simulation artifacts as supporting evidence.
- Grupo 7 → PDF Build: outputs · LaTeX source is compiled into the report PDF.