Gregory Jefferis

im3d [ operator (as alternative to imslice)

1

Should review why this was tricky ``` x=im3d(...) y=x[,10,] z=x[,,10] ``` is rather more intuitive than ``` y=imslice(x,10,slicedim='z') z=imslice(x,10) ```

This is in contrast to plot3d which plots all points. Controlling the behaviour could be useful, but it should definitely be consistent.

write.nrrd should be able to use header for core fields as well

3

Those specified as main arguments should still take priority. Should also normalise argument/field names e.g. ``` enc-> encoding dtype->type ``` though for dtype, should probably keep a deprecated alias.

threshold.im3d(x,thr) fails when thr is logical

1

should keep the attributes of x, but apparently does not

pull out all rgl dependencies into separate nat3d package

3

This is what e.g. vegan/analogue have done with: - http://cran.r-project.org/web/packages/vegan3d/index.html - https://github.com/vegandevs/vegan3d - http://cran.r-project.org/web/packages/analogueExtra/index.html The reasoning is that there are problems with the rgl build e.g. on snow leopard that...

as.im3d.matrix should round away floating point errors

1

See #263 also revealed by vim=as.im3d(xyzmatrix(v.jfrc2), voxdims(JFRC2), BoundingBox=boundingbox(JFRC2)) although the

nl[,]<- should look after rownames / ordering

1

see https://github.com/jefferis/nat/tree/feature/set-data.frame branch.

im3d should set dim on input data when possible

3

``` r im3d(1:12, dims=c(2,3,4)) ``` should give an array with real dimensions c(2,3,4).

all.equal.im3d does not check dim attribute

1

and it surely should when we are checking for equality rather than equality rather than equivalence