In ijulia, I tried to run the benchmark fileincluded in the source code
(~/julia/test/perf/micro/perf.jl):
*include("perf.jl")*
Why is that it dose not print out the results in ijulia while it works fine
in Julia itself?
thx!
Julia is somewhere between the first and the second quartile (closer to the
first), almost stationary since July, and up from below the first quartile,
a year ago (higher being better).
The bottom-left half of the chart is very noisy and volatile, though, so
the tiny progression since last summ
is this why I get this on latest julia studio on mac with recently updated
packages:
julia> using DataFrames
julia> using RDatasets
julia> iris = data("datasets", "iris")
data not defined
??
Hello,
I am new to Julia. I am coming from the background of Matlab. I would like
to get a list of current variables in Julia. In Matlab, when pressing whos
command,I get all
variables. Is there such commands in Julia?
julia> whos()
A 5x5 Array{Float64,2}
Base Module
Core Module
Main Module
ans 5x5 Array{Float64,2}
subl Function
On Thu, Jan 23, 2014 at 1:54 AM
Pandas has a 'query' method
(http://pandas.pydata.org/pandas-docs/dev/indexing.html#indexing-query) which
uses the Python numexpr package for delayed evaluation (if i understand what
you mean by that in this context).
Yeah, at some point in the future I’d like to see if we can imitate the
experimental query() and eval() methods from Pandas.
It’s the fact that those methods were just recently introduced which made me
decide we needed to stop spending time on getting them working right now. We’re
way behind Pa
I think that’s probably because you need to do using DataArrays now.
— John
On Jan 23, 2014, at 2:08 AM, Jon Norberg wrote:
> is this why I get this on latest julia studio on mac with recently updated
> packages:
>
> julia> using DataFrames
> julia> using RDatasets
> julia> iris = data("data
I'm using ODBC and DataFrames to query a database and just started getting
this error on a query return:
df = query("select * from tb1")
ERROR: no method display(DataFrame)
in display at multimedia.jl:159
df is populated correctly, but the error halts the running of my code.
Pointing a new D
Since you’re hitting display errors I think this is a bug in DataFrames.jl. But
I’m not totally sure. It would be super helpful if you could find an error case
that doesn’t depend on ODBC.
— John
On Jan 23, 2014, at 8:22 AM, bp2012 wrote:
> I'm using ODBC and DataFrames to query a database a
Hello,
I've been wondering what, if any kinds of checks or warnings Julia gives at
compile time, or if there are any packages that can type check and give you
warnings on your code.
Thank you
Sounds like this also might be a version issue. Can you confirm what
versions of Julia, DataFrames, and ODBC you're using? And just for kicks,
what frontend are you using? (e.g. IJulia, terminal, etc)
On Thu, Jan 23, 2014 at 11:24 AM, John Myles White wrote:
> Since you’re hitting display e
There are none at the moment, but Leah Hanson is working on a tool along
these lines.
On Thu, Jan 23, 2014 at 12:16 PM, William Beard wrote:
> Hello,
>
> I've been wondering what, if any kinds of checks or warnings Julia gives
> at compile time, or if there are any packages that can type check
On Wednesday, 22 January 2014 02:17:36 UTC+1, Ivan Tong wrote:
>
> I think the greedy solution is both behaviors? =D
>
>>
Although I get the idea of "let's try to please everyone", I think that it
will just lead to confusion and hard to find bugs in this particular case.
I get the following error when trying to build Julia. This is with the
latest version of master, 64-bit Windows, following the directions under
"Building on Windows with MinGW-builds/MSYS". Any ideas?
Adam@Adam-HP ~/julia
$ make
...
CC ui/repl.o
repl.c: In function 'parse_opts':
repl.c:5
To check Jacob's suggestion about versions mismatch I completely removed
the DataFrames and ODBC packages using Pkg.rm and physically deleted the
directories from disk. I then added them via Pkg.add and Pkg,update.
I am running the julia nightlies build.
julia> versioninfo()
Julia Version 0.3.
Hi
I followed suggestions and looked up help and searched for earlier similar
problem. Found few and tried those out.
For example I set PYTHONPATH and PYTHONHOME variables (Python 2.7 is
running because my path in windows was set to the bin for python).
Then I restarted Julia but I am getting sa
I do not think you are alone. See:
https://github.com/JuliaLang/julia/pull/5423#discussion_r9100469
If you checkout d3c6b5b8a998c602d7143e2fc20833f4d37f9185, you should be
fine until this gets fixed.
Ivar
kl. 21:12:11 UTC+1 torsdag 23. januar 2014 skrev Adam Kapor følgende:
>
> I get the follo
Any update on this? Having similar problems on Windows 7 with a fresh
install just this morning.
Seems to be related to some renaming of Stats vs. StatsBase? I've tried
fiddling with this myself within the packages, but haven't been able to
resolve it.
Thanks in advance for all your help, and
Great investigative work. Is
DataFrames( array_of_arrays, Index(column_names_array) )
not the right way to hand construct DataFrames any more? I think I can
allocate DataArrays instead, but at every step of the way, I was trying to
hand-optimize the result fetching process, which resulted in not cr
Some weeks ago I tried to implement a new type in Julia which should
basically behave like a subtype to an already existing type. Since Julia
does not allow any subtypes of composite types, I wondered about a simple
way to implement this. However, at that time I was not at all aware of all
the
That works, but columns will be Arrays instead of DataArrays. That's
the way it's always worked. If you want them to be DataArrays, then
convert to DataArrays right at the end.
To fix show to support columns that are arrays, we probably need (at
least) to define the following:
countna(da::Array)
Similar problem is a quite weak description.
The previous problem was that a new version of a pakcage
(NumericExtensions) was incorrectly marked as compatible with 0.2. This
does not appear to be fixed, so a bump on Dahua Lin and John Myles White
might be what is needed.
kl. 21:32:14 UTC+1 tor
Thanks Ivar. My incomplete description (which you have somewhat offensively
labeled as "weak") was intentionally so, to avoid hijacking the thread with
my own problem. With your encouragement, however, here is the problem I'm
having, which I suspect is related to the OP's problem: I installed v0
I am sorry that you found my use of the word "weak" offensive. It was
definitely not my intention. I can see that it was a poorly chosen word, and
you might have strong feelings connected to some words. When I think more about
it "brief" might have been the word I was looking for. As English is
It's mentioned here http://julialang.org/blog/2012/02/why-we-created-julia/
that Mathematica was one of the programs that inspired Julia. How does
Julia compare to Mathematica's language?
To make the question more specific,
- it's about languages, not implementations, so Mathematica's FrontEnd
On Thursday, January 23, 2014 3:30:00 PM UTC-5, Rajn wrote:
>
> I will appreciate some help here. And also I have only one python
> installation which is the Enthought edition.
> Also a related question, if I change something in *.jl such as what I
> changed above, I read that I have do reverse g
Run the following:
$ sudo add-apt-repository ppa:staticfloat/julia-deps
$ sudo apt-get update
$ sudo apt-get install julia
The additional repo contains Julia dependencies for Ubuntu 12.04 (found
here: https://launchpad.net/~staticfloat/+archive/julia-deps/)
$ sudo add-apt-repository ppa:stati
Hi Chris,
Unfortunately it’s very difficult for us to support 0.2 anymore because of the
badly breaking Stats -> StatsBase renaming. We’d have to rewrite the history of
every repo to resolve this name change, so we chose to instead push everything
up to our current development branches. That ch
I installed wolfram on my raspberry pi.
Mostly to play with free-form linguistics but I couldn't get it to work.
I considred D, Julia and Wolfram for a raspberry pi project.
But D(dmd) and Julia is not in the apt-get archve for raspberry pi
and wolfram is behind a paywall on other platforms.
Actually, now that I think back on it, that was a silly suggestion.
Question... Anyone want automatic promotion when using type annotations?
Honest question. It seems like people have only asked to _not_ have the
automatic promotion behavior (for Float32). Likewise, I can imagine anyone
wor
A couple of points that expand on Tom’s comments:
(1) We need to add Tom’s definition of countna(a::Array) = 0 to show() wide
DataFrame’s that contain any columns that are Vector’s. I never use DataFrame’s
like that, so I forgot that others might. It’s also impossible to produce such
a DataFram
OK, thanks John and Ivar. I'll probably put in some effort towards building
it myself, and wait for 0.3 binaries.
Thanks for the help,
Chris
On Thursday, January 23, 2014 5:35:16 PM UTC-8, John Myles White wrote:
>
> Hi Chris,
>
> Unfortunately it’s very difficult for us to support 0.2 anymor
We should hopefully have nightly binaries sometime soon that will help
alleviate some of these issues in the future. I’ve lost track of the work to
provide them, but I know it’s being done.
— John
On Jan 23, 2014, at 6:02 PM, Cgast wrote:
> OK, thanks John and Ivar. I'll probably put in some
I think of item #3 as a feature, not a bug. I don't like the idea of
auto-conversion. If I choose Vectors, I should not expect them to
support missing values. R sometimes irritates me by adding NA's when I
don't expect it. I'd rather have the error than have NA's sneak in
there. Also, there may be
Thanks! I'm trying out a SharedArray solution now, but wondered if you can
tell me if there's an easy way to reimplement many of the convenience
wrappers on arrays for shared arrays. Eg I get the following errors:
>> shared_array[1,:]
no method getindex(SharedArray{Float64,2}, Float64, Range1{In
even more problematic: I can't multiply by my SharedArray:
no method *(SharedArray{Float64,2}, Array{Float64,2})
On Thursday, January 23, 2014 7:22:59 PM UTC-8, Madeleine Udell wrote:
>
> Thanks! I'm trying out a SharedArray solution now, but wondered if you can
> tell me if there's an easy way
I would be a lot happier with that feature if we followed the lead of
traditional databases and constantly reminded users which columns are “NOT
NULL”. As it stands, the “types” of a DataFrame don’t tell you whether a column
could contain NA’s or not. If we exposed functionality through somethin
I'd think of #3 as a feature, too.
Just to throw another use case in the ring, if DataFrames with a mix of
Vectors and DataVectors (with NAs) were performant, my co-workers and I
would usually pull in data marking all columns as Vectors, these columns
would remain Vectors, and derived columns w
Sounds reasonable. As a temporary measure for people who want that
functionality immediately, I've taken a stab at wrapping pandas in a Julia
package (just as pyplot does for matplotlib),
at https://github.com/malmaud/pandas.
On Thursday, January 23, 2014 10:17:40 AM UTC-5, John Myles White wr
Just saw that. Seems like a very smart way to get us important functionality
while we continue to push things forward. Would be very cool if we could make
it possible to switch between the Pandas and native Julia implementations
totally seamlessly.
— John
On Jan 23, 2014, at 7:51 PM, Jonathan
Ok. I’m coming around to this.
How would you do I/O? If we make DataFrames expose a nullable property, we
could plausibly produce vectors instead of data vectors when parsing CSV files.
— John
On Jan 23, 2014, at 7:38 PM, Sean Garborg wrote:
> I'd think of #3 as a feature, too.
>
> Just to
My first thought was a Vector{Bool}.
On Thursday, January 23, 2014 10:05:25 PM UTC-6, John Myles White wrote:
>
> Ok. I’m coming around to this.
>
> How would you do I/O? If we make DataFrames expose a nullable property, we
> could plausibly produce vectors instead of data vectors when parsing CS
Julia and Mathematica are very, very different languages.
Mathematica's underlying model is heavily based on pattern matching and
term rewriting. Most function definitions in Mathematica should really be
thought of as replacement rules
> f[x_] := Sin[x^2]
means "replace any expression with t
Yeah, that seems totally reasonable to me. If we do this in a more formal way,
I’m now onboard.
Let’s add the idea of explicit restrictions on columns that can and can’t
contain NA’s to the spec: https://github.com/JuliaStats/DataFrames.jl/issues/502
— John
On Jan 23, 2014, at 8:21 PM, Sean G
The SharedArray object ha a field loc_shmarr which represents the backing
array. So S.loc_shmarr should work everywhere. But you are right, we need
to ensure that the SharedArray can be used just as a regular array.
On Fri, Jan 24, 2014 at 9:00 AM, Madeleine Udell
wrote:
> even more problematic:
46 matches
Mail list logo
