Xenotools Workflow Setup

From Catcliffe Development
Revision as of 14:06, 2 November 2024 by XenoEngineer (talk | contribs) (Created page with "{{menuSymbioPoietrix}} <div style="float:right; width:425PX;"> __TOC__ </div> <div style="background-color:azure; border:1px outset azure; padding:0 20px; max-width:860px; margin:0 auto; "> = <big>'''workflow.readme.txt'''</big> = '''''XenoTools Quantum-Semantic Development Environment Setup Created by: XenoEngineer & Claude Last Updated: 2024-11-02 == Environment Setup== # Navigate to project root cd C:\Users\donem\Desktop\projects\python\xenotools   # Cr...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

SymbioPoietrix ∞  XenoEngineer's Guide to Quantum-Semantic Knowledge Evolution ∞  Quantum-Semantic Symbiopoiesis Initialization ∞  Xenotools Workflow Setup ∞  Quantum Test Data Generation Prompt ∞ 

workflow.readme.txt

XenoTools Quantum-Semantic Development Environment Setup
Created by: XenoEngineer & Claude
Last Updated: 2024-11-02

Environment Setup

# Navigate to project root
cd C:\Users\donem\Desktop\projects\python\xenotools
 
# Create/activate virtual environment (if not exists)
python -m venv venv
.\venv\Scripts\activate
 
# Verify activation - should see (venv) in prompt
(venv) C:\Users\donem\Desktop\projects\python\xenotools>


Dependencies Installation

# Install all required packages
pip install anthropic python-dotenv pyyaml pandas numpy matplotlib seaborn
 
# Verify package installation
pip list

Project Structure Creation

# Ensure directories exist
mkdir pipeline speak_specs mind_models
mkdir test_data test_output
 
# Create __init__.py files
type nul > pipeline\__init__.py
type nul > speak_specs\__init__.py
type nul > mind_models\__init__.py

Development Workflow

# Always work from project root with venv active
# After creating new modules:
pip install -e .
 
# Run tests from project root:
python pipeline/test_config.py
python pipeline/test_data_reader.py
python pipeline/test_visualizer.py

Common Issues & Solutions

  • If module not found: Check working directory and venv activation
  • If import errors: Verify pip install -e . after new modules
  • If file not found: Use absolute paths from project root
  • If test data missing: Create test_data directory first

Best Practices

  • Run all commands from project root
  • Keep venv active during development
  • Use relative imports within modules
  • Clean test data after runs
  • Update setup.py when adding dependencies

File Naming Conventions

  • Modules: lowercase with underscores
  • Classes: CamelCase
  • Test files: test_modulename.py
  • Config files: lowercase with dots

Git Commands (if using version control)

git add .
git commit -m "Meaningful commit message"
git push origin main