[Yade-dev] [Bug 1813782] Re: Repeated plot.plot() fail
** Changed in: yade
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1813782
Title:
Repeated plot.plot() fail
Status in Yade:
New
Bug description:
Hi there,
Since bugs report get a lot of attention these days :-) let me add
another one:
###
from yade import plot
plot.addData(x = 1 , y = 5)
plot.plots = {'x':'y'}
plot.plot()
plot.plot()
###
gives error messages (pointing to py/plot.py, see [*] below) at the
second plot.plot() command.
It seems you can also replace any of the 2 plot.plot() (or both) with
eg plot.plot(noShow=True).savefig('test.png') and get the same
behavior.
I would prefer having the possibility to ask twice for a plot in one
YADE session, what do you think ?
[*] Error message with yadedaily 2018.02b-290bf6a54e~bionic or yade
2018.02b:
AttributeErrorTraceback (most recent call last)
/usr/bin/yadedaily in ()
> 1 plot.plot()
/usr/lib/x86_64-linux-gnu/yadedaily/py/yade/plot.py in plot(noShow, subPlots)
592 .. note:: For backwards compatibility reasons, *noShow*
option will return list of figures for multiple figures but a single figure
(rather than list with 1 element) if there is only 1 figure.
593 """
--> 594 createPlots(subPlots=subPlots)
595 global currLineRefs
596 figs=set([l.line.axes.get_figure() for l in currLineRefs])
/usr/lib/x86_64-linux-gnu/yadedaily/py/yade/plot.py in createPlots(subPlots,
scatterSize, wider)
370 def createPlots(subPlots=True,scatterSize=60,wider=False):
371 global currLineRefs
--> 372 figs=set([l.line.get_axes().get_figure() for l in
currLineRefs]) # get all current figures
373 for f in figs: pylab.close(f) # close those
374 currLineRefs=[] # remove older plots (breaks live updates of
windows that are still open)
AttributeError: 'Line2D' object has no attribute 'get_axes'
##
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/1813782/+subscriptions
___
Mailing list: https://launchpad.net/~yade-dev
Post to : yade-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yade-dev
More help : https://help.launchpad.net/ListHelp
[Yade-dev] [Bug 1813229] Re: Class Inheritance graphs in Yade.pdf are unreadable
It is fixed now: https://gitlab.com/yade- dev/trunk/commit/0d2d11a2eaaa2bcc2e253744914f80cdfaf7fee6 ** Changed in: yade Status: New => Fix Committed -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1813229 Title: Class Inheritance graphs in Yade.pdf are unreadable Status in Yade: Fix Committed Bug description: After documentation is generated, the inheritance graphs on the website look good, for example: https://yade-dem.org/doc/yade.wrapper.html#yade.wrapper.Material but in the Yade.pdf file the class names are completely unreadable. For example look at page 173 in pdf file. I would like to fix this before release. If you have any hints about where to search for place in code which causes this problem please tell! To manage notifications about this bug go to: https://bugs.launchpad.net/yade/+bug/1813229/+subscriptions ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
[Yade-dev] [Bug 1813401] Re: Potential Particles & Blcoks compilation warnings
OK, it is fixed now https://gitlab.com/yade- dev/trunk/commit/8d28c1ff138d4962f5abfe6d663848cadc0d6674 ** Changed in: yade Status: New => Fix Committed -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1813401 Title: Potential Particles & Blcoks compilation warnings Status in Yade: Fix Committed Bug description: When compiling yade without -DENABLE_POTENTIAL_BLOCKS=ON -DENABLE_POTENTIAL_PARTICLES=ON there are only 6 warnings, four of which are due to code in external libraries (and thus unfixable). When compiling yade with -DENABLE_POTENTIAL_BLOCKS=ON -DENABLE_POTENTIAL_PARTICLES=ON there are 198 warnings. Mostly about unused variable or narrowing conversion: Not sure if I should put them all here, but in any case here they are: pkg/common/Gl1_PotentialBlock.cpp:1035:81: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:1035:81: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:1035:81: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:1036:79: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:1036:79: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:1036:79: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:259:13: warning: unused variable ‘sphere’ [-Wunused-variable] pkg/common/Gl1_PotentialBlock.cpp:286:1: warning: control reaches end of non-void function [-Wreturn-type] pkg/common/Gl1_PotentialBlock.cpp:432:31: warning: ‘functionBool’ may be used uninitialized in this function [-Wmaybe-uninitialized] pkg/common/Gl1_PotentialBlock.cpp:476:20: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] pkg/common/Gl1_PotentialBlock.cpp:578:106: warning: unused variable ‘xAxis’ [-Wunused-variable] pkg/common/Gl1_PotentialBlock.cpp:578:130: warning: unused variable ‘yAxis’ [-Wunused-variable] pkg/common/Gl1_PotentialBlock.cpp:578:154: warning: unused variable ‘zAxis’ [-Wunused-variable] pkg/common/Gl1_PotentialBlock.cpp:578:65: warning: unused variable ‘angle’ [-Wunused-variable] pkg/common/Gl1_PotentialBlock.cpp:717:81: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:717:81: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:717:81: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:718:79: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:718:79: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:718:79: warning: narrowing conversion of ‘(double)((const Eigen::DenseCoeffsBase, 0>*) pkg/common/Gl1_PotentialBlock.cpp:877:10: warning: unused variable ‘value’ [-Wunused-variable] pkg/common/Gl1_PotentialBlock.cpp:928:106: warning: unused variable ‘xAxis’ [-Wunused-variable] pkg/common/Gl1_PotentialBlock.cpp:928:130: warning: unused variable ‘yAxis’ [-Wunused-variable] pkg/common/Gl1_PotentialBlock.cpp:928:154: warning: unused variable ‘zAxis’ [-Wunused-variable] pkg/common/Gl1_PotentialBlock.cpp:928:65: warning: unused variable ‘angle’ [-Wunused-variable] pkg/dem/BlockGen.cpp:1159:17: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] pkg/dem/BlockGen.cpp:1162:18: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] pkg/dem/BlockGen.cpp:1190:20: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] pkg/dem/BlockGen.cpp:1265:20: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] pkg/dem/BlockGen.cpp:1332:25: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] pkg/dem/BlockGen.cpp:1346:16: warning: unused variable ‘clumpId’ [-Wunused-variable] pkg/dem/BlockGen.cpp:1347:19: warning: comparison between signed and unsigned integer expressions [-Wsign-compare] pkg/dem/BlockGen.cpp:139:118: warning: unused variable ‘spacing’ [-Wunused-variable] pkg/dem/BlockGen.cpp:139:72: warning: unused variable ‘persistenceA’ [-Wunused-variable] pkg/dem/BlockGen.cpp:139:7: warning: unused variable ‘abdCount’ [-Wunused-variable] pkg/dem/BlockGen.cpp:139:95: warning: unused variable ‘persistenceB’ [-Wunused-variable] pkg/dem/BlockGen.cpp:1459:7: warning: unused variable ‘converge’ [-Wunused-variable] pkg/dem/BlockGen.cpp:1460:18:
[Yade-dev] buildbot warnings in Yade on yade-full
The Buildbot has detected a problem in the build on builder yade-full while building Yade. Full details are available at: https://yade-dem.org/buildbot/builders/yade-full/builds/4980 Buildbot URL: https://yade-dem.org/buildbot/ Buildslave for this Build: r0calcul9 Build Reason: The web-page 'rebuild' button was pressed by '': Build Source Stamp: 720a352989c9b1148cf04022d14ec3da233fe563 Blamelist: Build Had Warnings: warnings test test_1 sincerely, -The Buildbot ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
Re: [Yade-dev] gitlab work cycle
On 1/29/19 11:24 PM, Janek Kozicki wrote: Hi, have you seen merge request by Vasileios? https://gitlab.com/yade-dev/trunk/merge_requests/48 I remember that you said something about pipelines not working from other people's accounts. Yes. There should be a way to solve this in general manner. There could a way with future versions of gitlab, but current behavior is that the pipeline has to run on the account where the MR comes from, not on the destination. We can't change it. I guess that due to previous discussion, Could be, but It should be enough to read the documentation [1]. I am updating it again today but it was already relevant. [1]https://yade-dev.gitlab.io/trunk/github.html?highlight=gitlab#pushing-changes-to-remote-repository Cheers Bruno ___ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
