[julia-users] Why was a fundamental indexing inconsistency introduced in 0.5?

The change to indexing within matrices in 0.5.0 is fundamentally counterintuitive. For example: julia> frame32 = randn(16,7); julia> size(frame32[1,:]) (7,) julia> size(frame32[1:1,:]) (1,7) To be quite blunt, I think this is a terrible contradiction. It completely breaks the repmat syntax

Re: [julia-users] Reading from a TCP socket with quasi-continuous data transfer

On Wednesday, June 1, 2016 at 5:36:44 AM UTC-7, Isaiah wrote: > > > Yes: using multiprocess parallelism instead of tasks. '@everywhere' > executes code on other processes that do not share the same address space > as the head process and cannot access the same socket. See the section on > Tasks

Re: [julia-users] Reading from a TCP socket with quasi-continuous data transfer

> > >>1. I've read (here and elsewhere) that Julia does an implicit block >>while waiting for data. Is there a workaround? >> >> Do the blocking read asynchronously in a task. For network I/O (but not > file), `read` will only block at the task level. To end the read, `close` > the

[julia-users] Parallel read and preprocess variable-length data files

I'm looking for pointers on the best practice for parallel reading and preprocessing several files of variable-length time series data. I have little familiarity with parallelization, so it feels like I'm missing something obvious. I've read the Julia documentation and tried several approaches

[julia-users] Reading from a TCP socket with quasi-continuous data transfer

Hi, First post to the group, but I've been coding in Julia for about a year now. I'm working on a native Julia client for real-time access to geophysical data via. SeedLink. However, it seems like I need a way to interrupt blocking