Kyle Conroy
Kyle Conroy
changing system hierarchy (binary->triple, flipping roles of primary and secondary, etc) throws an error when any of the built-in constraints have been flipped.
Reflection support is currently implemented in phoebe-lib and has been incorporated into the backend but still needs thorough testing. - [2.0b] test reflection vs legacy (now PASS, see https://github.com/phoebe-project/phoebe2/issues/39) -...
``` import phoebe b = phoebe.default_binary() b.add_dataset('mesh', times=[0,0.25]) b.add_compute('legacy') b.run_compute(kind='legacy') ``` throws the following error at run_compute: ``` the curve you are trying to compute is not initialized. Traceback (most...
secondary luminosities need to be updated within phoebe1. Apparently this happens automatically for detached but not contact systems? For the 2.0 release - we either need to get to the...
if two times are within 1e-6 days (~0.1 s), the filtering logic will likely fail. We could probably push this precision to within np.float64, but may want to consider a...
will also need to change default value of long_an so that the orbital plane remains along the xz axis by default. This currently doesn't affect any of the observables -...
Pretty self-explanatory: implement the ability for the model to average over a provided exposure time per-datapoint. This will likely be computationally expensive and will require some infrastructure work to implement.
... because pblums are passband-dependent and heating/reflection is purely bolometric. But for situations where decoupling pblums makes sense (ie. degenerate objects), do we need some mechanism to also decouple bolometric...
Legacy wrapper (as well as importer and exporter) should support finite exposure times. For the legacy wrapper, this may mean making multiple calls to legacy since legacy only supports a...