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

Document I/O interfaces #648

Merged
merged 4 commits into from
Jul 25, 2024
Merged

Conversation

tmadlener
Copy link
Collaborator

@tmadlener tmadlener commented Jul 24, 2024

BEGINRELEASENOTES

  • Add docstrings to the Reader and Writer interface classes
  • Make sure that makeReader throws an exception if multiple SIO files are passed (see #647)

ENDRELEASENOTES

Copy link
Collaborator

@hegner hegner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks a lot!
Just a few minor remarks. Except for the exception handling they could be covered in the same PR

/// data from the passed files
///
/// @throws std::runtime_error in case the file extensions differ or in case
/// support for the necessary I/O backend has not been built
Reader makeReader(const std::vector<std::string>& filename);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually it should be filenames, not filename

/// reading. All files are assumed to be of the same I/O format, no switching
/// between formats is possible.
///
/// @note For SIO files this will only read the first file!
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should put in some exception handling or something of that kind. That is too burried in the docs.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean, throw an exception when more than one SIO file is passed?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should not silently ignore faulty states.

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

so yes

/// backend specific readers that this class wraps. In contrast to the lower
/// level readers that usually return arbitrary FrameData, this interface class
/// will return fully constructed Frames.
///
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In addition it provides convenience methods to deal specifically with the event frame category...

@tmadlener
Copy link
Collaborator Author

Thanks for checking. I think I addressed all of them.

Copy link
Collaborator

@hegner hegner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That was quick! thanks

@hegner hegner merged commit 977ca93 into AIDASoft:master Jul 25, 2024
18 checks passed
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

Successfully merging this pull request may close these issues.

2 participants