How namonaki1234/wsl works
Project type and purpose
• This is not a single full-stack web app or microservice; it’s a monolithic “code vault” or “monorepo” that lives under WSL, used to store and sync:
• Competitive programming solutions (AtCoder, Paiza, Codeforces, etc.)
• Scientific or simulation code (Fortran projects, grid generation, flow solvers)
• Python utilities and notebooks (data processing, Shogi and Sudoku camera recognition, playlist fetch, etc.)
• Shell scripts and helpers (count_file.sh, disc_volume.sh, test.sh)
• The README simply says “WSLのディレクトリ – どのデバイスでも同期できる!” (A WSL directory that can be synced across devices), confirming the goal is cross-device code synchronization.
File structure
• Top‐level folders group by domain or contest platform:
• atcoder/ – All AtCoder problem source files, organized by contest and problem
• paiza/ – Paiza problem solutions by category
• fortran/ – Various Fortran exercises, solvers, grid-generation tools; often with nested folders per assignment
• python/ – Python scripts, Jupyter notebooks, and two major sub‐projects:
– shogi-camera/ – CLI, data, models, Docker containers for GPU/CPU image recognition of Shogi boards
– sudoku-camera/ – Equivalent structure for Sudoku
• Other miscellaneous scripts at the root (e.g., anilist conversion scripts, playlist fetcher, helper .sh scripts)
• Nested configuration/build files, e.g., Dockerfiles under containers, setup.py in camera modules, .vscode settings in atcoder/.
README
• Python (scripts, .py, .ipynb, .h5 models)
• Fortran (.f90)
• C/C++ (some .cpp)
• Shell scripts
• Docker for containerizing camera projects
Elements
• Blue for Competitive Programming folders
• Green for Fortran/Scientific code
• Orange for Python Utilities
• Yellow for Containers