On 07/15/2014 10:51 PM, Roy Stogner wrote:
>
> On Tue, 15 Jul 2014, David Knezevic wrote:
>
>> I use MeshFunction a lot, it's very helpful. But sometimes due to
>> rounding error, I evaluate a MeshFunction at a point just outside the
>> mesh, and hence the evaluation fails.
>>
>> I'd like to preve
On Tue, 15 Jul 2014, David Knezevic wrote:
> I use MeshFunction a lot, it's very helpful. But sometimes due to
> rounding error, I evaluate a MeshFunction at a point just outside the
> mesh, and hence the evaluation fails.
>
> I'd like to prevent this type of failure.
>
> I was thinking of pertur
I use MeshFunction a lot, it's very helpful. But sometimes due to
rounding error, I evaluate a MeshFunction at a point just outside the
mesh, and hence the evaluation fails.
I'd like to prevent this type of failure.
I was thinking of perturbing the evaluation point in various directions
(p + (
On Tue, 15 Jul 2014, Sahai, Amal wrote:
> I have a compressible flow solver that solves for the conservative
> variables. I was wondering what would be the best way to store
> primitive variables? Right now I have attached a vector to the
> system that I solve and I update it after every iteratio
On Thu, 10 Jul 2014, Sahai, Amal wrote:
> 1) Compute momentum values (U*) at the new time step but without contribution
> of the pressure terms. (Predictor)
> 2) Update Pressure values using U*
> 3) Correct new momentum values by taking into account Pressure values.
> (Corrector)
> 4) Update En
I have a compressible flow solver that solves for the conservative variables. I
was wondering what would be the best way to store primitive variables? Right
now I have attached a vector to the system that I solve and I update it after
every iteration (I assemble it the way the system matrix is a
