Thanks, but I still have some doubt (inline)
Il 06/06/2016 19:29, Uwe Fechner ha scritto:
Well, you can load modules on demand in the following way (in this way I
load the module PyPlot on demand):
eval(Expr(:using, :PyPlot))
OK
To load a module from any path, push the directory, where you
Sounds awesome Chris +1
On Tue, 2016-06-07 at 05:47, David Parks wrote:
> Is there hidden logic behind this command that I don't see, or did I bump
> into a genuine bug here? v0.4.5
Are you referring to the random value?
help?> Array
...
Array{T}(dims) constructs an uninitialized dense array
Please answer the original question. What does Pkg.status() say?
Is there hidden logic behind this command that I don't see, or did I bump
into a genuine bug here? v0.4.5
julia> x = Array{Int64}()
0-dimensional Array{Int64,0}:
47917330527848
julia> for i in x; println(i); end
47917330527848
julia> println(x)
47917330527848
julia> print(typeof(x))
from http://docs.julialang.org/en/latest/manual/constructors/
...This automatic provision of constructors is equivalent to the following
explicit declaration:
type Point{T<:Real}
>
> x::T
>
> y::T
>
>
>> Point(x,y) = new(x,y)
>
> end
>
>
>> Point{T<:Real}(x::T, y::T) = Point{T}(x,y)
>
>
It also solves ODEs and SDEs, and I will be adding DDEs (delay equations)
and differential algebraic equations ASAP. It implements more solvers for
ODEs (with more tests) than ODE.jl, and implements more modern solvers for
SDEs than SDE.jl. It also implements solvers for common (S)PDEs, and I
Hey,
This is the author here. Let me address a few things. Giving the solution
is optional for any problem type. So you can just declare a
PoissonProblem(f). If you give it a solution, then it calculates errors and
a bunch of extra things. I'll clear up that part of the tutorial. You can
just to emphasize this is purely personal opinion.
On Tuesday, 7 June 2016 01:31:24 UTC+1, Christoph Ortner wrote:
>
> this package implements just a couple of specific problems, as required by
> its author. It is a nice package BUT
>
> it is far too specific to be called
this package implements just a couple of specific problems, as required by
its author. It is a nice package BUT
it is far too specific to be called DifferentialEquations.jl. (in my view
anyhow) For me this is a problem with the package eco-system. Such
specialised packages should maybe not be
Dear all,
Thank you very much for you help! I've been able to write a form of gcvspl
that seems to run, with calling:
ccall( (:gcvspl_, "./libgcvspl.so"), Void,
thanks
On Monday, June 6, 2016 at 7:43:28 PM UTC-4, David P. Sanders wrote:
>
> Wrapped in a function, obviously.
>
> El lunes, 6 de junio de 2016, 19:41:10 (UTC-4), David P. Sanders escribió:
>>
>>
>>
>> El lunes, 6 de junio de 2016, 18:53:46 (UTC-4), Jeffrey Sarnoff escribió:
>>>
>>> ```
>>>
Wrapped in a function, obviously.
El lunes, 6 de junio de 2016, 19:41:10 (UTC-4), David P. Sanders escribió:
>
>
>
> El lunes, 6 de junio de 2016, 18:53:46 (UTC-4), Jeffrey Sarnoff escribió:
>>
>> ```
>> indexOfFirstNonmatching("abcd","abcd") == 0
>> indexOfFirstNonmatching("abcd","abdc") == 3
El lunes, 6 de junio de 2016, 18:53:46 (UTC-4), Jeffrey Sarnoff escribió:
>
> ```
> indexOfFirstNonmatching("abcd","abcd") == 0
> indexOfFirstNonmatching("abcd","abdc") == 3
> ```
> what is a fast way to do this with strings of 50-1000 characters?
>
How about
s1 = "abcd"
s2 = "abdc"
for
```
indexOfFirstNonmatching("abcd","abcd") == 0
indexOfFirstNonmatching("abcd","abdc") == 3
```
what is a fast way to do this with strings of 50-1000 characters?
Yes. I am.
Am Dienstag, 7. Juni 2016 00:22:57 UTC+2 schrieb Stefan Karpinski:
>
> Are you talking about this package
> https://github.com/ChrisRackauckas/DifferentialEquations.jl ?
>
> On Mon, Jun 6, 2016 at 6:04 PM, digxx
> wrote:
>
>> Hey all,
>> I dont quite get the
sadly that get me back to the original problem
*julia> **Pkg.build("Homebrew")*
*INFO: Building Homebrew*
HEAD is now at dde20cd Remove (almost) everything (#50678)
HEAD is now at c377b50 Merge pull request #92 from staticfloat/staging
Error: Unknown command: outdated
Are you talking about this package
https://github.com/ChrisRackauckas/DifferentialEquations.jl ?
On Mon, Jun 6, 2016 at 6:04 PM, digxx wrote:
> Hey all,
> I dont quite get the essence of this package. Looking through the examples
> I found for a 2d poisson type problem:
Hey all,
I dont quite get the essence of this package. Looking through the examples
I found for a 2d poisson type problem:
Example problem with solution: ``u(x,y)= sin(2π.*x).*cos(2π.*y)/(8π*π)``"
function poissonProblemExample_wave() f(x) = sin(2π.*x[:,1]).*cos(2π.*x[:,2])
sol(x) =
Thanks Cedric. I've found a way to construct the product I needed.
Richard
That worked. Thanks!
> On Jun 6, 2016, at 1:45 PM, Tony Kelman wrote:
>
> Check in process monitor what is running there. It's been reported that git
> randomly freezes sometimes on osx, which is apparently a bug in git.
>
> If Pkg.status() says you have an unmodified install
For reference:
https://github.com/JuliaLang/julia/issues/3737
https://github.com/JuliaLang/julia/pull/8599
https://github.com/JuliaLang/julia/issues/10290
Cheers!
Kevin
On Mon, Jun 6, 2016 at 8:11 AM, Mauro wrote:
> This was discussed at length on github, have a look
Check in process monitor what is running there. It's been reported that git
randomly freezes sometimes on osx, which is apparently a bug in git.
If Pkg.status() says you have an unmodified install of Homebrew.jl version
0.2.1, try Pkg.build("Homebrew") or
using Homebrew
Homebrew.update()
On Monday, June 6, 2016 at 1:11:53 PM UTC-4, Milan Bouchet-Valat wrote:
>
> > tuples yes, but when I search for ``NTuples`` in the docs there is
> > barely any hit and all that come show it being used as a type
> > dfinition but found no mention of what it is. Yes, a ``ntuple``
> > function is
I'm seeing the exact same error after updating to Homebrew 0.2.1.
On Sunday, June 5, 2016 at 2:40:44 PM UTC-7, Tony Kelman wrote:
>
> Which version of Homebrew.jl did you update to? What does Pkg.status() say?
>
brand new instal
using the binary download of 0.4.5
having the same problem over the weekend
as of monday
*Version 0.4.5 (2016-03-18 00:58 UTC)*
*|__/ | x86_64-apple-darwin13.4.0*
*julia> **Pkg.update()*
*INFO: Updating METADATA...*
*INFO: Computing changes...*
Ah, simple than.
Thanks
segunda-feira, 6 de Junho de 2016 às 18:11:53 UTC+1, Milan Bouchet-Valat
escreveu:
>
> Le lundi 06 juin 2016 à 09:56 -0700, J Luis a écrit :
> >
> > > What exactly are you after?
> > >
> > What I'm after is simple. To be able to access the members
> > ``x_units``
Hi Uwe,
On Monday, June 6, 2016 at 12:55:28 PM UTC-4, Uwe Fechner wrote:
>
> I am very happy about your work. I had the hope, that the built-in method
> sleep could be improved to reach this level of performance:
> https://github.com/JuliaLang/julia/issues/12770
>
> But perhaps it is better to
Well, you can load modules on demand in the following way (in this way I
load the module PyPlot on demand):
eval(Expr(:using, :PyPlot))
To load a module from any path, push the directory, where you module lives
into the load path:
cd("/home/ufechner/00PythonSoftware/FastSim")
push!(LOAD_PATH,
Really useless – it doesn't know about integers or how add them, for
example. If you want to trim down the standard library, you can try editing
out parts of base/sysimg.jl and rebuilding, but that's kind of a tricky
process.
On Mon, Jun 6, 2016 at 12:43 PM, Avik Sengupta
Le lundi 06 juin 2016 à 09:56 -0700, J Luis a écrit :
>
> > What exactly are you after?
> >
> What I'm after is simple. To be able to access the members
> ``x_units`` and so on of
>
> http://gmt.soest.hawaii.edu/doc/latest/GMT_API.html#gmt-grids
>
> with the wrapper
>
>
segunda-feira, 6 de Junho de 2016 às 17:19:08 UTC+1, Simon Danisch escreveu:
>
> What exactly are you after?
>
What I'm after is simple. To be able to access the members ``x_units`` and
so on of
http://gmt.soest.hawaii.edu/doc/latest/GMT_API.html#gmt-grids
with the wrapper
I am very happy about your work. I had the hope, that the built-in method
sleep could be improved to reach this level of performance:
https://github.com/JuliaLang/julia/issues/12770
But perhaps it is better to have this in a separate package.
Uwe
On Monday, June 6, 2016 at 10:07:22 AM UTC+2,
Hi John,
I am currently pursuing similar effort. I got a GPIO pin on the BeagleBone
Black embedded board toggling in hard real-time and verified the jitter
with an oscilloscope. For that, I used a vanilla Linux 4.4.11 kernel with
the PREEMPT_RT patch applied. I also released an initial version
Julia is pretty useless without its standard library.
On Monday, 6 June 2016 14:42:02 UTC+1, Dmitry wrote:
>
> I tried to remove ".jl" library files from Julia installation directory,
> but it did not help. Then I tried to remove "libjulia.dll" but it does not
> want to run without this file.
What exactly are you after?
There's not much more to it than using tuples, which should be well
documented.
We wrapped Vulkan with this Clang
version:
https://github.com/JuliaGPU/VulkanCore.jl/blob/master/gen/api/vk_common_1.0.0.jl#L1367
Best,
Simon
Am Montag, 6. Juni 2016 01:41:34 UTC+2
Hi Páll,
Thanks for your reply. Please see below.
On Mon, Jun 6, 2016 at 5:30 AM, Páll Haraldsson
wrote:
> On Monday, June 6, 2016 at 8:07:22 AM UTC, Islam Badreldin wrote:
>>
>> Hi,
>>
>> I'm excited to announce the first release of POSIXClock, a package that
>>
I Installed via the OSX binary.
Here is the info on my install
julia> versioninfo()
Julia Version 0.4.5
Commit 2ac304d (2016-03-18 00:58 UTC)
Platform Info:
System: Darwin (x86_64-apple-darwin13.4.0)
CPU: Intel(R) Xeon(R) CPU E5-1650 v2 @ 3.50GHz
WORD_SIZE: 64
BLAS: libopenblas
This was discussed at length on github, have a look there. But
essentially to make it easier to create vectors of vectors.
On Mon, 2016-06-06 at 16:35, K leo wrote:
> Why deprecate array concatenation with "[]" and suggest to use "collect"?
> It requires more typing and
I'm interested in what the community at large thinks about trying to get a
standard for Julia, maybe for when are closer to a 1.0
If we had an ANSI standard or ISO standard, something that everyone could
rely on, I think it would really build trust in larger commercial
undertakings. I mean, if
Thanks Simon, some progress but I never worked with NTuples. Is there any
example wrapper that uses this technique that I can read/study?
segunda-feira, 6 de Junho de 2016 às 15:23:17 UTC+1, Simon Danisch escreveu:
>
> On master, Clang will emit NTuples, which is a bit nicer at least!
>
>
Why deprecate array concatenation with "[]" and suggest to use "collect"?
It requires more typing and makes code less elegant. What do we really
gain with inefficiency?
Also using "[]" directly in REPL does not have problem, but including code
generates warning. Why?
On master, Clang will emit NTuples, which is a bit nicer at least!
bytestring(UInt8[a...])
a = map(UInt8, ("abcd"...,))
Am Montag, 6. Juni 2016 01:41:34 UTC+2 schrieb J Luis:
>
> Hi,
>
> I have one of those types generated from a C struct with Clang.jl that
> turns a stack variable into a
Why wouldn't wrapping a simple NTuple work?
The problem is that the text is inside one of those immutables generated by
Clang (see:
https://github.com/joa-quim/GMT.jl/blob/master/src/libgmt_h.jl#L371) so no
simple bytestring(data) works because it complains that no method exists to
convert from GMT.Array_80_Uint8 type
And worst,
For nul-terminated ASCII or UTF-8 data, which is what it looks like you have
here, use bytestring(data), where data is either a Cstring, a Ptr{UInt8}, or a
Vector{UInt8}.
If you know the length of the string (in bytes), do bytestring(data, len).
(This allows embedded nul characters.)
In
Slight correction: if you pass bytestring(data) a Vector{UInt8}, it assumes the
length of the data is the length of the string (in bytes), and does not assume
nul-terminated data.
I tried to remove ".jl" library files from Julia installation directory,
but it did not help. Then I tried to remove "libjulia.dll" but it does not
want to run without this file.
Thanks for this tip. Freeing the package did the job.
Regards,
Jan
Dňa piatok, 1. apríla 2016 18:19:27 UTC+2 David Anthoff napísal(-a):
>
> You can’t be on master for JuliaParser if you use julia 0.4.x, Keno just
> sent around a message on julia-dev that JuliaParser master is now julia 0.5
>
Le lundi 06 juin 2016 à 04:08 -0700, FANG Colin a écrit :
> I find myself often writing code like this when dealing pop! with a
> Dict{A, B}
>
>
> if !haskey(my_dict, key)
> do_something...
> end
>
> value = pop!(my_dict, key)
>
> do_something_else...
>
>
> The code above has an issue:
Thanks but the string encoding is not an issue. This julia code is a
wrapper to a library that I know it uses only ASCII in the variables being
accessed.
segunda-feira, 6 de Junho de 2016 às 10:57:29 UTC+1, Páll Haraldsson
escreveu:
>
> On Sunday, June 5, 2016 at 11:41:34 PM UTC, J Luis wrote:
Don't forget: Meet-up this Thursday in Berlin for any who want to come
along!
David.
On Monday, 30 May 2016 15:16:08 UTC+2, David Higgins wrote:
>
> Hi all,
>
> I gave a talk at the recent PyData Berlin conference (
> http://pydata.org/berlin2016/) and there seems to be enough interest in
>
The contributors are happy to announce, that Optim.jl version 0.5 has now
been released.
Notice that this version is breaking in a few different ways, so please
update your code as necessary, and don't hesitate to ask over at
https://github.com/JuliaOpt/Optim.jl/issues or join Kristoffer
This is interesting thanks. I didn't realise you could re-assign j inside
the index like that. A very neat notational trick. But I agree that looking
forward the filter! option is probably best. I'll adjust my code
accordingly, many thanks.
As an aside, every time I post code to this list I get
Yep. Agreed. Totally redundant :-)
Cheers,
Colin
On 4 June 2016 at 05:11, DNF wrote:
> Your in-method is a bit odd:
>
> Base.in{T}(x::T, r::BasicInterval{T}) = (r.start <= x <= r.stop) ? true :
> false
>
> Why don't you just write
>
> Base.in{T}(x::T, r::BasicInterval{T}) =
I would use `Cint` as type, not `Int64`, as in `Ptr{Cint}`. Are you sure
that your Fortran code uses 64-bit integers? Technically, this violates the
Fortran standard. A Fortran integer is the same as a C int, except if you
use special flags while building the Fortran library (which you might be
On Mon, Jun 6, 2016 at 6:29 AM, Ulf Worsoe wrote:
> The symbol jl_signal_pending is exported, and the following appears to work
> (assuming, of course, sig_atomic_t is an int):
>
> function callback_func()
> if unsafe_load(cglobal(:jl_signal_pending, Cint),1) > Cint(0)
>
I find myself often writing code like this when dealing pop! with a Dict{A,
B}
if !haskey(my_dict, key)
do_something...
end
value = pop!(my_dict, key)
do_something_else...
The code above has an issue: it looks up the key in a dict twice
unnecessary.
I know I can opt for the
The symbol jl_signal_pending is exported, and the following appears to work
(assuming, of course, sig_atomic_t is an int):
function callback_func()
if unsafe_load(cglobal(:jl_signal_pending, Cint),1) > Cint(0)
return convert(Cint,1)
else
return convert(Cint,0)
end
end
function
The symbol jl_signal_pending is exported, and the following appears to work:
function callback_func()
if unsafe_load(cglobal(:jl_signal_pending, Cint),1) > Cint(0)
return convert(Cint,1)
else
return convert(Cint,0)
end
end
function do_native_call()
disable_sigint() do
I can see that the symbol jl_signal_pending is exported. Can I assume that
this is safe to check from the julia thread? So doing something like this
should work:
function callback_func()
if unsafe_load(cglobal(:jl_signal_pending, Cint),1) > Cint(0)
end
function do_native_call()
On Monday, June 6, 2016 at 3:22:47 AM UTC, Charles Ll wrote:
>
> Dear all,
>
> I am trying to call some Fortran code in Julia, but I have a hard time
> doing so... I have read the docs, looked at the wrapping of ARPACK and
> other libraries... But I did not find any way to make it work.
>
> I am
On Sunday, June 5, 2016 at 11:41:34 PM UTC, J Luis wrote:
>
> Hi,
>
> I have one of those types generated from a C struct with Clang.jl that
> turns a stack variable into a lng list of members (for example (but I
> have longer ones))
>
>
Since it seems you have a good overview in this domain I will give more
details:
We are working in signal processing and especially in image processing. The
goal here is just the adaptive optic: we just want to stabilize the image
and not get the final image.
The consequence is that we will not
On Monday, June 6, 2016 at 8:07:22 AM UTC, Islam Badreldin wrote:
>
> Hi,
>
> I'm excited to announce the first release of POSIXClock, a package that
> provides Julia bindings to clock_*() functions from POSIX real-time
> extensions (librt on Linux).
> https://github.com/ibadr/POSIXClock.jl
>
It appears to work in Julia 0.4 - at least I hasn't crashed yet - but I
have not really stress tested it.
Just disabling SIGINT only gets me half of the way. It will stop the
function from crashing, but these calls may run for a long time, and in
some cases it may be relevant to manually stop
Hi,
I'm excited to announce the first release of POSIXClock, a package that
provides Julia bindings to clock_*() functions from POSIX real-time
extensions (librt on Linux).
https://github.com/ibadr/POSIXClock.jl
But first, a full disclosure: I'm very new to Julia programming as well as
to
You are missing & in ccall for variables that put as Int64 but expected to
be passed as Ptr{Int64}.
ccall( (:gcvspl_, "./libgcvspl.so"), Void, (Ptr{Float64},Ptr{Float64},Ptr{
Int64},Ptr{Float64},Ptr{Float64},Ptr{Int64},Ptr{Int64},Ptr{Int64},Ptr{Int64
68 matches
Mail list logo