Contact

FracSTAT is developed and maintained by a small academic team spanning several institutions. The best way to reach us depends on what you need — see the options below.

On this page

1. Bug Reports and Feature Requests
2. Authors and Email Addresses
3. Affiliated Institutions
4. Other Questions

1. Bug Reports and Feature Requests

For anything code-related — a bug, an unexpected calculation result, a crash, or a feature request for a future release — the fastest and most trackable route is to open an issue directly on the GitHub repository. Please include your operating system, the FracSTAT version, and, where possible, the steps needed to reproduce the issue (and a sample dataset, if the issue is data-specific and shareable).

2. Authors and Email Addresses

For citation requests, collaboration inquiries, or questions about the underlying methodology, you can reach any of the authors directly:

Name / Team	Email
FracSTAT Support	fracstat@gmail.com
Sachida Nanda Mahanta	sachida5908@gmail.com
Priyadarshi Chinmoy Kumar	chinmoy@wihg.res.in

Tip: if your question is specific to one of FracSTAT's three modules (Static, Dynamic, or Uncertainty Analyzer), mentioning that up front — and linking the relevant documentation page, e.g. Dynamic Mohr Tab — helps the team route your message to the right person faster.

3. Affiliated Institutions

Institution	Department / Location
DHSGSU	Department of Applied Geology, Dr. Harisingh Gaur Vishwavidyalaya, Sagar, M.P., India
WIHG	Wadia Institute of Himalayan Geology, Dehradun, India
University of Palermo	Department of Earth and Marine Sciences, Palermo, Italy
University of Bari	Department of Earth Science and Geo-Environment, Bari, Italy
INGV	Istituto Nazionale di Geofisica e Vulcanologia, Rome, Italy
CSIR-NGRI	National Geophysical Research Institute, Hyderabad, India

4. Other Questions

For questions about how your information is handled, see the Privacy Policy; for licensing and citation terms, see the License page; for the scope and limits of what FracSTAT's outputs can be used for, see the Disclaimer. Anything not covered by those pages is welcome as a GitHub issue or a direct email above.