Forum

RE: Quickplot: View *.amu file

Julius Schlumberger, modified 4 Years ago.

Quickplot: View *.amu file

Youngling Posts: 15 Join Date: 12/20/20 Recent Posts
Dear all,
I have created an *.amu and *.amv file from a script which interpolated wind data from some stations to my model domain. I am uncertain about the convention on how D-Flow will interprete the the velocity values in the files: first value --> bottom left corner or top left corner? I am uncertain, because  the lower left corner id defined as the origin of the grid.
In order to visualize the interpretation, I wanted to use Quickplot. I tried ARC/INFO Asicii Grid Files, ArcInfo Ungenerate Files and Delft3D/SOBEK Meteo files as file formats. However, for all I got (different) error messages with the attached file. For example for the Delft3D/SOBEK Meteo files:
  • Error while opening
  • D:\MasterThesis\Grid_Develop\00_Original_Data\wind-pressure_venlag\Nov12Stormperiod_07_to_17_Nov\windxdir.amu
  • as Delft3D/SOBEK Meteo Files:
  • Index exceeds matrix dimensions.
  • In asciiwind>value2time at line 633
  • In asciiwind>Local_open_file at line 332
  • In asciiwind at line 68
  • In private\qp_fmem at line 591
  • In private\qp_proxy at line 42
  • In d3d_qp>d3d_qp_core at line 335
  • In d3d_qp at line 43
Is there somebody that either could suggest which file type should be specificed in Quickplot in order to view *.amu files or indicate how the velocity values are interpreted by the D-Flow?
Thank you in advance,
Julius

EDIT: I am using Quickplot version 2.60.67807 (64bit) which is delivered along with Delft3D-Suite 2021.02.
Dmitry Kushnir, modified 4 Years ago.

RE: Quickplot: View *.amu file

Padawan Posts: 25 Join Date: 11/9/12 Recent Posts
Hi Julius,
There was a problem with the header of your meteo-file.
I've modified it a bit (attached), and it can be opened with the Quickplot now.
Regards,
Dmitry 
Julius Schlumberger, modified 4 Years ago.

RE: Quickplot: View *.amu file

Youngling Posts: 15 Join Date: 12/20/20 Recent Posts
Hi Dmitry,
thank you very much for this swift support! Thanks for spotting that error. Now, it works.
Best Regards,
Julius