:point_up: 23. Februar 2018 20:23
the main thing would be tagging it on github as binder-ready
@kmader what do you mean by "tagging it as binder-ready"? The "launch binder" badge was added in December with imagej/tutorials@6ea704a
Is there something else missing?
binder-readyas a topic to https://github.com/imagej/tutorials
@kkangle I’m not 100% certain if this is where the NPE you asked me about earlier came from but its a possibility.
ij.display().createDisplay(...) calls a
DisplayService, possibly DefaultDisplayService. Which finds a matching
Display and calls
display(...). If the matched
Display is the
DefaultImageDisplay then it calls this method. And then again assuming it matches the default you get this method, which if you trace you wind up here. It creates an
ImgView with a
null factory, such that later in your notebook when you try to create a copy via the factory you get an NPE.
I'm making a lot of assumptions here ... so this may not be correct, but it seems promising?
To get around this in the meantime you could try using imagej-ops to convert your
RandomAccessibleInterval to an
Img in the notebook? (provided you can call Ops from your notebook, and there is a converter for RAI to Img - you may need to create an Img from the RAI and then copy the data over ... I can't remember). But then you call
ij.display().createDisplay(...) on this newly created
Img, which has hopefully been made with a non-null factory.
Hopefully that kind of made sense, feel free to let me know if you have any questions.