• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

sblunt / orbitize / 105
74%
main: 86%

Build:
Build:
LAST BUILD BRANCH: dummy
DEFAULT BRANCH: main
Ran 22 Feb 2018 12:45AM UTC
Jobs 2
Files 8
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

pending completion
105

push

travis-ci

sblunt
Draft API implementation

First draft of API.

Here are some notes about the structure of the code:

1. The standard way that I imagine users using orbitize is as follows:
   - Using Henry’s `read_input.py`, read in a data file, and produce a standardized data table.
   - Initialize a `System` object, with Henry’s data table as an attribute. The System object will initialize a list of `Prior` objects in a standard order that will be used by the `Sampler` object. The user can then overwrite priors they wish to customize.
   - Initialize a `Sampler` object (either a `PTMCMC` object or an `OFTI` object), with the `System` object and a `lnlike()` function as attributes. Right now we will only have a chi squared likelihood, but in the future we will add Gaussian process likelihoods & other fancy ones.
   - Run the `run_sampler()` method of the initialized Sampler object. This will involve calling `kepler.py` to compute orbits, and calling a helper function that will match the outputs of `kepler.py` with their appropriate data points (e.g. pairing “radec” data with position outputs, “rv” data with velocity outputs).
   - Save the results, and optionally make some plots.
2.  I’ve added a file, `driver.py` that contains a class to run through all the standard steps listed above automatically. At the highest level, users should just be able to feed all the information/data they have about into a Driver class, hit run, and relax.

Notes about things I’ve changed:
1. I’ve taken out the `CelestialDuo` class. I think it will be more readable and extensible if instead of using this class, we simply add another column to Henry's data table, specifying whether each data point corresponds to planet a, planet b (etc), or all planets (as in the case of RV/stellar astrometry measurements).
2. I’ve added an abstract base class to the `sampler.py` classes, just for tidiness.

142 of 232 relevant lines covered (61.21%)

1.22 hits per line

Jobs
ID Job ID Ran Files Coverage
1 105.1 22 Feb 2018 12:46AM UTC 0
61.21
Travis Job 105.1
2 105.2 22 Feb 2018 12:45AM UTC 0
61.21
Travis Job 105.2
Source Files on build 105
Detailed source file information is not available for this build.
  • Back to Repo
  • Travis Build #105
  • 330dbc3d on github
  • Prev Build on api_dev (#64)
  • Next Build on api_dev (#115)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc