-
Notifications
You must be signed in to change notification settings - Fork 21
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
converting panstarrs read_hipscat to read_hats #382
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -6,9 +6,9 @@ jupytext: | |
format_version: 0.13 | ||
jupytext_version: 1.16.4 | ||
kernelspec: | ||
display_name: science_demo | ||
display_name: notebook | ||
language: python | ||
name: conda-env-science_demo-py | ||
name: python3 | ||
Comment on lines
-9
to
+11
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. are these the new names on fornax? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sorry, I don't know, this all happens for me in the background when I open a notebook on Fornax. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. OK, we can change them, |
||
--- | ||
|
||
# Make Multi-Wavelength Light Curves Using Archival Data | ||
|
@@ -74,7 +74,7 @@ This cell will install them if needed: | |
|
||
```{code-cell} ipython3 | ||
# Uncomment the next line to install dependencies if needed. | ||
# !pip install -r requirements_light_curve_generator.txt | ||
#!pip install -r requirements_light_curve_generator.txt | ||
``` | ||
|
||
```{code-cell} ipython3 | ||
|
@@ -101,7 +101,7 @@ from tess_kepler_functions import tess_kepler_get_lightcurves | |
from wise_functions import wise_get_lightcurves | ||
# Note: ZTF data is temporarily located in a non-public AWS S3 bucket. It is automatically available | ||
# from the Fornax Science Console, but otherwise will require explicit user credentials. | ||
from ztf_functions import ztf_get_lightcurves | ||
# from ztf_functions import ztf_get_lightcurves | ||
``` | ||
|
||
## 1. Define the sample | ||
|
@@ -258,6 +258,8 @@ print('WISE search took:', time.time() - WISEstarttime, 's') | |
### 2.4 MAST: Pan-STARRS | ||
The function to retrieve lightcurves from Pan-STARRS uses a version of both the object and light curve catalogs that are stored in the cloud and accessed using [lsdb](https://docs.lsdb.io/en/stable/). This function is efficient at large scale (sample sizes > ~1000). | ||
|
||
Some warnings are expected. | ||
|
||
```{code-cell} ipython3 | ||
panstarrsstarttime = time.time() | ||
|
||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where does this coming from? Do we really need the extra dependency? (upath is not a direct dependency until this point)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think lsdb.read_hats() will be able to deal with raw s3 strings, so no need to wrap it up as a path object, directly use the urls
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is now required by
lsdb
. Sending a raw string for s3 now throws an error:It also will not accept a filesystem object, only a
UPath
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting. Before I commented I tried it locally and it worked.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Anyway, I think it's an upstream issue, their API should be user friendly enough to accept reasonable inputs like an s3 uri string
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the one todo here thus is to add
universal_pathlib
to the requirements file as we directly use it (although it's already an indirect requirement via hats/lsdb)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opened astronomy-commons/hats#462
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
astronomy-commons/hats#466 added support for submitting the s3 uri as a string when only an anonymous connection is needed. So this kind of call should work now:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It hasn't been released though, so I would just open a reminder issue to do the cleanup once we have it installed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh right, thanks. I see you opened #383.