Commit Graph

365 Commits

Author SHA1 Message Date
4282dcf080 More rearranging. 2015-10-06 16:55:13 +02:00
6bb64cd937 Hardly anything new. 2015-10-04 18:21:12 +02:00
c97f483f64 Shoving pieces of code back and forth. 2015-10-02 11:28:58 +02:00
1307dd7153 Some restructuring. 2015-10-01 22:08:16 +02:00
1ebaea53a1 Minor changes, far from being useful. 2015-09-30 19:36:09 +02:00
de96a638a3 Some files for new recurrenceCFD solver. Far from working. 2015-09-30 00:12:15 +02:00
8a97305e85 Added energyModel to handle heat transfer etc. 2015-08-22 11:53:12 +02:00
2ec3a3efe7 Included heat transfer between particles and fluid, thermal conductivity of fluid; 2015-08-21 12:49:30 +02:00
993af3bea9 Removed some unnecessary files. 2015-08-04 14:28:58 +02:00
892afa5105 Compressible CFD-DEM solver based on rhoPimpleFoam. No energy transfer between gas and particle phase yet. 2015-08-04 14:15:43 +02:00
bd4a11de47 fix generation of satellite points on sphere surface
integer division caused irregular gap; off-by-one error caused first set
of xySplit points to be at the same position
2015-04-13 10:40:56 +02:00
eaa75ad0b3 dataExchangeModel: fix potential memory leaks 2015-04-02 13:25:17 +02:00
0c66e15979 fix my own stupidity 2015-04-02 10:58:50 +02:00
6c07ee75c0 re-allocation: revert to original behaviour
The problem with allocateArray is that the base class dataExchangeModel
actually allocates new memory disregarding already allocated (and
populated) memory while derived classes like twoWayMPI and
twoWayMany2Many ultimately use realloc
2015-04-02 09:41:22 +02:00
47772ea9d4 use correct data type 2015-04-01 16:44:39 +02:00
e255c3c28e width of this array has nothing to do with maxCellsPerParticle_
This is effectively a 1D array, but there's no method to automatically
create a 1D array with the length of nParticles as there is for the 2D
case ...
2015-04-01 16:35:16 +02:00
4c5d63e966 remove unused calls of MPI_Comm_rank 2015-04-01 15:35:15 +02:00
46ca306ada re-allocation of memory part 2
first destroy already allocated memory, then allocate new memory
2015-04-01 15:24:09 +02:00
077e0ff8aa clean up namespace 2015-04-01 11:45:24 +02:00
fd3a6362bf re-allocation of memory
first destroy already allocated memory, then allocate new memory
2015-04-01 10:53:01 +02:00
7161d6f15f use correct data type
converting back and forth between double and integer may cause issues
2015-03-31 17:18:05 +02:00
e2343661bb reflect what OpenFOAM expects 2015-03-31 16:35:05 +02:00
d387a2117f use const word& instead of word in parameter list
oops .. here as well
2015-03-31 16:31:36 +02:00
ededde9190 MPI: (rank < size) is always true 2015-03-31 15:48:16 +02:00
851deae90b use const word& instead of word in parameter list 2015-03-31 15:34:56 +02:00
6ad466dcea remove extra semicolons 2015-03-31 15:08:50 +02:00
f5c277b1c7 formatting 2015-03-31 15:02:51 +02:00
87536c03fd reduce divisions 2015-03-31 14:57:07 +02:00
5246a1ec66 integer division 2015-03-31 14:52:32 +02:00
e5dfd4b4eb Simplified twoWayMPI
The code seems to be derived from the LAMMPS COUPLE library. The original COUPLE code
allowed using a subset of the global processors for the coupled code. Some fractions
of that code remained, but on their own don't make sense anymore. Since no additional
colors are assigned to processors, MPI_Comm_split effectively just duplicates the
global communicator, which can be easily done using MPI_Comm_dup.

The second simplification is that the code tried to limit IO to MPI rank 0. The filename
of the input script was read in by one MPI rank and then broadcasted to all other ranks.
While from the outside this seems to make sense from an MPI programmer standpoint, it does
not take the OpenFOAM implementation into account. IODictionary is already multi-processor
aware. Reading operations are done only on the master processor. This means the dictionary
is already in memory for each MPI processor at this point in time and lookup() is an
in-memory operation.
2015-03-31 11:36:31 +02:00
1f0efcae7f make the value that is set useable ... 2015-03-30 15:46:18 +02:00
78918f8831 using predefined constant 2015-03-30 15:31:18 +02:00
11632e0539 improve readability 2015-03-30 14:20:26 +02:00
3ee0bf41de remove temp variables / simplify 2015-03-30 14:17:35 +02:00
3ca84c7dea accidentially removed parenthesis 2015-03-27 14:47:16 +01:00
d697c7afe0 white space clean up 2015-03-27 13:11:34 +01:00
981a8390c6 be generous with comment characters 2015-03-27 13:11:04 +01:00
d786f9680f use constants from math.h 2015-03-27 10:17:52 +01:00
3c1e7ca6a5 fun with OpenFOAM data types
OpenFOAM Switches default to false ...
2015-03-26 17:56:06 +01:00
142d87252b usage of OpenFoam::List 2015-03-26 17:30:20 +01:00
81b8c9cdad you've got to slow down, yeah, yeah, yeah, slow down
pow() used at its best
2015-03-26 16:52:31 +01:00
d3a0036acf don't use pow() for squaring 2015-03-26 16:25:49 +01:00
29cc6d9d74 inheritance is cool, pointers to local objects not so much 2015-03-26 16:09:44 +01:00
343d1cba5b use const std::string& instead of std::string as parameter 2015-03-26 15:06:05 +01:00
8566c7eaa4 convert tabs to spaces 2015-03-26 14:49:18 +01:00
acf0673e38 simplify string operations & initialization 2015-03-26 14:48:21 +01:00
c60bf9bf80 clean up twoWayMPI allocate/destroy functions
just the way LIGGGHTS is doing it ...
2015-03-25 17:42:04 +01:00
f4501938ff just mpi gather no need to sum up 2015-03-25 16:29:23 +01:00
69d18478fd remove extra semicolons 2015-03-25 14:24:14 +01:00
a1d8c61241 merge with CFDEMcoupling-PUBLIC 2.9.0 2015-03-25 14:23:49 +01:00