Converting error from WDM to HDF5 file format with own dataset.

[scalet98]

Hello !
Currently, I am trying to apply your code with my dataset. So for now, I am trying to converting wdm file to HDF5 format.

After I applying my own dataset (as a test I used BASINS4 sample sediment dataset which is mostly larger dataset(56timeseries) than your test01 code(19timeseries)) with your ReadWDM module, I have got an error as below picture shows.

Point-1

• Do you have any specific rules, when we are developing wdm file format to apply your HDF5 converter?

Point-2

• Now I am reviewing your ReadWDM file code.
• But until now I could not find any troubled line.
• Eventhough some lines are questionable due to the some number you are using to develop the codes. But for now, I do not have detailed WDM DB specification for variables.
• For reference, could you share the original WDM database table or column specifications for variables? Then It would be easier task I think.

If you know why it is coming up. Please let me know.
Thank you for developing this package and reading this question.

Jiheon Lee.

[PaulDudaRESPEC]

I think the issue is related to the WDM attributes available on those data sets. It seems to me the ReadWDM code looks for this list of attributes: search = ['STAID', 'STNAM', 'SCENARIO', 'CONSTITUENT','LOCATION'] If it finds any of them, it expects the same set to exist for all the data sets.

A quick work-around might be to add the missing attributes so that the same set exists for each timeseries in the WDM file.

[scalet98]

PaulDuda ! Thank you !

Unexpectedly, solution is too simple. I did not expect that the sample file has the corrupted parts. I was just obsessed with the code. After adding the missing parts in the sample code, all things works very well :)

I was too serious about the issue I think. I checked out every single line in the code.

Always, Simple is the best way !~ Thank you again !

Jiheon Lee :)

I think the issue is related to the WDM attributes available on those data sets. It seems to me the ReadWDM code looks for this list of attributes: search = ['STAID', 'STNAM', 'SCENARIO', 'CONSTITUENT','LOCATION'] If it finds any of them, it expects the same set to exist for all the data sets.

A quick work-around might be to add the missing attributes so that the same set exists for each timeseries in the WDM file.

[PaulDudaRESPEC]

Glad I could help!
I believe it is an issue to be fixed, in that it should not be a requirement that there be the same set of attributes on each WDM timeseries data set.

[scalet98]

Hello !~ PaulDuda !

Yes I think It needs to be upgraded for more general case application. But if it is not, more users will study about your code probably. :)

I have one more question. In the ReadWDM file, you are using the number 512 in the code line 37. ( I have attached the related pic with red line marker below)

• It seems like that you are using 512, when you are identifying the times series starting index. For instance, first times series starts from index no. = 512, and second one starts from 512*n and so on. But here is the question. * Where does the number 512 come from?**

• It seems like that the no. comes from the WDM DB/ Table specification which defines the specifications including ID, DSN, and etc. for WDM DB variables. If that is the case Could you send me one of this or could you let me know the source of it?

• Sorry for bothering you again. Even though, I have resolved the issue this time, I would like to understand what the code lines say exactly for further application.

I appreciate your help. Thank you for reading the comments again !~

Best regards, Jiheon Lee

Glad I could help! I believe it is an issue to be fixed, in that it should not be a requirement that there be the same set of attributes on each WDM timeseries data set.

[PaulDudaRESPEC]

I believe the 512 is the record length in the WDM file, but I'm at the limit of my knowledge in that territory. Someone else on the team may have to answer the follow-on questions.

[scalet98]

Hello ! PaulDuda !

Thank you for your kind reply. It was not my territory either, but I just wanted to understand the code thoroughly.

I think I need to upload the question again or contact the code designer directly. Thank you ! Have a good one !~:)

Jiheon Lee.

I believe the 512 is the record length in the WDM file, but I'm at the limit of my knowledge in that territory. Someone else on the team may have to answer the follow-on questions.