Ansys Hfss Full Form

[Eliecer Brathwaite]

I am trying to export each time step of my analysis (available as rst file) into the VTK format using a python script and ansys.dpf.core. I don't want to save the whole model, but only a selection of elements, which I have as named_selection. This seems to work in general with my script (see below).

The problem I have is that the stress tensor is not written for some reason. It doesn't matter if I write it into fields1 or fields2. I would also like to export other results (e.g. total strain) but the operator only has two variables for fields. Is there a way to save more than two results?

Finally, I would like to assign a name to the results. At the moment the result of the displacement is called e.g. "3_displacement_1.s_()" in the first time step, "3_displacement_2.s_()" in the second time step and "3_displacement_3.s_() in the third time step. Can I rename the result so that the displacement in each time step is called "displacement" or "displ"?

The vtk_export operator only allows two fields ( _export.html?highlight=vtk#module-ansys.dpf.core.operators.serialization.vtk_export). The way to go here will be to export one vtk file per result that you want to export.

Hi @Sven Lohmann , after checking with the dev team they confirmed that vtk_export() does not support ElementalNodal results (as you have experienced). However you can look into vtu_export that should be able to do that.

Hi @Sven Lohmann, welcome to the forum! @Pernelle Marone-Hitz is correct concerning the code formatting. I've edited your post for now, to change the code to a code block, although I think you still need to fix the indentation to get the code highlighting to work properly.

Thanks for adjusting the code. I have tweaked the code block further, however, it seems that it is not formatted properly until the comments are removed completely. After a #, all lines that come after that seem to be interpreted as comments.

To obtain the files needed to follow this tutorial, click on the Job Setup link below and clone the job hosting the file. Next, click the Save icon to have a copy of the files in your Rescale cloud files.

NOTE : Although you can run this job directly, to continue with this tutorial do not submit it directly. We are cloning the job in order to import the simulation input file ansys-hfss-electronics-example.aedtz into your account. You can also obtain the results of the job by clicking on Get Job Results.

If you have an archived simulation .aedtz file in your local environment ready for batch submission, feel free to skip the next few sections. You can go ahead and begin the batch submission section. Or if you want to just create the packed .aedtz from the ANSYS HFSS GUI, you can skip to this section before going on to batch submission. Otherwise, please continue:

Since we have prepared our simulation and uploaded the file back to the Rescale Cloud, we are done using our ANSYS Electronics GUI for the time being. We can now shutdown this Desktop instance. You can choose to keep the instance running to perform post-processing after the simulation is completed.

Additional Guide: Generally, HFSS workflows are very memory bound, so it is recommended to use high memory coretypes such as, Zinc or Melanite for your workflows. If you discover that during frequency sweeps the memory usage is low, then switch to a lower memory coretypePre-configured and optimized architectures for different HPC... More such as Emerald.

3a8082e126