antonioscalaunina/pyANTI-FASc: User-defined rake & EFSM20 example

🆕 New Feature: Flexible Rake Input and Database-Driven Fault Example

This release introduces full support for user-defined rake values, allowing either a single constant value or a CSV input per fault cells. The code automatically validates input values and provides fallback to a default rake of 90° if needed, ensuring robust handling of diverse scenarios.

✨ Highlights

Users can now specify rake as a single number or as a CSV file with per-cell values
Automatic validation of rake values, with warnings for invalid or unsupported formats
Default rake fallback (90°) for missing or incorrect inputs
Added a practical example using a fault whose geometry and discretization are directly selected from the EFSM20 – European Database of Seismogenic Faults (https://www.seismofaults.eu/efsm20)
Demonstrates how to integrate database-driven fault configurations into your workflow

🧩 Quick Start

Edit config.json to define a rake value (single number or CSV file)
Run the PyANTI-FASc pipeline as usual
The EFSM20 example is fully detailed [here](https://github.com/antonioscalaunina/pyANTI-FASc/blob/main/Example2_Mediterranean.md) for immediate testing

🧠 Notes

Invalid or missing rake inputs automatically default to 90°
The EFSM20 example illustrates realistic fault setups, useful for both testing and production scenarios and shows the full interoperability with the EFSM20 meshes service
Fully compatible with previous pipeline workflows

✅ Benefits

Greater flexibility in defining fault slip directions
Direct integration with a curated European fault database
Robust error handling for input inconsistencies
Streamlined example to get started quickly

💡 In short: With this release, PyANTI-FASc allows users to control rake input precisely and leverages realistic fault geometries as they can be obtained from EFSM20 — making seismic modeling more flexible, realistic, and user-friendly.