So let's say I have a function of the form:
function f(x::Bool)
for i in 1:1000
*(bunch of stuff)*
if x
do something
end
*(even more stuff)*
end
As you can see I only need to evaluate this if statement once, but instead
I'm (in theory) evaluating it millions of
h the if and one
>> without. Then you can @time the results and see if it makes a
>>
>
> Which is generally bad except for synthetic benchmarks except for rare
> cases.
>
>
>> difference.
>>
>>
>> On Tuesday, August 2, 2016 at 5:29:41 AM UTC
Ok great! Thanks Kenta and Lyndon for your quick responses!
On Tuesday, July 5, 2016 at 4:23:47 AM UTC-7, Lyndon White wrote:
>
> You can use the `names` function to search a module for all constants it
> defines.
> By evaluating the names to get the values, then checking if they are
>
cially with the documentation! Have you benchmarked
> it against other implementations?
>
> On Saturday, July 2, 2016 at 12:32:13 AM UTC-4, esproff wrote:
>>
>> Hi all!
>>
>> So I have just released a new variational Bayes topic modeling package
>> for Julia, which can be
has an implementation of LDA.
>
> Cheers,
>Kevin
>
> On Saturday, July 2, 2016, esproff <esp...@gmail.com > wrote:
>
>> thanks!
>>
>> So I know there is a Java implementation of LDA (MALLET Pkg), which I
>> believe uses collapsed Gibbs sampling,
Hi all!
So I have just released a new variational Bayes topic modeling package for
Julia, which can be found here:
https://github.com/esproff/TopicModelsVB.jl
The models included are:
1.
Latent Dirichlet Allocation (LDA)
2.
Filtered Latent Dirichlet Allocation (fLDA
Hi all!
So I have just released a new variational Bayes topic modeling package for
Julia, which can be found here:
https://github.com/esproff/TopicModelsVB.jl
The models included are:
1.
Latent Dirichlet Allocation (LDA)
2.
Filtered Latent Dirichlet Allocation (fLDA
I'm trying to run Pkg.publish(), however when it asks for my GitHub host
password I enter it (although nothing shows up when I type), and then I hit
return and I get:
Error 401: Bad credentials
Does anyone know how to fix this?
; format is pretty general allows a ton of flexibility. If there's something
> about the design that you see not working for this, it's better to help
> them fix their design than to attempt to double up efforts and (most
> likely) not get more optimized algorithms.
>
> On Monday, September
I'd be interested in getting involved in this, I've been writing up some
portfolio optimization and visualization routines in Julia with the help of
Convex.jl and Gadfly.jl, this could possibly eventually be merged into
Ito.jl or QuantLib.jl or w/e we decide is the official Julia quant finance
Ok Chris I'll definitely check out Plots.jl.
As for optimization packages, more than one will probably have to be used
depending on the problem: disciplined convex vs numerical vs global vs etc.
And, as always, some optimization algorithms will have to be custom rolled
out since established
Consider the code:
abstract AbstractFoo
type Foo <: AbstractFoo
end
f(x::AbstractFoo, y::Integer) = "method 1"
f(x::Foo, y::Real) = "method 2"
foo = Foo()
f(foo, 1)
This code results in an ambiguity error, since both methods contain one
argument with a more specific type declaration than the
12 matches
Mail list logo
