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
"excerpt": "Dear all,\nI am trying to validate my fluid and structure mesh for the FSI1 case of cylinder-flap test. As the refinement of the fluid and structure mesh increases, it is difficult for implicit FSI coupling to converge. Therefore, my idea is to use a \u2026"
"excerpt": "Hello preCICE community,\nI am opening this topic in the hopes of following:\n\nIt works as guidance for future developers working on OF adapters\nGetting help on debugging OpenFOAM adapter or OF related things\n\n\nMy System:\nKubuntu 20.04 LTS\npreCICE v2.3\u2026"
"excerpt": "Common question: \u201cMy simulation crashed after hours of running, but my solvers already has stored restart files. Do I need to do anything special in preCICE?\u201d"
"excerpt": "Is preCICE indeed free software, or is it too good to be true?"
@@ -228,7 +228,7 @@
228
228
"views": 466,
229
229
"posts_count": 2,
230
230
"like_count": 0,
231
-
"excerpt": ""
231
+
"excerpt": "I always hear that monolithic coupling is the only way to go, as partitioned coupling introduces error. Is this correct?"
232
232
},
233
233
{
234
234
"id": 54,
@@ -240,7 +240,7 @@
240
240
"views": 507,
241
241
"posts_count": 2,
242
242
"like_count": 0,
243
-
"excerpt": ""
243
+
"excerpt": "Can the individual solvers run on two different platforms on two different machines in/out of a network?"
244
244
},
245
245
{
246
246
"id": 52,
@@ -252,7 +252,7 @@
252
252
"views": 511,
253
253
"posts_count": 2,
254
254
"like_count": 0,
255
-
"excerpt": ""
255
+
"excerpt": "Which code is executing the coupling iterations given that preCICE does not really have a centralized engine to orchestrate the simulation?"
"excerpt": "There are multiple OpenFOAM \u201cvariants\u201d, including openfoam.com, openfoam.org, and the early fork foam-extend. Which versions of them are compatible?"
280
280
},
281
281
{
282
282
"id": 43,
@@ -288,7 +288,7 @@
288
288
"views": 1003,
289
289
"posts_count": 3,
290
290
"like_count": 0,
291
-
"excerpt": ""
291
+
"excerpt": "Marta asked on the mailing list (March 28, 2019)\n\nI\u2019m using preCICE to couple two codes: the lattice Boltzmann code LUMIS and OpenFOAM. LUMIS has a time step 10 times smaller than OpenFOAM so during the coupling LUMIS subcycles before exchanging data\u2026"
292
292
},
293
293
{
294
294
"id": 29,
@@ -300,7 +300,7 @@
300
300
"views": 810,
301
301
"posts_count": 2,
302
302
"like_count": 0,
303
-
"excerpt": ""
303
+
"excerpt": "My solver offers adaptive mesh refinement.\nCan I use this with preCICE?"
304
304
},
305
305
{
306
306
"id": 38,
@@ -312,7 +312,7 @@
312
312
"views": 1115,
313
313
"posts_count": 3,
314
314
"like_count": 1,
315
-
"excerpt": ""
315
+
"excerpt": "A preCICE developer told me to try a \u201cPR\u201d (Pull Request). What is this and how do I try it?"
316
316
},
317
317
{
318
318
"id": 44,
@@ -324,7 +324,7 @@
324
324
"views": 1487,
325
325
"posts_count": 2,
326
326
"like_count": 0,
327
-
"excerpt": ""
327
+
"excerpt": "Alex started a good discussion on the mailing list (May 3, 2019) about best practices when writing a new adapter:\nI wanted to ask if there are some additional guidelines on how to write good adapters for preCICE. I have the feeling that I might think\u2026"
328
328
},
329
329
{
330
330
"id": 42,
@@ -336,7 +336,7 @@
336
336
"views": 718,
337
337
"posts_count": 7,
338
338
"like_count": 0,
339
-
"excerpt": ""
339
+
"excerpt": "We had a good discussion with Satish on the mailing list about the re-partitioning process and the connection to parallel data mapping in preCICE.\nSatish asked (July 24, 2019):\n\nIt seems to me that mappings can occur in parallel in preCICE. Is that c\u2026"
340
340
},
341
341
{
342
342
"id": 41,
@@ -348,7 +348,7 @@
348
348
"views": 739,
349
349
"posts_count": 2,
350
350
"like_count": 2,
351
-
"excerpt": ""
351
+
"excerpt": "Nikrouz asked on the mailing list (Sep 13, 2019):\n\nI am going to use OpenFoam-CalculiX for FSI simulations.\nAt this time, I am have technical question for preparing preCICE config file. The case I am going to run has very large deformations. Fortunat\u2026"
352
352
},
353
353
{
354
354
"id": 36,
@@ -360,7 +360,7 @@
360
360
"views": 638,
361
361
"posts_count": 2,
362
362
"like_count": 0,
363
-
"excerpt": ""
363
+
"excerpt": "The OpenFOAM adapter has the form of an OpenFOAM function object. This mechanism is commonly used only for post-processing, so a reasonable question is:\n\nDoes the OpenFOAM adapter also take care of the checkpointing? In other words, can a function ob\u2026"
Copy file name to clipboardExpand all lines: assets/data/news.json
+4-4Lines changed: 4 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
{
2
-
"generated_at": "2025-11-21T06:26:37.409490",
2
+
"generated_at": "2025-11-22T06:22:44.047495",
3
3
"topics": [
4
4
{
5
5
"id": 217,
@@ -20,7 +20,7 @@
20
20
"last_posted_at": "2025-11-12T19:55:51.000Z",
21
21
"like_count": 2,
22
22
"posts_count": 2,
23
-
"views": 39,
23
+
"views": 40,
24
24
"description": "We just uploaded a new preprint on arXiv A waveform iteration implementation for black-box multi-rate higher-order coupling, which is a compact summary of the dissertation of Benjamin Rodenberg. We explain..."
25
25
},
26
26
{
@@ -108,7 +108,7 @@
108
108
"last_posted_at": "2025-04-07T04:59:59.909Z",
109
109
"like_count": 4,
110
110
"posts_count": 4,
111
-
"views": 163,
111
+
"views": 164,
112
112
"description": "Summary: We have been developing a JSON schema for preCICE adapters and tools improving interoperability and enabling tooling support. Find out more about the schema and what you can do..."
113
113
},
114
114
{
@@ -229,7 +229,7 @@
229
229
"last_posted_at": "2024-02-27T09:42:45.629Z",
230
230
"like_count": 8,
231
231
"posts_count": 4,
232
-
"views": 1004,
232
+
"views": 1005,
233
233
"description": "The longer you wait for something, the more you appreciate it, right? preCICE v3 is finally out and we are pretty happy about it. v3.0.0 is a breaking release. This..."
0 commit comments