-
Notifications
You must be signed in to change notification settings - Fork 53
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
Problem with Dashboard #93
Comments
Hi @lordfiftyfive , Thanks for the feedback! Mind if I ask which link you mean by the previous link? The error you mentioned would definitely result in nothing being written to the dashboard. Can you share code for your study.add_observation ? It seems like objective in add_observation is getting a dtype that it argmin cannot be applied to. Best, |
I think I actually saw a link which explained how to run sherpa on google colab on a runtime which was not tensorflow 2.0 so after doing some digging I figured out that this was the correct way to pull up the sherpa dashboard with the latest tensorflow version. from tensorboard import notebook This is the code for my study. batch_size =19 ' lr = trial.parameters['lrinit']
]) optimizer = tf.keras.optimizers.Adam(learning_rate=lr)#
study.finalize(trial=trial) ' |
Hmmm....does Regarding the dashboard link. I hadn't used
before. Thanks for sharing. I normally just put |
Thanks! That did the trick. |
I am running sherpa with tensorflow 2.1 on google colab. The first problem I ran into was that the previous link explaining how to run sherpa with tensorflow 2.1 in google didn't work fortunately I was able to resolve this and pull up the dashboard using
from tensorboard import notebook
notebook.display(port=8880, height=1000)
Unfortunately it is not printing anything to the dashboard. I believe that it may be related to this error which I am receiving in my final line of code after it finishes running all the trials
---> 34 study.finalize(trial=trial)
TypeError: reduction operation 'argmin' not allowed for this dtype
The text was updated successfully, but these errors were encountered: