Development issueshttps://develop.openfoam.com/groups/Development/-/issues2021-07-06T12:58:41Zhttps://develop.openfoam.com/Development/openfoam/-/issues/872prescribed rotation restraint2021-07-06T12:58:41ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comprescribed rotation restraintThe restraint currently
- does not use time step
- diverges if not underrelaxed
Ideas:
- under relax applied momentum
- do multiple iterations of motion system (nIter)The restraint currently
- does not use time step
- diverges if not underrelaxed
Ideas:
- under relax applied momentum
- do multiple iterations of motion system (nIter)Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/871uniform/rigidBodyMotionState dictionary cannot be re-read if running in binary2019-12-09T22:18:11ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comuniform/rigidBodyMotionState dictionary cannot be re-read if running in binaryMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/870distanceSurface is very picky2018-07-02T09:34:41ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comdistanceSurface is very pickyIf
- the surface is open
- and the nearest point on the surface is on one of the open edges
the distanceSurface seems to pick up the 'wrong' normal. What is the normal on an open edge?
Workaround is to always make sure your surface is ...If
- the surface is open
- and the nearest point on the surface is on one of the open edges
the distanceSurface seems to pick up the 'wrong' normal. What is the normal on an open edge?
Workaround is to always make sure your surface is big enough so all mesh points project onto its interior.Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/869extract cell centres with velocity as CSV2018-07-02T09:34:55ZMark OLESENextract cell centres with velocity as CSVRef EP#675
- approach is to define a sampledSet with cell centres.
- provision for bounding box limitsRef EP#675
- approach is to define a sampledSet with cell centres.
- provision for bounding box limitsv1812Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/868fragile ensight surface reader2018-12-11T10:42:03ZMark OLESENfragile ensight surface readerexpects the following only:
model: 1 xxx.000.mesh
which means that any of the following (correct input) will break it:
model: xxx.000.mesh
model: data/000/geomexpects the following only:
model: 1 xxx.000.mesh
which means that any of the following (correct input) will break it:
model: xxx.000.mesh
model: data/000/geomv1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/867Medium Test - 12.06.20182019-12-09T22:18:11ZPrashant SonakarMedium Test - 12.06.2018All cases could be accessed at: /home/alex4/prashant/SUPPORT/ESI/MEDIUM_TEST/tutorials_1806
- [x] DNS/dnsFoam/boxTurb16 - solver crash
- [x] IO/fileHandler/machineA/fileHandler - re-verify if we need `cp -r` while copying constant, line ...All cases could be accessed at: /home/alex4/prashant/SUPPORT/ESI/MEDIUM_TEST/tutorials_1806
- [x] DNS/dnsFoam/boxTurb16 - solver crash
- [x] IO/fileHandler/machineA/fileHandler - re-verify if we need `cp -r` while copying constant, line 36; 90 of Allrun
- [x] combustion/PDRFoam/flamePropagationWithObstacles - solver crash
- [x] mesh/foamyHexMesh/mixerVessel - solver crash
- [x] compressible/rhoSimpleFoam/gasMixing/injectorPipe - solver crash
- [x] compressible/sonicFoam/RAS/nacaAirfoil - solver crash
- [x] incompressible/pimpleFoam/LES/vortexShed - surface noise failed 'expected word error'
- [x] multiphase/compressibleInterFoam/laminar/climbingRod - solver failure
- [x] multiphase/driftFluxFoam/RAS/dahl - solver failure
- [x] multiphase/reactingTwoPhaseEulerFoam/RAS/LBend - solver failure
- [x] multiphase/compressibleInterFoam/laminar/depthCharge2D - solver failure
- [x] multiphase/interFoam/RAS/DTCHullMoving - solver failure
- [ ] ~~multiphase/interFoam/RAS/DTCHullWave - decomposePar failure 'missing entry value'~~ REMOVED
- [x] multiphase/interFoam/RAS/motorBike - rename solver in controlDict_nextWrite
- [x] multiphase/interFoam/laminar/vofToLagrangian/lagrangian* - both cases replace combustionModel type noCombustion to none
@andy @Mattijs @Sergio @markv1806https://develop.openfoam.com/Development/openfoam/-/issues/866vtkWrite support for Lagrangian data2019-06-28T09:51:57ZAdminvtkWrite support for Lagrangian dataHas vtkWrite support been implemented for Lagrangian? If not, could this be implemented ASAP. We have some cases that we want to animate, and using the old approach of writing the Lagrangian data only, then reconstructing, then convert...Has vtkWrite support been implemented for Lagrangian? If not, could this be implemented ASAP. We have some cases that we want to animate, and using the old approach of writing the Lagrangian data only, then reconstructing, then converting to vtk is very unwieldy. We’d like to write the spray data in vtk format directly from a functionObject, and be able to select which associated spray properties (d, U, nP, etc.) get output.
KarlMark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/865rndGen.position<label>(0, XXX) is not evenly distributed2019-12-09T22:18:11ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrndGen.position<label>(0, XXX) is not evenly distributedWhen using the
```
rndGen.position<label>(0, nDomains - 1);
```
to determine random decomposition it seems the entries 0 and nDomains-1 have only half the number of entries.
Replicate: run randomDecomp on a scaled up cavity (e.g. 1000x...When using the
```
rndGen.position<label>(0, nDomains - 1);
```
to determine random decomposition it seems the entries 0 and nDomains-1 have only half the number of entries.
Replicate: run randomDecomp on a scaled up cavity (e.g. 1000x1000).Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/864refineWallLayer -useSet incorrect2018-07-04T10:45:24ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comrefineWallLayer -useSet incorrectrefineWallLayer -useSet should limit the refinement to the specified set. Instead it does the opposite.refineWallLayer -useSet should limit the refinement to the specified set. Instead it does the opposite.Mattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comhttps://develop.openfoam.com/Development/openfoam/-/issues/863Coordinate system issues: cylindricalCS / fixedProfileFvPatchField2020-06-19T14:43:50ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.comCoordinate system issues: cylindricalCS / fixedProfileFvPatchField- cyclindricalCS cannot be run-time selected: missing TypeName and addToRunTimeSelectionTable.
- hard to specify
```
coordinateSystem
{
coordinateRotation
{
type axesRota...- cyclindricalCS cannot be run-time selected: missing TypeName and addToRunTimeSelectionTable.
- hard to specify
```
coordinateSystem
{
coordinateRotation
{
type axesRotation;
e3 (1 0 0);
e1 (0 1 0);
}
type cylindricalCS;
origin (0 0 0.01);
}
```
With this in place we could re-write various boundary conditions to use cylindrical coordinates. E.g. `fixedProfileFvPatchField`.
@matej
Remark: cylindrical coordinateRotation currently stores transformation tensors. This should be stored outside.
https://develop.openfoam.com/Development/ThirdParty-common/-/issues/37makeParaview - BUILD_SUFFIX2018-06-11T09:48:04ZPrashant SonakarmakeParaview - BUILD_SUFFIX- using makeParaview with mesa leads to installation in e.g. ParaView-5.5.0`-mesa`
- whereas the etc/config.*sh/paraview search for existence of ParaView-5.5.0 to set up ParaView_INCLUDE_DIR etc.
- another issue is search for \*-qt\* ins...- using makeParaview with mesa leads to installation in e.g. ParaView-5.5.0`-mesa`
- whereas the etc/config.*sh/paraview search for existence of ParaView-5.5.0 to set up ParaView_INCLUDE_DIR etc.
- another issue is search for \*-qt\* instead of \*qt\*, which leads to failure in setting up Qt5_DIR, needed for building PVReaders.
using qt-5.6.3 and ParaView-5.5.0v1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/862segfault: sampling field transfer to triSurfaceMesh (as surfMesh)2018-07-02T09:35:28ZMark OLESENsegfault: sampling field transfer to triSurfaceMesh (as surfMesh)- in surfMeshSampleDiscrete, face/point ownership is transferred to surfMesh, but this means they are not available for discreteSurface when sampling
@Prashant @SonVo- in surfMeshSampleDiscrete, face/point ownership is transferred to surfMesh, but this means they are not available for discreteSurface when sampling
@Prashant @SonVov1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/861residual FO : DebugInfo2018-07-04T10:44:48ZPrashant Sonakarresidual FO : DebugInfoIn controlDict we have,
lduMatrix 1;
This causes to print "Setting residual field for first *" lines for each field and each time step, with writeFields true;
Please reconsider. @andy @Sergio @mark @MattijsIn controlDict we have,
lduMatrix 1;
This causes to print "Setting residual field for first *" lines for each field and each time step, with writeFields true;
Please reconsider. @andy @Sergio @mark @Mattijsv1806https://develop.openfoam.com/Development/openfoam/-/issues/860foamLog extract min, max, avg2021-07-06T12:57:16ZMark OLESENfoamLog extract min, max, avg- can currently only extract min value (EP 690), and foamLog is not sophisticated enough to handle arbitrary parsing.
- adjust AMI reporting as `min = ... max = ...` instead of `min/max/average = ...` for easier parsing.
@Prashant- can currently only extract min value (EP 690), and foamLog is not sophisticated enough to handle arbitrary parsing.
- adjust AMI reporting as `min = ... max = ...` instead of `min/max/average = ...` for easier parsing.
@Prashantv1806Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/859STYLE: correct syntax in header file of noise.C2019-12-09T22:18:11ZvilfayeauSTYLE: correct syntax in header file of noise.CHi,
Could you update the syntax in the noise.C header file? Headerfile of noise.C and noiseDict should be consistent.
https://develop.openfoam.com/Development/OpenFOAM-plus/blob/master/applications/utilities/postProcessing/noise/noise...Hi,
Could you update the syntax in the noise.C header file? Headerfile of noise.C and noiseDict should be consistent.
https://develop.openfoam.com/Development/OpenFOAM-plus/blob/master/applications/utilities/postProcessing/noise/noise.C
`// Input file
inputFile "postProcessing/faceSource1/surface/patch/patch.case";
`
should be
`// Input file
files ( "postProcessing/faceSource1/surface/patch/patch.case");
`
Best,
Sebastienv1806https://develop.openfoam.com/Development/openfoam/-/issues/858swirlFanVelocity2018-06-11T14:48:02ZPrashant SonakarswirlFanVelocityoptional entry rEff is set to zero. Please reconsider division.optional entry rEff is set to zero. Please reconsider division.v1806Sergio FerrarisSergio Ferrarishttps://develop.openfoam.com/Development/openfoam/-/issues/857interDyMFoam/RAS/motorBike tutorial fails2020-01-03T13:58:32ZMattijs Janssens4-Mattijs@users.noreply.develop.openfoam.cominterDyMFoam/RAS/motorBike tutorial fails(branch develop-pre-release)
[log.interFoam](/uploads/3b57a8add908b399ebf6add29ab0125d/log.interFoam)(branch develop-pre-release)
[log.interFoam](/uploads/3b57a8add908b399ebf6add29ab0125d/log.interFoam)https://develop.openfoam.com/Development/openfoam/-/issues/856Unit tests: 06-06-20182018-07-02T05:02:01ZPrashant SonakarUnit tests: 06-06-2018- multiphase/interDyMFoam/RAS/motorBike should move to interFoam
- multiphase/interFoam/RAS/DTCHullWave :
- inlet BC expects entry 'value' - field alpha.water
- call for setWaves application, which doesn't exist
- lagrangian/rea...- multiphase/interDyMFoam/RAS/motorBike should move to interFoam
- multiphase/interFoam/RAS/DTCHullWave :
- inlet BC expects entry 'value' - field alpha.water
- call for setWaves application, which doesn't exist
- lagrangian/reactingParcelFoam/verticalChannelLTS : solver exit with maxIter 100
unconfirmed completions
- compressible/rhoSimpleFoam/gasMixing/injectorPipe: solver
cases run at /home/alex2/prashant/OpenFOAM/OpenFOAM-plus.feature-xxx/tutorialsTest
@andy @Mattijs @mark @Sergiov1806https://develop.openfoam.com/Development/openfoam/-/issues/855Inaccurate radiation calculation2023-06-02T13:36:58ZAdminInaccurate radiation calculationI tried a validation problem with fvDOM on axisymmetric case. The example case is attached.
Radiative analytical heat flux from "hot" wall comes out to 260.9 kW/m2.
Axisymmetric test case under-predicts the heat flux (15% error) (wed...I tried a validation problem with fvDOM on axisymmetric case. The example case is attached.
Radiative analytical heat flux from "hot" wall comes out to 260.9 kW/m2.
Axisymmetric test case under-predicts the heat flux (15% error) (wedge patch)
Steps to reproduce:
1. Download the zip
2. Extract and execute Allrun (50 or 100 timestep entry is sufficient to analyze the issue)
3. Observe qr field on hot and cold patches in paraview
Is there a way to solve this problem?
Thanks in advance!
.[multiRegionHeaterRadiation.zip](/uploads/2e14f8503eb768712bc0a8c79ce00045/multiRegionHeaterRadiation.zip)https://develop.openfoam.com/Development/openfoam/-/issues/854Empty Confirmation Mail - OpenFOAM Mailing List2018-06-04T09:43:03ZKutalmış BerçinEmpty Confirmation Mail - OpenFOAM Mailing ListHi,
I subscribed the newsletter three days ago, and received an email from `no-reply@openfoam.com via cp04.hosting.zen.net.uk`. The title reads `Confirm to join the OpenFOAM mailing list!`; so, I expected to see a confirmation click, b...Hi,
I subscribed the newsletter three days ago, and received an email from `no-reply@openfoam.com via cp04.hosting.zen.net.uk`. The title reads `Confirm to join the OpenFOAM mailing list!`; so, I expected to see a confirmation click, but the email is empty. Also nothing was blocked. I use `gmail.com`.
Then, today I used another mail provider. Everything was fine.
Assuming nothing has changed from your side, might be some problem with `gmail`?
PS: I have just checked with another gmail account. Email passed SPF check, but the whole content was somehow blocked. Here, the original content to diagnose: https://www.writeurl.com/text/1qxtxc2kvowyu55qmsp8/ar6q2cavoapfn8wh610a
Considering gmail is the most common provider, it might be useful to consider it.