Welcome, Guest
Username: Password: Remember me

TOPIC: Tomawac - Artemis chaining

Tomawac - Artemis chaining 4 years 3 weeks ago #37026

  • Fab
  • Fab's Avatar
Hello,

I am trying to use NESTING WITHIN TOMAWAC OUTER MODEL option number 2 to impose wave spectrum from a Tomawac model along an Artemis model boundary.

I wonder how to generate the binary liquid boundary file called by Artemis with the keyword TOMAWAC LIQUID BOUNDARY FILE (like "tom_westcoast.lqd" file called in Artemis westcoast example).

Thanks for your answer,

Regards
The administrator has disabled public write access.

Tomawac - Artemis chaining 4 years 3 weeks ago #37028

  • TimN
  • TimN's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 67
Hello community,
and hi Fab,

Fab, thank you for the question. I'm struggling with the same problem at the moment and couldn't find any "how-to" tutorial for running an artemis simulation with a superimposed tomawac run. I also couldn't find a current artemis user-manual in v8p1, am I missing something?

I also tried using the option "NESTING WITHIN TOMAWAC OUTER MODEL = 2" and gave my TOMAWAC OUTER RESULT FILE , as well as the desired INSTANT FOR READING TOMAWAC SPECTRUM at which I want the waves beeing initiated into my artemis domain.

As far as I understand from the "westcoast" example, also the TOMAWAC OUTER SPECTRAL FILE , the TOMAWAC LIQUID BOUNDARY FILE and the COORDINATES OF THE REFERENCE F SPECTRUM are mandatory?
Any deeper insight in what's mandatory or how to nest an artemis in a tomowac simulation would be much appreciated.

kind regards,
Tim
The administrator has disabled public write access.

Tomawac - Artemis chaining 4 years 3 weeks ago #37032

  • cyamin
  • cyamin's Avatar
  • OFFLINE
  • openTELEMAC Guru
  • Posts: 997
  • Thank you received: 234
Hello Tim and Fab,

You are right about the latest ARTEMIS manual, there is none. Regarding your issue, first of all I suggest you read the paper "ARTEMIS developments at HR Wallingford" from the TUC2018 Conference Proceedings. It is the only documentation of the TOMAWAC-ARTEMIS chaining.

I believe things have moved on a bit since then and developments are undocumented. I quickly mention the keywords you need to define to setup chaining (from my notes, in hope they are not outdated):
TOMAWAC
PUNCTUAL RESULTS FILE
FILE WITH COORDINATES OF SPECTRA TO WRITE (a dat file with sample coordinates along the ARTEMIS boundary)
2D RESULTS FILE (of course)
ARTEMIS
TOMAWAC OUTER SPECTRAL FILE: .SPE <--PUNCTUAL RESULTS FILE
TOMAWAC OUTER RESULT FILE : .SLF <-- 2D RESULTS FILE
TOMAWAC LIQUID BOUNDARY FILE: .LQD <--Created with 'convert_to_bnd.py' python script from 'pretel'.

INSTANT FOR READING TOMAWAC SPECTRUM: [time]
NESTING WITHIN TOMAWAC OUTER MODEL: 2
COORDINATES OF THE REFERENCE F SPECTRUM: [x];[y]

The .LQD file can be created as follows:
convert_to_bnd.py ARTEcliFile ARTEgeoFile TOMslfFile ARTEbndFile

Best Regards,
Costas
The administrator has disabled public write access.
The following user(s) said Thank You: TimN, Malliouri

Tomawac - Artemis chaining 4 years 3 weeks ago #37034

  • TimN
  • TimN's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 67
HI Costa,

thank you very much. Your explanation was of great help! From the TOMAWAC part, I got everything worked out.
So, I created the .dat file, got my PUNCTUAL RESULTS FILE, and the 2D RESULTS FILE.

I found out that the convert_to_bnd.py is replaced by the converter.py module. However, by using the option "generate_bnd" in the way like -> converter.py generate_bnd ARTcli_file ARTgeo_file TOMslf_file new.lqd_file it does probably the same as the former python module.

Therefore I set up my artemis steering file and paid attention to the keyword you gave.
But I receive an error and I guess it's down to the INSTANT FOR READING TOMAWAC SPECTRUM.
In my artemis .cas file I defined the instant to be at 6 h of the tomawac simulation (which was a 12h simulation). Therefore I put INSTANT FOR READING TOMAWAC SPECTRUM to 21600. thinking the instant is in sec. which didn't work. I then tried the half of my computational steps which was 24 (total runtime TOMAWAC: time step 900. sec with 48 time steps).

The comandline gives the error for READ_BIN_FRLIQ...-1 DURING CALL OF READ_BIN_FRLIQ:GET_DATA_TIMESTEP

I have uploaded a screenshot of the problem. Have you ever encounter this? Any Idea what is wrong? I've also the feeling there is some problem in my data format as the Note indicates a floating-point exception and an error in IEEE_DENORMAL in WACLQD

Cheers Tim
Attachments:
The administrator has disabled public write access.

Tomawac - Artemis chaining 4 years 3 weeks ago #37036

  • cyamin
  • cyamin's Avatar
  • OFFLINE
  • openTELEMAC Guru
  • Posts: 997
  • Thank you received: 234
Hello Tim,
INSTANT FOR READING TOMAWAC SPECTRUM refers to TIME not TIMESTEP. Scan your results file and ask for a time that actually exists. Maybe you need to adjust the time asked with respect to PERIOD FOR GRAPHIC PRINTOUTS. Anyway, it is difficult to say what could be your issue without looking at your steering files.
Also, set DEBUGGER=1 and redirect console output to a .txt file and post it on the forum.
Costas
The administrator has disabled public write access.

Tomawac - Artemis chaining 4 years 3 weeks ago #37037

  • TimN
  • TimN's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 67
Hi Coastas,

as I wasn't sure about the TIME I already tried different setups in the ART steering file; trying both a certain number of timesteps and an actual time. By trying different time formats I found out that it has to be an actual time written in seconds.
As my tomawac simulation is 12h I then defined the INSTANT FOR READING TOMAWAC SPECTRUM to be 21600. to read the waves from tomawac after 6h of simulation time in ARTEMIS. I also set the DEBUGGER to 1 as you mentioned.
However, I still get the same error of 'floating-point exceptions'.

I've checked comparable example cases from the artemis (beach, westcoast) and tomawac (imposed_spect) directories and compared steering files as well as result files in hope to find any deviations.

I've now generated the console output and put both .cas files in the attachment. At the moment I'm pretty stuck.

Hope you have an idea :)

cheers,
Tim
Attachments:
The administrator has disabled public write access.

Tomawac - Artemis chaining 4 years 3 weeks ago #37038

  • cyamin
  • cyamin's Avatar
  • OFFLINE
  • openTELEMAC Guru
  • Posts: 997
  • Thank you received: 234
Hi Tim,
Have you checked the results are OK, i.e. you don't have NAN (or too small) values in your results. You can use 'scan_selafin.py' and 'scan_spectral.py' scripts to read LQD and SPE files and check they are OK.
TIMESTEP looks too large. I am also sure you could get away with NUMBER OF DIRECTIONS less than 180.
To troubleshoot, I would advise you to try:
NUMBER OF DIRECTIONS = 36
TIME STEP = 5
NUMBER OF TIME STEP = 8640 to keep the same duration.
PERIOD FOR GRAPHIC PRINTOUTS = 180 to keep the same output size.
You 'll save some time from the fewer directions and spend it on the timesteps.
Costas
The administrator has disabled public write access.
The following user(s) said Thank You: TimN

Tomawac - Artemis chaining 4 years 3 weeks ago #37041

  • TimN
  • TimN's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 67
Hi Costas,
No, I haven't checked the results yet. I'm not familiar with the subroutines. But I tried to do the checks as you recommended. Unfortunately the python scripts both weren't found by the terminal. I then copied them from the pretel folder to the level above 'python3' folder. It didn't run, the terminal gave me the signal 'permission denied'. I'm not sure why, I checked the rights and these were the same as for the other .py scripts.

I now run the simulation with your recommendations and do the setup procedure for artemis again. Maybe the changes you recommended do the trick.

Cheers, Tim
The administrator has disabled public write access.

Tomawac - Artemis chaining 4 years 3 weeks ago #37042

  • cyamin
  • cyamin's Avatar
  • OFFLINE
  • openTELEMAC Guru
  • Posts: 997
  • Thank you received: 234
Hi Tim, my bad, I am used to importing the modules on my own scripts. If you want to run them from cmd prompt, this is the command:
run_telfile.py scan path\myfile.slf or .spe or .lqd
You can type
run_telfile.py scan -h
for help.
You can also check 2D SLF files using BlueKenue. But BK cannot handle LQD or SPE files.
Have a look at the jupyter notebooks in 'notebooks' subfolder. They are VERY helpful for understanding the python script library.
Costas
The administrator has disabled public write access.

Tomawac - Artemis chaining 4 years 3 weeks ago #37047

  • TimN
  • TimN's Avatar
  • OFFLINE
  • Senior Boarder
  • Posts: 67
Costas,
sorry for bothering you, but now I'm really lost. I can't find the run_telfile.py script. And also in the notebook subfolder jupyter doesn't exist. I'm on v8p1r0, don't know if thats the reason.

I'm trying now to import the modules to my python3. Maybe that way works:)
Cheers,
Tim
The administrator has disabled public write access.

The open TELEMAC-MASCARET template for Joomla!2.5, the HTML 4 version.