-
**Describe the bug**
Importing TriggerSelector from GtBurst AFTER importing threeML causes crashes when viewing lightcurves or other plots. Specifically, after importing threeML then TriggerSelector,…
-
pgmuvi should create an output table so that people can understand what the results are and what they mean.
This might involve two separate implementations for MAP and MCMC solutions, as credible …
-
we should choose another dataset to test our algorithms on. the way I envisioned it with Rafael is that we would describe and tune our models on Kepler data then test them on another dataset and comme…
-
**Feature request**
We expect users that are applying their functions via reduce to sometimes want more complex outputs. For example, if I'm applying Lombscargle to all lightcurves in my nested datas…
-
We need simulated data sets to run the models on before we move to real data sets.
@kponder will work on this and @rbiswas4 will send his existing code.
-
A good idea for this project, so that it can be ported over multiple UKIRT WFCAM time-series datasets:
Have a "generic" lightcurve-plotting package that is configured for WFCAM JHK data but is agnost…
-
The `welter` outline resides in `document/README.md`. Consider updating this outline to the present document.
gully updated
6 years ago
-
**Describe the bug**
The current implementation of the `Lightcurve` object allows the creation of a 1-element light curve, but subsequently throws an error when the `set_model` method is called:
```…
-
#### Problem description
For lightcurves from CDIPS, I found the following discrepancies from what one would normally expect in using a `LightCurve` object:
1. `lc.time`'s values are in BJD, but…
-
# PLAsTiCC Data Exploration Website
Adding content to the Data Exploration [Website](https://aimalz.github.io/plasticc-explorer/index.html) for PLAsTiCC.
Contacts: @aimalz @Catarina-Alves @kpon…