|
[Sponsors] |
September 27, 2010, 11:06 |
Crash using DirectMappedVelocityFluxField
|
#1 |
Senior Member
Francois
Join Date: Jun 2010
Posts: 107
Rep Power: 20 |
Dear developers, debuggers and forum readers,
When using the directMappedVelocityFlux patch to remap the U field, pisoFoam crashes when using the NEARESTFACE option. If interested, I can post the error message associated with the crash, but I've traced the origin back to the following piece of code in directMappedVelocityFluxFixedValueFvPatchField: Code:
00209 newUValues = patch().patchSlice(newUValues); Code:
00176 vectorField newUValues; Reading the similar routine used in directMappedFixedValueFvPatchField.C, I guess the variable in brackets should be allUValues and not newUValues, leading to: Code:
00209 newUValues = patch().patchSlice(allUValues); I was also wondering if a kind soul could also make good use of this discussion and explain to me what the patch().patchSlice() command does? Kind regards, Francois. |
|
Tags |
directmapped, nearestface, remapping |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Graphic/plotted monitors causing Fluent 12.0 to crash | Autumn | FLUENT | 6 | May 25, 2010 01:19 |
Flow Simulation Crash with Trajectories | D.Castle | FloEFD, FloWorks & FloTHERM | 2 | August 5, 2009 14:50 |
Error%7eerror triggers crash after handling exceptions thrown by errorexit twice | 7islands | OpenFOAM Bugs | 2 | September 4, 2007 05:24 |
Design Modeler crash | LR | CFX | 3 | May 13, 2005 19:52 |
track cause of crash | Matt | Phoenics | 2 | October 5, 2001 09:16 |