Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #3213
    rikvaerenberg
    Participant

    Dear Organizers,

    It appears that some HDF5 files of experiment F are missing critical operating condition data (i.e., ‘PAU Speed’, ‘PAU Torque’, and ‘Temperature’). Based on our investigation, these parameters are typically stored under the /Context group. However, while “Normal” files contain this group, “Abnormal” files do not. This happens on both high-frequency and low-frequency HDF5 files. One example of such file would be Dyno Gear309Run5_00001.hdf5. Would it still be possible to obtain these operating conditions and temperature data from somewhere in the file?

    Furthermore, we have noticed some inconsistencies regarding the files located within the ‘Run 2’, ‘Run 4’ folder. Specifically, there are files named with much higher run indices than expected. Are these duplicate files that can be deleted? Or did something go wrong with the naming convention?

    #3215
    huanhuang
    Keymaster

    We will review the data from Experiment F and get back to you.

    Regarding the file names, the runs are organized by folders. The appearance of multiple runs based on file names within a folder is an artifact of the LabVIEW implementation. You may choose to remove duplicated files during your model training. To identify duplicate files, you will need to compare the data rather than rely on file names.

    #3218
    huanhuang
    Keymaster

    Regarding the missing data in Experiment F, unfortunately, there is no way to obtain data that was not recorded in the files.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.