PHOEBE 2 is officially released, but does not fully support all features in the original version of PHOEBE and should still be used with some caution.
Below are the versions we suggest using based on your needs:
- PHOEBE 1.0 (legacy) should be used for reliable trustable science results and for cases that do not require the precision or additional physics introduced by PHOEBE 2.x. PHOEBE 1.0 (legacy) is still significantly faster than PHOEBE 2.x.
- PHOEBE 2.0-alpha is no longer actively supported or developed.
- PHOEBE 2.x should be used to learn the interface for PHOEBE going forward, and will be updated with future releases to include new physics. Although we have made every effort to test the science-results, please make sure all results make sense and report any issues.
IPython Notebook | Python
PHOEBE Logic for Computing Observables
The general logic steps that PHOEBE uses for each observable type are as
- Dynamics - each star or body in the system hierarchy needs to be
placed in the correct position in the orbit at any given time. Some
observables (dynamical RVs and ETVs) simply use information from the
dynamics and do not use any of the following steps.
- Meshing - each star or body in the system needs to be discretized (if
applicable), creating a mesh of triangles that describe the shape of
- Local Quantities - at any given time, each surface element needs to
have its local quantities populated. These include things like
effective temperature and intensity.
- Eclipse Detection - each star needs to detect which of its surface
elements are eclipsed, and handle subdivision if necessary to
increase the resolution along the eclipse edge.
- Integration - lastly, the local quantities need to be integrated over
all visible surface elements to compute a single observable value at
the given time
See more information about options for dynamics in the section on the
See more information about the options for eclipse detection and
subdivision in the section on the MESH dataset