[FLASH-USERS] V-cycle not converging

[seyit]

Tomek,

> By the way, can you remind this audience what you are missing from
FLASH2?

I think you mean at which part of the migration I have difficulties
switching to FLASH3? It has been some while now, but the last thing that I
did together with a colleague was solving some problems. I think the only
place we were stuck was trying to implement eos (eos1d in FLASH2.5). But I
will work on that after I finish my article with the results of FLASH2.5,
which are almost finished btw.

Anyway, could anyone answer the two "simple" questions I asked earlier?

1) Is this warning something bad?
2) would reducing mgrid_max_residual_norm (or using -O3 optimization) help?

Kind Regards,
Seyit

PS: have I mentioned how bad ifort 8 is?... I guess I have. I was reminded
of that again today, when I noticed yet again that that compiler messed up
some results.




On Thu, 18 Sep 2008 13:57:04 -0400, Tomasz Plewa <tplewa at fsu.edu> wrote:
> Seyit -
> 
> Moving to FLASH3 will potentially offer you more support. It does not
> guarantee that your problem will be automatically solved. Well, in
> general nothing can be taken for granted. But in this particular case,
> we have seen problems with FLASH2 multigrid that migrated to FLASH3. As
> I said, no guarantee (but still worth trying).
> 
> By the way, can you remind this audience what you are missing from
FLASH2?
> 
> Tomek
> --
> Seyit Hocuk wrote:
>> Hi,
>>
>> In some of my simulations after some time into the simulation, I get a
>> lot! of V-cycle warnings. What is the best way to avoid these and how
>> bad are these warnings. I mean should I restart simulations or can I
>> waive this warning.
>>
>> Is changing "mgrid_max_residual_norm" a good option? Or should I use
>> better optimizations. At the moment I am not using optimizations, but I
>> noticed that using -03 reduced these warnings. How can I avoid them.
>>
>> I bet you all will say that FLASH3 will solve my problems :)
>>
>> Thanks,
>> Seyit
>>
>>