[julia-users] Re: using chol command in Julia v.0.4.0

Try chol(B, Val{:L}) and chol(B, Val{:U}) On Sunday, October 18, 2015 at 2:19:29 AM UTC+2, james...@gmail.com wrote: > > Hi All: > > This has got to be simple, yet beyond me. > > I construct a matrix QQ that causes isposdef(QQ) to return true. > > However, at the Julia command line > >

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

I have to take back a couple things. The Julia docs are clearer than I thought about the BigFloat type: it's fixed-sized but arbitrarily large, with size resettable by a function call. Second, julia> eps(BigFloat)

[julia-users] Re: CCALL to intel MKL on MAC ?

You can build Julia with MKL (see the build instructions in the README). Then you example (slightly modified) simply works by: julia> function myasum(n::Integer, X::Vector{Float64}, incx::Integer) ccall((:cblas_dasum, :libmkl_rt), Float64, (Int64,

[julia-users] Re: ANN: NullableArrays.jl package

How does NullableArray{T,N} compare to Array{Nullable{T},N}?

[julia-users] using chol command in Julia v.0.4.0

Hi All: This has got to be simple, yet beyond me. I construct a matrix QQ that causes isposdef(QQ) to return true. However, at the Julia command line cQQ = chol(QQ, :L) returns WARNING: chol(a::AbstractMatrix, uplo::Symbol) is deprecated, use chol(a::AbstractMatrix,

[julia-users] Re: Is there a direct way to get binary representation of a float?

Thanks to the pointers given I dug a little bit under the hood ad found the promising unbox intrinsic function. It would exactly be what I was looking for but it seems to work only one way: *julia> **using Base.Intrinsics* *julia> **theFloat=1.0* *1.0* *julia> **b=unbox(Int64,theFloat)*

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

Use a truncated Taylor series around the point maybe?

[julia-users] Announcing TimeZones.jl

The TimeZones.jl package has been around for a while but now it has a functional interface. The latest v0.1.0 release includes: - New types including: `ZonedDateTime`, `FixedTimeZone`, and `VariableTimeZone` - "Calendrical" `ZonedDateTime` math (see documentation) - Local system

[julia-users] Questions on Julia language stablity and backward-incompatible changes for future release

Hi Everyone: I have been followed Julia for some time and think this is a great language for high performance computing. With 0.4 I am seriously thinking about using it for my project. One concern is the language still in developing phase and constantly evolving, and some breaking changes may

[julia-users] Re: Questions on Julia language stablity and backward-incompatible changes for future release

What is the scope of your project?

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

Jeffrey: If you're building your own floating point library specifically geared toward ensuring exact results when mathematically possible, then I highly recommend you read up on Unums and come collaborate with me: https://github.com/tbreloff/Unums.jl. There's a bunch of info/links in the wiki

Re: [julia-users] @example a + :b

macroexpand() might be useful. The distinction between QuoteNode and Expr(:quote, sym) is often a gotcha. --Tim On Saturday, October 17, 2015 08:45:06 AM Matt wrote: > I thought > @example a + :b > passed the expression :(a + :b) to the internal body of the macro. > > But it's not the case: >

Re: [julia-users] Re: Questions on Julia language stablity and backward-incompatible changes for future release

It depends on your project and you. If you're ready to make some code changes here and there and maintain an adequate test suite for your purposes, then I think it's plenty ready for production. You can always pick a release that you like and pin all your packages to ensure stability. The

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

That has promise, Kristoffer. I did port something of that nature, expecting it to work well -- but there was some numerical mush in more than a couple of trailing bits in some cases. Using more terms did not help. Thinking about it just now, it might be more robustly stable if I expand in

[julia-users] Re: [ANN] JuliaIO and FileIO

So your biggest concern doesn't seem to be a problem: You can just do query("file.ext") and get back the format without loading the file. I see that in the way you want to use it, a hierarchy would be a nice addition. You could just do this: myload(path) = myload(query(path)) myload{T <:

Re: [julia-users] Deprecation of require

Hard to say without a more complete example of what you're trying to do. Another candidate for your troubles is https://github.com/JuliaLang/julia/issues/3674 --Tim On Friday, October 16, 2015 02:03:05 PM David Smith wrote: > Thanks, Tim. I feel like I'm getting closer, but I tried either and

Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

Deprecation warnings are typically very specific and going through a large code base only takes a couple of hours in my experience and doesn't require deep Julia expertise. It's pretty similar to fixing compiler warnings in C. Using Compat is a little harder but not by much. I would recommend this

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

I had tried to find a clean way to jump into the taylor series using the well approximated sin(x) or cos(x) and so additionally limit the terms used -- there may be / probably is a way in concert with an additional tabulation (which would be fine in this case). Taylor's theorem is not

Re: [julia-users] Does anyone have a fork/branch of Sundials.jl that works on 0.4/0.5?

Dear Mauro, I think the fixes, at least for cvode, have already been done in one of the branches, but there isn't a PR yet. Apart from some minor API differences, which hopefully will be ironed out in the future, cvode in Sundials.jl is a lot faster than ode23s in ODE.jl. Best Simon

Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

It might also be worth looking at using Lint.jl.

Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

Okay, looks like a good exercise in practicing new syntax... :>{ and I'll just have to compare my modified v3 tk package with the unmodified v4 tk package's code for 'button'. On Sat, Oct 17, 2015 at 4:20 AM, wrote: > It might also be worth looking at using Lint.jl.

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

thanks, good pointer. I am working on routines for a double-double-like floating point type. Straight double-double implementations have very nice arithmetic properties; in my experimentation, most double-double trig routines resolve fewer bits than I want. I want to take as much advantage

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

Why are you trying to roll your own sin(x) function? I think you will be hard pressed to improve on the library sin(x) in either speed or accuracy. John On Saturday, October 17, 2015 at 3:38:17 AM UTC-4, Jeffrey Sarnoff wrote: > > I had tried to find a clean way to jump into the taylor series

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

Search for the comment that begins "OK kiddies, time for the pros" in http://stackoverflow.com/questions/2284860/how-does-c-compute-sin-and-other-math-functions John On Saturday, October 17, 2015 at 9:00:35 AM UTC-4, John Gibson wrote: > > Why are you trying to roll your own sin(x)

Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

rrrgh!!! 99.9% of the warnings are about syntax being used within the v4 tc package!!! Can I suppress these & get on with it? On Sat, Oct 17, 2015 at 6:26 AM, Forrest Curo wrote: > Okay, looks like a good exercise in practicing new syntax... :>{ > > and I'll just have

[julia-users] Re: ANN: NullableArrays.jl package

This brings to mind a question that commonly comes up in scientific computing: nullable arrays simulated through means of a canonical "no-data value", e.g in a domain where all values are expected to be negative, using +. It's ugly, but it's really common. From what I can see of the

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

It is Float128 in resolution and modulo the refining the trig, in accuracy of results if one allows the least sig nibble to be inexact . Float125, Float127 are working titles. BigFloat is not used except as an intermediary for IO/strings (and for running tests). BigFloat is problematic

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

My local design will enfold any type <: Real that supports the usual ops for an AbstractFloat and for which fma is defined. Float12x does not do that, to be more transparent for others' useful play. On Saturday, October 17, 2015 at 2:41:41 PM UTC-4, Jeffrey Sarnoff wrote: > > My local design

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

> > Have you found Unums to more a probable solution or more of an exploratory > project? A little of both, I guess. I do think the framework has the potential to solve many problems that are seemingly impossible using floating points with any precision (including infinite!) This is due to the

[julia-users] Announcing TimeZones.jl

Good job! PS: Quinn is such a beautiful name, just had to say that.

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

Have you found Unums to more a probable solution or more of an exploratory project? On Saturday, October 17, 2015 at 1:27:44 PM UTC-4, Tom Breloff wrote: > > Jeffrey: If you're building your own floating point library specifically > geared toward ensuring exact results when mathematically

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

My local design will enfold any type <: AbstractFloat for which fma is defined. Float12x does not do that, to be more transparent for others. On Saturday, October 17, 2015 at 1:27:44 PM UTC-4, Tom Breloff wrote: > > Jeffrey: If you're building your own floating point library specifically >

[julia-users] Getting error for "using PyPlot" -- Need help

Hello, I installed python-matplotlib as sudo apt-get install python-matplotlib I am getting following error : D900C:~/julia$ julia _ _ _ _(_)_ | A fresh approach to technical computing (_) | (_) (_)| Documentation: http://docs.julialang.org _ _

RE: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

I very much agree, adding deprecation warnings should be treated as a feature change, i.e. those should really go in before a feature freeze (whereas for 0.4 very many went in even after RC1), but at least before the RC sequence starts. From: julia-users@googlegroups.com

Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

Okay, I've found that inconvenient default setting I'd changed in my own tk package [in src/tk/dialogues.jl] : ## Message box function Messagebox(parent::MaybeWidget; title::String="", message::String="", detail::String="") args = Dict() if !isa(parent, Nothing) args["parent"] =

[julia-users] Re: Getting error for "using PyPlot" -- Need help

On Saturday, October 17, 2015 at 2:57:28 PM UTC-4, ssarkaray...@gmail.com wrote: > > ImportError('cannot import name scimath',) > You could be seeing https://github.com/stevengj/PyCall.jl/issues/65 which was due to a conflict between the Julia libopenblas and the one linked by numpy. It

Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

… julia doesn’t like ‘foo ()’ anymore, she now prefers ‘foo()’ … In a recent thread I vowed to start helping with enforcing the Julia Community Standards , so I guess it’s now time to walk the walk. In the Standards, we can read While “Julia” is a

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

On Saturday, October 17, 2015 at 9:39:54 AM UTC-4, Jeffrey Sarnoff wrote: > > I am working on routines for a double-double-like floating point type. >> >> There are plenty of such libraries already existing as free/open-source software. Why not crib from them?

[julia-users] Re: Questions on Julia language stablity and backward-incompatible changes for future release

On Saturday, October 17, 2015 at 12:57:34 PM UTC-4, Jacob Dang wrote: > > I notice in 0.4 release documentation ( > https://github.com/JuliaLang/julia/blob/release-0.4/NEWS.md), all > breaking changes are clearly stated, which is a good thing. Just a small > suggestion, it would be better to

Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

I'm sure julia can adopt any gender identification [] prefers, but I frankly doubt [] cares... In the interests of 'truth in confusers' standards, could we please see fewer 'ok' buttons and more 'Take that, human!' messages with "ohno!" bottons? Anyway, yes, I've found this a very helpful

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

I have been -- this has taken up much of the past month. The better double-double libraries are very good +,-,*,^, exp, slightly less so with /; I found some trig lsbs to be wiggly. I hand down-converted some quad-double algorithms and routines to be triple-double work-alikes. I use them

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

I have re-implemented a number of them. The better double-double libraries are very good +,-,*,^, exp, slightly less so with /; I found some trig lsbs to be wiggly. I mapped triple-double basics and quad-double algorithms into a triplet cooperative, used internally to assure the manifold

Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

You can start julia with -depwarn=no to turn off deprecation warnings. On a personal note, I think that the time between type deprecation and the release was possibly a bit short. It feels that whatever package I import now I get pages of deprecation warnings. This is particularly inconvenient

Re: [julia-users] numerical trig question about refining good approximation to sin,cos

Ok, I see from github that you're working on a Float125 and Float127 implementation. Why not Float128?, and why not use Julia BigFloats? Out of curiosity, I did a few tests on Julia's sin(BigFloat). julia> p=Float64(pi) 3.141592653589793 julia> length(string(p)) 17 julia> sin(p)

Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

Thanks, all! Most of my booboos seem to be due to the fact that julia doesn't like 'foo ()' anymore, she now prefers 'foo()' which I suppose makes the parsing simpler. And I now know where to find that pesky tk button code... On Sat, Oct 17, 2015 at 8:00 AM, Kristoffer Carlsson

Re: [julia-users] Re: Everything I wrote in version .3 is now 'depreciated'

@Kristoffer, it definitely was a bit short, but not for the reason you'd think. The types were deprecated very early in 0.4 development (mostly), but code to generate warnings wasn't added until quite late. Definitely an oversight, several of us have been fixing them wherever we can. Won't

[julia-users] Is there a direct way to get binary representation of a float?

I don't see the point of passing through a string like this: *julia> **hex2bytes(num2hex(1.0))* *8-element Array{UInt8,1}:* * 0x3f* * 0xf0* * 0x00* * 0x00* * 0x00* * 0x00* * 0x00* * 0x00* I assume that the intermediate passage slows down the conversion. Same question for the way back

[julia-users] Re: Is there a direct way to get binary representation of a float?

Also possible with the bits function: julia> bits(1.0) "0011"

[julia-users] Re: Is there a direct way to get binary representation of a float?

julia> a = [1.0] 1-element Array{Float64,1}: 1.0 julia> b = reinterpret(UInt8, a) 8-element Array{UInt8,1}: 0x00 0x00 0x00 0x00 0x00 0x00 0xf0 0x3f julia> c = reinterpret(Float64, b) 1-element Array{Float64,1}: 1.0 On Saturday, October 17, 2015 at 6:04:14 PM UTC+2, Uliano Guerrini

[julia-users] Re: What features are interesting in a VS Code plug-in?

I would imagine most of the things on this list would apply readily to any IDE, but since you ask. 1) One of the best IDE experiences out of MSFT was the F# IDE, where you could easily interrogate expression types by hovering. this helped immensely in that statically typed language. Now Julia