Article: Exploring Scientific Data Files in VS Code with Xarray#821
Article: Exploring Scientific Data Files in VS Code with Xarray#821etienneschalk wants to merge 9 commits intoxarray-contrib:mainfrom
Conversation
✅ Deploy Preview for xarraydev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
hi @etienneschalk I am going to close and immediately re-open this in order to refresh the build so i can read this for review. |
|
that did not work. when you have a chance would you mind rebasing. that will solve the merge conflict and make the build render so we can look at this the way it was meant to be read |
ianhi
left a comment
There was a problem hiding this comment.
Hi @etienneschalk over all this reads nicely and is a neat looking tool! It makes me wish it was available on even more platforms, including my beloved juptyerlab :)
Some minor comments:
- some of screenshots seem to use an older version
0.3.0this is fine if the UI hasn't changed much, but thought i'd point it out - update the date please
- You can write the table in markdown instead of HTML if you prefer
- Can you update the banner on the main page. Code here:
xarray.dev/src/components/layout.js
Lines 16 to 23 in 5f44c00
it might be nice to include a small picture up towards the top - it could help the tldr hit a little harder, but not neceessary. Or you can rmeove the TLDR. the problem statement is already quite compelling.
Formats
This is fairly geo focused. does it work well with data from another field (e.g. an ome-zarr? https://idr.github.io/ome-ngff-samples/
82d5210 to
291c443
Compare
✅ Deploy Preview for xarraydev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
for more information, see https://pre-commit.ci
|
Hi @ianhi, thanks a lot for your review! I solved the merge conflict. This was due to an update of the dependencies in I also had this error when running
The solution was:
Regarding your comments:
Indeed, having such an extension for opening scientific files on Jupyterlab might be beneficial. I do not use myself this environment often, as I spend most of my time in VSCode. I wonder if some of the code of the current extension might be reusable. When I have more time I should explore this! My answers to points 1-4:
I would prefer to keep the TLDR section so that people who don't read articles in entirety but click on them to read the first lines still get some information out of it, if it's OK for you. Regarding the picture: I added the logo of the extension (it does not take too much place, and fits on one screen with the TLDR section) as well as the download links. So the first screen of reading looks like a "home page".
When I wrote the extension, my original goal was to be able to open and have an overview of the structure of any file openable by xarray. So if ome-zarr is based on Zarr, and since the extension can open a Zarr store thanks to xarray, I would say it should work in theory. I tried to download a zarr from https://idr.github.io/ome-ngff-samples/ but did not succeed (eg when clicking on BR00109990_C2.zarr I see an error "NoSuchKey"). If you have a sample I can download, I can check (currently the extension can only open Zarr stores stored locally on the filesystem ; it is not possible to do so from remote sources) If you have any other comment regarding the updated version please tell me! |
|
I will attempt to revert my changes to the dependencies to see if this might help. |
|
✔️ After the revert, the preview now works again: https://deploy-preview-821--xarraydev.netlify.app/blog/scientific-data-viewer |

Following the comment pydata/xarray#10825 (comment) from @dcherian, I took the opportunity and wrote a blog article presenting the VS Code extension I created, Scientific Data Viewer.
I tried to keep it concise, present what the extension can, but also cannot do, not to oversell it.
Disclaimer: generative AI was used to help me write this article ; english is not my native language. Please feel free to tell me if any sentence can be improved!