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

Added flexibility to user to frequency of output writing #69

Merged
merged 3 commits into from
Sep 25, 2019

Conversation

stevetorr
Copy link
Contributor

I have been iterating with train_gp_from_AIMD and have found that the Output module only flushing its buffer periodically and therefore intermittently writing to the output files, while computationally more efficient in general, is undesirable for watching it run in real-time. I propose adding a few arguments to the Output class which make it write instantly to the output if the user wishes to follow output in real time and otherwise does not change the functionality of the module.

@codecov-io
Copy link

codecov-io commented Sep 24, 2019

Codecov Report

Merging #69 into master will increase coverage by 0.48%.
The diff coverage is 78.94%.

Impacted file tree graph

@@            Coverage Diff             @@
##           master      #69      +/-   ##
==========================================
+ Coverage   46.95%   47.44%   +0.48%     
==========================================
  Files          37       37              
  Lines        5641     5704      +63     
==========================================
+ Hits         2649     2706      +57     
- Misses       2992     2998       +6
Impacted Files Coverage Δ
flare/gp_from_aimd.py 90.74% <100%> (+2.24%) ⬆️
flare/output.py 92.57% <76.47%> (-1.84%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3b3345a...40e959a. Read the comment docs.

Copy link
Collaborator

@nw13slx nw13slx left a comment

Choose a reason for hiding this comment

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

Nice. I have thought about using the "buf" argument when opening the file. But that is not as flexible as flushing the output on request.

@nw13slx nw13slx merged commit 0d2e1e5 into master Sep 25, 2019
@jonpvandermause
Copy link
Collaborator

jonpvandermause commented Sep 25, 2019

Could we do the same for otf.py? @stevetorr @nw13slx

@stevetorr stevetorr deleted the output_buffer_flush_flexibility branch September 26, 2019 15:23
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.

4 participants