🌐 English|한국어

Troubleshooting Guide

This guide provides solutions to common problems and errors you may encounter while using Modan2.

Where Modan2 Keeps Your Files

Several problems below come down to a file being missing or unwritable, so it helps to know where things are. ~ is your home folder (for example C:\Users\<you> on Windows).

What

Where

Database

~/PaleoBytes/Modan2/Modan2.db

Images, 3D models

~/PaleoBytes/Modan2/data/

Log files

~/PaleoBytes/Modan2/logs/

Backups

~/PaleoBytes/Modan2/backups/

Preferences

your OS settings folder (see below)

Installation Issues

Application Will Not Start

Windows

  • Windows Defender or SmartScreen may block the unsigned installer. Choose “More info” → “Run anyway” if you trust the source.

  • If the installer itself will not run, check that you extracted it from the downloaded ZIP first — running it from inside the archive can fail.

macOS

  • On first launch, right-click the app and choose “Open” to get past the Gatekeeper warning for unsigned applications.

Linux

  • Make sure the AppImage is executable: chmod +x Modan2-Linux-*.AppImage

  • If it exits complaining about FUSE, either install it (sudo apt-get install libfuse2 on Ubuntu/Debian) or run it with --appimage-extract-and-run.

Note

Only the Windows build is well tested. If the macOS or Linux package fails in a way not covered here, please report it on the issues page.

Permission Issues

Problem: “Permission denied” when opening the database or saving files

Windows Solution:

  1. Right-click Modan2.exe → “Run as administrator” (not recommended for normal use)

  2. Or change folder permissions:

    • Right-click the folder → Properties → Security

    • Ensure your user has “Full control”

Linux/macOS Solution:

# Check permissions
ls -la ~/PaleoBytes/Modan2

# Fix permissions if needed
chmod -R u+rw ~/PaleoBytes/Modan2

Problem: Settings not saving

Preferences are written when the application exits, to your operating system’s settings folder:

Platform

Location

Windows

%LOCALAPPDATA%\PaleoBytes\Modan2\preferences.json

macOS

~/Library/Application Support/PaleoBytes/Modan2/preferences.json

Linux

~/.config/PaleoBytes/Modan2/preferences.json

Solution:

  1. Check write permissions on that directory

  2. Delete a corrupted settings file to regenerate defaults — quit Modan2 first:

    # Windows (PowerShell)
rm "$env:LOCALAPPDATA\PaleoBytes\Modan2\preferences.json"

# macOS
rm ~/Library/Application\ Support/PaleoBytes/Modan2/preferences.json

# Linux
rm ~/.config/PaleoBytes/Modan2/preferences.json

Database Issues

Database File Corrupted

Problem: “Database is locked” or “Database disk image is malformed”

Symptoms:

  • Cannot open Modan2

  • Error messages about database

  • Data not saving

Solution 1: Close other instances

Ensure no other Modan2 processes are running:

# Windows
tasklist | findstr Modan2
# If found: taskkill /F /IM Modan2.exe

# Linux/macOS
ps aux | grep Modan2
# If found: kill <pid>

Solution 2: Backup and restore

# 1. Locate database
# Database: ~/PaleoBytes/Modan2/Modan2.db

# 2. Make backup
cp Modan2.db Modan2.db.backup

# 3. Try SQLite repair
sqlite3 Modan2.db "PRAGMA integrity_check;"

# 4. If corrupted beyond repair, restore from backup
cp Modan2.db.backup Modan2.db

Solution 3: Export and reimport

If you have a recent backup:

  1. Use backup database

  2. Export all datasets as JSON+ZIP

  3. Create new database (delete Modan2.db)

  4. Import datasets from JSON+ZIP

Cannot Access Database

Problem: “Unable to open database file” error

Causes:

  • Database file missing

  • Incorrect permissions

  • Disk full

  • File locked by another process

Solution:

  1. Check file exists:

    # Linux/macOS
ls -la ~/PaleoBytes/Modan2/Modan2.db

  2. Check disk space:

    # Linux
df -h ~

# Windows (PowerShell)
Get-PSDrive C

  3. Create directory if missing:

    mkdir -p ~/PaleoBytes/Modan2

  4. Let Modan2 create new database:

    • Start Modan2

    • New database created automatically

    • Import data from backups

Data Loading and Import Issues

Import File Format Not Recognized

Problem: “Unknown file format” or “Failed to import” error

Supported formats:

  • Landmark data: TPS, NTS, X1Y1, Morphologika, JSON+ZIP

  • 3D models: OBJ, PLY, STL

  • Images: JPG, PNG, BMP, TIF

Solution:

  1. Verify file format:

    • Check file extension matches content

    • Open in text editor to verify format

  2. TPS file issues:

    # Valid TPS format
LM=5
100.5 200.3
150.2 180.9
...
ID=specimen1
IMAGE=path/to/image.jpg

    Common issues:

    • Missing LM= line

    • Incorrect coordinate format

    • Missing ID= or IMAGE= lines

  3. Try different format:

    • Convert to TPS using tpsUtil

    • Or use Morphologika format

Missing Data After Import

Problem: Objects imported but no landmarks visible

Causes:

  • Landmark coordinates all zero

  • Incorrect dimension (2D vs 3D)

  • Scale mismatch

Solution:

  1. Check coordinates in table:

    • Open object dialog

    • View landmark table

    • Verify non-zero coordinates

  2. Check dimension:

    • Dataset should match file (2D/3D)

    • Recreate dataset with correct dimension

  3. Check scale:

    • Landmarks may be outside viewing range

    • Try “Fit to View” or zoom out

    • Check coordinate values are reasonable

Image/Model Not Loading

Problem: “Failed to load image” or “Model file not found”

Solution:

  1. Check file paths:

    • Image/model paths stored in database

    • If files moved, update paths

    • Use relative paths when possible

  2. Verify file integrity:

    # Check file size
ls -lh image.jpg

# Try opening in another program
# Images: Image viewer
# 3D models: MeshLab, Blender

  3. Supported formats:

    • Images: JPG, PNG, BMP, TIF (RGB or grayscale)

    • 3D models: OBJ, PLY, STL (text or binary)

  4. Re-attach files:

    • Right-click object → Properties

    • Attach image/model again

    • Browse to correct file

Analysis Errors

PCA/CVA/MANOVA Fails

Problem: Analysis fails with error message

Common causes:

  1. Not enough objects:

    • PCA: Need at least 3 objects

    • CVA/MANOVA: Need at least 2 groups with 3+ objects each

  2. Missing landmarks:

    • Some landmarks marked as missing

    • Not enough complete configurations

    • Solution: Estimate missing landmarks or exclude objects

  3. No grouping variable (CVA/MANOVA):

    • Need categorical variable for groups

    • Solution: Add grouping variable to objects

  4. Insufficient variation:

    • All objects identical or nearly identical

    • Solution: Check data quality

Solution:

  1. Check object count:

    • Select dataset

    • View object count in status bar

    • Ensure sufficient objects

  2. Check for missing data:

    • Review objects for missing landmarks

    • Use “Estimate Missing” feature or exclude

  3. Verify grouping variable:

    • CVA/MANOVA require categorical variable

    • Create variable in dataset dialog

    • Assign values to objects

Procrustes Alignment Issues

Problem: “Procrustes failed” or incorrect alignment

Causes:

  • Collinear landmarks (all on one line)

  • Insufficient landmarks (< 3 for 2D, < 4 for 3D)

  • All landmarks at same position

  • Scale issues

Solution:

  1. Check landmark quality:

    • View objects in viewer

    • Ensure landmarks properly distributed

    • No duplicates at same position

  2. Try different method:

    • Try Bookstein registration (needs a baseline on the dataset)

    • Or try Resistant Fit, which resists a few badly-placed landmarks

  3. Check for outliers:

    • Some objects very different from others

    • May cause alignment issues

    • Try excluding outliers

Analysis Results Look Wrong

Problem: Unexpected PCA/CVA results

Possible causes:

  • Incorrect Procrustes method

  • Wrong grouping variable

  • Outliers affecting results

  • Missing landmarks not handled properly

Solution:

  1. Verify Procrustes settings:

    • Check which superimposition used

    • Try different method

  2. Check for outliers:

    • View PC score plots

    • Look for extreme points

    • Investigate unusual specimens

  3. Verify grouping:

    • CVA: Ensure correct grouping variable selected

    • Check group assignments

  4. Check sample size:

    • Small samples may give unstable results

    • Need larger sample for robust analysis

3D Visualization Issues

3D Viewer Black Screen

Problem: 3D viewer shows black screen or nothing visible

Solution:

  1. Reset view:

    • Double-click in 3D viewer

    • Or use View → Reset Camera

  2. Check OpenGL:

    # Linux - verify OpenGL working
glxinfo | grep "OpenGL version"

# Install if needed
sudo apt-get install mesa-utils libglu1-mesa

  3. Update graphics drivers:

    • Windows: NVIDIA, AMD, or Intel website

    • Linux: Use distribution’s driver manager

    • macOS: Use Software Update

  4. Check model loaded:

    • Verify 3D model file attached

    • Try different model

    • Check file is valid OBJ/PLY/STL

OpenGL Errors

Problem: “OpenGL error” or “Failed to initialize OpenGL context”

Linux Solution:

# Install OpenGL libraries
sudo apt-get install mesa-utils libglu1-mesa-dev \
  freeglut3-dev mesa-common-dev

# Test OpenGL
glxinfo | grep "OpenGL version"

Windows Solution:

  1. Update graphics drivers

  2. Try forcing software rendering (slower but works):

    set LIBGL_ALWAYS_SOFTWARE=1
Modan2.exe

macOS Solution:

  • OpenGL should work out of the box on macOS 10.14+

  • Update macOS to latest version if issues

Landmark Spheres Not Visible

Problem: Cannot see landmark spheres in 3D viewer

Solution:

  1. Increase sphere size:

    • Settings → Visualization → Landmark size

    • Increase value

  2. Check lighting:

    • Spheres may be too dark

    • Adjust lighting in settings

  3. Zoom in:

    • Spheres may be too small at current zoom

    • Scroll to zoom closer

  4. Check wireframe:

    • Wireframe may obscure spheres

    • Toggle wireframe visibility

Performance Issues

Application Slow to Start

Problem: Modan2 takes long time to start

Causes:

  • Large database

  • Many datasets/objects loaded

  • Disk I/O issues

Solution:

  1. Check database size:

    • Location: See FAQ

    • Large database (>1GB) may slow startup

  2. Optimize database:

    sqlite3 Modan2.db "VACUUM;"

  3. Move to SSD:

    • Database on HDD is slower

    • Move to SSD for better performance

  4. Reduce loaded data:

    • Close unused datasets

    • Archive old analyses

Slow Analysis or Visualization

Problem: Analysis takes very long or UI freezes

Expected performance:

  • 100 objects: < 1 second

  • 1000 objects: 1-5 seconds

  • 2000 objects: 5-15 seconds

If much slower:

  1. Check object count:

    • Select dataset → View object count

    • Verify within expected range

  2. Close other applications:

    • Free up RAM

    • Close web browsers

    • Stop background processes

  3. Check system resources:

    • Task Manager / Activity Monitor

    • Look for high CPU or memory usage

    • Close resource-heavy apps

  4. Simplify visualization:

    • Reduce polygon count for 3D models

    • Disable wireframes

    • Close object viewers not in use

Out of Memory Errors

Problem: “Out of memory” or crash with large datasets

Solution:

  1. Check RAM usage:

    • Task Manager / Activity Monitor

    • Ensure sufficient RAM available

  2. Close other applications:

    • Web browsers use lots of RAM

    • Close unnecessary programs

  3. Work with subsets:

    • Analyze smaller groups

    • Export subsets of data

  4. Upgrade RAM:

    • 4GB: Small datasets only

    • 8GB: Recommended for most work

    • 16GB+: Large datasets

UI and Display Issues

UI Elements Not Displaying Correctly

Problem: Buttons, menus, or dialogs appear garbled or cut off

Solution:

  1. Check display scaling (Windows):

    • Right-click desktop → Display settings

    • Set scaling to 100% or 125%

    • Restart Modan2

  2. Reset window geometry:

    • Delete settings file (see above)

    • Restart Modan2

    • Windows repositioned to defaults

Font Issues

Problem: Text appears too small or too large

Solution:

  1. Adjust system font size:

    • Windows: Settings → Display → Scale

    • macOS: System Preferences → Displays

    • Linux: Display settings in DE

  2. Application-specific (future):

    • Font size settings planned

    • Currently uses system fonts

High DPI Display Issues

Problem: UI elements tiny on 4K/high DPI displays

Solution:

  1. Enable high DPI scaling (Windows):

    • Right-click Modan2.exe → Properties

    • Compatibility → High DPI settings

    • Override scaling behavior

  2. Set the Qt scaling environment variable before launching Modan2:

    # Windows (PowerShell)
$env:QT_AUTO_SCREEN_SCALE_FACTOR=1

# Linux/macOS
export QT_AUTO_SCREEN_SCALE_FACTOR=1

    This is a Qt setting, not a Modan2 one; it must be set in the same shell you start the application from.

Advanced Troubleshooting

Collecting Debug Information

When reporting issues, include this information:

  1. System Information:

    • Your OS and its version (Windows: winver; macOS: sw_vers; Linux: lsb_release -a)

  2. Modan2 version:

    • Help → About Modan2

    • Note the version and build number, which also appear in the name of the package you downloaded

  3. Log files:

    • ~/PaleoBytes/Modan2/logs/ — attach the most recent one

Enabling Debug Logging

Start Modan2 with --debug for verbose logging. Launch it from a terminal (or a Windows shortcut with the flag appended) so you can also see any startup error printed there:

# Linux (AppImage)
./Modan2-Linux-v<version>-build<build>.AppImage --debug

# macOS
/Applications/Modan2.app/Contents/MacOS/Modan2 --debug

# Windows (PowerShell), from the installation folder
.\Modan2.exe --debug

View logs in real time:

# Linux/macOS
tail -f ~/PaleoBytes/Modan2/logs/*.log

# Windows PowerShell
Get-Content -Path "$env:USERPROFILE\PaleoBytes\Modan2\logs\*.log" -Wait

Other Startup Options

  • --db <path> — open a different database, useful for testing whether the problem is in your data or in the application

  • --config <path> — use a different configuration file, to rule out a bad setting without deleting your own

  • --no-splash — skip the splash screen

  • --lang <en|ko> — force the interface language

Common Error Messages

“Failed to connect to database”

Cause: Database file locked or inaccessible

Solution: See “Database Issues” section above

“Procrustes superimposition failed”

Cause: Insufficient or collinear landmarks

Solution: See “Procrustes Alignment Issues” section above

“Not enough objects for analysis”

Cause: Insufficient sample size

Solution:

  • PCA: Need at least 3 objects

  • CVA/MANOVA: Need at least 2 groups with 3+ objects each

“Invalid landmark count”

Cause: Object has wrong number of landmarks for dataset

Solution:

  1. Check dataset landmark count

  2. Verify object landmarks match

  3. Re-digitize object if needed

Getting Additional Help

If this guide doesn’t solve your problem:

  1. Check FAQ:

    Quick answers to common questions

  2. Check GitHub Issues:

    https://github.com/jikhanjung/Modan2/issues

    Search for similar problems - they may already be solved

  3. Create New Issue:

    Include:

    • Operating system and version

    • Modan2 version and build number

    • Error message or description

    • Steps to reproduce

    • Log files (see “Collecting Debug Information” above)

  4. GitHub Discussions:

    For questions and general discussion:

    https://github.com/jikhanjung/Modan2/discussions

  5. Email Support:

    Contact: jikhanjung@gmail.com

    (Please try above resources first)

Known Issues and Limitations

Current Limitations

  1. Semi-landmark curves are 2D only:

    • Curve tracing is available for 2D specimens; 3D curve tracing is not implemented yet

    • Semi-landmarks are not slid during Procrustes alignment

  2. Testing coverage by platform:

    • Only the Windows build is well tested

    • macOS builds are not code-signed (first launch requires manual approval)

    • The Linux AppImage may need FUSE installed

  3. GUI only:

    • There is no batch/headless mode; the startup options exist to configure a normal GUI session, not to run analyses without one

  4. Language:

    • English and Korean interfaces are available

    • Some newer dialogs (notably Curve mode) are still English-only in the Korean interface

Planned Improvements

See the CHANGELOG and GitHub milestones for planned features:

  • 3D semi-landmark curve tracing

  • Sliding semi-landmarks during alignment

  • Image-assisted landmark suggestion

  • Better cross-platform support

Contributing

Found a bug or have suggestions? Contributions welcome!

See CONTRIBUTING.md for detailed contribution guidelines (when available).