-
Notifications
You must be signed in to change notification settings - Fork 351
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
Add HistogramPlot and minor fix to Plot #569
Conversation
If you want the server to accept connections from any address use | ||
<ip>= 0.0.0.0. | ||
|
||
Parameter |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Parameters*
Wow, @dwf I never received a review so fast! I am working on it. |
@@ -4,14 +4,12 @@ | |||
from subprocess import Popen, PIPE | |||
|
|||
try: | |||
from bokeh.plotting import (curdoc, cursession, figure, output_server, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
were curdoc and cursession never used, I guess?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
curdoc
was used by __setstate__
, while cursession()
is now unused because I use self.session
. This prevents problems when you have multiple extensions plotting (i.e. multiple sessions open)
Travis error doesn't seem related to my PR and I should have addressed all your requests. |
I restarted Travis but these did in fact look related... the demos run with
the plotting extension, and there was an error regarding Bokeh schema.
|
@@ -63,9 +61,7 @@ class Plot(SimpleExtension): | |||
server_url : str, optional | |||
Url of the bokeh-server. Ex: when starting the bokeh-server with | |||
``bokeh-server --ip 0.0.0.0`` at ``alice``, server_url should be | |||
``http://alice:5006``. When not specified the default configured | |||
by ``bokeh_server`` in ``.blocksrc`` will be used. Defaults to | |||
``http://localhost:5006/``. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why did you remove this configuration setting?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Indeed, this documentation looks useful.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apparently I failed to merge 9c8ad24 for some reason. It's not intentional.
I pushed another minor commit. The changes are mostly aesthetic, but they improve the plot quite a bit in my opinion. If you don't have any other comment, I don't plan to modify it further. |
- Add HistogramPlot to plot histograms of the mean of each component of a channel - Call push only once at the beginning in Plot, afterwards it is sufficient to modify the data source for the plot to update
- Visualize the right value on x axis in Plot - Show the axes's labels - Iterate only on the provided keys
Travis build passed, is it ready for merge or I am not noticing something? |
Hey, is there a reason why this PR has not been merged yet? If there is something missing can you please point that out? |
Personally I'd like to wait till we have |
Don't worry! I know you are busy, I just wanted to make sure it wasn't due to something I was missing. For what concerns the merge, I would like to see it merged so that I can use it without copying and pasting the code from/to different branches, but it's just a bit annoying, I wouldn't define it a big pain. Nonetheless, I fear that the creation of |
I'll try to do my best to get it up and running soon! So let's hope it won't end up being continuously delayed. The annoying thing about merging it is that it then becomes a copy-paste job later to move things later, breaking people's code, etc. There's no need to copy-paste by the way. Whenever you want to use this, you can just branch |
@fvisin , seems like you also have batch normalization PR in this one. Also I am afraid that your extension is not training resumption friendly, see Regarding the merge, I think I support @bartvm in his reluctance. For every bit of code merged in Blocks we become responsible, we have to review further PRs and bug fixes. We would much rather concentrate on the core functionality than doing that. Cross-post! |
In fact I think that creation of a non-tested repo that would simply contain bits and pieces of Blocks-compatible code is a matter of 10 minutes, and I can gladly do that. All the rest, like @bartvm, do you have anything against going this way? |
It all depends on what you want to do. If it's just a collection of code snippets, I don't think it should even go in a repo, in that case we can just add a collection of links to the wiki of this repo. If we want to set up Travis CI, Scrutinizer, write documentation, move code from here to there, etc. it becomes more than 10 minutes. Either way, the main thing holding it back is the fact that we're supposed to create the repos as part of the new GitHub organisation, but I don't have admin rights there, so I've been unable to do anything :p I'll poke Fred/Pascal about that! |
Collections of links does not do the job because one can not check out them all and import from this the checkout directory. The whole transition is a of course a lot of work, especially moving things out from Blocks, but now I am more worried about making it possible for people to share their useful code in a convenient way. |
@bartvm thank you for the merge trick. I didn't think about it, very useful! @rizar You are right, I was using batch normalization for a test and forgot to delete the commit. I did it now. For what concerns training resumption, Bart and I agreed on removing that part:
For what concerns the PR, it can wait until the extras repo will be available. |
@fvisin , for your information, blocks-extras is already there! |
a channel