-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
What stack version to read NERSC Gen3 skymap? #83
Comments
Even simpler reproduce script is:
|
I don't know much about the NERSC setup, but the skyMap itself is intended to be backwards compatible. I wonder if the |
It appears I used |
If it's helpful @wmwv I can make w_2021_48 available as a jupyter kernel - basically importing that specific docker image into shifter and pass you the kernel.json file you'd need to set it up. |
That'd be great, thanks, @heather999 . |
I'd recommend using |
Oh, I see. I was also confused because |
Actually, a quick sanity check has the same issue with that version:
Let me poke around. I'm surprised this didn't work. |
|
Right desc-stack-weekly is not recent, desc-stack-weekly-latest hasn't moved past w_2022_10 - on the list to fix this week :) |
Description
A clear and concise description of what the issue is.
Can't read skyMap for Gen 3 Run2.2i, Run3.1i with recent
desc-stack-weekly
.@jchiang87 @heather999 What version of the stack was used to produce the skyMap for the NERSC Gen3 Run2.2i and Run3.1i datasets? I think it's incompatible with recent stack versions. Specifically I'm using the Jupyter kernel desc-stack-weekly as of today (2012-04-12).
/global/cfs/cdirs/lsst/production/gen3/DC2/Run2.2i/repo/skymaps/skyMap/
Choose all applicable topics by placing an 'X' between the [ ]:
To Reproduce
Steps to reproduce the behavior:
desc-stack-weekly
for kernelScreenshots
If applicable, add screenshots to help explain your problem.
The text was updated successfully, but these errors were encountered: