How simsine/eos_upload works
1. Overall shape
- This is a Python/Streamlit application packaged as the atlantest module.
- The app is run locally through streamlit_app.py, with dependency management handled by uv.
2. Runtime and entrypoint
- streamlit_app.py is the main launch target for Streamlit.
- run.sh and run.ps1 are thin wrappers around the same Streamlit startup command, intended for Linux/macOS and Windows respectively.
3. Primary UI architecture
- The application is organized as a multi-page Streamlit app.
- The page modules live under atlantest/streamlit_pages/, which suggests the UI is split into separate workflows rather than a single monolithic screen.
4. Page-level subsystems
- The named pages indicate distinct functional areas:
- dc_test.py
- eos_uploader.py
- metrology.py
- visual_inspection.py
- Architecturally, these look like independent workflow pages that likely share common UI scaffolding but serve different operational tasks.
5. Shared UI foundation
- atlantest/base_page.py is the main shared abstraction.
- This likely centralizes common page behavior such as layout, navigation, styling, validation, or access to shared services.
6. Static assets boundary
- atlantest/static/ is the repository’s asset boundary for non-code resources.
- In a Streamlit app this usually means images, logos, or other UI assets used by one or more pages.
7. External system integrations
- The README makes it clear the app integrates with ITkdb and ITkpd, and also needs access to EOS.
- These are the main external dependencies that materially affect the architecture; the UI is not self-contained.
8. Authentication/configuration flow
- The app depends on environment variables ITKDB_ACCESS_CODE1 and ITKDB_ACCESS_CODE2.
- That means access to external systems is configured out-of-band from the UI and injected at runtime via the shell/environment.
9. Likely data flow
- User opens the Streamlit app locally.
- The selected page collects operational input or inspection/test data.
- That page then interacts with external services such as ITkdb/ITkpd, and the EOS uploader page likely handles artifact transfer or publishing.
- Results are then reflected back in the Streamlit UI.
10. Packaging and dependency management
- pyproject.toml and uv.lock define the project environment and dependency set.
- This repo is designed to be reproducible through uv rather than manual virtualenv/package management.
11. What is not present
- There is no evidence of a separate backend server, database, or message queue in the repository layout.
- The architecture appears to be a single-process UI app with direct integrations to external enterprise systems.
12. Diagramming takeaway
- A good architecture diagram would show:
- Local user/browser UI at the top
- Streamlit app entrypoint in the middle
- Shared page base class plus four functional pages beneath it
- External integrations to ITkdb, ITkpd, and EOS on the side
- Environment variables and uv-based launch/configuration as operational dependencies
Main entry points: streamlit_app.py App entry · base_page.py Base page · dc_test.py DC test · eos_uploader.py EOS upload
Components 17
Runtime
Local launch and Streamlit execution boundary.
- Browser · Local user interacting with the Streamlit UI.
- App entry · Main Streamlit launch target.
streamlit_app.py - Linux launch · Thin shell wrapper for starting the app.
run.sh - Windows launch · Thin PowerShell wrapper for starting the app.
run.ps1
UI
Shared page framework and Streamlit workflows.
- Base page · Common page abstraction shared by Streamlit workflows.
atlantest/base_page.py - DC test · Streamlit workflow for DC test operations.
atlantest/streamlit_pages/dc_test.py - EOS upload · Workflow for sending artifacts to EOS.
atlantest/streamlit_pages/eos_uploader.py - Metrology · Workflow for measurement and inspection tasks.
atlantest/streamlit_pages/metrology.py - Visual inspect · Workflow for visual inspection tasks.
atlantest/streamlit_pages/visual_inspection.py - Static assets · Repository boundary for UI resources and images.
atlantest/static
External systems
Enterprise services and runtime configuration used by the app.
- ITkdb · External database or service integration.
- ITkpd · External production-data integration.
- EOS · External storage used for upload and retrieval.
- ITkdb creds · Environment-provided access codes for ITkdb.
Operations
Packaging, dependency, and asset support.
- Project config · Python project metadata and dependency definitions.
pyproject.toml - Lockfile · Pinned dependency resolution for reproducible installs.
uv.lock - uv · Tooling used to manage and run the environment.
Connections 25
- Browser → App entry: uses · User opens the local Streamlit app in a browser.
- Linux launch → App entry: starts · Linux/macOS wrapper launches the app.
- Windows launch → App entry: starts · Windows wrapper launches the app.
- uv → App entry: runs · uv manages the environment used to execute the app.
- Project config → Lockfile: pins · Project metadata and resolved dependencies stay aligned.
- Project config → uv: configures · Project metadata defines the uv-managed environment.
- App entry → Base page: loads · Entry point wires shared page behavior.
- App entry → DC test: routes · App exposes the DC test page.
- App entry → EOS upload: routes · App exposes the EOS upload page.
- App entry → Metrology: routes · App exposes the metrology page.
- App entry → Visual inspect: routes · App exposes the visual inspection page.
- Base page → DC test: shared with · Common base behavior is reused by the page.
- Base page → EOS upload: shared with · Common base behavior is reused by the page.
- Base page → Metrology: shared with · Common base behavior is reused by the page.
- Base page → Visual inspect: shared with · Common base behavior is reused by the page.
- DC test → ITkdb: integrates · DC test workflow interacts with ITkdb.
- DC test → ITkpd: integrates · DC test workflow interacts with ITkpd.
- EOS upload → EOS: uploads to · Upload workflow pushes artifacts to EOS.
- EOS upload → ITkdb: integrates · Upload workflow references ITkdb data.
- Metrology → ITkdb: integrates · Metrology workflow reads or writes ITkdb data.
- Metrology → ITkpd: integrates · Metrology workflow references ITkpd data.
- Visual inspect → ITkdb: integrates · Visual inspection workflow reads or writes ITkdb data.
- Visual inspect → ITkpd: integrates · Visual inspection workflow references ITkpd data.
- ITkdb creds → ITkdb: authenticates · Access codes are injected at runtime for ITkdb access.
- App entry → Static assets: uses · The UI consumes shared static resources.