Up to Starting with OASIS3-MCT (first steps, tutorial, ...)
Hi, I just download and compile OASIS3-MCT 5.0 and I also compile the tutorial model. I could also run the tutorial model and apparently it worked ok. Now I am trying to run the tutorial coupled model(tutorial_oa), so I followed the instructions of the document,Instead of doing extra file changes, I compiled atmos.F90_oa and ocean.F90_oa directly and ran run_tutorial_oa directly after changing the paths to the files within run_tutorial_oa, and it didn't show the error in the terminal. But in the debug file (I chose nproc_ exe1=4, nproc_exe2=4) only debug01.000000 and debug02.000000 show (oasis_terminate) SUCCESSFUL RUN, according to the instructions of the document, if run successfully, all the debugs will be run. files should show a successful run. Later I checked the out file (atmos.out_100 as an example) and it settled as follows: ----------------------------------------------------------- I am atmos process with rank : 0 in my local communicator gathering 4 processes ---------------------------------------------------------- Local partition definition il_extentx, il_extenty, il_size, il_offsetx, il_offsety, il_offset = 96 18 1728 0 0 0 ig_paral = 1 0 1728 grid_lat_atmos maximum and minimum -46.901409149169922 -90.000000000000000 var_id FRECVATM, var_id FSENDATM 1 2 End of initialisation phase Timestep, field min and max value 0 0.0000000000000000 2.3569737913148856 1800 -1.0000000000000000 -1.0000000000000000 3600 0.0000000000000000 2.3569737017329220 5400 -1.0000000000000000 -1.0000000000000000 7200 0.0000000000000000 4.7139474034658440 9000 -1.0000000000000000 -1.0000000000000000 10800 0.0000000000000000 7.0709211051987655 12600 -1.0000000000000000 -1.0000000000000000 End of the program This is obviously some problem with the coupling process, similarly I have looked at files like FIELD_SEND_ATM_atmos_component_02.nc and the plotting reveals that the latitude and longitude in these nc's don't even correspond to each other (e.g. A is an island at a certain latitude and longitude and B is an ocean at that latitude and longitude), can you please tell me if these problems are due to the namcouple_ LAG file setting problem(I'm using namcouple directly from the example folder without modification)? Or is it a problem with the model code itself? I have generated all the files that should be generated during the coupling model process, and the coupler itself should run successfully, right? Thanks in advance. Regards Tony
Hi Tony, Sorry for taking so long to answer your mail. Your run seems perfectly fine to me and I do have the same results. You are right that only debug01.000000 and debug02.000000 show "SUCCESSFUL RUN" (I would have to go in the code to check why this is the case) but all debug files show "EXIT (oasis_terminate)" which means that everything is fine. I will have to correct the local documentation, sorry about that. In the atmos.out_xxx files you get -1 for the timesteps where the coupling does not occur but this is normal. Hoping this helps, Sophie
Hi Sophie, Thank you very much for your answer, I will continue to carry out the coupling between different software models and communicate with you in real time about the problem, I hope OASIS3-MCT is getting better and better! Regards Tony