RE: [julia-users] Can't add PostgreSQL

I got it working before your update. Yay! Thank you! There were a couple of issues, mostly documentation, leaving aside getting ODBC setup outside of julia. The docs (the help at https://github.com/JuliaDB/ODBC.jl) say to use DSN to get things going. As far as I can tell, it doesn't exist.

Re: [julia-users] Can't add PostgreSQL

Hey Ross, Just confirmed that connecting to Postgres does indeed work; haven't seen any issues yet. I'm using the PostgreSQL ODBC Driver from their website with unixODBC on a mac. I'm using a connection string I built by following the guidelines here:

[julia-users] Re: Newbie question. Need help with grouping dataframes, cumulative sums and plotting.

Something like using RDatasets df = dataset("datasets", "iris") df[:cumulative_PetalLength] = 0.0 by(df, :Species) do sub_df sub_df[:cumulative_PetalLength] = cumsum(sub_df[:PetalLength]) sub_df end though I hope someone can provide a more elegant solution. `sub_df` a SubDataFrame, and

RE: [julia-users] Can't add PostgreSQL

Attempting to post comments inline, even though my mailer is allergic. Look for >> From: karbar...@gmail.com [karbar...@gmail.com] on behalf of Jacob Quinn [quinn.jac...@gmail.com] Sent: Tuesday, May 03, 2016 5:47 PM I'm not sure I understand: I don't see DBI.jl nor PostgreSQL.jl at

RE: [julia-users] Can't add PostgreSQL

I'm not sure I understand: I don't see DBI.jl nor PostgreSQL.jl at pkg.julialang.org, which tells me they aren't officially registered as packages. The difficulties you're seeing then aren't that surprising because they haven't felt comfortable enough to officially register. ODBC actually works

Re: [julia-users] [ANN] Major Breaking Release/Overhaul for ODBC.jl

Amazing work, Jacob. On Tue, May 3, 2016 at 5:15 PM, Jacob Quinn wrote: > Hey everyone, > > A new release is imminent for the ODBC.jl > package (will be released later > today). As a quick history: > > >- ODBC.jl was the first

RE: [julia-users] Can't add PostgreSQL

That's odd. After cloning the Postgres package, and then executing the script from the command line, it gets further: $ julia trouble.jl ERROR: LoadError: DBI API not fully implemented in fetchdf at /home/ross/.julia/v0.4/DBI/src/DBI.jl:97 in include at ./boot.jl:261 in include_from_node1 at

RE: [julia-users] Can't add PostgreSQL

Thank you, Jacob, for the pointer. I'm further along but still not there. I did the clone and then build. I'm not sure if the build was necessary, but it took awhile. This process did not install DBI although it's listed as a requirement, and the installer gave no warning about it. When

Re: [julia-users] Can't add PostgreSQL

I don't think the PostgreSQL.jl package was ever officially registered. You could try Pkg.clone("https://github.com/JuliaDB/PostgreSQL.jl;) to manually download/install it; you may need to do Pkg.build("PostgreSQL") as well after cloning. Alternatively, you might try the latest master of

[julia-users] Can't add PostgreSQL

Am I misunderstanding how things work? Is the package only available for julia 0.3? I have a julia obtained via git a few days ago, on the release-0.4 branch and built locally. Seeing https://github.com/JuliaDB/PostgreSQL.jl I tried, from within an ESS session, julia> Pkg.add("PostgreSQL")

[julia-users] Re: Venturebeat 11/2015: Open-source DL Frameworks? Take your pick

The right link http://venturebeat.com/2015/11/14/deep-learning-frameworks/ On Tuesday, May 3, 2016 at 6:44:13 PM UTC-3, Kevin Liu wrote: > > > http://venturebeat.com/2016/05/03/microsoft-launches-new-website-for-developer-documentation-with-user-friendly-urls-estimated-reading-time/ > > Would

[julia-users] Re: Venturebeat 11/2015: Open-source DL Frameworks? Take your pick

Google moves to TF http://googleresearch.blogspot.com.br/2016/04/deepmind-moves-to-tensorflow.html Would like for Julia to be the World's research-to-mass-scale engine. On Tuesday, May 3, 2016 at 6:44:13 PM UTC-3, Kevin Liu wrote: > > >

[julia-users] Venturebeat 11/2015: Open-source DL Frameworks? Take your pick

http://venturebeat.com/2016/05/03/microsoft-launches-new-website-for-developer-documentation-with-user-friendly-urls-estimated-reading-time/ Would like to see Julia here! Kevin

[julia-users] [ANN] Major Breaking Release/Overhaul for ODBC.jl

Hey everyone, A new release is imminent for the ODBC.jl package (will be released later today). As a quick history: - ODBC.jl was the first package I ever worked on with Julia (indeed, the first commit is from January 2013) - A lot of refinements

[julia-users] Newbie question. Need help with grouping dataframes, cumulative sums and plotting.

I have the following dataframe with values of the form date1,label1,qty1_1 date2,label1,qty1_2 date3,label1,qty1_3 dateN,label1,qty1_N date1,label2,qty2_1 date2,label2,qty2_2 date3,label2,qty2_3 dateN,label2,qty1_N I would like to cumulative sum the qtys such that the value of

Re: [julia-users] promotion and conversion

I ran into the same confusion the first time I tried following that section. Maybe adding something like "In most cases, you must ``import Base: convert`` or explicitly extend ``Base.convert``." to that section of the docs would help. Probably similar language should be added to promote_rule

Re: [julia-users] promotion and conversion

Hi Arda, As Stefan sad, you need import those Base functions or use Base.convert and Base.promote_rule to add a new method to them. You may notice in repl that if you do not import them after typing those methods you have only 1 methods for each of those functions.

Re: [julia-users] promotion and conversion

Did you import the convert and promote_rule functions? On Tue, May 3, 2016 at 12:21 PM, Arda Aytekin wrote: > Hey, > > I am sorry if this question is either irrelevant or stupid, but I am > having problems figuring out the type promotion and conversions. > Could you

[julia-users] promotion and conversion

Hey, I am sorry if this question is either irrelevant or stupid, but I am having problems figuring out the type promotion and conversions. Could you please explain to me why the below code excerpt is not giving me what I want it to return: abstract A; immutable A1 <: A num::Float64 end;

Re: [julia-users] Re: Compose.jl drawing in IJulia

Yes, you can use draw for that draw(SVG(10inch, 10inch), ...your compose context here...) you can also change SVG to PNG in IJulia - recommended if there are too many objects in the image On Tue, May 3, 2016 at 10:28 PM, Christoph Ortner < christophortn...@gmail.com> wrote: > Thank you - can I

Re: [julia-users] Re: Compose.jl drawing in IJulia

Thank you - can I also specify the dimensions of the image on a case by case basis? Christoph On Tuesday, 3 May 2016 15:43:41 UTC+1, Shashi Gowda wrote: > > The diameter of a circle without a specified radius is taken to be the > width of the context iirc. The default width of the drawing

[julia-users] Re: main function error

Not for me: julia> function main(M,N) d_cleftvector=115e-7; cv_matrix=zeros(length(d_cleftvector),1); signal_matrix=zeros(length(d_cleftvector),1); num_cleft=0; for d_cleft=d_cleftvector d_cleft

Re: [julia-users] main function error

Do you call main in one of the included file? On Tue, May 3, 2016 at 11:54 AM, new to Julia wrote: > Hi all: I run the following code in Julia: > > include("rec_LRd.jl") > include("constants_2D.jl") > > function main(M,N) > > d_cleftvector=115e-7; > >

[julia-users] main function error

Hi all: I run the following code in Julia: include("rec_LRd.jl") include("constants_2D.jl") function main(M,N) d_cleftvector=115e-7; cv_matrix=zeros(length(d_cleftvector),1); signal_matrix=zeros(length(d_cleftvector),1); num_cleft=0; for d_cleft=d_cleftvector d_cleft

Re: [julia-users] sparse function

You could consider putting the code in a Github gist and posting the link: https://gist.github.com/ On Tue, May 3, 2016 at 11:29 AM, new to Julia wrote: > I use mail file to call a different file, which using sparse function. It > is a long code, what part do you expect

[julia-users] Re: sparse function

On Monday, May 2, 2016 at 11:47:49 PM UTC-4, new to Julia wrote: > > when I use sparse function in Julia coding, I have the following error: > > LoadError: MethodError: `sparse` has no method matching > sparse(::Array{Float64,1}, ::Array{Float64,1}, ::Array{Float64,1}, ::Int64, > ::Int64,

Re: [julia-users] sparse function

I use mail file to call a different file, which using sparse function. It is a long code, what part do you expect to put here? On Tuesday, May 3, 2016 at 12:36:33 AM UTC-5, Patrick Kofod Mogensen wrote: > > Can you try to show a small script that reproduces the error? > > On Tuesday, May 3,

Re: [julia-users] Re: Compose.jl drawing in IJulia

The diameter of a circle without a specified radius is taken to be the width of the context iirc. The default width of the drawing surface is greater than its height, resulting in the clipping of some part of the circle. Making the drawing surface a square will show it properly. You can do this

[julia-users] Re: ANN: Optim.jl v0.4.5 released

Thank you guys. That makes perfect sense :+1:

[julia-users] Re: Compose.jl drawing in IJulia

Here is an Python output here is the PNG file:

[julia-users] Re: ANN: Optim.jl v0.4.5 released

What Kristoffer and Miles said, but specifically all algorithm constructors accept a linesearch! keyword, and in the case of ConjugateGradient we have (see https://github.com/JuliaOpt/Optim.jl/blob/1cf3fbe053edeb8a388ff0d03af75386ad2e3457/src/cg.jl#L106 ) immutable ConjugateGradient{T} <:

[julia-users] Re: ANN: Optim.jl v0.4.5 released

Yes, the motivation was to allow passing options specific to the BFGS algorithm by using BFGS(foo=bar). On Tuesday, May 3, 2016 at 6:27:42 AM UTC-4, Kristoffer Carlsson wrote: > > Dispatching on Type{xx} is quite inconvenient and loocks the API a lot. By > using an instance you still have the

[julia-users] Re: Compose.jl drawing in IJulia

Hello colleague, how did you set the correct dimensions? On Tuesday, May 3, 2016 at 10:53:59 AM UTC+2, Christoph Ortner wrote: > > If I create a context using `compose`, and then call `display(ctx)`, then > I end up with an image that looks roughly right but doesn't have the > correct

[julia-users] Re: What are the best ways to define scenarios?

I have heard good things about Parameters.jl , which lets you make types representing individual models or scenarios that have default values. You would want to do something like using Parameters @with_kw immutable Scenario par1::Float64 =

Re: [julia-users] Why does the warning go away? (Or: my first Julia WAT)

> > > I am not sure what the question is about {}. It has been deprecated so > that it can be freed for new syntax. See > https://github.com/JuliaLang/julia/pull/10380 > > Best, > > Tamas I was contrasting the behavior of the warning system, which "gave up" after three warnings in the

[julia-users] Re: ANN: Optim.jl v0.4.5 released

Dispatching on Type{xx} is quite inconvenient and loocks the API a lot. By using an instance you still have the option to add fields to the type and to use different types that dispatch to the same function.

[julia-users] Re: ANN: Optim.jl v0.4.5 released

This sounds great and your changes with the API and dispatch are reassuring because I recently implemented something similar (for a totally unrelated package). A general question... You wrote optimize(df, x0, BFGS()) I'm curious why you didn't make this optimize(df, x0, BFGS) Is there any

[julia-users] TensorSpace in ApproxFun

Hello, I am confused by `ApproxFun.TensorSpace`. I understand the following. dom1, dom2 = Fourier(), Chebyshev() dom = dom1 ⊗ dom2 @assert TensorSpace(Fourier(), Chebyshev()) == dom1 ⊗ dom2 d1, d2 = Derivative(dom1), Derivative(dom2) @assert Derivative(dom1, 1) == Derivative(dom1) Here are the

[julia-users] Compose.jl drawing in IJulia

If I create a context using `compose`, and then call `display(ctx)`, then I end up with an image that looks roughly right but doesn't have the correct dimensions. How can I fix it? Thanks, Christoph

[julia-users] ANN: Optim.jl v0.4.5 released

The contributors are happy to announce, that Optim.jl version 0.4.5 has now been released. This is the last patch before the next minor version bump to v0.5.0. The next release will remove deprecations introduced in this patch, and will also include breaking changes to the API. This patch