Development issueshttps://develop.openfoam.com/groups/Development/-/issues2017-09-28T12:04:04Zhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/16makeParaView and makeVTK possibly assume lib64 for mesa libraries2017-09-28T12:04:04ZMark OLESENmakeParaView and makeVTK possibly assume lib64 for mesa librariesexchange platform https://exchange.openfoam.com/node/398
@Pawan @Prashantexchange platform https://exchange.openfoam.com/node/398
@Pawan @PrashantVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/ThirdParty-common/-/issues/13COMP: Inconsistent files for ADIOS2019-07-21T22:56:27ZPrashant SonakarCOMP: Inconsistent files for ADIOShttps://develop.openfoam.com/Development/ThirdParty-plus/blob/master/BUILD.md has following section for download
```
adios repo or github download or alt download
```
- The github download returns `ADIOS-1.11.0`, but doesn't contain...https://develop.openfoam.com/Development/ThirdParty-plus/blob/master/BUILD.md has following section for download
```
adios repo or github download or alt download
```
- The github download returns `ADIOS-1.11.0`, but doesn't contain `Makefile.in` (has Makefile.am) and gets terminated during compilation.
- The alt download returns `adios-1.11.0` but makeADIOS script expects the folder name in CAPITAL.
@andyVersion v1706Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/567require weighting with absolute values for surfaceFieldValue2017-09-12T08:01:03ZMark OLESENrequire weighting with absolute values for surfaceFieldValue- The current weightedAverage (eg, with rhoU . dA) includes the direction, but should also provide a variant without the direction.
- the derived `pTotal` in surfMeshSamplers only works for compressible cases.
@Pawan- The current weightedAverage (eg, with rhoU . dA) includes the direction, but should also provide a variant without the direction.
- the derived `pTotal` in surfMeshSamplers only works for compressible cases.
@Pawanv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/478surface sample writing using Ostream2020-01-16T18:08:52ZMark OLESENsurface sample writing using OstreamThese should largely be using OSstream or even std::ostream since the output target is normally a file etc.These should largely be using OSstream or even std::ostream since the output target is normally a file etc.v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/549BUG: nearWallField FO with overset2017-08-21T05:55:35ZPrashant SonakarBUG: nearWallField FO with oversetnearWallField FO seems to fail with overset mesh
```
nearWallFields near: Sampling 1 fields
#0 Foam::error::printStack(Foam::Ostream&) at ??:?
#1 Foam::sigSegv::sigHandler(int) at ??:?
#2 ? in "/lib64/libc.so.6"
#3 double Foam::parti...nearWallField FO seems to fail with overset mesh
```
nearWallFields near: Sampling 1 fields
#0 Foam::error::printStack(Foam::Ostream&) at ??:?
#1 Foam::sigSegv::sigHandler(int) at ??:?
#2 ? in "/lib64/libc.so.6"
#3 double Foam::particle::trackToFace<Foam::findCellParticle::trackingData>(Foam::Vector<double> const&, Foam::findCellParticle::trackingData&) at ??:?
```
However the same case works with zeroGradient FO approach.
Refer EP#460
@mark @Mattijsv1712https://develop.openfoam.com/Development/openfoam/-/issues/595simplify/extend List, DynamicList2021-01-26T20:22:11ZMark OLESENsimplify/extend List, DynamicListInspired by some of Franjo's @Juretic work, I've started looking into how to incorporate the short list optimization into the standard DynamicList as well as other methods and possible optimizations. I'd like some feedback on some of the...Inspired by some of Franjo's @Juretic work, I've started looking into how to incorporate the short list optimization into the standard DynamicList as well as other methods and possible optimizations. I'd like some feedback on some of these ideas @andy @Mattijs
The static allocation size needs to be templated but the number of parameters for DynamicList is growing too much. My current thought is to remove the SizeInc,SizeMult,SizeDiv from templates and replace with a run-time sizing policy that we can combine with templated factory methods for some compile-time safety.
Eg,
template<class T, unsigned StaticSize = 16>
class DynamicList
{
...
//-
inline void setSizingPolicy(const sizingPolicy& policy);
};
In use this would mean something like this:
DynamicList<label> lst;
lst.setSizingPolicy(sizingPolicy::increment<10>());
lst.setSizingPolicy(sizingPolicy::factor<2>());
lst.setSizingPolicy(sizingPolicy::factor<3,2>());
lst.setSizingPolicy(sizingPolicy::general<10,3,2>());
This is still a long way from handling allocations with an allocator, but I think it is an improvement.
To accommodate some other routines, I've tentatively added in these methods:
UList
//- Find index of the first occurence of the value.
// Linear search.
// \return -1 if not found.
label find(const T& val, const label start=0) const;
//- True if the value if found in the list. Linear search.
inline bool found(const T& val, const label start=0) const;
//- Move element to the first position.
void moveFirst(const label i);
//- Move element to the last position.
void moveLast(const label i);
//- Swap with the first element. Fatal on an empty list.
void swapFirst(const label i);
//- Swap with the last element. Fatal on an empty list.
void swapLast(const label i);
DynamicList
//- Remove and return the last element. Fatal on an empty list.
inline T remove();
//- Remove and return the specified element. Fatal on an empty list.
// With fast=true (default), the removed element is replaced with
// the last one in the list.
// With fast=false, the elements are copied down in the list.
inline T remove(const label i, const bool fast=true);v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/608stitchMesh doesn't work with restart2017-12-18T23:12:46ZMark OLESENstitchMesh doesn't work with restartCross-reference EP#313. EP#444Cross-reference EP#313. EP#444v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/526enable profiling output for postProcess and -postProcess2017-07-19T11:59:17ZMark OLESENenable profiling output for postProcess and -postProcessLike most utilities, these two don't use the normal run() mechanism - so there is no profiling output possible.
- fix by adding an explicit print, but only report the profiling to the log file from master process. We don't wish to overw...Like most utilities, these two don't use the normal run() mechanism - so there is no profiling output possible.
- fix by adding an explicit print, but only report the profiling to the log file from master process. We don't wish to overwrite any profiling that was conducted during the simulation. Besides which, we don't have a proper Time object for handling the write nicely either.
@Prashant - this is the first solution. Please see if it is adequate.
STYLE: could discuss trimming down the cpu/sys information. It doesn't seem to make much sense to write it every time.v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/548STYLE: correct the reference noiseDict file to new syntax2017-08-17T13:51:46ZPrashant SonakarSTYLE: correct the reference noiseDict file to new syntaxRefer EP#457
https://develop.openfoam.com/Development/OpenFOAM-plus/blob/OpenFOAM-v1706/applications/utilities/postProcessing/noise/noiseDictRefer EP#457
https://develop.openfoam.com/Development/OpenFOAM-plus/blob/OpenFOAM-v1706/applications/utilities/postProcessing/noise/noiseDictv1712AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/554remove Foam::string::operator() operator2017-10-06T07:53:53ZMark OLESENremove Foam::string::operator() operatorThis is a holdover from foamString and is functionally identical to the substr() method, but is also harder to notice when it is being invoked.
I think that we should finally remove it.
@andy @Mattijs @petebachantThis is a holdover from foamString and is functionally identical to the substr() method, but is also harder to notice when it is being invoked.
I think that we should finally remove it.
@andy @Mattijs @petebachantv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/536remove ccm26ToFoam2017-11-30T13:37:05ZMark OLESENremove ccm26ToFoamThis single-purpose application has less functionality than ccmToFoam.This single-purpose application has less functionality than ccmToFoam.v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/529combine externalCoupler from lumpedPoints and function object2017-07-18T15:02:49ZMark OLESENcombine externalCoupler from lumpedPoints and function objectshould also name as externalFileCoupler, to allow the future possibility of other coupling mechanisms.should also name as externalFileCoupler, to allow the future possibility of other coupling mechanisms.v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/556feature: Fan BC with swirl2018-05-01T08:54:48ZPrashant Sonakarfeature: Fan BC with swirlRefer EP#467Refer EP#467v1712AdminAdminhttps://develop.openfoam.com/Development/openfoam/-/issues/600BUG: failures in latest develop2017-11-13T05:39:58ZPrashant SonakarBUG: failures in latest develop```
Application decomposePar - case heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater: ** FOAM FATAL ERROR **
Application chtMultiRegionFoam - case heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater: ** FOAM ...```
Application decomposePar - case heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater: ** FOAM FATAL ERROR **
Application chtMultiRegionFoam - case heatTransfer/chtMultiRegionFoam/externalCoupledMultiRegionHeater: ** FOAM FATAL ERROR **
Application decomposePar - case heatTransfer/chtMultiRegionFoam/multiRegionHeater: ** FOAM FATAL ERROR **
Application chtMultiRegionFoam - case heatTransfer/chtMultiRegionFoam/multiRegionHeater: ** FOAM FATAL ERROR **
Application pimpleDyMFoam - case incompressible/pimpleDyMFoam/wingMotion/wingMotion2D_pimpleDyMFoam: ** FOAM FATAL ERROR **
Application WatersKing - case incompressible/pimpleFoam/laminar/planarPoiseuille: ** FOAM FATAL ERROR **
Application snappyHexMesh - case incompressible/pisoFoam/LES/motorBike/motorBike: ** FOAM FATAL ERROR **
Application reactingParcelFoam - case lagrangian/reactingParcelFoam/cylinder: ** FOAM FATAL ERROR **
Application reactingParcelFoam - case lagrangian/reactingParcelFoam/hotBoxes: ** FOAM FATAL ERROR **
Application reactingParcelFoam - case lagrangian/reactingParcelFoam/rivuletPanel: ** FOAM FATAL ERROR **
Application reactingParcelFoam - case lagrangian/reactingParcelFoam/splashPanel: ** FOAM FATAL ERROR **
Application reactingParcelFoam - case lagrangian/reactingParcelFoam/verticalChannelLTS: ** FOAM FATAL ERROR **
Application reactingParcelFoam - case mesh/parallel/filter: ** FOAM FATAL ERROR **
Application reactingParcelFoam.parallel - case mesh/parallel/filter: ** FOAM FATAL ERROR **
Application redistributePar.1 - case mesh/parallel/filter: ** FOAM FATAL ERROR **
Application decomposePar - case preProcessing/createZeroDirectory/snappyMultiRegionHeater: ** FOAM FATAL ERROR **
Application createZeroDirectory - case preProcessing/createZeroDirectory/snappyMultiRegionHeater: ** FOAM FATAL ERROR **
Application chtMultiRegionFoam - case preProcessing/createZeroDirectory/snappyMultiRegionHeater: ** FOAM FATAL ERROR **
```
Also uncofirmed completion of
- multiphase/interFoam/laminar/vofToLagrangian/lagrangianParticleInjection/log.sprayFoam
- multiphase/interFoam/laminar/vofToLagrangian/lagrangianDistributionInjection/log.sprayFoam
For quick reference files are available at:
/home/alex2/prashant/OpenFOAM/OpenFOAM-plus.develop/tutorialsTest
@andyv1712https://develop.openfoam.com/Development/openfoam/-/issues/551Feature: improve TAB functionality2017-10-06T07:54:11ZPrashant SonakarFeature: improve TAB functionalityRefer EP#456
@andy @markRefer EP#456
@andy @markv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/645-decomposeParDict invokes MPI2017-12-18T23:12:32ZMark OLESEN-decomposeParDict invokes MPIIt looks like "decomposeParDict" should not really be part of [validParOptions](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/src/OpenFOAM/global/argList/argList.C#L84) since this triggers detection as a [parallel r...It looks like "decomposeParDict" should not really be part of [validParOptions](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/src/OpenFOAM/global/argList/argList.C#L84) since this triggers detection as a [parallel run](https://develop.openfoam.com/Development/OpenFOAM-plus/blob/develop/src/OpenFOAM/global/argList/argList.C#L610)
@andyv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/644fieldMinMax reporting wrong location2017-12-18T05:07:55ZRoger AlmenarfieldMinMax reporting wrong locationUsing v1706.
I am monitoring min/max velocities in a thermal case using the fieldMinMax FO (rhoSimpleFoam). The report of the maximum velocity seems to be going OK, but I have an issue with the location: the cell number stays constant, w...Using v1706.
I am monitoring min/max velocities in a thermal case using the fieldMinMax FO (rhoSimpleFoam). The report of the maximum velocity seems to be going OK, but I have an issue with the location: the cell number stays constant, whilst the actual XYZ location changes along the iterations, as shown here:
*> max(mag(U)) = 20.252895 in cell 110637 at location (0.38 0.004410381 0.004410381) on processor 12
> max(mag(U)) = 20.257627 in cell 388740 at location (0.476 -0.004410381 -0.004410381) on processor 3
> max(mag(U)) = 20.262458 in cell 388740 at location (0.47866667 -0.004410381 -0.004410381) on processor 3
> max(mag(U)) = 20.267294 in cell 388740 at location (0.484 -0.004410381 -0.004410381) on processor 3
> max(mag(U)) = 20.272106 in cell 388740 at location (0.48933333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.276871 in cell 388740 at location (0.49466667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.281582 in cell 388740 at location (0.5 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.286253 in cell 388740 at location (0.50533333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.290906 in cell 388740 at location (0.51333333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.295564 in cell 388740 at location (0.52133333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.300241 in cell 388740 at location (0.532 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.304942 in cell 388740 at location (0.54 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.309656 in cell 388740 at location (0.548 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.314368 in cell 388740 at location (0.556 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.319065 in cell 388740 at location (0.564 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.323737 in cell 388740 at location (0.572 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.328381 in cell 388740 at location (0.58 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.333002 in cell 388740 at location (0.59066667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.337603 in cell 388740 at location (0.59866667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.342193 in cell 388740 at location (0.60933333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.346773 in cell 388740 at location (0.62 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.351343 in cell 388740 at location (0.628 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.355903 in cell 388740 at location (0.63866667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.360447 in cell 388740 at location (0.64933333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.364974 in cell 388740 at location (0.66 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.369483 in cell 388740 at location (0.668 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.373976 in cell 388740 at location (0.67866667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.378457 in cell 388740 at location (0.68933333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.382929 in cell 388740 at location (0.7 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.387393 in cell 388740 at location (0.71066667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.391851 in cell 388740 at location (0.71866667 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.396301 in cell 388740 at location (0.72933333 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.40074 in cell 388740 at location (0.74 -0.0022061122 -0.0022061122) on processor 3
> max(mag(U)) = 20.405165 in cell 388740 at location (0.75066667 -0.0022061122 -0.0022061122) on processor 3*v1712https://develop.openfoam.com/Development/openfoam/-/issues/637ensight surface format missing space2017-11-21T07:09:14ZMark OLESENensight surface format missing spacewhen variables are too long - EP#547
@Prashantwhen variables are too long - EP#547
@Prashantv1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/520consolidate table bounding2017-07-08T09:14:05ZMark OLESENconsolidate table boundingduplicate or nearly duplicate older code for handling table bounds. Can use Enum instead.duplicate or nearly duplicate older code for handling table bounds. Can use Enum instead.v1712Mark OLESENMark OLESENhttps://develop.openfoam.com/Development/openfoam/-/issues/524provide build information about intel-mpi + gcc combination2017-07-13T06:34:55ZMark OLESENprovide build information about intel-mpi + gcc combination@Pawan@Pawanv1712Mark OLESENMark OLESEN