Re: [Nektar-users] Aeroacoustics using cwipi in nektar++-5
******************* This email from originates from outside Imperial. Do not click on links and attachments unless you recognise the sender. If you trust the sender, add them to your safe senders list https://spam.ic.ac.uk/SpamConsole/Senders.aspx to disable email stamping for this address. ******************* Hi Nitish, i am glad to hear you got the setup working. Regarding the forcing, you need to set <FIELDFORCETIMEFCN> 1.0 </FIELDFORCETIMEFCN> (see e.g. solvers/DummySolver/Tests/Dummy_3DCubeCwipi_0.xml for an example) This is a workaround for an incompatibility between the way the forcing is implemented and how the coupling works. Let me know if it worked for you so i can add this piece if info to the userguide. Cheers, Kilian Am 09.01.20 um 16:16 schrieb Nitish Arya:
Dear Kilian,
Thank you very much for your suggestion. The cwipi functionality in the new release really solved my problem. I also successfully compiled the openfoam interface [3] with the acoustic solver in nektar. The reception of base fields (u0,v0,w0) is absolutely fine. However, when I tried receiving the source terms (F_0_p, F_0_u, F_0_v, F_0_w), the corresponding fields are not reflected in nektar. The source terms are zero everywhere (since they were initialized to zero in the configuration file). This could mean that after the transfer they are being modified to the value in the configuration file. Am I missing something?
I have also attached the conditions file in the mail.
regards, Nitish
participants (1)
- 
                
                Kilian Lackhove