-
I'm facing a problem while running Stage 4 to fit the lightcurves using fit_lightcurves.py and fit_lightcurves.yaml. It is unable to fit the mid-transit time. There is always a large random shift in t…
-
At the moment we just create keep up adding new extracted sources to the database without a retention policy. This will cause slowdowns and eventually disk fill up.
I think we should implement (optio…
-
ZTF recently published this preprint on their second data release of SNIa lightcurves: https://arxiv.org/abs/2406.01434. This data would be very complementary to the timeseries already included in Ast…
-
### Describe the desired workflow.
_Including details and what needs to be run, on what system (if relevant), and any technologies that will be used alongside Nested-Dask_
This driver is straightf…
-
Another issue I brough up on the starry repo is the ability to fit multi-wavelength lightcurves. With the advent of JWST, I and many others are wanting to simultaneously fit multi-wavelength data. Thi…
-
MOP currently stores every datapoint as separate ReducedDatums, rather than as whole lightcurves.
Consider refactoring the DB to store as lightcurves instead.
-
I seriously doubt the file below is 3.9 gigs. LIkely an incorrect exposure start/stop or bad times in the corrtag are making it much larger then it actually should be.
Perhaps raising an exception i…
-
PyLIMA's internal error checking is really great for robust fitting but there are occasions when this causes a fit process to end prematurely. This is fine, but in these circumstances, it would be re…
-
SNN was not designed to handle None values in light-curves. A simple pdf = pdf[~ pdf.FLUXCAL.isna()] in line 120 in snn/processor.py should deal with that
-
This is easy to do with BAGLE. We could add tutorials or we could add helpful functions inside PopSyCLE.