Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HDF5 plugin: failed to create dataset #398

Closed
ulrikpedersen opened this issue Apr 9, 2019 · 6 comments
Closed

HDF5 plugin: failed to create dataset #398

ulrikpedersen opened this issue Apr 9, 2019 · 6 comments
Assignees

Comments

@ulrikpedersen
Copy link
Member

As reported by @hinxx in #397 (comment):

Messages Failed to create dataset: timestamp. Continuing to next. when using default built-in XML layout should not happen.

@MarkRivers
Copy link
Member

I did a number of tests with the default built-in XML layout yesterday and did not see those messages. Under what circumstances did they occur?

@hinxx
Copy link
Contributor

hinxx commented Apr 9, 2019

Under what circumstances did they occur?

I've seen them if I just replaced the asynPrint(this->pasynUserSelf, ASYN_TRACE_WARNING, in the next line with printf(.

@MarkRivers
Copy link
Member

I just enabled ASYN_TRACE_WARNING in the HDF5 plugin. Indeed I see this message once for each file created:

2019/04/09 13:56:16.512 NDFileHDF5::createTree Failed to create dataset: timestamp. Continuing to next.

@ulrikpedersen I see comments in NDFileHDF5.cpp from you about creating this dataset, which is in the performance group? Can you take a look to see what we are getting this error?

@ulrikpedersen
Copy link
Member Author

Sorry about the delay. @ajgdls will take a look at this one.

@ajgdls
Copy link
Contributor

ajgdls commented May 14, 2019

The warning here is being printed due to the fact that the performance/timestamp dataset is a bit hardcoded into the system. It shows up in the structure but specifically does not get created at this point in the code. There is a comment that states only detector and constant datasets are created, which is why the warning is raised.
The timestamp dataset is then created further on and still gets saved into the file as expected. I think the solution is to check specifically for the performance/timestamp dataset and do not attempt to create it at this point, which will stop the warning from being generated. I'll raise a PR for people to comment on.

@MarkRivers
Copy link
Member

Closed via #408

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants