Failure to start from latest time when BC stores scalarlist
I have observed that OpenFOAM fails to start from latest time when a custom boundary condition stores (and not even needs to read) a scalarlist. The error is as follows:
I have created an easy-to-check scenario, so it can be reproduced in a direct manner (v. 2.2.2 or 2.3). Please, find it attached. The case is based on the cavity tutorial, only that the new BC has been applied. The new BC is called 'failFixedValue' and is a modified version of 'oscillatingFixedValue', tailored to behave as fixedValue and to store a dummy scalarList associated to the BC.
Am I doing something wrong or this is in fact a bug?
That was quick.
I have further questions and hope that someone is able to answer or correct me.
Defining the former scalarList as a scalarField in the following way yields the same error for the binary case:
However some questions arise, as for example, if the BC is applied to two different boundaries, with different dumfield values, one would overwrite the other and mess everything, wouldn't it?
I could try to create the field as dumfield_boundaryName, but isn't it a mess? Any thoughts on a better solution?
Well, problem solved, it works either way as a scalarList or scalarField, but it has to be written out using the following command:
Thanks mattijs for your guidance!
This is great... now paraview fails to open this binary case due to not understanding the scalarLists embedded in the BC. Of course, no trouble with the ascii format.
|All times are GMT -4. The time now is 16:44.|