Author Topic: Reaction forces using parFEAP  (Read 10372 times)

JReinoso

  • Jr. Member
  • **
  • Posts: 15
Reaction forces using parFEAP
« on: July 24, 2024, 06:26:19 AM »
Dear All,

I am attaching here the following files:

- Ishear, where I define the geometry, material, BCs and parameters for the paralelization of the problem. I am using 8 tasks.
- solve.shear, where I define the solution of the problem. In here, I am indicating that I want to write a file with the reaction forces from the x-coordinate of the node located in the right top corner of the specimen.


When running this problem in parFEAP I am getting eight different .rea files with eight different values for the reaction force. In order to find out which one is the correct, I have to open the .vtu file in Paraview to check the task to which the node of interest is associated with. For example, if I see that the node is contained in the 5th partition, the file with the correct values is Pshear_0005a.rea.

Here is the problem, we are trying to automatize this process and we find that by having one correct and seven wrong .rea files may jeopardize this process. Therefore, I ask: is there any way to get rid of the extra .rea files without having to do the time consuming operation of checking in Paraview which one is the correct? 

Many thanks in advance. Best regards,
JReinoso.
« Last Edit: July 25, 2024, 12:32:05 AM by JReinoso »

wklausler

  • Jr. Member
  • **
  • Posts: 27
Re: Reaction forces using parFEAP
« Reply #1 on: July 24, 2024, 07:36:20 AM »
One approach would be to write a script that scans the partition input files, e.g. Ishear_000x, for the desired coordinate.

Alternatively, if your problem permits, you could use a custom, simple domain decomposition, e.g. cutting a cube into 8 partitions, and you know a priori which partition contains the nodes of interest.

FEAP_Admin

  • Administrator
  • FEAP Guru
  • *****
  • Posts: 993
Re: Reaction forces using parFEAP
« Reply #2 on: July 26, 2024, 02:49:46 AM »
Are you seeing that the desired node is being split across partitions? Or is it that you are finding empty files.