Hi Spencer,

thanks for your answer. I will test it, but first of all, I will try to realize this by a filter added to the conditions.xml file of my simulation. I think this could work, too, right?

Best 
Fabian
Von: Sherwin, Spencer J [s.sherwin@imperial.ac.uk]
Gesendet: Freitag, 14. Oktober 2016 11:26
An: Selbach, Fabian
Cc: nektar-users
Betreff: Re: [Nektar-users] Output of L2 and LInf norms during simulation

HI Fabian,

Sorry it has been a busy week and I am certainly behind on Nektar emails. 

I actually needed to do a similar thing for a run yesterday in the IncNavierStokes Solver. If you have a look at the feature/IncNS_Sensor branch  you will see I have made a few modifications v_PostIntegrate() method within IncNavierStokes.cpp what dumps the error at a user specified IO_NormSteps. You will also need to update the internal integer holding m_normsteps.

Hope this helps.

Cheers,
Spencer.

On 14 Oct 2016, at 09:58, Selbach, Fabian <fabian.selbach@student.uni-siegen.de> wrote:

Dear All,

okay, let me define it in another way. Is there a possibility to define an output by user for example to calculate the norms or other variables and print them to the screen during simulation? Where is the best possibility to do so in the program-code? 

Thanks a lot for any help!

Best

Fabian Selbach
Von: nektar-users-bounces@imperial.ac.uk [nektar-users-bounces@imperial.ac.uk]" im Auftrag von "Selbach, Fabian [fabian.selbach@student.uni-siegen.de]
Gesendet: Donnerstag, 13. Oktober 2016 12:45
An: nektar-users@imperial.ac.uk
Betreff: [Nektar-users] Output of L2 and LInf norms during simulation

Dear Nektar++ community,

I would like to know how it's possible to get the L2 and LInf norms during a simulation at every InfoStep and not only at the end of a simulation? Is there an easy way to do so?

The postprocessing tool of fieldconvert just can do it at every CheckStep and to do so I will have to do it very often and I always need a chk.-file. Furthermore (maybe it's a bug) the postprocessing module "printfldnorms" of fieldconvert always compares to an exact solution of 0 and never to the given exact solution (but the ouput file of the solver itself compares the exact solution - so there is only a bug in the postprocessing tool).

I hope I will get an answer. Thank you.

Best regards

Fabian Selbach
_______________________________________________
Nektar-users mailing list
Nektar-users@imperial.ac.uk
https://mailman.ic.ac.uk/mailman/listinfo/nektar-users

Spencer  Sherwin
McLaren Racing/Royal Academy of Engineering Research Chair, 
Professor of Computational Fluid Mechanics,
Department of Aeronautics,
Imperial College London
South Kensington Campus
London SW7 2AZ

+44 (0) 20 759 45052