Closed debryant closed 4 years ago
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
The following VIs could not be diffed:
@debryant , in the situation where you configure a new log file based on a time span, the time then elapses to create a new file but no data was ever written to previous log file. Do you expect that a new file will be created regardless, potentially creating a set of empty files?
Whatever the decision, to be ok with empty files, or only generate new files when the previous file is >0kb, please add a test that validates that behavior.
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
The following VIs could not be diffed:
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
The following VIs could not be diffed:
Done. Thanks for catching these :)
Bleep bloop!
LabVIEW Diff Robot here with some diffs served up hot for your pull request.
Notice something funny? Help fix me on my GitHub repo.
The following VIs could not be diffed:
What does this Pull Request accomplish?
Add file spanning support to the embedded data logger custom device such that a tdms file can optionally be closed and a new one opened after a defined time has passed or the tdms file reaches a defined size.
Why should this Pull Request be merged?
Some tests may execute over an extended period of time, which can issue in a very large tdms file when only a single file is generated to contain all of the logged data. Very large files can be unmanageable, taking longer times to load into a viewer or search for particular data sets. Allowing files to be broken into manageable chunks can increase usability and access of the tdms data.
Fixes #2
What testing has been done?
Created new unit tests for the feature and ran the full set of existing tests.