This document tracks all known issues in the Genesis-Sphere project that need to be addressed.
Problem: Athena rejects certain boundary condition types that are specified in input files.
Files Affected:
time_density_spherical.intime_density_spherical_fixed.in- Other
.infiles with invalid boundary conditions
Error Message: FATAL ERROR related to boundary conditions
Solution: Use only valid boundary conditions supported by your Athena build:
reflecting- Working in most buildsoutflow- Appears to work in some configurationspolar_wedge- For spherical coordinatesperiodic- Works in most cases
Problem: Athena simulations complete but don't produce output files
Files Affected: All simulation output files
Symptoms: No .out* or .vtk files are generated despite successful execution
Solution:
- Check that output directories exist and are writable
- Verify the
-oparameter has no space (e.g.,-ooutput_namenot-o output_name) - Add explicit
out_dirparameter in the<output1>block
Problem: Some simulations fail to initialize or complete
Files Affected:
time_density_cartesian.intime_density_spherical.in
Error Symptoms: Docker exits without proper error message
Solution:
- Include required parameters for the chosen problem generator
- For
blastproblems, ensureradius,center_x1, etc. are defined - For custom problems, add all required parameters
Problem: Windows path mounting in Docker sometimes fails
Files Affected: Docker execution scripts
Error Symptoms: "Cannot mount volume" or "No such file or directory"
Solutions:
- Use absolute paths:
-v "C:\full\path\to\directory:/workspace" - Replace backslashes with forward slashes
- Try using Docker Desktop settings to share drives
Problem: Files created inside Docker containers have incorrect permissions
Files Affected: Output files from Docker runs
Symptoms: Cannot modify or delete files after Docker creates them
Solution:
- Add appropriate user mapping to Docker run command
- Fix permissions after creation:
chmod -R 777 output_directory
Problem: Input files missing required parameters for the chosen problem
Files Affected:
time_density_spherical.in- Other
.infiles
Error Symptoms: "Required parameter not found" or silent failures
Solution: Ensure all required parameters are present for each problem type:
- For
blast: Addradius,center_x1,center_x2, and pressure parameters - For
time_density: Add matching parameters to meet expectations
Problem: Some input files specify invalid time integrators
Files Affected: Multiple .in files
Error Symptoms: "Invalid integrator" or "Unknown integrator"
Solution: Use only valid integrators in the <time> block:
rk2- 2nd-order Runge-Kutta (recommended)- Instead of
vl2userk2
Problem: Analysis scripts fail due to missing VTK library
Files Affected:
athena_analysis.pyfixed_analysis.py
Error Symptoms: ImportError for VTK module
Solution:
- Install VTK:
pip install vtk - Add error handling for missing VTK
- Use conditional imports
Problem: Analysis scripts sometimes fail to read data files
Files Affected:
- Analysis scripts
- Output data files
Error Symptoms: "Error reading file" or KeyError for missing data
Solution:
- Add better format detection and error handling
- Support multiple file formats (VTK, HDF5, text)
- Standardize on a single output format
Problem: Scripts assume different directory structures
Files Affected: Multiple scripts and batch files
Symptoms: File not found errors, incorrect paths
Solution:
- Standardize directory structure
- Use relative paths consistently
- Add configuration options for output directories
Problem: Dependencies aren't consistently managed across scripts
Files Affected: All Python scripts
Symptoms: Missing module errors, version conflicts
Solution:
- Create and document a consistent environment setup
- Use virtual environments
- Maintain a single comprehensive requirements.txt
Problem: Documentation doesn't cover all error scenarios
Files Affected: README.md and other docs
Symptoms: Users struggle to resolve errors
Solution:
- Add troubleshooting section to README
- Document common errors and solutions
- Create example scripts with validated configurations
- Invalid Boundary Conditions - This is preventing simulations from running
- Missing Required Parameters - Causes silent failures in simulations
- Docker Path Mounting - Prevents Docker workflows from functioning
- Missing Output Files - Makes analysis impossible even when simulations run
- VTK Library Dependencies - Prevents analysis scripts from functioning
- Create a minimal working input file with validated parameters and boundary conditions
- Test Docker workflows with absolute paths to ensure consistent mounting
- Add better error handling to analysis scripts
- Document valid parameter combinations for each problem type
- Create a troubleshooting guide with common error messages and solutions