[META] PyMAPDL ROADMAP

[germa89]

This issue covers the PyMAPDL roadmap, and as such, it will be updated constantly.

Warning

⚠️ Disclaimer: No Guarantee of Resolution or Deadlines
This roadmap is for informational purposes only. There is no guarantee that the issues listed here will be resolved by the specified deadlines—if at all. Priorities may shift, and timelines are subject to change.
However discussion about priorities is welcomed. If you have any suggestion about the roadmap you can leave your comment in this issue. If your comment is about an specific issue or theme, you can comment any of the relevant issues.

ROADMAP

Spring 2025: DPF

From now, until 23th June.
We are currently working on DPF integration.

• MAPDL container improvement process https://github.com/ansys-internal/mapdl-docker-image-builder/pull/140
• MAPDL-DPF docker image:
  • Add it to the workflow ci: adapting workflow for new docker container #3805
  • Test MacOS support: Build docker image within macos #3581
• Fix DPF support on CICD.
  • ci: adding dpf testing to cicd #3852
  • Including DPF example: Removed DPF CDB example because unknown failure #3486
• Replace PyMAPDL-Reader by DPF
  • Replace main features on backend: feat: using dpf instead of reader in "results" module #1300
  • Replace mesh object
  • Replace element_solution_data
• Decide what to do with ans_to_vtk functionality from the reader (it is also in DPF). Related to Avoid mapdl.amesh in mapdl.aplot #3613
• Implement beam operators from MAPDL-GUI.

Pre-Summer 2025: PyMAPDL

From 23th June to 4th July.
Short sprint (2 weeks) focus on developer tools.
I should consider to extend it more, two weeks seems not enough for all these issues plus other hot fix.

• Implement PYMAPDL_DEBUG env var #3347
• document developer tools #3510
• Implement a function which helps debugging #2703
• Better error handling #2822
• [FEAT] Lines transfering should not depend on the IGES format, since it can generate slighly diferent plotting. #3811 [Optional] This might require server changes.
• TBD. General issues cleanup in those 2 weeks.
• Add a docker launcher. So we can spawn and connect to MAPDL instances.

Summer 2025: HPC

From 7th July to 19th September

• Finishing PyMAPDL launching MAPDL instances on remote HPC clusters: feat: adding support to launch MAPDL on remote HPC clusters #3713
• Actual CICD testing on cluster
• Better documentation with examples.
• Support for other types of clusters: LSF first.

Pre-autumn 2025: PyMAPDL

From 22nd September to 3rd October
Short sprint (2 weeks) to fix general PyMAPDL bugs

• TBD. General issues cleanup in those 2 weeks.

Autumn 2025: MAPDL gRPC server

From 6th October to 23rd December

• Evaluate what to do with the MAPDL database module. v251 database module crashes #3248 (comment)
• Implement session ID: Performance decline during loops after update to newer version of apdl-mapdl-core #2608
• Implement gRPC methods for array retrieval: API method to transfer arrays to the MAPDL instance #1038
• Transfer areas to avoid remeshing during APLOT: Avoid mapdl.amesh in mapdl.aplot #3613
• Study some of the gRPC issues and consider improvements: [SUMMARY] MAPDL features/bugs implementation list #2715
• Implement gRPC methods for variables (VGET) retrieval: Add mapdl.variables for variables. #2021

Themes

HPC theme

Reference: #3467

DPF theme

Reference: #1298

MAPDL gRPC theme

Reference: #2715