Error while initializing space-varying wind (solved) https://dlt-acc.firelay.cloud/en/c/message_boards/find_thread?p_l_id=4041874&threadId=4391792 2026-05-12T15:58:43Z 2026-05-12T15:58:43Z Hemerson Tonin https://dlt-acc.firelay.cloud/en/c/message_boards/find_message?p_l_id=4041874&messageId=4391858 2021-06-17T07:23:56Z 2021-06-17T07:23:56Z

I have the same problem (version: 1.2.110.68456M)

Hemerson Tonin 2021-06-17T07:23:56Z Sunghoon Han https://dlt-acc.firelay.cloud/en/c/message_boards/find_message?p_l_id=4041874&messageId=4391791 2021-10-04T05:51:05Z 2021-05-10T02:21:02Z

Hello,<br />The diagnosis file shows the error below when I use the time- and space-varying wind on an equidistant grid format,<br />even with the same computational grid that worked well with different external forcing input such as spider-web.<br /> ----------------------------------------------------------------------------------------------------------------------------------<br />** WARNING: ERROR: Looking for ncols (arc-info), but getting: FileVersion = 1.03<br />** ERROR  : flow_initexternalforcings: Error while initializing quantity: windx Check preceding log lines for details.<br />----------------------------------------------------------------------------------------------------------------------------------<br />(but log file shows nothing)<br /><br />Have you experienced such errors?<br />I would appreciate it if you can share any ideas or check if the attached files have anything wrong.<br /><br />=================================================================================================<br />I&#39;ve found how to deal with this.<br />This can be solved by inserting three comments lines before the input information of each file (.amu, .amv, and .amp),<br />because it is sensitive to the number of lines of the header to be initialized.<br />For example: <br /><em>### Start of Header<br />### This file is created by ...<br />### Additional comments<br />FileVersion = 1.03<br />...<br />unit1 = m s-1<br />### End of Header<br />TIME = 0 minutes since 0000-00-00 00:00:00 +00:00<br />...</em>

Sunghoon Han 2021-05-10T02:21:02Z