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

Improve tensorboard monitoring #514

Merged
merged 9 commits into from
Feb 23, 2022

Conversation

uri-granta
Copy link
Collaborator

@uri-granta uri-granta commented Feb 22, 2022

Some initial improvements, based on suggestions at #401:

  1. Group related plots together (wallclock, observations, etc)
  2. Plot query points, either as one scalar plot per dimension (if batch=1) or one histogram per dimension (if batch>1)
  3. Rename best_new to best_in_batch
  4. Rename .i to [i] when plotting specific elements
  5. Add wallclock plotting (plus the changes above) to ask_tell

summary_writer = get_tensorboard_writer()
if summary_writer:
with summary_writer.as_default(step=get_step_number()):
if tf.rank(query_points) == 2:
Copy link
Collaborator

Choose a reason for hiding this comment

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

why wouldnt this be true?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Because the type system doesn't tell me so :-)

Seriously: does it have to be true (i.e. do we assume/assert it anywhere) or is just always true in practice?

Copy link
Collaborator

@henrymoss henrymoss left a comment

Choose a reason for hiding this comment

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

LGTM

@uri-granta uri-granta marked this pull request as ready for review February 22, 2022 16:14
f"{tag}.observation.best_overall",
np.min(datasets[tag].observations),
step=step,
tf.summary.histogram(
Copy link
Collaborator

Choose a reason for hiding this comment

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

histogram makes sense only for batches, no?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I mean it still works for batch size one (though it doesn't provide any more information that the best_in_batch scalar plot).

Copy link
Collaborator

@hstojic hstojic left a comment

Choose a reason for hiding this comment

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

looks ok to me

what I found needed was recording some info about the run, like size of the data at the beginning (i.e. num initial points), budget aka number of steps, and information about the model and acq rule - this can all be filed as text, can serve as a useful metadata when comparing several runs

@uri-granta
Copy link
Collaborator Author

what I found needed was recording some info about the run, like size of the data at the beginning (i.e. num initial points), budget aka number of steps, and information about the model and acq rule - this can all be filed as text, can serve as a useful metadata when comparing several runs

good suggestion, though i'd rather add text summaries in a separate pr

@uri-granta uri-granta merged commit 4e5769f into develop Feb 23, 2022
@uri-granta uri-granta deleted the uri/improve_tensorboard_monitoring branch February 23, 2022 11:42
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.

3 participants