Jump to content

error in the importing .txt wind data


Recommended Posts

Posted

Dear WAsP team,

There is an error happened in the process of importing wind data,

Exception report produced at 2023-07-01 10:34:37

根级别上的数据无效。 第 1 行,位置 1。 raised at: 2023-07-01 10:31:03
    2023-07-01 10:31:03: Exception raised in: 在 System:Xml:XmlTextReaderImpl:Throw
    2023-07-01 10:31:03: Message added: Could not restore from file
    2023-07-01 10:31:03: Exception raised in: 在 Rvea0331:cObservedWindClimate:RestoreFromFile
    2023-07-01 10:31:03: Message added: Could not restore an OWC from file
    2023-07-01 10:31:03: Exception raised in: 在 Rvea0331:ObservedWindClimateClass:RestoreInstanceFromFile
    2023-07-01 10:31:03: Message added: Could not restore preservable object from file
    2023-07-01 10:31:03: Exception raised in: 在 Rvea0331:ObservedWindClimateClass:IRveaPreservableClass_RestoreInstanceFromFile
    2023-07-01 10:31:03: Message added: Could not open the OWC data file
    2023-07-01 10:31:03: Exception raised in: Rvea0334:cObservedWindClimate:OpenDataFile
    2023-07-01 10:31:03: Message added: Could not insert a Observed wind climate from file 'Daily_20200101_20201231_10m' to the hierarchy
    2023-07-01 10:31:03: Exception raised in: Rvea0334:cHierarchyInsertionFromFile:InsertFromFile
    2023-07-01 10:31:03: Message added: There was a problem with the insertion
    2023-07-01 10:31:03: Exception raised in: WAsP:cWorkspaceController:ExecuteHierarchyInsertion
    2023-07-01 10:31:04: Message added: Could not insert a wind atlas
    2023-07-01 10:31:04: Exception raised in: WAsP: cWorkspaceController:PerformNewWindAtlasInsertion
    2023-07-01 10:31:04: Message added: The insertion was not successfully completed
    2023-07-01 10:31:04: Exception raised in: WAsP:cMemberPopupMenuMediator:ProcessInsertionFromMenu
    Latest thread started in: Wiab0007:TextSmart:TextBox_Change

 

The .txt file I imported is like this,

Date                   WS[m/s]    WD[º]
2020-01-01    7.38             65.31
2020-01-02    7.53            64.5
2020-01-03    6.92           60.56
2020-01-04    6.38           59.12
2020-01-05    7.83            63.56
2020-01-06    7.43            62.25

 

May I ask if it's the format leading to this error? or what format I should follow?

Many thanks.

Posted

This is just a guess without having the file, but you will need more measurements more than once a day to make a histogram wind climate for WAsP (typically every 10 or 30 min). The WAsP method may not work when you use measurements (model output?) that are available only once per day. So I would not recommend it, but you could probably solve the error by adding a time stamp in your date column.

  • 8 months later...
Posted (edited)

Dear Wasp team,

I am posting here since this seems to be the most recent post about this kind of error.

During data import on Climate Analyst 3.1 I get the following message: "It seems we were unable to the file structure for provided file". There's an error stated as: "Unable import file to WAsP Climate Analyst. No protocol could be generated for a file".

I am, however, pretty sure I have alredy successfully used the same .txt file before, on the same software, with the same version but with another computer (presently I am using a dell i7 13th generation running Windows Pro 11). The file is just as following:

date,wind speed,wind direction
2022-09-01 00:00:03,2.7,36.6
2022-09-01 00:10:03,2.3,28.8
2022-09-01 00:20:02,1.8,25.1
2022-09-01 00:30:03,1.3,26.3
2022-09-01 00:40:03,1.0,24.0
2022-09-01 00:50:03,1.1,20.7
2022-09-01 01:00:03,1.0,8.8
2022-09-01 01:10:03,1.2,356.4
2022-09-01 01:20:03,1.5,12.4
2022-09-01 01:30:03,1.4,10.3
2022-09-01 01:40:03,1.3,18.4
2022-09-01 01:50:03,1.4,345.9
2022-09-01 02:00:03,1.1,350.9
2022-09-01 02:10:03,1.4,5.3
2022-09-01 02:20:02,1.6,4.4
2022-09-01 02:30:03,1.5,0.5
2022-09-01 02:40:03,1.8,359.1
2022-09-01 02:50:03,1.8,351.9
2022-09-01 03:00:03,2.0,352.2
2022-09-01 03:10:03,1.7,356.9
2022-09-01 03:20:03,1.6,5.6
2022-09-01 03:30:03,1.5,356.3
2022-09-01 03:40:03,1.5,16.2
2022-09-01 03:50:03,1.2,24.1
2022-09-01 04:00:02,1.6,16.3
2022-09-01 04:10:03,1.5,19.1
2022-09-01 04:20:03,1.4,15.1
2022-09-01 04:30:03,1.5,5.5

 

Is it possible to know if it's something related to the format? Maybe some installation issue? Any clarification would be of great help.

Thanks a lot!

Edited by Turan
Posted (edited)
27 minutes ago, Turan said:

Dear Wasp team,

I am posting here since this seems to be the most recent post about this kind of error.

During data import on Climate Analyst 3.1 I get the following message: "It seems we were unable to the file structure for provided file". There's an error stated as: "Unable import file to WAsP Climate Analyst. No protocol could be generated for a file".

I am, however, pretty sure I have alredy successfully used the same .txt file before, on the same software, with the same version but with another computer (presently I am using a dell i7 13th generation running Windows Pro 11). The file is just as following:

date,wind speed,wind direction
2022-09-01 00:00:03,2.7,36.6
2022-09-01 00:10:03,2.3,28.8
2022-09-01 00:20:02,1.8,25.1
2022-09-01 00:30:03,1.3,26.3
2022-09-01 00:40:03,1.0,24.0
2022-09-01 00:50:03,1.1,20.7
2022-09-01 01:00:03,1.0,8.8
2022-09-01 01:10:03,1.2,356.4
2022-09-01 01:20:03,1.5,12.4
2022-09-01 01:30:03,1.4,10.3
2022-09-01 01:40:03,1.3,18.4
2022-09-01 01:50:03,1.4,345.9
2022-09-01 02:00:03,1.1,350.9
2022-09-01 02:10:03,1.4,5.3
2022-09-01 02:20:02,1.6,4.4
2022-09-01 02:30:03,1.5,0.5
2022-09-01 02:40:03,1.8,359.1
2022-09-01 02:50:03,1.8,351.9
2022-09-01 03:00:03,2.0,352.2
2022-09-01 03:10:03,1.7,356.9
2022-09-01 03:20:03,1.6,5.6
2022-09-01 03:30:03,1.5,356.3
2022-09-01 03:40:03,1.5,16.2
2022-09-01 03:50:03,1.2,24.1
2022-09-01 04:00:02,1.6,16.3
2022-09-01 04:10:03,1.5,19.1
2022-09-01 04:20:03,1.4,15.1
2022-09-01 04:30:03,1.5,5.5


Is it possible to know if it's something related to the format? Maybe some installation issue? Any clarification would be of great help.

Thanks a lot!

Just downloaded the latest Climate Analyst version with the WAsPSuite-2024-A- and everything works perfectly now.   I would delete the post but it could be great for people to know that checking for the latest version could help about it.

Edited by Turan

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...