2D geometry but rotates about the z_axis
******************* This email 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. ******************* Hello Stan, I'm grateful for your response. I'm sorry, but I'm new at using Nektar. For me, it doesn't matter which axis the channel spins on as long as it does it from the channel's face. I thought that Nektar only offers the option of rotation about the z axis. Is that correct? I.e., can I rotate the channel around any axis I want? Or can I just insert velocity values for the channel wall instead of using the "forcing" option and all of its requirements? I mean like this <REGION REF="0"> <D VAR="u" VALUE="-2.0*y"/> <D VAR="v" VALUE="2.0*(x-0.4)"/> <D VAR="T" VALUE="1600"/> <N VAR="p" USERDEFINEDTYPE="H" VALUE="0"/> </REGION> In addition, according to your suggestion, can making a homogeneous (Fourier) expansion result in a 3D mesh with a high computational cost? I want to know whether there is a difference in computation time between quasi-3D and normal 3D so that I can just create a 3D model using Gmesh and convert it to Nektar. Thank you in advance, Ali -- *University of Kerbala* website : https://uokerbala.edu.iq/en/ <https://uokerbala.edu.iq/en/> Location : https://goo.gl/maps/pNQ9LkdMbi72 <https://goo.gl/maps/pNQ9LkdMbi72> *This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. *
Hi Ali, So, if I understand you want to apply body forcing, that mimics the rotational motion? I think this should be possible, but I did not do anything like that. Also you might want to look at the MovingReferenceFrame Forcing in the manual. The quasi-3D (Fourier) expansion is computationally less expensive in general, but requires that the problem be periodic in the expansion direction. Cheers, Stan *Faculty of Power and Aeronautical Engineering* Nowowiejska 21/25 Str. 00-665 Warsaw, Poland phone +48 (22) 234 51 70 <https://www.pw.edu.pl/engpw> On 9.02.2023 19:32, Ali Ahmed Abdulrasool - علي احمد عبد الرسول wrote:
This email from ali.abdulrasool@uokerbala.edu.iq 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.
Hello Stan,
I'm grateful for your response. I'm sorry, but I'm new at using Nektar. For me, it doesn't matter which axis the channel spins on as long as it does it from the channel's face. I thought that Nektar only offers the option of rotation about the z axis. Is that correct? I.e., can I rotate the channel around any axis I want?
Or can I just insert velocity values for the channel wall instead of using the "forcing" option and all of its requirements? I mean like this
<REGION REF="0"> <D VAR="u" VALUE="-2.0*y"/> <D VAR="v" VALUE="2.0*(x-0.4)"/> <D VAR="T" VALUE="1600"/> <N VAR="p" USERDEFINEDTYPE="H" VALUE="0"/> </REGION>
In addition, according to your suggestion, can making a homogeneous (Fourier) expansion result in a 3D mesh with a high computational cost? I want to know whether there is a difference in computation time between quasi-3D and normal 3D so that I can just create a 3D model using Gmesh and convert it to Nektar.
Thank you in advance,
Ali
------------------------------------------------------------------------ *University of Kerbala*
website : https://uokerbala.edu.iq/en/ <https://uokerbala.edu.iq/en/> Location : https://goo.gl/maps/pNQ9LkdMbi72 <https://goo.gl/maps/pNQ9LkdMbi72>
/This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. /
_______________________________________________ Nektar-users mailing list Nektar-users@imperial.ac.uk https://mailman.ic.ac.uk/mailman/listinfo/nektar-users
******************* This email 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. ******************* Dear Stan, Thank you again for your reply. Exactly, I wanted to rotate the channel by applying body forcing. I found only two ways to do that in Nektar: 1. Time-dependent mapping of coordinates, 2, add a MovingReferenceFrame body force and solve the absolute velocity in the body frame. However, neither is helpful for me. If I use " VCSMapping", the temperature will not work for me. If I select "MovingReferenceFrame", y_axis rotation will not work for me either. I still don't want to go for Qusi-3D or 3D simulations, can I modify something in " VCSMapping" scheme to include temperature? I really appreciate your help, Best, Ali PS: I am attaching the files that I am dealing with. On Thu, Feb 9, 2023 at 9:32 PM Ali Ahmed Abdulrasool - علي احمد عبد الرسول <ali.abdulrasool@uokerbala.edu.iq> wrote:
Hello Stan,
I'm grateful for your response. I'm sorry, but I'm new at using Nektar. For me, it doesn't matter which axis the channel spins on as long as it does it from the channel's face. I thought that Nektar only offers the option of rotation about the z axis. Is that correct? I.e., can I rotate the channel around any axis I want?
Or can I just insert velocity values for the channel wall instead of using the "forcing" option and all of its requirements? I mean like this
<REGION REF="0"> <D VAR="u" VALUE="-2.0*y"/> <D VAR="v" VALUE="2.0*(x-0.4)"/> <D VAR="T" VALUE="1600"/> <N VAR="p" USERDEFINEDTYPE="H" VALUE="0"/> </REGION>
In addition, according to your suggestion, can making a homogeneous (Fourier) expansion result in a 3D mesh with a high computational cost? I want to know whether there is a difference in computation time between quasi-3D and normal 3D so that I can just create a 3D model using Gmesh and convert it to Nektar.
Thank you in advance,
Ali
-- *University of Kerbala* website : https://uokerbala.edu.iq/en/ <https://uokerbala.edu.iq/en/> Location : https://goo.gl/maps/pNQ9LkdMbi72 <https://goo.gl/maps/pNQ9LkdMbi72> *This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. *
participants (2)
-
Ali Ahmed Abdulrasool - علي احمد عبد الرس ول
-
Stanisław Gepner