Community & support

H2sim grows through conversations between users, researchers, and developers. Ask the maintainers a question, share a storage example, or work through a modeling idea together in GitHub Discussions.

Join the H2sim community ↗

Find your conversation

Questions & answers

Ask about installation, thermodynamics, microbial reactions, PHREEQC coupling, or adapting an example. Maintainers and other users can reply; helpful answers can be marked so future users can find them.

https://github.com/sintefmath/h2-sim/discussions/categories/q-a
Developer conversations

Discuss equations, solver behavior, coupling strategies, documentation, and contributions in the General category. Link to code or a pull request when discussing a specific implementation.

https://github.com/sintefmath/h2-sim/discussions/categories/general
Ideas & requests

Propose capabilities, benchmarks, notebooks, and useful comparisons. Explain the storage question you want to investigate.

https://github.com/sintefmath/h2-sim/discussions/categories/ideas
Examples & results

Share a simulation, figure, tutorial, or application of H2sim. Include enough context for others to understand your setup.

https://github.com/sintefmath/h2-sim/discussions/categories/show-and-tell

You can read discussions without an account. Sign in to GitHub to start a conversation or reply. Posts are public, and replies are asynchronous. The Talk to the team button in the corner of each documentation page provides quick access to the same conversations.

Ask a useful question

Describe what you are trying to simulate, the example or workflow you used, and what you expected to happen. For a technical problem, include your H2sim revision, MATLAB and MRST versions, the error message, and a small code snippet when possible. Share only files and data you are allowed to make public.

Ask a question ↗

Report a reproducible bug in the bug-report form. Use Discussions for questions and open-ended conversations; link the two when a discussion identifies a code change.

Stay involved

Follow Announcements for release and project updates. To receive discussion notifications, use Watch → Custom → Discussions on the repository and choose the notifications that suit you.

Developers can use the same categories to coordinate changes and invite feedback. Keep implementation decisions alongside the relevant issue or pull request so the code review retains that context.