You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Extracting displacements from d3plots that contain EP (electrophysiology) data fails for DPF servers 24R2 (and above). 24R1 is working (and also allows user to read EP results, although somewhat less conveniently through variable ids).
So far I haven't had issues when extracting displacements from d3plots that do not contain EP, so I suspect the issue is related to EP data being present.
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "d:\development\conda-envs\debug-dpf\lib\site-packages\ansys\dpf\core\dpf_operator.py", line 736, in eval
return self.outputs._outputs[0]()
File "d:\development\conda-envs\debug-dpf\lib\site-packages\ansys\dpf\core\outputs.py", line 75, in __call__
return self.get_data()
File "d:\development\conda-envs\debug-dpf\lib\site-packages\ansys\dpf\core\outputs.py", line 72, in get_data
return self._operator.get_output(self._pin, type_output)
File "d:\development\conda-envs\debug-dpf\lib\site-packages\ansys\dpf\core\dpf_operator.py", line 543, in get_output
internal_obj = type_tuple[1](self, pin)
File "d:\development\conda-envs\debug-dpf\lib\site-packages\ansys\dpf\gate\generated\operator_capi.py", line 422, in operator_getoutput_fields_container
raise errors.DPFServerException(sError.value)
ansys.dpf.gate.errors.DPFServerException: U:29<-lsdyna::d3plot::U:38<-error code 4:DPF error - runtime error: dpf core function call; the entry obj is not of type scoping
The above will work when you substitute "2024.1" for "2024.2" (should ofcourse be instlaled):
Moreover with 24R2 we can access EP data in an attribute-like way, however some results also contain invalid characters. For instance the attached d3plot has data fields where the name contains +, since this does not give a valid Python attribute name we won't be able to access this data in an attribute-like fashion:
print(model)
gives:
Available results:
...
- displacement: Nodal Displacement
- electrical_conductivity: Elemental Electrical Conductivity
- ep_transmembrane_pot: Nodal Ep Transmembrane Pot
- ep_extra_cell_pot: Nodal Ep Extra Cell Pot
- ep_intra_cell_pot: Nodal Ep Intra Cell Pot
- ep_ca2+_concentration: Nodal Ep Ca2+ Concentration
- ep_intra_cell_pot: Nodal Ep Intra Cell Pot
- ep_ca2+_concentration: Nodal Ep Ca2+ Concentration
The following would be invalid:
model.results.ep_ca2+_concentration
I have seen the same when history variable results are present - the attribute names contain [ and ] - in the d3plots (data not attached):
Available results:
...
- history_variablesihv__[1__27]: Elemental History Variables(ihv: [1, 27])
- displacement: Nodal Displacement
...
- ep_transmembrane_pot: Nodal Ep Transmembrane Pot
- ep_extra_cell_pot: Nodal Ep Extra Cell Pot
- ep_intra_cell_pot: Nodal Ep Intra Cell Pot
- ep_activ__time: Nodal Ep Activ. Time
- ep_ca2+_concentration: Nodal Ep Ca2+ Concentration
- : Nodal
mhoeijm
changed the title
Displacement operator throws an error for d3plot results with 24R2 (and up) when EP-data is present
Displacement operator throws an error when EP-data is present (24R2 and up)
Jan 6, 2025
Before submitting the issue
Description of the bug
Extracting displacements from d3plots that contain EP (electrophysiology) data fails for DPF servers 24R2 (and above). 24R1 is working (and also allows user to read EP results, although somewhat less conveniently through variable ids).
So far I haven't had issues when extracting displacements from d3plots that do not contain EP, so I suspect the issue is related to EP data being present.
@ayush-kumar-423, @PProfizi, @wenfengye, @KarimElHouari
Steps To Reproduce
The d3plot below contains EP results and should return 0 displacement for all time-steps (no mechanics involved).
data to reproduce: d3plot.zip
Gives me the following traceback:
The above will work when you substitute "2024.1" for "2024.2" (should ofcourse be instlaled):
Moreover with 24R2 we can access EP data in an attribute-like way, however some results also contain invalid characters. For instance the attached d3plot has data fields where the name contains
+
, since this does not give a valid Python attribute name we won't be able to access this data in an attribute-like fashion:gives:
The following would be invalid:
I have seen the same when history variable results are present - the attribute names contain
[
and]
- in the d3plots (data not attached):Which Operating System causes the issue?
Windows
Which DPF/Ansys version are you using?
Ansys 2024 R2
Which Python version causes the issue?
3.10
Installed packages
The text was updated successfully, but these errors were encountered: