Closed zoghbi-a closed 7 months ago
Update the README.
When I opened the wwt notebook, it was automatically using the heasoft kernel, which is what is used by default. But the pywwt stuff isn't installed in the heasoft environment but the base one. Is there a way to make the wwt notebook open with the correct kernel? This would be cool if we can figure out, because ultimately we'd hope to have ciao, fermi, xmm, etc. notebooks, and they'll need to be run in the right kernel as well. Not sure how though....
Yes. part of the recent update was to separate the heasoft stuff from the rest, and it seems I forget to update the file to point to the correct kernel.
Yes. part of the recent update was to separate the heasoft stuff from the rest, and it seems I forget to update the file to point to the correct kernel.
And the notebook errored at the end with
layer2 = wwt.layers.add_image_layer(image=(cutout.data,cutout.wcs))
ValueError: ndarray is not C-contiguous
Sigh. We shouldn't hold it up for this.
I think we need a prominent warning in the introduction.md that the workspace/sciserver_cookbooks is temporary and not persistent. If the user wants to store their results between sessions, the need to copy/move into their persistent area.
Yes. part of the recent update was to separate the heasoft stuff from the rest, and it seems I forget to update the file to point to the correct kernel.
And the notebook errored at the end with
layer2 = wwt.layers.add_image_layer(image=(cutout.data,cutout.wcs))
ValueError: ndarray is not C-contiguous
Sigh. We shouldn't hold it up for this.
This is fixed in ff1d4f420c0bf003b2f2732d7937c274f8af8b9a
I think we need a prominent warning in the introduction.md that the workspace/sciserver_cookbooks is temporary and not persistent. If the user wants to store their results between sessions, the need to copy/move into their persistent area.
Added in d8d3a7495f9e7e048283e150a509d7c06d52c114
There are several updates: