How lamalab-org/photocat-hte works
Project type and purpose
• This is a single‐language (Python) orchestration tool for running high-throughput photocatalysis experiments (HTE) using a Chemspeed AutoSuite, programmable power supply, and FireSting sensor. It also contains a data‐analysis pipeline for processing experimental results.
File structure
• Top-level directories:
• config – YAML definitions (experiments.yml, setup.yml, etc.)
• experiments – entrypoint “run.py” that kicks off the experiment loop
• src/photolooper – core library: hardware interfaces and experiment logic
• data – raw .app blobs captured from AutoSuite runs
• data_analysis – scripts and folders to parse raw data into CSV/JSON and generate visualizations
• Key files:
• setup.py – package installer
• src/photolooper/main.py – CLI entrypoint for the photolooper tool
• data_analysis/*.py – analysis pipelines
• External interfaces: Chemspeed AutoSuite program (reads/writes CSV), FireSting pH sensor, programmable power supply.
README for additional insights
• The flow:
a. Load setup.yml and experiments.yml
b. Configure hardware (ports, folders)
c. Launch AutoSuite program (external)
d. Run “python run.py” → Python code monitors/writes values_for_experiment.csv, loops based on “run” flag
e. Collects .app experiment output into data/
f. Separate data_analysis scripts parse those .app files into CSV/JSON and produce visualizations.
• Configuration Loader (YAML)
• Experiment Orchestrator (experiments/run.py + photolooper.main)
• Hardware Abstraction Layer (photolooper.firesting, .powersupply)
• AutoSuite External Controller (Chemspeed)
• File System Storage (raw .app files in data/, config files)
• Data Analysis Pipeline (data_analysis/*.py → CSV/JSON → plots)
1. Configuration Loader → Experiment Orchestrator
2. Experiment Orchestrator → Hardware Abstraction → Power Supply & FireSting Sensor
3. Experiment Orchestrator ↔ AutoSuite (via values_for_experiment.csv and .app files)
4. Raw .app files written to data/
5. Data Analysis Pipeline reads data/, writes processed CSV/JSON, then Visualizations
c. Architectural patterns / design principles:
• Modularization: separate packages for CLI, hardware drivers, experiment logic, and analysis
• File-based messaging: coordination with AutoSuite via a shared CSV file
• Config-first design: all runtime parameters come from YAML
d. Relevant technologies:
• Python 3, PyYAML (for config), pandas (in data_analysis, presumed), matplotlib/PDF for plots
• Chemspeed AutoSuite (external Windows program)
• FireSting pH sensor, programmable power supply (via serial ports)