• Re: GPUs not recognized since updating to Mike 2020 Update 1

    Also note that some older cards may not be supported anymore (I haven't looked up yours): https://faq.dhigroup.com/default.asp?module=Installation+/+Hardware&ID=418
  • Re: Plot Composer 2017 issues.

    So I dug a little deeper...

    The problem arises when manually setting the X-axis "from" and "to" properties (right click, properties, x-axis).

    For some reason, the issue is when setting the date to 00:00:00 on the 1st day of any Year-Month (YYYY/MM/01 00:00:00). The date is saved in the .plc as 24:00:00 on the last day of the previous month - which the Plot Composer fails to read correctly. The fix is currently to add 1 second to the DateTime (or not to use the Day 1 @ 00:00:00).
  • Re: Plot Composer 2017 issues.

    [quote author=Ann link=topic=20561.msg26847#msg26847 date=1510579788]
    A hotfix to resolve this issue is now available from the hotfix download page (MIKE ZERO hotfix 18-10-2017)
    [/quote]

    Thanks. The Service Pack 1 update did manage to fix the ASCII problem.

    ...but now Time Series plots (dfs0) keep losing the Start-time axis (have to manually setup the x/time-axis everytime I open the plc).
  • Re: Plot Composer 2017 issues.

    Update: Seems like the "name" parameter is populated with non-"UTF-8" encoded characters. Might be ISO 8859-1 but I don't have any luck with the conversion.
  • Re: e-Mail Notification MIKE21FM

    It seems like the best solution at the moment is to add a simple program like "Blat" to your batch script. Blat can be setup with most mailbox types, though I haven't tested it myself.

    Something like

    start /wait C:\"Program Files (x86)"\DHI\2017\bin\x64\MzLaunch.exe model_A.mfm -x
    start C:\"Program Files (x86)"\Blat\blat.exe message.txt -to receive@gmail.com -attach model_A.mfm.log

    start /wait C:\"Program Files (x86)"\DHI\2017\bin\x64\MzLaunch.exe model_B.mfm -x
    start C:\"Program Files (x86)"\Blat\blat.exe message.txt -to receive@gmail.com -attach model_B.mfm.log

    start /wait C:\"Program Files (x86)"\DHI\2017\bin\x64\MzLaunch.exe model_C.mfm -x
    start C:\"Program Files (x86)"\Blat\blat.exe message.txt -to receive@gmail.com -attach model_C.mfm.log

    etc...

  • Re: e-Mail Notification MIKE21FM

    Hi C,

    Had no luck myself. Would be interested to know if someone has a solution to this.

    S
  • Re: Plot Composer Plot Area

    You have to use the zoom in function (right click > zoom in), then select and drag the area you want to view.

    The process is always as follows for FM / dfsu / meshes:
    * resize plot to the wanted dimensions or aspect ratio
    * zoom in to area to "fill" in the extents.

    Plot composer does not feel as intuitive at first, but you'll get the hang of it after awhile.

    Cheers
  • Request: Mike 2017 Manuals (incl. M21-MA / -FRC)

    In previous versions (2016 and before) DHI provided scientific documents and step-by-step guides to use their software.

    I'm not managing to find any manuals for the 2017 version.

    I am specifically looking for documentation on the new mooring analysis and frequencey response calculator modules. Any ideas where I could find these pdf's?

    Thanks
  • Re: "Import data from background" problem

    Hi Rupak

    It appears that the Background data have [i]already[/i] been imported.

    When the data is still in the background (not imported) the Water points will be green and the land-boundary will be red.
    [img width=200 height=104]http://i.imgur.com/iZAHebg.png[/img]

    When you click on the "Import from Background" button and select the data, they will highlight as red.
    [img width=200 height=103]http://i.imgur.com/iO6m0Sx.png[/img]

    Clicking again on the "Import from Background button finally imports the data. The imported data will now appear as blue dots (water) and a dark green boundary (land-boundary).
    [img width=200 height=103]http://i.imgur.com/K5eFu7c.png[/img]

    So it appears that your data is already imported.

    Regards,
    Stephan
  • Re: Mike 21BW - Large Breaking Waves causing High-Frequency Noise

    Update 2: The issue is probably fundamental: The wave series of: 3.2m / 12 sec  isn't a realistic case. The wave-period should be in the order of 15-18sec