The duration of the data output in probes.dat is ten times longer than the value set for T_stop in the input_HOS.dat file.

[banzhiqing]

May I ask why there is data for 300s in the generated probes.dat file after running the program, even though I set T_stop = 30s in the input_HOS.dat file?

[gducrozet]

I do not see how this is possible... Did you check that the probes.dat file was really generated with this input file?

Best,
G.

[banzhiqing]

I do not see how this is possible... Did you check that the probes.dat file was really generated with this input file?

Best, G.

Thank you very much for your response! Indeed, I have confirmed that the probes.dat file represents the outcome of running the program with the input_HOS.dat input file. Additionally, I've noticed a discrepancy in the initial lines of information between the output probes.dat file and the data provided in my input file input_HOS.dat, as illustrated in the provided screenshot. When compiling the HOS-ocean program, I only made modifications to the makefile, specifically adjusting the address in LIBDIR and incorporating libblas.a within the LINKLIB section. Could this compilation error potentially be the cause of the observed discrepancy?

Best,
B.

[gducrozet]

Sorry, I did not notice this query was for HOS-ocean for which I am not always using probes outputs.

The behavior you observe is expected. When you choose i_case=3, the stop time you indicate in the number of peak periods, not the physical time. Since you have a peak period of 10s, the stop time is 20*10=200s. The same applies for the dimensions of the domain in the horizontal plane, it is specified in number of peak wavelengths.

[banzhiqing]

Sorry, I did not notice this query was for HOS-ocean for which I am not always using probes outputs.

The behavior you observe is expected. When you choose i_case=3, the stop time you indicate in the number of peak periods, not the physical time. Since you have a peak period of 10s, the stop time is 20*10=200s. The same applies for the dimensions of the domain in the horizontal plane, it is specified in number of peak wavelengths.

"Ah, I see! I understand the meaning of your expression now. Thank you once again for your sincere response."

[95nq]

@gducrozet
Dear professors
I have some questions for you.
Firstly,I don't really understand the difference between ky_n2 and ky.Why are there two kinds of wave number expressions in the y-direction.
Secondly,I don't understand the meanings of function"build_kth" and variable"kth_local" in "resol_HOS"
Thirdly,What does module''velocities" do? Hasn't the module "resol_HOS" sovle the problems of phiz(velocity) ?

Best Wishes

[gducrozet]

Some elements below:

• ky_n2 and ky are simply using a different number of modes in the description along y-direction. Different defintions are easier to manipulate due to the storage of positive and negative values for ky (and ky_n2).
• the build_kth simply compute ktanh(kh)
• module velocities computes the velocities inside the fluid domain (and not only on the free surface)

[95nq]

Some elements below:

• ky_n2 and ky are simply using a different number of modes in the description along y-direction. Different defintions are easier to manipulate due to the storage of positive and negative values for ky (and ky_n2).
• the build_kth simply compute k_tanh(k_h)
• module velocities computes the velocities inside the fluid domain (and not only on the free surface)

Thank you very much for your reply!Recently,I've always wondered why kth(kh) is multiplied by temp_C_Nd as shown in the figure below.I don't really understand this loop, even though it's commented.Can you explain in more detail?

Best

[gducrozet]

This loop corresponds to the computation of the vertical derivatives of phi^(m) at different orders.
The build_kth build the factor you need to multiply the modal amplitude to compute this derivative at a given order.

In short, it is computing the following equations:

[banzhiqing]

@gducrozet

Dear Professor,

I would like to inquire about a matter regarding post-processing in HOS-Ocean. I am interested in obtaining the x-direction velocity profile Vx at the point (0,0). Specifically, I wish to acquire evenly spaced Vx values within a depth of 200 meters (i.e., z=(-200,0)), with an interval of 0.5 meters. However, I have noticed that the settings in my plot result in additional content in the output VP_card.dat file. Could you kindly advise if my setup is correct?

[gducrozet]

Hello @banzhiqing

It seems there is an issue in the writing of the VP_card file. Not sure where it comes from. I do not have a lot of time to look at it but if you change the following file in sources/PostProcessing it should solve your issue: output_post_process.f90.txt
NB: Remove the .txt extension, GitHub comments does not support .f90 files

Please let me know if it solves your issue

[95nq]

@gducrozet
Dear Professor,I think the default wave main direction is the x-axis,How can I change the main direction wave?I wanna transform it to y-axis for 3D wave