Le jeudi 23 juillet 2015 à 15:31 -0700, Brandon Taylor a écrit :
I'm not saying inherent slowness will be particularly useful. I'm
saying environment access will be particularly useful. The point of
Julia is no compromise between speed and code-ability. If it is not
possible to integrate
I recently poked around a bit with the @code_warntype macro in my code and
quickly realized that a lot of my variables were assigned Any at compile
time. I tried to find the reason for it and got down to the eig function:
julia @code_warntype eig(rand(Float64, 5,5))
Variables:
I recently poked around a bit with the @code_warntype macro in my code and
quickly realized that a lot of my variables were assigned Any at compile
time. I tried to find the reason for it and got down to the eig function:
julia @code_warntype eig(rand(Float64, 5,5))
Variables:
Sounds good to me.
On Friday, July 24, 2015 at 4:14:57 PM UTC+2, Stefan Karpinski wrote:
Cool. Just to get an early start on package name bikeshedding, maybe
InverseLaplace.jl?
On Fri, Jul 24, 2015 at 8:07 AM, lapeyre@gmail.com javascript:
wrote:
The link
Cool. Just to get an early start on package name bikeshedding, maybe
InverseLaplace.jl?
On Fri, Jul 24, 2015 at 8:07 AM, lapeyre.math1...@gmail.com wrote:
The link
https://github.com/jlapeyre/ILT.jl
Ok, maybe I was being harsh when I used the word mis-marketing. The post
here: http://julialang.org/blog/2012/02/why-we-created-julia/ specifically
mentions that one of Julia's goals is to be as easy for statistics as
R. Building a domain specific language is more difficult (but clearly not
I can understand that if you're used to building interfaces that use R's
non-standard evaluation and reified environments heavily, it can be
frustrating to not have those features. But I don't think that means that
you cannot build convenient and safe interfaces for data analysis.
On Fri, Jul 24,
I just ran into the same issue, any change?
On Tuesday, 16 June 2015 00:37:11 UTC+2, Alex Ames wrote:
I submitted an issue
https://github.com/one-more-minute/Julia-LT/issues/198to Julia-LT; it
seems we're running into the same bug. No responses to the issue yet on
Github.
On Wednesday,
New url:
https://github.com/jlapeyre/InverseLaplace.jl/blob/master/src/InverseLaplace.jl
On Friday, July 24, 2015 at 4:14:57 PM UTC+2, Stefan Karpinski wrote:
Cool. Just to get an early start on package name bikeshedding, maybe
InverseLaplace.jl?
On Fri, Jul 24, 2015 at 8:07 AM,
I should give you a hard time about arguing from authority ;-), but I was
there at the same time and knew KMP, so I wouldn't want to argue too much
with him either, and I am in agreement with you about fexprs vs. macros,
and the equivalent issues in Julia.
On Friday, July 24, 2015 at 2:31:54
If I am developing a package with multiple julia versions, will anything
terrible happen if I Pkg.clone() the project twice (one for each version)
and then replace one of those directories with a link to the other?
So change from
.julia/v0.3/MyPackage
.julia/v0.4/MyPackage
to
Hi,
Is there any definition of NaN for Integer types? Let's say I want to
create a matrix with some unspecified entries, that is entries marked
special. I am using NaN for Float64 but would like to make it work with
other types too. Suggestions?
-Júlio
Package looks beautiful.
I see that you are using Gadfly, and using rendering offered up by the
Compose package.
Any thoughts about how I would render a d3-based infrastrcture?
Michael
On Monday, June 8, 2015 at 12:23:21 PM UTC-4, Shashi Gowda wrote:
Hello all!
I have been working on a
Thank you all, that is what I thought, I will stick with plain Float64 for
now.
-Júlio
2015-07-24 10:59 GMT-07:00 Erik Schnetter schnet...@gmail.com:
On Fri, Jul 24, 2015 at 1:09 PM, Júlio Hoffimann
julio.hoffim...@gmail.com wrote:
Hi,
Is there any definition of NaN for Integer types?
Every bit pattern in a Signed or Unsigned represents an integer,
there is no representation for a NaN like in eg Float64 etc. You
would have to use Nullable types, see
https://julia.readthedocs.org/en/latest/manual/types/#nullable-types-representing-missing-values
Best,
Tamas
On Fri, Jul 24
Thanks for the replies. I filed the issue here
https://github.com/JuliaLang/julia/issues/12304 (#12304)
On Friday, July 24, 2015 at 4:09:07 PM UTC+2, Stefan Karpinski wrote:
Please do file an issue https://github.com/JuliaLang/julia/issues if
you haven't already.
On Fri, Jul 24, 2015 at
Le vendredi 24 juillet 2015 à 08:48 -0700, Brandon Taylor a écrit :
Ok, maybe I was being harsh when I used the word mis-marketing. The
post here: http://julialang.org/blog/2012/02/why-we-created-julia/ sp
ecifically mentions that one of Julia's goals is to be as easy for
statistics as R.
Macros seem to have a bunch of limitations. They can't be overloaded to take
advantage of Julia's typing system. Their functionality can somewhat mimic
evaluation within a function in its direct parent environment, but what if you
want to write functions within your macro, or macros inside your
Macros seem to have a bunch of limitations. They can't be overloaded to take
advantage of Julia's typing system. Their functionality can somewhat mimic
evaluation within a function in its direct parent environment, but what if you
want to write functions within your macro, or macros inside your
Lisp has already been down this path – fexprs
https://en.wikipedia.org/wiki/Fexpr were special forms with behavior
similar to R's functions, and they were deprecated in the 1980s in favor of
macros, https://en.wikipedia.org/wiki/Fexpr#Mainstream_use_and_deprecation:
His central objection was
If you end up trying the `Nullable` route, you might find our in-progress
`NullableArrays` package
helpful: https://github.com/johnmyleswhite/NullableArrays.jl. Its designed
to extend the functionality of the `AbstractArray` interface to a container
type specialized to handle `Nullable`
By the way, is it a v0.4 feature?
On Friday, July 24, 2015 at 7:56:54 PM UTC+2, Tamas Papp wrote:
Every bit pattern in a Signed or Unsigned represents an integer,
there is no representation for a NaN like in eg Float64 etc. You
would have to use Nullable types, see
seems to work fine.
On Friday, 24 July 2015 18:36:05 UTC-3, andrew cooke wrote:
If I am developing a package with multiple julia versions, will anything
terrible happen if I Pkg.clone() the project twice (one for each version)
and then replace one of those directories with a link to the
Yes, but available with Compat too.
On Jul 24, 2015, at 5:54 PM, Sisyphuss zhengwend...@gmail.com wrote:
By the way, is it a v0.4 feature?
On Friday, July 24, 2015 at 7:56:54 PM UTC+2, Tamas Papp wrote:
Every bit pattern in a Signed or Unsigned represents an integer,
there is no
The time when this could go awry is if you were to update your package to
support only 0.3 or only 0.4, then the versions of the package that each
version of Julia would attempt to load would be different, resulting in the
directory flip-flopping between the 0.3 and 0.4 versions every time you
Please do file an issue https://github.com/JuliaLang/julia/issues if you
haven't already.
On Fri, Jul 24, 2015 at 5:09 AM, Mauro mauro...@runbox.com wrote:
I recently poked around a bit with the @code_warntype macro in my code
and
quickly realized that a lot of my variables were assigned
Maybe you could make your own 64-bit bitstype, which restricted values to
integer values in the range that will fit in a Float64 (around -2^53 to
2^53). Then you could be sure you didn't lose any information (give an
InexactError if a value doesn't fit), and still allow for a NaN value, and
Le vendredi 24 juillet 2015 à 11:21 -0700, Brandon Taylor a écrit :
Macros seem to have a bunch of limitations. They can't be overloaded
to take advantage of Julia's typing system. Their functionality can
somewhat mimic evaluation within a function in its direct parent
environment, but what
This is definitely possible, but integer operations will be a bit slower
since you'll have to do something like this:
bitstype 64 NullableInt
+(x::NullableInt, y::NullableInt) = ifelse(
(reinterpret(Int,x) !== typemin(Int)) (reinterpret(Int,y) !==
typemin(Int)),
Le vendredi 24 juillet 2015 à 05:29 -0700, lapeyre.math1...@gmail.com a
écrit :
Here is a generalized gamma distribution.
https://github.com/jlapeyre/GenGammaDist.jl
https://en.wikipedia.org/wiki/Generalized_gamma_distribution
Only rand() and mean() are implemented, and again no tests.
I agree, it would be very helpful to the discussion to have some examples
of the problems Brandon is looking to solve.
On Fri, Jul 24, 2015 at 3:09 PM, Milan Bouchet-Valat nalimi...@club.fr
wrote:
Le vendredi 24 juillet 2015 à 11:21 -0700, Brandon Taylor a écrit :
Macros seem to have a bunch
On Fri, Jul 24, 2015 at 1:09 PM, Júlio Hoffimann julio.hoffim...@gmail.com
wrote:
Hi,
Is there any definition of NaN for Integer types? Let's say I want to
create a matrix with some unspecified entries, that is entries marked
special. I am using NaN for Float64 but would like to make it work
yep, that's all i'm doing. seems to be working fine so far. i'm hoping to
do only the minimal Pkg stuff in 0.3.
if i drop support for 0.3 i guess i'll be wiping my juila/v0.3 too.
cheers, andrew
On Friday, 24 July 2015 21:00:41 UTC-3, Tom Breloff wrote:
I do this as well to test changes
I do this as well to test changes quickly on 0.3.10. You might consider
calling Pkg.pin() so it's less likely to flip-flop when calling update, but
that could bring its own problems I suppose. I primarily use 0.4 so I
haven't had any issues.
On Friday, July 24, 2015, Elliot Saba
Hi,
Here is a numeric Inverse Laplace Transform. It needs some tests and stuff
before making an ANN:,
That may not happen for a while, due to the standard excuses: baby, avoid
getting fired. (Unless someone else writes them ;) )
-John
Here is a generalized gamma distribution.
https://github.com/jlapeyre/GenGammaDist.jl
https://en.wikipedia.org/wiki/Generalized_gamma_distribution
Only rand() and mean() are implemented, and again no tests. This depends on
Distributions. The authors of Distributions may want to include
The link
https://github.com/jlapeyre/ILT.jl
37 matches
Mail list logo
