Project Group¶
Principal Investigator: Giovanni Castellazzi
Affiliations: Associate Professor in Solids and Structural Mechanics, DICAM — University of Bologna
Email: giovanni.castellazzi@unibo.it
Collaborators | Affiliations |
---|---|
Giovanni Castellazzi | Solids and Structural Mechanics, DICAM — University of Bologna |
Stefano de Miranda | Solids and Structural Mechanics, DICAM — University of Bologna |
Antonio Maria D'Altri | Solids and Structural Mechanics, DICAM — University of Bologna |
Francesco Ubertini | Solids and Structural Mechanics, DICAM — University of Bologna |
Nicolò Lo Presti | PhD Student, DICAM — University of Bologna |
Kaj Kolodziej | Master Student, University of Bologna |
Former Collaborators | |
Gabriele Bitelli | Geomatics, DICAM — University of Bologna |
Alessandro Lambertini | Geomatics, DICAM — University of Bologna |
Report a Problem / Bug¶
Preferred channel: GitHub Issues (recommended for tracking & transparency)
Alternative: Email support (for private data or access‑restricted material)
1) Via GitHub Issues¶
Recommended Method for Reporting Problems¶
The preferred way to report issues is via GitHub Issues, as it ensures transparency and allows for better tracking and collaboration. Follow the steps below:
- Navigate to the repository’s Issues page.
- Click New issue and select Bug report.
- Fill out the template, providing as much detail as possible (refer to the checklist below).
- Attach relevant files, such as screenshots, logs, or minimal datasets. If your data is sensitive, consider using the email option instead.
By using GitHub Issues, you help streamline the process and contribute to improving the project for everyone.
If your dataset is confidential, please do not upload it publicly. Instead, strip/obfuscate sensitive parts or use the email channel.
2) Via Email¶
In the case of private or urgent communications send an email to giovanni.castellazzi@unibo.it with subject:
[C2F4DT] Bug report: <short description>
Include the same checklist information below. You may attach files or share a secure link (e.g., institutional cloud drive).
Bug Report Checklist¶
Please provide the following to help us reproduce and fix the issue quickly:
- Summary
- Short, descriptive title.
-
What did you expect to happen? What happened instead?
-
Steps to Reproduce
- Step-by-step instructions.
-
Minimal files (e.g., a small VTK demonstrating the issue).
-
Screenshots / Videos
-
UI state, error dialogs, wrong rendering outcomes, etc.
-
Logs & Console Output
- Copy any text from the built-in Console or terminal.
-
If available, attach
_vtk_report/report.json
or similar validator outputs. -
Environment
- OS (Windows/macOS/Linux + version), Python version.
- Package versions:
pyvista
,vtk
,numpy
,matplotlib
,scipy
. -
GPU/driver info if rendering‑related.
-
Configuration
- Representation settings (Surface/Wireframe/etc.).
- Color by (Solid/PointData/CellData + vector component).
- LUT + invert, scalar bar on/off, edges visibility, opacity.
-
Any custom plugins or local modifications.
-
Frequency / Regression
- Does it happen always or intermittently?
- Did it appear after an update? Which version worked?
Example (Minimal) Issue Template¶
Optional: GitHub Issue Templates¶
To streamline reports, consider adding .github/ISSUE_TEMPLATE/
files to your repo:
.github/ISSUE_TEMPLATE/bug_report.md
.github/ISSUE_TEMPLATE/feature_request.md
Example bug_report.md
:
FAQ¶
Q: I found a bug while using a confidential dataset. How should I proceed?
A: Prefer the email channel. Provide a minimal, anonymized extract if possible, or share access privately.
Q: Where do I ask for new features or improvements?
A: Use GitHub Issues → Feature request to track discussion and prioritization.
Q: I’m offline and cannot reach GitHub.
A: Send an email to giovanni.castellazzi@unibo.it with the Bug Report Checklist filled in.
Thank you for helping improve C2F4DT! Your clear reports save everyone time and make the tool better for the community.