-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MethodError: start
has no method matching start(::Type{Int64})
#25
Comments
Got the same... |
Have you run |
Wop, actually error solved after |
What do you get from |
Here we are:
|
...and |
The whole list is:
|
I'm trying to use it, to see how it runs. So far almost so good (almost): julia> dzeros((100,100), workers()[1:4], [1,4])
ERROR: MethodError: `dzeros` has no method matching dzeros(::Tuple{Int64,Int64}, ::Array{Int64,1}, ::Array{Int64,1})
Closest candidates are:
dzeros{T}(::Type{T}, ::Tuple{Vararg{Int64}}, ::Any...)
dzeros(::Tuple{Vararg{Int64}}) |
Try dzeros(Float64, (100,100), workers()[1:4], [1,4]) It has just been changed, but I think we should default to |
Runs smoothly. |
By the side, I'm discovering a = zeros(100000)
@parallel for i=1:100000
a[i] = i
end and being informed that P.S. Sorry for the off topic, if there is a better place to discuss this please let me know. |
I think questions like these fits well on the Julia-users list, but see my reply below anyway. I think it depends on what you are calculating. If you are running a heavy simulation that you'd like to execute in parallel, while the result can just be processed on the master process, I'd just use something like @parallel (vcat) for i = 1:100000
1+2+3+i
end or collect the simulation in a function, say r = pmap(simfun, 1:100000) In other cases a julia> A = drandn((10,10,5000), workers(), [1,1,4]);
julia> mapslices(inv, A, (1,2)); to invert each of the 5000 10x10 matrices in the array. |
👍 Thanks, the |
@gvdr I added the missing defaults for |
Any idea when the fix will appear in stable? |
This package is currently only works for 0.4-dev, so I don't think it makes sense to tag a new release until 0.4 is released. |
The error below is probably due to a very recent change; it didn't happen with
0.4.0-dev+4294
(commit b7d7955):The text was updated successfully, but these errors were encountered: