Closed dlfivefifty closed 8 years ago
Reverting to the 31 Oct update fixes the issue
I see... Well, to be honest, I wasn't very careful with GLPlot/GLAbstraction master lately, so it's not a big surprise...The only versions guaranteed to work are the tagged versions.
2014-11-06 10:56 GMT+01:00 dlfivefifty notifications@github.com:
Reverting to the 31 Oct update fixes the issue
— Reply to this email directly or view it on GitHub https://github.com/SimonDanisch/GLWindow.jl/issues/4#issuecomment-61953671 .
Oddly, going back to the tagged versions had the same bug, so I'm on master for everything except GLWindow.
I think the camera control is also going a lot slower, though maybe it has to do with upgrade to Yosemite?
PS I'll probably be using GLPlot in an ApproxFun talk at the Supercomputing conference and at the Boston Julia Group, thanks for developing it!
That's pretty exciting!! =) If you tell me what'll you show, I could polish things a little (besides getting master back on track).
I don't really know the reason for the slower Camera control, but I had it as well, and it was gone when I rebuild Julia with the newest master. It must have been something about Reactive and some temporary bug in Julia, I suppose.
If the tagged versions don't work, I don't really understand tagging... Well I'll look into this tonight or tomorrow!
I'll probably show the time evolution examples from ApproxFun. This includes plots of a function on a disk and I think on a square with a fairly sparse grid
I'll try the Julia master again, last time I did there were too many problems with pkgs
I'll be visiting NYU also next week, probably no ApproxFun related talk but may show it to people anyways
Sent from my iPad
On 7 Nov 2014, at 8:53 pm, Sdanisch notifications@github.com wrote:
That's pretty exciting!! =) If you tell me what'll you show, I could polish things a little (besides getting master back on track).
I don't really know the reason for the slower Camera control, but I had it as well, and it was gone when I rebuild Julia with the newest master. It must have been something about Reactive and some temporary bug in Julia, I suppose.
— Reply to this email directly or view it on GitHub.
Okay master should be fixed!
I’m getting this error in Julia 0.3.2
ERROR: error compiling createdisplay#89: error compiling createwindow#79: unsupported or misplaced expression => in function createwindow#79 in glsurf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/GLPlot.jl:57 in surf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/Plot.jl:66 in plot at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/Plot.jl:186 in timeevolution at /Users/solver/.julia/v0.3/ApproxFun/src/PDE/timeevolution.jl:36
On 8 Nov 2014, at 3:52 am, Sdanisch notifications@github.com wrote:
Okay master should be fixed!
— Reply to this email directly or view it on GitHub https://github.com/SimonDanisch/GLWindow.jl/issues/4#issuecomment-62174396.
And on 0.4 I get this repeated.
WARNING: apply(f, x) is deprecated, use f(x...)
instead
in call at /Users/solver/.julia/v0.4/GLAbstraction/src/GLCamera.jl:128
in OrthographicPixelCamera at /Users/solver/.julia/v0.4/GLAbstraction/src/GLCamera.jl:67
in createwindow at /Users/solver/.julia/v0.4/GLWindow/src/reactglfw.jl:383
in createdisplay at /Users/solver/.julia/v0.4/GLPlot/src/GLPlot.jl:46
in glsurf at /Users/solver/.julia/v0.4/ApproxFun/src/Plot/GLPlot.jl:57
in surf at /Users/solver/.julia/v0.4/ApproxFun/src/Plot/Plot.jl:66
in plot at /Users/solver/.julia/v0.4/ApproxFun/src/Plot/Plot.jl:186
in timeevolution at /Users/solver/.julia/v0.4/ApproxFun/src/PDE/timeevolution.jl:36
On 8 Nov 2014, at 9:16 am, Sheehan Olver solver@mac.com wrote:
I’m getting this error in Julia 0.3.2
ERROR: error compiling createdisplay#89: error compiling createwindow#79: unsupported or misplaced expression => in function createwindow#79 in glsurf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/GLPlot.jl:57 in surf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/Plot.jl:66 in plot at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/Plot.jl:186 in timeevolution at /Users/solver/.julia/v0.3/ApproxFun/src/PDE/timeevolution.jl:36
On 8 Nov 2014, at 3:52 am, Sdanisch <notifications@github.com mailto:notifications@github.com> wrote:
Okay master should be fixed!
— Reply to this email directly or view it on GitHub https://github.com/SimonDanisch/GLWindow.jl/issues/4#issuecomment-62174396.
Guess I forgot some @compat. I fixed the one in GLWindow, hope there are not more missing!
The warning comes probably from Reactive.jl, which is fixed in the master of Reactive.jl
OK, checked out Reactive. Now I get
ERROR: stack overflow in Texture at /Users/solver/.julia/v0.4/GLAbstraction/src/GLTexture.jl:151 (repeats 4505 times) in toopengl at /Users/solver/.julia/v0.4/GLPlot/src/surface.jl:65 in toopengl at /Users/solver/.julia/v0.4/GLPlot/src/surface.jl:62 in glplot at /Users/solver/.julia/v0.4/GLPlot/src/GLPlot.jl:23 in glsurf at /Users/solver/.julia/v0.4/ApproxFun/src/Plot/GLPlot.jl:60 in surf at /Users/solver/.julia/v0.4/ApproxFun/src/Plot/Plot.jl:66 in plot at /Users/solver/.julia/v0.4/ApproxFun/src/Plot/Plot.jl:186 in timeevolution at /Users/solver/.julia/v0.4/ApproxFun/src/PDE/timeevolution.jl:36
On 8 Nov 2014, at 9:27 am, Sdanisch notifications@github.com wrote:
The warning comes probably from Reactive.jl, which is fixed in the master of Reactive.jl
— Reply to this email directly or view it on GitHub https://github.com/SimonDanisch/GLWindow.jl/issues/4#issuecomment-62224771.
That's odd.. Are you on GLPlot master?
So I tried it out on a fresh install and yes the tagged versions don't work anymore (Especially on 0.4). :( So you need to be on master with the following packages: GLPlot, GLWindow, GLAbstraction, Reactive, ModernGL and GLText(Optional) If it works for you, I can tag them!
It was still broken before when the grid was specified with xrange and yrange.
I just updated everything and now its broken even when thats not specified:
julia> obj = GLPlot.glplot(map(GLAbstraction.Vec1,vals) , primitive=GLPlot.SURFACE())
ERROR: instancedobject
has no method matching instancedobject(::Dict{Symbol,Any}, ::Int64, ::GLProgram, ::UInt32)
in toopengl at /Users/solver/.julia/v0.4/GLPlot/src/surface.jl:109
in toopengl at /Users/solver/.julia/v0.4/GLPlot/src/surface.jl:62
in glplot at /Users/solver/.julia/v0.4/GLPlot/src/GLPlot.jl:23
On 8 Nov 2014, at 5:21 am, Sdanisch notifications@github.com wrote:
So I tried it out on a fresh install and yes the tagged versions don't work anymore (Especially on 0.4). :( So you need to be on master with the following packages: GLPlot, GLWindow, GLAbstraction, Reactive, ModernGL and GLText(Optional) If it works for you, I can tag them!
— Reply to this email directly or view it on GitHub https://github.com/SimonDanisch/GLWindow.jl/issues/4#issuecomment-62252856.
Okay, this is getting embarrassing for me! I simply didn't notice that one commit didn't go through -.- Well I hope this charade has an end for now! I tested xrange+yrange with a matrix, but I couldn't test the tensor plot, as the example code that I have doesn't seem to match ApproxFun anymore.
OK Works again!
For some reason its much faster on v0.3 than v0.4. I suspect they changed something in type-inference so that the pde solve is not compiling to the right type.
On 11 Nov 2014, at 6:11 am, Sdanisch notifications@github.com wrote:
Okay, this is getting embarrassing for me! I simply didn't notice that one commit didn't go through -.- Well I hope this charade has an end for now! I tested xrange+yrange with a matrix, but I couldn't test the tensor plot, as the example code that I have doesn't seem to match ApproxFun anymore.
— Reply to this email directly or view it on GitHub https://github.com/SimonDanisch/GLWindow.jl/issues/4#issuecomment-62533131.
INFO: loaded GLFW 3.0.4 Cocoa NSGL chdir menubar dynamic from /Users/solver/.julia/v0.3/GLFW/deps/usr64/lib/libglfw Window from callback unrecognized. Window: Window(GLPlot) ptr Ptr{Void} @0x00007fc788d6fdb0 available windows:
while loading In[1], in expression starting on line 8
in error at error.jl:21 in update at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:195 in window_position at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:213 in createwindow at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:351 in createdisplay at /Users/solver/.julia/v0.3/GLPlot/src/GLPlot.jl:46 in glsurf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/GLPlot.jl:57 in surf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/Plot.jl:66 in timeevolution at /Users/solver/.julia/v0.3/ApproxFun/src/PDE/timeevolution.jl:32 in timeevolution at /Users/solver/.julia/v0.3/ApproxFun/src/PDE/timeevolution.jl:35
Okay, different error than I expected. There's a new commit to ProjectorPatch, lets see if we can solve this with a dirty workaround!
Now I get
Empty Screen Stacks initialized warning not defined while loading In[1], in expression starting on line 8
in update at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:193 in window_position at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:218 in createwindow at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:356 in createdisplay at /Users/solver/.julia/v0.3/GLPlot/src/GLPlot.jl:46 in glsurf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/GLPlot.jl:57 in surf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/Plot.jl:66 in timeevolution at /Users/solver/.julia/v0.3/ApproxFun/src/PDE/timeevolution.jl:32 in timeevolution at /Users/solver/.julia/v0.3/ApproxFun/src/PDE/timeevolution.jl:35
On 20 Nov 2014, at 4:58 pm, Sdanisch notifications@github.com wrote:
Okay, different error than I expected. There's a new commit to ProjectorPatch, lets see if we can solve this with a dirty workaround!
— Reply to this email directly or view it on GitHub https://github.com/SimonDanisch/GLWindow.jl/issues/4#issuecomment-63887721.
Changing warning to warn give
INFO: loaded GLFW 3.0.4 Cocoa NSGL chdir menubar dynamic from /Users/solver/.julia/v0.3/GLFW/deps/usr64/lib/libglfw Empty Screen Stacks initialized WARNING: Window from callback unrecognized. Window: Window(GLPlot) ptr Ptr{Void} @0x00007fe9da609640 available windows:
BoundsError() while loading In[1], in expression starting on line 8
in update at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:195 in window_position at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:218 in createwindow at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:356 in createdisplay at /Users/solver/.julia/v0.3/GLPlot/src/GLPlot.jl:46 in glsurf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/GLPlot.jl:57 in surf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/Plot.jl:66 in timeevolution at /Users/solver/.julia/v0.3/ApproxFun/src/PDE/timeevolution.jl:32 in timeevolution at /Users/solver/.julia/v0.3/ApproxFun/src/PDE/timeevolution.jl:35
On 20 Nov 2014, at 4:58 pm, Sdanisch notifications@github.com wrote:
Okay, different error than I expected. There's a new commit to ProjectorPatch, lets see if we can solve this with a dirty workaround!
— Reply to this email directly or view it on GitHub https://github.com/SimonDanisch/GLWindow.jl/issues/4#issuecomment-63887721.
So the question is, why are all the arrays containing the screen suddenly empty....
Should we Skype? I’m
fivefifty
On 20 Nov 2014, at 5:05 pm, Sheehan Olver solver@mac.com wrote:
Changing warning to warn give
INFO: loaded GLFW 3.0.4 Cocoa NSGL chdir menubar dynamic from /Users/solver/.julia/v0.3/GLFW/deps/usr64/lib/libglfw Empty Screen Stacks initialized WARNING: Window from callback unrecognized. Window: Window(GLPlot) ptr Ptr{Void} @0x00007fe9da609640 available windows:
BoundsError() while loading In[1], in expression starting on line 8
in update at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:195 in window_position at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:218 in createwindow at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:356 in createdisplay at /Users/solver/.julia/v0.3/GLPlot/src/GLPlot.jl:46 in glsurf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/GLPlot.jl:57 in surf at /Users/solver/.julia/v0.3/ApproxFun/src/Plot/Plot.jl:66 in timeevolution at /Users/solver/.julia/v0.3/ApproxFun/src/PDE/timeevolution.jl:32 in timeevolution at /Users/solver/.julia/v0.3/ApproxFun/src/PDE/timeevolution.jl:35
On 20 Nov 2014, at 4:58 pm, Sdanisch <notifications@github.com mailto:notifications@github.com> wrote:
Okay, different error than I expected. There's a new commit to ProjectorPatch, lets see if we can solve this with a dirty workaround!
— Reply to this email directly or view it on GitHub https://github.com/SimonDanisch/GLWindow.jl/issues/4#issuecomment-63887721.
Just reinstalled GLPlot and its breaking with the following error:
size
has no method matching size(::Texture{Float32,1,2}, ::Int64) while loading In[2], in expression starting on line 10in _methods at /Applications/Julia-0.3.0.app/Contents/Resources/julia/lib/julia/sys.dylib (repeats 5 times) in abstract_call_gf at /Applications/Julia-0.3.0.app/Contents/Resources/julia/lib/julia/sys.dylib in abstract_call at /Applications/Julia-0.3.0.app/Contents/Resources/julia/lib/julia/sys.dylib in abstract_eval_call at /Applications/Julia-0.3.0.app/Contents/Resources/julia/lib/julia/sys.dylib in abstract_eval at /Applications/Julia-0.3.0.app/Contents/Resources/julia/lib/julia/sys.dylib in abstract_interpret at /Applications/Julia-0.3.0.app/Contents/Resources/julia/lib/julia/sys.dylib in typeinf at /Applications/Julia-0.3.0.app/Contents/Resources/julia/lib/julia/sys.dylib (repeats 2 times) in typeinf_ext at /Applications/Julia-0.3.0.app/Contents/Resources/julia/lib/julia/sys.dylib in update at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:72 in cursor_position at /Users/solver/.julia/v0.3/GLWindow/src/reactglfw.jl:143 in renderloop at /Users/solver/.julia/v0.3/GLPlot/src/GLPlot.jl:67 in anonymous at task.jl:340