Welcome,
Guest
|
TOPIC: ARTEMIS-TELEMAC2D-SISYPHE COUPLED MODEL
ARTEMIS-TELEMAC2D-SISYPHE COUPLED MODEL 6 years 5 months ago #30665
|
Hello community,
I have 2 questions if some one can help me: 1- First i tried to chaining TOMAWAC and ARTEMIS, i have done all the necessary and the computation run!!, but with-out result and any errors, it's juste run for a long time and it's don't stop. When i stop it, i notice that it's related to the spectrum. It's mentionned below that i am out of the TOMAWAC SPECTRUM. The problem ,i don't know how i can check this? OUT OF THE TOMAWAC SPECTRUM INDD,INDF= 1 0 27.922207999999998 245.952000000000 0 FMIN , FMAX= 5.0000000745058060E-002 5.0000000745058060E-002 ALARM ROUTINE STWC : YOU ASK FOR A PERIOD/DIRECTION OUT OF THE TOMAWAC SPECTRUM INDD,INDF= 1 0 27.942205999999995 245.952000000000 0 FMIN , FMAX= 5.0000000745058060E-002 5.0000000745058060E-002 ALARM ROUTINE STWC : YOU ASK FOR A PERIOD/DIRECTION OUT OF THE TOMAWAC SPECTRUM INDD,INDF= 1 0 27.962203999999996 245.952000000000 0 FMIN , FMAX= 5.0000000745058060E-002 5.0000000745058060E-002 ALARM ROUTINE STWC : YOU ASK FOR A PERIOD/DIRECTION OUT OF THE TOMAWAC SPECTRUM INDD,INDF= 1 0 27.982201999999997 245.952000000000 0 FMIN , FMAX= 5.0000000745058060E-002 5.0000000745058060E-002 ALARM ROUTINE STWC : YOU ASK FOR A PERIOD/DIRECTION OUT OF THE TOMAWAC SPECTRUM INDD,INDF= 1 0 28.002199999999998 245.952000000000 0 2- My second question is for the coupling of ARTEMIS-TELEMAC2D-SISYPHE, i want to use this coupling model the make in consideration the phenomena of reflection. So in this version, i can use this coupling method or it's don't possible? Thank you in advance. Best regards. YASMINA. |
The administrator has disabled public write access.
|
ARTEMIS-TELEMAC2D-SISYPHE COUPLED MODEL 6 years 5 months ago #30678
|
Hello Yasmina,
Costas |
The administrator has disabled public write access.
|
ARTEMIS-TELEMAC2D-SISYPHE COUPLED MODEL 6 years 5 months ago #30686
|
Hello costas,
1. Yes i had followed your advices, my fault is in the direction of propagation wave, it's not the same in ARTEMIS and TOMAWAC so now i had make 135° for TOMAWAC and -45° for ARTEMIS. The simulation now get an error below: NAME OF THE STUDY : EXEMPLE UTILISATION : AGITATION baie saint malo OPENING FILES FOR ARTEMIS - FILE C:\Stage_yasmina\ModÚlisation_hydrodynamique\medium_box\ARTEMIS_TO WAC\art_chwac.cas_2018-06-20-14h41min01s\ARTGEO OF TYPE BIG_ENDIAN - FILE C:\Stage_yasmina\ModÚlisation_hydrodynamique\medium_box\ARTEMIS_TO WAC\art_chwac.cas_2018-06-20-14h41min01s\ARTGEO IS SINGLE PRECISION ***************************** * MEMORY ORGANIZATION * ***************************** READ_MESH_INFO: TITLE= newSelafin NUMBER OF ELEMENTS: 353661 NUMBER OF POINTS: 178645 FORMAT NOT INDICATED IN TITLE MXPTEL (BIEF) : MAXIMUM NUMBER OF ELEMENTS AROUND A POINT: 9 MAXIMUM NUMBER OF POINTS AROUND A POINT: 9 CORRXY (BIEF):NO MODIFICATION OF COORDINATES MESH: MESH ALLOCATED ************************************* * END OF MEMORY ORGANIZATION: * ************************************* INBIEF (BIEF): NOT A VECTOR MACHINE (ACCORDING TO YOUR DATA) STRCHE (BIEF): NO MODIFICATION OF FRICTION THERE IS 25 ISLAND(S) IN THE DOMAIN THERE IS 1 LIQUID BOUNDARIES: BOUNDARY 1 : BEGINS AT BOUNDARY POINT: 2693 , WITH GLOBAL NUMBER: 177073 AND COORDINATES: 332862.4 6854134. ENDS AT BOUNDARY POINT: 3294 , WITH GLOBAL NUMBER: 2 AND COORDINATES: 323600.8 6850620. THERE IS 26 SOLID BOUNDARIES: BOUNDARY 1 : BEGINS AT BOUNDARY POINT: 3294 , WITH GLOBAL NUMBER: 2 AND COORDINATES: 323600.8 6850620. ENDS AT BOUNDARY POINT: 2693 , WITH GLOBAL NUMBER: 177073 AND COORDINATES: 332862.4 6854134. BOUNDARY 2 : BEGINS AT BOUNDARY POINT: 3344 , WITH GLOBAL NUMBER: 13921 AND COORDINATES: 325303.7 6851330. ENDS AT BOUNDARY POINT: 3344 , WITH GLOBAL NUMBER: 13921 AND COORDINATES: 325303.7 6851330. BOUNDARY 3 : BEGINS AT BOUNDARY POINT: 3338 , WITH GLOBAL NUMBER: 13160 AND COORDINATES: 325242.8 6851400. ENDS AT BOUNDARY POINT: 3338 , WITH GLOBAL NUMBER: 13160 AND COORDINATES: 325242.8 6851400. BOUNDARY 4 : BEGINS AT BOUNDARY POINT: 3374 , WITH GLOBAL NUMBER: 33212 AND COORDINATES: 326825.9 6851141. ENDS AT BOUNDARY POINT: 3374 , WITH GLOBAL NUMBER: 33212 AND COORDINATES: 326825.9 6851141. BOUNDARY 5 : BEGINS AT BOUNDARY POINT: 3616 , WITH GLOBAL NUMBER: 119384 AND COORDINATES: 329804.8 6848206. ENDS AT BOUNDARY POINT: 3616 , WITH GLOBAL NUMBER: 119384 AND COORDINATES: 329804.8 6848206. BOUNDARY 6 : BEGINS AT BOUNDARY POINT: 3365 , WITH GLOBAL NUMBER: 32429 AND COORDINATES: 326766.1 6851296. ENDS AT BOUNDARY POINT: 3365 , WITH GLOBAL NUMBER: 32429 AND COORDINATES: 326766.1 6851296. BOUNDARY 7 : BEGINS AT BOUNDARY POINT: 3576 , WITH GLOBAL NUMBER: 105675 AND COORDINATES: 329622.7 6849623. ENDS AT BOUNDARY POINT: 3576 , WITH GLOBAL NUMBER: 105675 AND COORDINATES: 329622.7 6849623. BOUNDARY 8 : BEGINS AT BOUNDARY POINT: 3590 , WITH GLOBAL NUMBER: 114946 AND COORDINATES: 329741.5 6849635. ENDS AT BOUNDARY POINT: 3590 , WITH GLOBAL NUMBER: 114946 AND COORDINATES: 329741.5 6849635. BOUNDARY 9 : BEGINS AT BOUNDARY POINT: 3615 , WITH GLOBAL NUMBER: 118317 AND COORDINATES: 329790.4 6849640. ENDS AT BOUNDARY POINT: 3615 , WITH GLOBAL NUMBER: 118317 AND COORDINATES: 329790.4 6849640. BOUNDARY 10 : BEGINS AT BOUNDARY POINT: 3624 , WITH GLOBAL NUMBER: 121848 application called MPI_Abort(MPI_COMM_WORLD, 2) - process 0 AND COORDINATES: 329839.4 6849648. ENDS AT BOUNDARY POINT: 3624 , WITH GLOBAL NUMBER: 121848 AND COORDINATES: 329839.4 6849648. BOUNDARY 11 : BEGINS AT BOUNDARY POINT: 3628 , WITH GLOBAL NUMBER: 124099 AND COORDINATES: 329870.3 6849652. ENDS AT BOUNDARY POINT: 3628 , WITH GLOBAL NUMBER: 124099 AND COORDINATES: 329870.3 6849652. BOUNDARY 12 : BEGINS AT BOUNDARY POINT: 3633 , WITH GLOBAL NUMBER: 125587 AND COORDINATES: 329890.9 6849724. ENDS AT BOUNDARY POINT: 3633 , WITH GLOBAL NUMBER: 125587 AND COORDINATES: 329890.9 6849724. BOUNDARY 13 : BEGINS AT BOUNDARY POINT: 3655 , WITH GLOBAL NUMBER: 127545 AND COORDINATES: 329917.6 6849741. ENDS AT BOUNDARY POINT: 3655 , WITH GLOBAL NUMBER: 127545 AND COORDINATES: 329917.6 6849741. BOUNDARY 14 : BEGINS AT BOUNDARY POINT: 3532 , WITH GLOBAL NUMBER: 71515 AND COORDINATES: 329080.8 6850968. ENDS AT BOUNDARY POINT: 3532 , WITH GLOBAL NUMBER: 71515 AND COORDINATES: 329080.8 6850968. BOUNDARY 15 : BEGINS AT BOUNDARY POINT: 3352 , WITH GLOBAL NUMBER: 28675 AND COORDINATES: 326486.9 6853654. ENDS AT BOUNDARY POINT: 3352 , WITH GLOBAL NUMBER: 28675 AND COORDINATES: 326486.9 6853654. BOUNDARY 16 : BEGINS AT BOUNDARY POINT: 3393 , WITH GLOBAL NUMBER: 30063 AND COORDINATES: 326589.8 6853662. ENDS AT BOUNDARY POINT: 3393 , WITH GLOBAL NUMBER: 30063 AND COORDINATES: 326589.8 6853662. BOUNDARY 17 : BEGINS AT BOUNDARY POINT: 3546 , WITH GLOBAL NUMBER: 91823 AND COORDINATES: 329478.7 6850854. ENDS AT BOUNDARY POINT: 3546 , WITH GLOBAL NUMBER: 91823 AND COORDINATES: 329478.7 6850854. BOUNDARY 18 : BEGINS AT BOUNDARY POINT: 3389 , WITH GLOBAL NUMBER: 34110 AND COORDINATES: 326894.6 6853688. ENDS AT BOUNDARY POINT: 3389 , WITH GLOBAL NUMBER: 34110 AND COORDINATES: 326894.6 6853688. BOUNDARY 19 : BEGINS AT BOUNDARY POINT: 3656 , WITH GLOBAL NUMBER: 145338 AND COORDINATES: 330209.5 6851138. ENDS AT BOUNDARY POINT: 3656 , WITH GLOBAL NUMBER: 145338 AND COORDINATES: 330209.5 6851138. BOUNDARY 20 : BEGINS AT BOUNDARY POINT: 3510 , WITH GLOBAL NUMBER: 47588 AND COORDINATES: 327835.6 6854149. ENDS AT BOUNDARY POINT: 3510 , WITH GLOBAL NUMBER: 47588 AND COORDINATES: 327835.6 6854149. BOUNDARY 21 : BEGINS AT BOUNDARY POINT: 3505 , WITH GLOBAL NUMBER: 47063 AND COORDINATES: 327805.8 6854192. ENDS AT BOUNDARY POINT: 3505 , WITH GLOBAL NUMBER: 47063 AND COORDINATES: 327805.8 6854192. BOUNDARY 22 : BEGINS AT BOUNDARY POINT: 3523 , WITH GLOBAL NUMBER: 67745 AND COORDINATES: 328893.2 6854456. ENDS AT BOUNDARY POINT: 3523 , WITH GLOBAL NUMBER: 67745 AND COORDINATES: 328893.2 6854456. BOUNDARY 23 : BEGINS AT BOUNDARY POINT: 3514 , WITH GLOBAL NUMBER: 59617 AND COORDINATES: 328485.2 6854993. ENDS AT BOUNDARY POINT: 3514 , WITH GLOBAL NUMBER: 59617 AND COORDINATES: 328485.2 6854993. BOUNDARY 24 : BEGINS AT BOUNDARY POINT: 3517 , WITH GLOBAL NUMBER: 60905 AND COORDINATES: 328549.1 6854946. ENDS AT BOUNDARY POINT: 3517 , WITH GLOBAL NUMBER: 60905 AND COORDINATES: 328549.1 6854946. BOUNDARY 25 : BEGINS AT BOUNDARY POINT: 3520 , WITH GLOBAL NUMBER: 64354 AND COORDINATES: 328722.8 6854947. ENDS AT BOUNDARY POINT: 3520 , WITH GLOBAL NUMBER: 64354 AND COORDINATES: 328722.8 6854947. BOUNDARY 26 : BEGINS AT BOUNDARY POINT: 3674 , WITH GLOBAL NUMBER: 174742 AND COORDINATES: 332485.5 6853334. ENDS AT BOUNDARY POINT: 3674 , WITH GLOBAL NUMBER: 174742 AND COORDINATES: 332485.5 6853334. =================================================== ========== READING SPECTRUM FROM TOMAWAC ========== ERROR 1003 DURING CALL OF GET_MESH_COORD_SRF:GET_OBJ ERROR TEXT: HERMES_FILE_NOT_OPENED_ERR PLANTE: PROGRAM STOPPED AFTER AN ERROR RETURNING EXIT CODE: 2 so with this error i understand that i must use the fortran file, but i am not good in programming so when i run my simulation i get another error below: Loading Options and Configurations ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ _____ ____ __ |___ | |___ \ /_ | __ __ _/ / _ __ __) | _ __ | | \ \ / / |_ _| | '_ \ |__ < | '__| | | \ V / / / | |_) | ___) || | | | \_/ /_/ | .__/ |____/ |_| |_| | | |_| _ _ __ __ _____ __ __ _| || |_ /_ |/_ || ____| / / /_ | _ __ ___ __ __ |_ __ _| | | | || |__ / /_ | | | '__| / _ \\ \ / / _| || |_ | | | ||___ \ | '_ \ | | | | | __/ \ V / _ |_ __ _| | | | | ___) || (_) | | | |_| \___| \_/ (_) |_||_| |_| |_||____/ \___/ |_| ... parsing configuration file: C:\opentelemac-mascaret\v7p3r1\configs\systel_pa rallel_v7p3r1.cfg Running your CAS file for: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ +> configuration: wing64mpi +> root: C:\opentelemac-mascaret\v7p3r1 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ... reading the main module dictionary ... processing the main CAS file(s) +> running in English ... handling temporary directories ... checking coupling between codes ... checking parallelisation ... first pass at updating all input files copying: art_chwac.cas C:\Stage_yasmina\ModÚlisation_hydrodynamique\med ium_box\ARTEMIS_TOMAWAC\art_chwac.cas_2018-06-20-14h44min49s\ARTCAS copying: bathy_baie.slf C:\Stage_yasmina\ModÚlisation_hydrodynamique\me dium_box\ARTEMIS_TOMAWAC\art_chwac.cas_2018-06-20-14h44min49s\ARTGEO copying: BC_baie.cli C:\Stage_yasmina\ModÚlisation_hydrodynamique\mediu m_box\ARTEMIS_TOMAWAC\art_chwac.cas_2018-06-20-14h44min49s\ARTCLI copying: artemis.dico C:\Stage_yasmina\ModÚlisation_hydrodynamique\medi um_box\ARTEMIS_TOMAWAC\art_chwac.cas_2018-06-20-14h44min49s\ARTDICO ... checking the executable > requires re-compilation creating: C:\Stage_yasmina\ModÚlisation_hydrodynamique\medium_box\ARTEMI S_TOMAWAC\art_chwac.cas_2018-06-20-14h44min49s\user_fortran copying: art.f90 C:\Stage_yasmina\ModÚlisation_hydrodynamique\medium_bo x\ARTEMIS_TOMAWAC\art_chwac.cas_2018-06-20-14h44min49s\user_fortran compiling objs: art.f90:242.9: END DO 1 Error: Expecting END SUBROUTINE statement at (1) art.f90:315.56: CALL FILTER(ZF,MAS,T1,T2,AM1,'MATMAS ', 1 Error: Syntax error in argument list at (1) art.f90:316.6: & 1.D0,T1,T1,T1,T1,T1,T1,MESH,MSK,MASKEL,LISFON) 1 Error: Invalid character in name at (1) art.f90:360.6: & (X,Y,NPOIN) 1 Error: Invalid character in name at (1) art.f90:123.21: HB%R(I) = HSARTE(MESH%NBOR%I(I)) 1 Error: Function 'hsarte' at (1) has no IMPLICIT type art.f90:124.21: TETAB%R(I) = HSARTE(MESH%NBOR%I(I)) 1 Error: Function 'hsarte' at (1) has no IMPLICIT type art.f90:167.25: DO I= 162011,154571 1 Warning: DO loop at (1) will be executed zero times art.f90:174.25: DO I= 161117,137278 1 Warning: DO loop at (1) will be executed zero times art.f90:190.21: DO I= 171548,162011 1 Warning: DO loop at (1) will be executed zero times art.f90:204.19: DO I= 173417,161117 1 Warning: DO loop at (1) will be executed zero times art.f90:213.25: DO I= 212426,210968 1 Warning: DO loop at (1) will be executed zero times art.f90:220.20: DO I= 179375,7 1 Warning: DO loop at (1) will be executed zero times art.f90:227.25: DO I= 186032,142983 1 Warning: DO loop at (1) will be executed zero times art.f90:412.34: INTEGER, INTENT(IN) :: NPOIN 1 Error: Symbol at (1) is not a DUMMY variable art.f90:413.49: DOUBLE PRECISION, INTENT(INOUT) :: X(NPOIN),Y(NPOIN) 1 Error: Symbol at (1) is not a DUMMY variable art.f90:413.58: DOUBLE PRECISION, INTENT(INOUT) :: X(NPOIN),Y(NPOIN) 1 Error: Symbol at (1) is not a DUMMY variable runCAS: failed to compile |processExecutable: could not compile your FORTRAN (runcode=1). | |... The following command failed for the reason above (or below) |gfortran -c -cpp -O2 -fconvert=big-endian -DHAVE_MPI -frecord-marker=4 -I C :\opentelemac-mascaret\v7p3r1\builds\wing64mpi\lib\utils\special -I C:\opentele mac-mascaret\v7p3r1\builds\wing64mpi\lib\utils\hermes -I C:\opentelemac-mascare t\v7p3r1\builds\wing64mpi\lib\utils\parallel -I C:\opentelemac-mascaret\v7p3r1\ builds\wing64mpi\lib\utils\damocles -I C:\opentelemac-mascaret\v7p3r1\builds\wi ng64mpi\lib\utils\bief -I C:\opentelemac-mascaret\v7p3r1\builds\wing64mpi\lib\a rtemis -I C:\opentelemac-mascaret\mpich2\include art.f90 The ARTEMIS-TOMAWAC.CAS: The TOMAWAC steering file: The fortran file that i used: 02-For my second question, no i am not good in programing and the reflection i realy need it because i will simulate sediment transport near a harbour. So what do you think if i run the ARTEMIS-TELEMAC2D, after i will extract from ARTEMIS the height wave varying in time and space, i will use this file in TELEMAC2D as a limit condition of wave, what do you think? is it a good and possible methodology? Sorry for all this question but i am still beginner in TELEMAC system. Best regards. YASMINA. |
The administrator has disabled public write access.
|