Up to Installation and compilation
Hello!
I am trying to couple the two toy models given in the oasis installation files but I have several problems. I run both toy models on 4 processors each and run them on a slurm based server with
>>> srun -np 4 atmos : -np 4 ocean
1. I never get past the end of the 'initialisation phase'.
2. Even though, I initialised the two toy models with
CALL oasis_init_comp (compid,'ocean_component',ierror)
and
CALL oasis_init_comp (compid,'atmos_component',ierror)
the values of the variable 'compid' is always the same. Unfortunately I then get the error
(oasis_coupler_setup) ERROR: namcouple variable not used: FIELD_SEND_ATM
(oasis_coupler_setup) ERROR: namcouple variable not used: FIELD_SEND_OCN
But I'm pretty sure my fields are well written and I think my mistake could be from the definition of the oasis init file. I also saw that the partition id ('il_part_id') is the same on all processors, which seems weird but could be a result of the previous mistake. Any help would help.
Thanks in advance,
CE
Hey CE, Your init looks ok. As long as they register with different compnames (arg #2 in OASIS_INIT_COMP), you should get different IDs back (arg #1 in OASIS_INIT_COMP). See mod_oasis_method.F90: INTEGER (kind=ip_intwp_p),intent(out) :: mynummod !< component model ID CHARACTER(len=*) ,intent(in) :: cdnam !< model name Not sure why you would get the same id though.. The error you posted typically originates from variables that are designated for coupling in the namcouple file, but do not get called for and oasis_put or oasis_get in the source codes of your models. What do these calls look like for you? Best, Jan S.
Hi CE, Are you sure that the srun command launches the two applications atoms and ocean into one same MPI_COMM_WORLD MPI communicator ? I typically use mpirun: mpirun -np $nproces1 ./$exe1 : -np $nproces2 ./$exe2 regards, Sophie