Re: [julia-users] Re: Why these 2 functions generate very different llvm?

It would be great if this is resolvable. It took me quite some time to determine that this is an issue in my own code. My mental model was that type stability is about the return type being statically dependent on the input parameter types. That a local binding has changed is quite a different

[julia-users] Calculus.hessian result oddities

The hessian produced by Calculus.hessian has some properties that seem odd to me. First, the resulting matrix is not symmetric (though it's really close). Second, it is not positive definite even though the eigenvalues are all positive. This might partly be the result of the first problem.

Re: [julia-users] Signal / slot (or publish-subscribe) libraries in Julia

Reactive.jl?

Re: [julia-users] Re: Why these 2 functions generate very different llvm?

On Mon, May 30, 2016 at 7:54 PM, Erik Schnetter wrote: > Yichao > > What is the known bug here: That Julia doesn't handle this more efficiently, The bug is that the type instability here is spurious. > or that the variable `x` can change its type from Int to Float64? > > In

Re: [julia-users] Re: Why these 2 functions generate very different llvm?

Yichao What is the known bug here: That Julia doesn't handle this more efficiently, or that the variable `x` can change its type from Int to Float64? In this example, are there two variables `x` (the argument and the explicitly declared local variable), or should the declaration be an error?

Re: [julia-users] Re: Why these 2 functions generate very different llvm?

On Mon, May 30, 2016 at 7:23 PM, David P. Sanders wrote: > > > El lunes, 30 de mayo de 2016, 19:11:47 (UTC-4), FANG Colin escribió: >> >> function t1(n::Int, x::Int, a::Float64) >>x::Float64 = x >>for i in 1:n >> x += a >>end >> x >> end >> @time

[julia-users] Re: Why these 2 functions generate very different llvm?

El lunes, 30 de mayo de 2016, 19:11:47 (UTC-4), FANG Colin escribió: > > function t1(n::Int, x::Int, a::Float64) >x::Float64 = x >for i in 1:n > x += a >end > x > end > @time t1(10^6, 1, 1.0) > > 0.005445 seconds (1.00 M allocations: 15.259 MB) > In t1, x changes type

[julia-users] Why these 2 functions generate very different llvm?

function t1(n::Int, x::Int, a::Float64) x::Float64 = x for i in 1:n x += a end x end @time t1(10^6, 1, 1.0) 0.005445 seconds (1.00 M allocations: 15.259 MB) function t2(n::Int, y::Int, a::Float64) x::Float64 = y for i in 1:n x += a end x end @time

[julia-users] Re: Grant funding and Julia Computing?

Another option might be the "Bountysource" website: https://www.bountysource.com/teams/julialang This would get around having to have a contract, and so may be easier to use with grant funds. On Thursday, April 21, 2016 at 1:58:02 PM UTC+10, Sheehan Olver wrote: > > > Has anyone included

[julia-users] Re: Using Julia for real time astronomy

If you are prepared to make your code to not perform any heap allocations, I don't see a reason why there should be any issue. When I once worked on a very first multi-threading version of Julia I wrote exactly such functions that won't trigger gc since the later was not thread safe. This can

Re: [julia-users] Re: What is the difference between bitwise and logical operators?

Don't get sidetracked by the implementation. Also, inlining has nothing to do with it. & is a function, && is a control flow construct. The only way you could replicate && and || is with a macro, such that a && b would get expanded to something like if a b else false end But of course

Re: [julia-users] Re: What is the difference between bitwise and logical operators?

On Mon, May 30, 2016 at 2:25 PM, Ford Ox wrote: > Yeah I have read it. Multiple times, since I forget things and I still don't > remember all the things. > > So basically the difference is that bitwise operators are functions. That > means its arguments get evaluated before

[julia-users] Re: What is the difference between bitwise and logical operators?

Yeah I have read it. Multiple times, since I forget things and I still don't remember all the things. So basically the difference is that bitwise operators are functions. That means its arguments get evaluated before they are passed in. That also means, that if that function would be inlined,

Re: [julia-users] Re: What is the difference between bitwise and logical operators?

Yeah I have read it. Multiple times, since I forget things and I still don't remember all the things. So basically the difference is that bitwise operators are functions. That means its arguments get evaluated before they are passed in. That also means, that if that function would be inlined,

[julia-users] Re: doc fix: transposition operators in section highlighting difference to R

Worked out how to do markup from the Sphinx documentation: http://www.sphinx-doc.org/en/stable/markup/inline.html#inline-markup Submitted pull request.

[julia-users] Re: doc fix: transposition operators in section highlighting difference to R

Worked out how to do markup from the Spinx documentation: http://www.sphinx-doc.org/en/stable/markup/inline.html#inline-markup Submitted pull request.

Re: [julia-users] Bizarre Segfault during ccall on OSX

Helge, Not sure if this helps, but below the (successful) output on my machine. I’m on OS X 11.6-beta, but I don’t think that is important. I do remember installing an updated Xcode. Regards, Rob > On May 30, 2016, at 08:41, Helge Eichhorn wrote: > > > > Hi! > > I

[julia-users] Re: Getting sequence of time and subset it

I'm not 100% sure I understand your question, but let me give it a shot. First thing is to note why you're getting that MethodError. It's from the line println(si in sdt1[i, [:BreakTime1, :BreakTime2]]) Define sdt1 as you do (I just copied into a Julia REPL) and set i = 1 to for the first

[julia-users] Bizarre Segfault during ccall on OSX

Hi! I am having a strange problem with a segfault that seemingly appeared out of nowhere while calling Fortran code on OSX. When I try to run the tests of my Dopri.jl package on Julia 0.4.5 on OSX 10.11.5 the process consistently fails with this error

[julia-users] What do @_inline_meta and @_propagate_inbounds_meta do?

Hi, code in abstractarray.jl (master) is filled with calls to @_inline_meta and @_propagate_inbounds_meta. Can someone explain what do these to macro do? Thanks!

[julia-users] Re: Julia Users Berlin

That's awesome! I'm based in Berlin and just recently discussed with different people that we really need a meetup... So, thanks for doing this! I should be able to attend, looking forward seeing everyone there. Best, Simon Am Montag, 30. Mai 2016 15:16:08 UTC+2 schrieb David Higgins: > > Hi

Re: [julia-users] Julia users Berlin

Hi all, I've announced a new meet-up with a visiting speaker here https://groups.google.com/forum/#!topic/julia-users/S3eMY64c_dE Hope to see you in two weeks. David. On Thursday, 26 March 2015 22:55:02 UTC+1, Max Suster wrote: > > > I would have loved to join too, but it was too short notice

[julia-users] Julia Users Berlin

Hi all, I gave a talk at the recent PyData Berlin conference (http://pydata.org/berlin2016/) and there seems to be enough interest in forming a regular users group in the city. Some of you may recall that we had a preliminary meeting a year ago, which happened to coincide with Viral Shah

Re: [julia-users] Re: Using Julia for real time astronomy

You could test whether the GC is fast enough by implementing the computational core (using simulated data or something similar), then just running it. Then if you find it is not acceptable, you haven't wasted time on writing the code for interfacing with the equipment. Also, you could think about

Re: [julia-users] Re: Using Julia for real time astronomy

Thanks for the answer. I don't intend to use any package, only use my array so I can confirm that I will not have dynamic memory allocation (let's hope that I'm true ;) ). But even in this case Julia itself may do allocations, so my question would be more: if there is nearly nothing to do, is

[julia-users] Re: Using Julia for real time astronomy

I think, that would be difficult. As soon as you use any packages for image conversion or estimation you have to assume that they use dynamic memory allocation. The garbage collector of Julia is fast, but not suitable for hard real-time requirements. Implementing a garbage collector for hard

Re: [julia-users] Re: What is the difference between bitwise and logical operators?

See http://docs.julialang.org/en/release-0.4/manual/control-flow/#man-short-circuit-evaluation A lot of effort went into writing and improving the language manual, so that you can find very detailed answers to questions like this one. It is fine to ask on the list if you can't find it, but

[julia-users] Re: doc fix: transposition operators in section highlighting difference to R

Ah, there is! Didn't refresh the tab I left open with this thread. On Monday, 30 May 2016 12:07:14 UTC+1, James Gilbert wrote: > > Hmm, this line was introduced in this commit: > > Major cleanup of 'Noteworth differences' >

[julia-users] Re: doc fix: transposition operators in section highlighting difference to R

Hmm, this line was introduced in this commit: Major cleanup of 'Noteworth differences' where it appears to be correct. Is there some kind of bug rendering :obj:`.'`?

[julia-users] Re: What is the difference between bitwise and logical operators?

The && and || operators are conditional, as in other languages. The second operand is not always evaluated.

[julia-users] Re: What is the difference between bitwise and logical operators?

Ye I know what bitwise operator does. I will ask in different way, maybe it will be clearer to you. Why people use logical operators ( f.e. in conditions ) instead of bitwise operators? Is && <: & ? On Monday, May 30, 2016 at 9:58:02 AM UTC+2, Kaj Wiik wrote: > > > Here's a clue: > > > julia>

[julia-users] Using Julia for real time astronomy

Hi everyone, I am working in astronomy and we are thinking of using Julia for a real time, high performance adaptive optics system on a solar telescope. This is how the system is supposed to work: 1) the image is read from the camera 2) some correction are applied 3) the atmospheric

Re: [julia-users] doc fix: transposition operators in section highlighting difference to R

See https://github.com/JuliaLang/julia/issues/16259#issuecomment-217703153 On Sun, May 29 2016, James Gilbert wrote: > In Noteworthy Differences to R it says: > > * Julia performs matrix transposition using the ' operator and conjugated > transposition using > the ' operator. Julia’s A.' is

[julia-users] Getting sequence of time and subset it

I have a dataset similar to the one below sdt1 = DataFrame(ID = 1:2, StartTime = DateTime(["4/13/2016 07:00", "4/13/2016 07:15"], "m/d/y H:M"), EndTime = DateTime(["4/13/2016 12:00", "4/13/2016 12:15"], "m/d/y H:M"), BreakTime1 =

[julia-users] Re: What is the difference between bitwise and logical operators?

Here's a clue: julia> 0b10010011 & 0b10010011 0x93 julia> 0b10010011 && 0b10010011 ERROR: TypeError: non-boolean (UInt8) used in boolean context Kaj On Monday, May 30, 2016 at 9:30:22 AM UTC+3, Ford Ox wrote: > > For example > true & false == true && false > > Is it just artifact from c

[julia-users] Getting sequence of datetime and format it

I have a data similar to the one below sdt1 = DataFrame(ID = 1:2, StartTime = DateTime(["4/13/2016 07:00", "4/13/2016 07:15"], "m/d/y H:M"), EndTime = DateTime(["4/13/2016 12:00", "4/13/2016 12:15"], "m/d/y H:M")) I would like to get the sequence between StartTime and EndTime by 30 minutes

[julia-users] What is the difference between bitwise and logical operators?

For example true & false == true && false Is it just artifact from c where bool types don't exist?