If you need code to keep working without hassle, definitely stick with
the 0.3 series.
Nightly builds for bleeding-edge tinkering only.
On Thu, Aug 21, 2014 at 2:27 AM, Kevin Squire wrote:
>
>
> On Wednesday, August 20, 2014, K Leo wrote:
>>
>> Now the nightlies will be the early builds of 0.4
On Wednesday, August 20, 2014, K Leo wrote:
>
> Now the nightlies will be the early builds of 0.4. Is that reasonable to
> assume these early builds will be less reliable and so I should better stay
> with 0.3 for some time?
>
They probably won't get t broken, but there are a lot of potentia
It is great now that we have 0.3 released. Thank you all very much!
A question on future updates.
In the past months, I have been using julia nightlies PPA to get the
most updated builds. Generally, it has been working well for me. The
nightlies have not caused big problems for my applicati
For 2D, would switching to Gadfly be advisable? Not sure how to get
Gadfly to plot in a separate window to do the animation.
On 21 Aug 2014, at 9:51 am, Simon Danisch wrote:
> Good to hear.
> The test looks funny, as I overlay everything GLPlot is able to do ;)
> I should remove ex
On Wednesday, August 20, 2014 3:22:07 PM UTC-7, Jeff Bezanson wrote:
> You know, it's interesting: it's easy to write down a grammar in
> formal language that is actually ambiguous. Code is not ambiguous.
>
I think this was at least part of the motivation for PEGs. They are closer
to modeling t
If you called f(x) which calls g(x), but g(x) does not exist, you are going
to get a no-method error. Or if you are using run-time eval to insert code
into the compile-time environment, you are forcing Julia to re-evaluate a
lot of assumptions anyways, so any performance benefits of assuming const
Jameson,
You wrote that the compiler can already tell whether or not a function
modifies one of its mutable arguments. Say that the function is f, the
mutable argument is x, and that f contains a call like g(x), where g is
another function. Then apparently in order to analyze f the compiler wo
The "It" in my second sentence was supposed to refer to "const in C", but I
deleted an interposing sentence as I was revising. But the argument applies
to both.
In C, violating const is only a compile-time warning. And it is trivial to
cast away const. One website dedicated to reducing coding erro
To be more precise...
SSH is only used to launch Julia on the worker nodes. Afterwards, Julia sets up
a socket on both nodes and passes messages through that. If the sockets can't
be bound, because of a restrictive firewall for instance, Julia would try for
60 seconds and then time out.
At fir
Sorry again. I thought that the N in '-p N' meant the total number of
processes, not the number of addition (worker) processes. I was wrong. I
just did a 'julia -p 4' and the ran procs() and it returned [1:5]. But my
issue still stands. Adding processors from the command line really works
to
Sorry, typo - yes, I meant addprocs(), not addproc().
On Wednesday, August 20, 2014 6:05:22 PM UTC-7, Jiahao Chen wrote:
>
> Did you type "addproc(3)" or "addprocs(3)"?
> Thanks,
>
> Jiahao Chen
> Staff Research Scientist
> MIT Computer Science and Artificial Intelligence Laboratory
Oh! I misread what you wrote (I should be sleeping already).
I suggest you try to connect on the remote node to check wether Julia is
started and trying to connect to the master node (with ps to spot julia and
netstat or ss to spot the socket usage).
Maybe the worker can't connect back to the m
You're right. "Single" might have been a better word than "simple," since
^v0.3.0-rc3 has to come from somewhere too.
--Gray
On Wednesday, August 20, 2014 8:53:35 PM UTC-5, Simon Kornblith wrote:
>
> From that script it looks like it's
>
> git rev-list ^v0.3.0-rc3 | wc -l
>
> On Wednesday, Augu
I still can't check but I'm wondering if Julia is alway trying to resolve what
it is given in a machonefile.
Did you try with "127.0.0.1" (assuming you got ssh setup on that machine)?
Jameson,
My proposal for inargs is here:
https://groups.google.com/forum/#!searchin/julia-users/inargs/julia-users/FK_29Dj4eDo/A_drp4-i8DcJ
It is not compile-time; it is run-time. And it is not a warning; it is an
error to violate the constraint. And I'm not sure what you mean by "weak":
t
>From that script it looks like it's
git rev-list ^v0.3.0-rc3 | wc -l
On Wednesday, August 20, 2014 9:22:36 PM UTC-4, Gray Calhoun wrote:
>
> On Wednesday, August 20, 2014 12:56:42 PM UTC-5, Simon Kornblith wrote:
>>
>> Does it still not work to use 0.4.0-dev+n as the version in the REQUIRE
>>
Somewhat trivial, but I notice that you add 4 processes in the first call,
but only 3 in the second call. Presumably you meant to add 4 in both cases
(master prompt + 4 workers)? In either case, `-p N` and `addprocs(N)`
should work exactly equivalently.
On Wed, Aug 20, 2014 at 6:53 PM, wrote:
>
I think the primary argument against inarg is that it is incredibly weak.
It is essentially only a self-imposed compile-time warning.
I'm not opposed to being able to prevent modification of an object, but I
think that is more useful as a requirement imposed by the caller, rather
than self imposed
On Wednesday, August 20, 2014 10:06:49 PM UTC-3, gael@gmail.com wrote:
>
> I can't test right now. Did you setup passwordless ssh?
Yes, I can ssh passwordless ( typing: ssh "hostname_of_remote_machine"
'julia' starts a julia session on the remote machine).
I also added the hostname and I
On Wednesday, August 20, 2014 12:56:42 PM UTC-5, Simon Kornblith wrote:
>
> Does it still not work to use 0.4.0-dev+n as the version in the REQUIRE
> file? This used to almost work, but some of the nightlies were missing the
> commit number. It certainly seems easier than searching through all th
I can't test right now. Did you setup passwordless ssh?
Did you type "addproc(3)" or "addprocs(3)"?
Thanks,
Jiahao Chen
Staff Research Scientist
MIT Computer Science and Artificial Intelligence Laboratory
On Wed, Aug 20, 2014 at 6:53 PM, wrote:
> Forgive me if this has been answered before; I couldn't find the answer.
>
> I'm having fun with IJulia
Sounds to me like another reason for deprecating this special syntax (and
replacing it with an improved ccall, as part of the jn/ccall3 WIP)
:)
On Monday, August 18, 2014, Elliot Saba > wrote:
> Probably because of our special parsing of & in ccall invocations.
> -E
>
>
> On Mon, Aug 18, 2014 at
Good to hear.
The test looks funny, as I overlay everything GLPlot is able to do ;)
I should remove example.jl, as it uses legacy code.
I'm not sure about the surface example, though... Did you change anything?
This might be due to a change of the output from imread (Images.jl) and
shouldn't be a p
We are pleased to announce the immediate release of Julia 0.3.0. This
release contains numerous improvements across the board from standard
library changes to pure performance enhancements as well as an expanded
ecosystem of packages as compared to the 0.2 releases. A summary of changes
is availab
Forgive me if this has been answered before; I couldn't find the answer.
I'm having fun with *IJulia Notebook*, and wanted to create a demo to show
how easy it is to speed up a loop by using the
julia> *@parallel (+) for . . .*
construction. In the past, I've launched plain julia from the comma
Whether you *like* the grammar is totally unrelated to whether there
is a formal spec for it. It's fine to dislike the special treatment of
`&` as a prefix operator. However this would not be fixed by
describing the behavior you dislike in some formal language.
You know, it's interesting: it's eas
OK I rebuilt julia and cleared my .julia folder, which seems to have cleared
that issue. Pkg.test(“GLPlot”) seems to work, though the output looks funny.
I also get the following:
julia> include("surface.jl")
INFO: loaded GLFW 3.0.4 Cocoa NSGL chdir menubar dynamic from
/Users/solver/.julia/
Huh. I must have mistyped something when I tried it last. It totally
works now. Nevermind then!
Júlio, if you want, you could specify the following in your REQUIRE file,
which should work:
julia 0.4.0-dev+23
But I personally think the chances of someone trying your file when using a
0.4.0-dev
How did you test it? On my system it seems to work: I can get Pkg to
upgrade a package if the REQUIRE file specifies julia 0.4.0-dev+274 but not
if it specifies julia 0.4.0-dev+275. (I'm on 0.4.0-dev+274.)
Simon
On Wednesday, August 20, 2014 4:29:36 PM UTC-4, Elliot Saba wrote:
>
> @Simon I jus
0.3- = 0.3.0- smallest version starting with 0.3.0
0.3 = 0.3.0
0.3+ = 0.3.0+ largest version starting with 0.3.0
On Wed, Aug 20, 2014 at 3:32 PM, Júlio Hoffimann
wrote:
> What do you recommend for my use case?
>
> Could you please clarify the meaning of all the following version numbers?
>
>
@Simon I just tried it out and on my machine at least, it didn't work. The
REQUIRE file doesn't honor the + symbol for some reason, so things like
0.3.0-rc4 work, but things like 0.4.0-dev+158 don't work. (They are
treated the same as 0.4.0-dev I believe)
-E
On Wed, Aug 20, 2014 at 3:32 PM, Júl
That would be my favorite, too. But you're right, it *is* a very hard
problem.
Am Mittwoch, 20. August 2014 19:11:27 UTC+2 schrieb Stefan Karpinski:
>
> There is actually one other approach that would work and produce a lot of
> side benefit: write a parser generator in Julia that uses the langu
What do you recommend for my use case?
Could you please clarify the meaning of all the following version numbers?
0.3-
0.3
0.3+
Thanks,
Júlio.
Raring went EOL in January; if you're stuck on it, you might be able to
switch over to a different package repository URL (see
http://askubuntu.com/questions/499712/is-distribution-of-raring-packages-officially-ended),
but you should seriously consider upgrading instead.
Note that the latest U
After running Julia on MacOS decided to give a try on my Linux machine (i7
Haswell running 13.04 raring).
sudo apt-get install julia
I got the following:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be insta
Soon you'll be able to use https://github.com/JuliaLang/julia/pull/6884
and everything can be much nicer :)
On Wednesday, August 20, 2014 11:52:38 AM UTC-4, Júlio Hoffimann wrote:
>
> Doesn't just adding Main in front solve the problem?
>>
>> view = Main.ImageView.view
>>
>> --Tim
>
>
> Thanks
Does it still not work to use 0.4.0-dev+n as the version in the REQUIRE
file? This used to almost work, but some of the nightlies were missing the
commit number. It certainly seems easier than searching through all the
hashes, although I don't know the git command to get the commit number for
a
On Wednesday, August 20, 2014 10:47:17 AM UTC-7, Sam L wrote:
>
> [...] replace `@test_throws Graph("http://not.an.URI.but.a.string";)` with
> `@test_throws MethodError Graph("http://not.an.URI.but.a.string";)` in
> your testing script, and the warning should disappear.
>
Doh! I guess I shou
The @test_throws macro wants you to specify the type of exception you
expect so that if some other exception is thrown, the test will not pass.
Assuming MethodError is the exception you expect to be thrown by Graph("
http://not.an.URI.but.a.string";), just replace `@test_throws Graph("
http://not
Hello,
My unit tests are working fine, but I see the following output in the
console:
WARNING: @test_throws without an exception type is deprecated
Use @test_throws MethodError Graph("http://not.an.URI.but.a.string";)
in backtrace at error.jl:30
in include_from_node1 at loa
That would only require storing ~2 sha1 hashes and search through, so it is
definitely computationally possible. If we limit the selection to all commits
since last tag, we will only have a few thousand.
The big question is whether anyone will actually use this functionality
correctly. Pack
For things like this, where we're currently in the midst of merging lots of
crazy changes, it's not uncommon to simply require 0.4.0-dev or later, and
expect users to have a version that is less than a few days old. Users who
want to use -dev versions should be aware that they will need to update
There is actually one other approach that would work and produce a lot of
side benefit: write a parser generator in Julia that uses the language's
JIT and metaprogramming capabilities to turn a formal grammar into a really
fast parser and then use that parser for Julia itself. Then you not only
get
No one is against the existence of a formal grammar – and anyone is free to
write one. Of course, for it to be really meaningful, you have to make sure
it stays in sync with Julia's actual parser. The only ways I can think of
to reliably make sure the parser and the grammar stay in sync is to (a)
m
Adam,
I was the originator of this thread, and in the end I conceded that the
current way that Julia handles immutable makes sense. Indeed, I authored a
paragraph about the definition of immutable composite types for the 0.4.0
version of the Julia manual in which I put Stefan's explanation da
It's currently not possible… and it's probably not computationally
practical: https://github.com/JuliaLang/julia/issues/7449#issuecomment-47558296
On Wednesday, August 20, 2014 12:45:31 PM UTC-4, Júlio Hoffimann wrote:
>
> Dear all,
>
> I want to register a package, but before doing it, could you
Rafael,
Thanks very much for taking the time to explain this. I agree that this is
a very nice technique that I will probably start using. I have expressed
the opinion in other threads that Julia could do more to enforce
type-correctness, and I see your functor proposal as a big step in the
Dear all,
I want to register a package, but before doing it, could you please guide
me on how to require a Julia build newer than a specific commit? (e.g.
https://github.com/JuliaLang/julia/pull/7917)
My *REQUIRE* file is here:
https://github.com/juliohm/ImageQuilting.jl/blob/master/REQUIRE
Best
Maybe there *are* drawbacks of ad-hoc parsers, after all. I don't want to
be offensive, really, I like Julia... but the absence of a formal
specification of the grammar is nothing to be proud of.
Am Dienstag, 19. August 2014 01:39:53 UTC+2 schrieb Stefan Karpinski:
>
> That seems likely.
>
> On
>
> Doesn't just adding Main in front solve the problem?
>
> view = Main.ImageView.view
>
> --Tim
Thanks Tim! It did the trick. The correct solution:
https://github.com/juliohm/ImageQuilting.jl/blob/master/src/imquilt.jl#L22-L28
It's not ideal, but it works. It would be much nicer if `using
On Wednesday, August 20, 2014 10:10:15 AM UTC-5, John Myles White wrote:
>
> Try typing the sequence \_1
>
Thanks.
Try typing the sequence \_1
— John
On Aug 20, 2014, at 8:08 AM, Douglas Bates wrote:
> I find it convenient to use identifiers like
>
> julia> a₁ = 2
> 2
>
> In the iESS emacs mode for a Julia session I can set the input-mode to TeX
> and type "a_1" to create this identifier. Is there a k
I find it convenient to use identifiers like
julia> a₁ = 2
2
In the iESS emacs mode for a Julia session I can set the input-mode to TeX
and type "a_1" to create this identifier. Is there a key sequence in the
REPL to create such an identifier?
Let’s see my suggestion actually helps. If it does, then you should thank me. :)
— John
On Aug 20, 2014, at 7:37 AM, Thomas Covert wrote:
> sorry if I was unclear - what I meant to say is that a single call to the
> objective function and its gradients represents considerably more
> computat
On Tuesday, August 19, 2014 8:04:29 AM UTC-4, Ning Yin wrote:
> I was trying to convert an array of char's to string, and I've noticed
> functions such as string or CharString, but non of these seem to work for
> my case:
>
> Julia console:
> ==
> julia> a = ['a', 'b', 'c']
>
Char
>
> 'Traditional' Julia: you can pass a function f as an argument to another
> function g.
>
> Rafael's functors: instead you create new type F whose constructor is f,
> and then you make g a parametric function with a parameter F instead of an
> argument f.
>
A typo here, the constructor of type
Hi,
Can I use the IP instead of the hostname to launch a process on a remote
machine at the 'machinefile' file ? I mean, if I put in a machinefile.txt
file, the line:
xxx.xxx.xxx.xxx
and try to start a process with
julia --machinefile machinefile.txt
I get an error: "Master process (id 1) co
sorry if I was unclear - what I meant to say is that a single call to the
objective function and its gradients represents considerably more
computational work than what goes in inside the optimizer.
I will see if L-BFGS does a better job later today. Thanks for your help.
-thom
On Wednesday,
It seems odd that your objective function takes less time than the optimization
routine itself, unless you include the calls to your objective function in the
cost of the optimization routine. The optimization routine does very little
work: most of the line search’s cost is induced by repeatedly
My (current) objective function has about 30 parameters, so N^2 complexity
isn't a problem (storage-wise or matrix multiplication time wise). Also,
for my current work, the objective function is much slower than the
optimization routine itself, so the overhead of a full inverse Hessian is
rela
I don’t think I’m going to have time to look into this soon, but why do you use
BFGS? In my experience L-BFGS is almost always better.
Of course, we want our BFGS code to be better. But I use BFGS only quite rarely
because of its O(N^2) complexity.
— John
On Aug 20, 2014, at 7:16 AM, Thomas C
Ok after reading the paper which the hz_linesearch! routine is based on, I
can see that I'm wrong about this. Still puzzled, but definitely wrong!
On Tuesday, August 19, 2014 1:51:37 PM UTC-5, Thomas Covert wrote:
>
> I'm seeing this same error (ERROR: assertion failed: lsr.slope[ib] < 0)
> aga
Copying things by default isn’t a very good strategy for a language used to do
linear algebra on large arrays.
Requiring that people use Ref to get reasonable performance for linear algebra
operations would make Julia feel like a much more low-level language than it is
currenty.
— John
On Au
Frankly current Julia semantics is pretty confusing and IMHO inflexible at
least for me as a programmer and scientists at once using C++ everyday. Why
not have by-value as default behavior for types and Ref{...} turns by-val
type to reference type? E.g.:
type Point
x; y
end
rotate!(p::Ref{Poi
Hi Tim, yes, I do know about Ctrl-R, but it is much lazier to use the
up/down arrows, particularly when navigating history (otherwise you have to
use Ctrl-R repeatedly, and Ctrl-Shift-R to go back).
El miércoles, 20 de agosto de 2014 00:39:33 UTC+2, Tim Holy escribió:
>
> You know about the Ctrl
You might need a Pkg.update(), or Pkg.build("Images") if the update doesn't
solve it.
--Tim
On Wednesday, August 20, 2014 09:23:16 PM Sheehan Olver wrote:
> OK Now I get
>
> could not open file
> /Users/solver/.julia/v0.3/Images/src/ioformats/../../deps/deps.jl while
> loading /Users/solver/.ju
Hm, well I'm neither used to OSX nor the building of Images.jl, but this
still looks like a problem with Images.jl not having the right binaries.
Did you do Pkg.build() ?
Also it might be, that you have to install the binaries manually.
For OSX, I can't give you more informations than given on
ht
OK Now I get
could not open file
/Users/solver/.julia/v0.3/Images/src/ioformats/../../deps/deps.jl
while loading /Users/solver/.julia/v0.3/Images/src/ioformats/libmagickwand.jl,
in expression starting on line 24
while loading /Users/solver/.julia/v0.3/Images/src/Images.jl, in expression
startin
Yes I do =)
You need to install Images.jl properly with its dependency.
https://github.com/timholy/Images.jl
I should at some point load this conditional, as you don't really need
Images.jl as long as you don't read images from your HD.
2014-08-20 13:01 GMT+02:00 Sheehan Olver :
> OK I cloned al
OK I cloned all the necessary projects but get the following error on OS X, and
thoughts?
julia> include("surface.jl")
ERROR: error compiling Texture: error compiling __Texture#30__: error compiling
imread: error compiling imread: error compiling MagickWand: could not load
module : dlopen(.dyli
In theory it does support 2D plotting, but I didn't invest much work into
it, as 3D is my main focus.
In other words:
There's nothing working out of the box, but if you are willing to invest
some work, there are already a lot of tools to make 2D plotting possible
and I would be willing to suppor
Cool!! Definitely will give it a try. The reason I settled on PyPlot was its
support for 3D. But its slowness is slowly driving me insane.
Does it do 2D plotting as well, or should I use another package for that?
Sheehan
On 20 Aug 2014, at 7:43 pm, Simon Danisch wrote:
> Depending on wha
Depending on what you want to plot, you can also try to use GLPlot:
https://github.com/SimonDanisch/GLPlot.jl/wiki
Its in its early stage, so things might not work as easily as expected, or
you might miss functionality.
In both cases, I'm eager to help, to improve the package ;)
Best,
Simon
Am
Doesn't just adding Main in front solve the problem?
view = Main.ImageView.view
--Tim
On Tuesday, August 19, 2014 07:45:04 PM Miles Lubin wrote:
> This may do what you want (snippet from JuMP):
>
> if isdir(Pkg.dir("ArrayViews"))
> eval(Expr(:import,:ArrayViews))
> const subarr = Ar
75 matches
Mail list logo