mapdl.result.filename has mixture of \ and / (windows)
See original GitHub issueI was looking for an easy way to get an pymapdl
result into dpf
(see issue). A possible solution would be mapdl.result.filename
, but it seems somewhat broken. I get something like:
d:/Al_cantilever/stat\AlCantilever.rst
As a general remark, maybe its possible to use pathlib
instead of str
-paths (-> discussion at #645)?
Issue Analytics
- State:
- Created 2 years ago
- Comments:6 (6 by maintainers)
Top Results From Across the Web
Incompatible with numpy==1.21.1 on Windows #1223 - GitHub
On Windows with Python 3.9 and numpy==1.21.1 , there seems to be a binary incompatibility between numpy and ansys-mapdl-reader .
Read more >10 Things Every ANSYS Mechanical APDL (MAPDL) User ...
Displaying More than 9 Results Contours 6. CNCHECK 7. Copy and Paste into Input Window 8. /EOF for Input File Debugging 9. Use...
Read more >3.2. Solution Output - BME-MM
The output file is viewable via the GUI. The database and results file data can be postprocessed. The following solution-output topics are available:....
Read more >ansys-mapdl-reader - PyPI
Pythonic interface to files generated by MAPDL. ... As the geometry of the model is contained within the result file, ... Animating a...
Read more >result files - Ansys Learning Forum
nI am creating input file, the input file is taken into cluster( linux) ... solution with 10 CPU's, then this creates a result...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I should have clarified. I meant we can’t fix it in this repo*, since the changes need to happen in the other one, but otherwise yes.
We can fix it there as needed. It’s an upstream package that we modify and it grows (or changes) in tandem with
ansys-mapdl-core
.That’s probably the best solution since it’s future focused rather than the patchwork of fixes we currently have. Recommend using
pathlib.Path
withinansys-mapdl-reader
first, then fixing it here.