added deprecated message for k3d visualisation

[kzqureshi]

PR Type

documentation

---

Description

• Added a deprecation message in the documentation for the k3d visualisation method, indicating it will be removed in future versions.
• Recommended using PyVista for field visualisation instead of k3d.

---

Changes walkthrough 📝

	Relevant files
Documentation	field-k3d-visualisation.ipynb Add deprecation notice for `k3d` visualisation method        docs/field-k3d-visualisation.ipynb Added a deprecation note for the k3d visualisation method. Suggested using PyVista as an alternative for field visualisation. +3/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

[github-actions]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[github-actions]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
Enhancement	Consolidate the deprecation notice and browser recommendation into a single paragraph for clarity Consider consolidating the deprecation notice and the browser recommendation into a single, concise paragraph to improve readability and emphasis on the deprecation. docs/field-k3d-visualisation.ipynb [9-11] -"**Note:** The visualisation method using `k3d` is deprecated and will be removed in future versions, please use `PyVista` for visualising fields instead.\n", -"\n", -"If you experience any problems in plotting with `k3d`, please make sure you run the Jupyter notebook in Google Chrome.\n" +"**Note:** The `k3d` visualisation method is deprecated and will be removed in future versions. Please use `PyVista` for visualising fields. If you experience any issues with `k3d`, ensure you are using Google Chrome.\n" Suggestion importance[1-10]: 7 Why: The suggestion improves readability and conciseness by combining related information into a single paragraph, which is beneficial for documentation clarity and user understanding.	7