How rishik2007-sudo/bioactive-ps-project works
This is a compound-catalog and bioactivity-prediction application: users submit a SMILES structure and receive an active/inactive COX-2 prediction with confidence and molecular descriptors; the API records prediction history. A catalog API supports browsing and editing compounds, categories, and health checks. The backend initializes its database and starter catalog at startup. The README describes a Streamlit deployment, but the tree instead contains a separate frontend; its runtime connection to the API is not shown, so that link is marked unverified.
Main entry points: database.py SQL database access · predict.py Prediction endpoint · main.py FastAPI application · router.py API router
Components 15
User interface
- Web interface
Frontend/script.js
API orchestration
- FastAPI application
Backend/app/main.py - API router
Backend/app/api/v1/router.py - Health endpoint
Backend/app/api/v1/endpoints/system.py - Application settings
Backend/app/config.py
Prediction workflow
- Prediction endpoint
Backend/app/api/v1/endpoints/predict.py - Descriptor and prediction service
Backend/app/services/prediction.py - Trained XGBoost model
Backend/models/xgb_cox2.joblib - Prediction schemas
Backend/app/schemas_prediction.py
Catalog and persistence
- Compound catalog endpoints
Backend/app/api/v1/endpoints/compounds.py - Compound schemas
Backend/app/schemas.py - Catalog and history models
Backend/app/models.py - SQL database access
Backend/app/database.py - Starter catalog seeding
Backend/app/seed.py
Other components
- Molecule researcher
Connections 21
- Molecule researcher → Web interface: enters SMILES
README.md - Web interface → FastAPI application: uses API
- FastAPI application → API router: mounts routes
Backend/app/main.py - FastAPI application → SQL database access: initializes schema
Backend/app/main.py - FastAPI application → Starter catalog seeding: seeds catalog
Backend/app/main.py - API router → Health endpoint: registers route
Backend/app/api/v1/router.py - API router → Compound catalog endpoints: registers routes
Backend/app/api/v1/router.py - API router → Prediction endpoint: registers route
Backend/app/api/v1/router.py - Health endpoint → Application settings: reads settings
Backend/app/api/v1/endpoints/system.py - SQL database access → Application settings: reads settings
Backend/app/database.py - Prediction endpoint → Descriptor and prediction service: requests prediction
Backend/app/api/v1/endpoints/predict.py - Prediction endpoint → Prediction schemas: validates and returns
Backend/app/api/v1/endpoints/predict.py - Descriptor and prediction service → Trained XGBoost model: loads model
Backend/app/services/prediction.py - Prediction endpoint → Catalog and history models: records history
Backend/app/api/v1/endpoints/predict.py - Prediction endpoint → SQL database access: queries and writes
Backend/app/api/v1/endpoints/predict.py - Compound catalog endpoints → Compound schemas: validates responses
Backend/app/api/v1/endpoints/compounds.py - Compound catalog endpoints → Catalog and history models: queries and edits
Backend/app/api/v1/endpoints/compounds.py - Compound catalog endpoints → SQL database access: queries and writes
Backend/app/api/v1/endpoints/compounds.py - Starter catalog seeding → Catalog and history models: creates compounds
Backend/app/seed.py - Starter catalog seeding → SQL database access: commits seed data
- Catalog and history models → SQL database access: maps tables
Backend/app/models.py