Sorry, how should I convert that into a viewable diagram.
Thanks!
> On Apr 1, 2020, at 11:17 PM, Hauke Rehr wrote:
>
> Actually, I’m a little bit confused as well:
> I thought I understood it but obviously didn’t
> so I tried redoing the diagram but with one
> set of arrows altered.
> Am I rig
Actually, I’m a little bit confused as well:
I thought I understood it but obviously didn’t
so I tried redoing the diagram but with one
set of arrows altered.
Am I right these should be different or do I
misinterprete the way atop is meant to work?
thanks
Am 29.03.20 um 03:36 schrieb ethiejiesa
Brian Schott wrote:
> All,
> I think Bill's solution works for my question: dbover'' (13!:20).
> In contrast to Gilles, I think dbinto'' (13!:21) works as designed, because
> changing the value of t to 99 does not change the code in line [0], which
> it then executes with dbinto or dbover.
>
> It
the step is calculated rather than given
you’d need to preprocess the argument(s)
Am 02.04.20 um 01:26 schrieb Fraser Jackson:
No one has mentioned the simple function
load 'stats/base'
steps 5 19 14
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
steps 5 9 8
5 5.5 6 6.5 7 7.5 8 8.5 9
steps _3 10 13
_3
No one has mentioned the simple function
load 'stats/base'
steps 5 19 14
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
steps 5 9 8
5 5.5 6 6.5 7 7.5 8 8.5 9
steps _3 10 13
_3 _2 _1 0 1 2 3 4 5 6 7 8 9 10
steps 4.25 8.75 9
4.25 4.75 5.25 5.75 6.25 6.75 7.25 7.75 8.25 8.75
steps 9 4 5
9 8 7 6 5 4
Also use
I like this and find your approach to thru interesting as it works both
ways 5 thru 19 and 19 thru 5. A 'one way' approach could be this
thru2=. }. [:i.>:
5 thru2 19
5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
some time difference but no space difference
(100)6!:2 '5 thru2 200'
1.117e_6
(100)
I don't know what the debug commands are supposed to do. If anyone
knows and can put it into NuVoc that would be great.
I rewrote the whole interface to debug in 9.01 so there is a good chance
some things don't work right. Several such places have been fixed, but
if you know you have an erro
So... I'm stuck at home and am explicitly not allowed to work on
production systems, so... anyways... here's a partially tested
implementation of something close to request #4. (I tested with
blocksize being 150 instead of 1e7 and with the test data provided):
example use:
(jpath '~user/output
All,
I think Bill's solution works for my question: dbover'' (13!:20).
In contrast to Gilles, I think dbinto'' (13!:21) works as designed, because
changing the value of t to 99 does not change the code in line [0], which
it then executes with dbinto or dbover.
It is rather difficult to find the na
There is definitely a way to do this by mapping the files, but if you don't
know what mmap is you're going to have a hard time doing it. I think you
might also have a hard time writing a better parser than is in the csv
addon (which is pretty slow last I checked).
Jd is really the right way to go
dbnxt (13!:5) works, 13!:21 does not.
h=: 3 : ('t=. 2 3*y'; '1+t'; 't')
dbr 1
3 4,h 5 6 7
|length error: h
| t=.2 3 *y
|h[0]
t=.99
13!:21 ''
|length error
* t=.2 3 *y
|h[0]
13!:5 ''
|stop
* 1+t
|h[1]
13!:5 ''
3 4 99
JVERSION
Engine: j901/j64avx/wi
Hi Brian,
Looking at the debug foreign conjunction 13!: in the vocabulary it looks as if
[x] 13!:21 yStep Into. Run the current line (or line x if specified),
stopping at the next line.
I haven't done too much debugging from the command line, but that looks like
the right place to start.
You could cut and paste the line into the session. Other than that, I
think you have to set the stop for the next line and resume with " 13!:4''
".
On Wed, Apr 1, 2020 at 12:06 PM Brian Schott wrote:
> WITHOUT using the jqt debug window, if debug is on (dbr 1) and a stop has
> been reached, is
I think it's dyad dbover.
type dbhelp for a terse help.
On Thu, Apr 2, 2020, 12:06 AM Brian Schott wrote:
> WITHOUT using the jqt debug window, if debug is on (dbr 1) and a stop has
> been reached, is there a way to execute the current stopped line and then
> stop on the very next line even if
WITHOUT using the jqt debug window, if debug is on (dbr 1) and a stop has
been reached, is there a way to execute the current stopped line and then
stop on the very next line even if there is no stop set for that next line?
(I find the debug box/pane is very hard to use on my Mac, so I prefer to
c
Bo's 'Hist' is new to me. I substituted 'Bar' for 'Hist' and got the same
result, though.
An alternative that could be adapted, perhaps, is at the following link.
It's strength, if there is one, is to plot histograms with varying x
buckets,
but it would have to be adapted to fill in the buckets wit
Hello Ruda.
Try this.
E =. +/%# NB. Mean
RMS=. E&.:*: NB. Root Mean Square
D =. -E NB. Deviation from mean
S =. RMS&D NB. Standard deviation
Z =. D%S NB. Normalized deviation.
'hist'plot +/(Z ,+/~i.10):
Dear list,
are there somewhere utilities rea
Same result here, Win10.
R.E. Boss
> -Oorspronkelijk bericht-
> Van: Programming
> Namens David Mitchell
> Verzonden: dinsdag 31 maart 2020 23:40
> Aan: [email protected]
> Onderwerp: Re: [Jprogramming] Programmatic way to save plot images
>
> Sorry, I did not include all the
Dear list,
are there somewhere utilities ready to plot 2D histograms? (I.e.,
having, say, x and y coordinates of points, we would have bins with some
x- and y- extent into which one pours the data).
Thanks
Ruda
--
For informati
19 matches
Mail list logo
