API - Configuring Erebus
Planet
To find the parameters for a planet we recommend you use the Exoplanet Archive wheret0is the time of conjunction (tcon the Exoplanet archive),pis the orbital period in days,rp_rstaris the ratio of the planet's radius to the star's radius,a_rstaris the ratio of the planet's semi-major axis to the star's radius,incis the inclination of the planet (in degrees),eccis the eccentricity of the planet (0 inclusive to 1 exclusive), andwis the agument of periastron of the planet (in degrees).Class which represents known planet values with uncertainties. Loaded from a yaml file and optionally validated against a schema. Uncertainties are expressed by writing the values into the yaml file as a list of floats, where the first value is the absolute value of the measurement. The second value is taken as the symmetric error, and if a third value is provided it is taken a the upper error.
Attributes:
Name Type Description namestrThe name of the planet.
t0uncertainties.core.Variable | floatMidpoint time of reference transit in BJD
t0_lookup_pathstrOptional replacement for t0, relative path to csv file with calculated TTVs (Two columns: t0 in BJD-2,450,000, error)
a_rstaruncertainties.core.Variable | floatThe ratio of semi-major axis to star radius.
puncertainties.core.Variable | floatThe period of the planet in days.
rp_rstaruncertainties.core.Variable | floatThe ratio of the planet's radius to the star's radius.
incuncertainties.core.Variable | floatThe inclination of the planet in degrees.
eccuncertainties.core.Variable | floatThe eccentricity of the planet (0 inclusive to 1 exclusive).
wuncertainties.core.Variable | floatThe argument of periastron of the planet (degrees).
Methods:
Name Description get_closest_t0Given a start time in BJD-2,400,000.5, use the lookup file to get
get_next_t0Given a start time in BJD-2,400,000.5, use the lookup file to get
get_predicted_tsecGiven a start time in BJD-2,400,000.5, use the lookup file or t0
get_closest_t0(obs_start)Given a start time in BJD-2,400,000.5, use the lookup file to get the closest t0
get_next_t0(obs_start)Given a start time in BJD-2,400,000.5, use the lookup file to get the following t0
get_predicted_tsec(obs_start)Given a start time in BJD-2,400,000.5, use the lookup file or t0 and P to get the next eclipse time
ErebusRunConfig
Bases:
pydantic.BaseModelSettings for running through the entire Erebus pipeline. Serializable to/from YAML. One of perform_joint_fit or perform_individual_fits must be true else the run will not do anything.
Attributes:
Name Type Description fit_fnpcaboolOptional bool to use FN-PCA in the systematic model.
fit_exponentialboolOptional bool to use an exponential curve in the systematic model.
fit_linearboolOptional bool to use a linear slope in the systematic model.
perform_joint_fitboolOptional bool to fit all visits together with a shared eclipse depth.
perform_individual_fitsboolOptional bool to fit each visit with their own eclipse depth.
calints_pathstrRelative path from the folder containing this file to where the .fits files are.
planet_pathstrRelative path from the folder containing this file to where the planet config is.
aperture_radiusintPixel radius for aperture photometry.
annulus_startintInner pixel radius of disk used for background subtraction.
annulus_endintOuter pixel radius of disk used for background subtraction.
skip_visitslist[int]Optional list of indices to skip when doing individual fits. Index based on visit ID.
trim_integrationslist[int]Length-two list with the number of integrations to clip from the start and end. Optional.
star_positionlist[int]X and y pixel coordinates of the star. Optional (will search for the star or assume its centered).
prevent_negative_eclipse_depthboolOptional bool to force eclipse depth to be positive.
fix_eclipse_timingboolOptional bool to force t0, period, ecosw to be fixed
Methods:
Name Description set_custom_systematic_modelOptionally provide a callable function and dictionary of Parameter objects for bayesian priors.
set_custom_systematic_model_prior_for_visit_indexOptionally override custom systematic model priors for specific visits
set_custom_systematic_model(model, params)Optionally provide a callable function and dictionary of Parameter objects for bayesian priors.
Order of parameters must match their order in the model method signature.
Params are given as a dictionary of their names (matching the method signature) to a Parameter object.
Model method signature must start with x.
When used in conjunction with built-in fitting model provided by Erebus this model will be multiplied by those fitting models and a best-fit y-offset applied.
set_custom_systematic_model_prior_for_visit_index(index, params)Optionally override custom systematic model priors for specific visits
Params are given as a dictionary of their names (matching the method signature) to a Parameter object.
Parameters
Represents a parameter with Bayesian priors To be used with mcmc_model.py
Methods:
Name Description fixedCreates a fixed parameter
gamma_priorCreates a gamma prior
gaussian_priorCreates a gaussian prior
positive_gaussian_priorCreates a positive gaussian prior
set_initial_valueSet the initial value of this parameter. Will print an error if this value is impossible according to our priors
set_valueSet the current value of this parameter, will update the log_prior accordingly
uniform_priorCreates a uniform prior, constant between min and max
fixed(value)classmethodCreates a fixed parameter
gamma_prior(alpha, beta)classmethodCreates a gamma prior
gaussian_prior(mu, sigma)classmethodCreates a gaussian prior
positive_gaussian_prior(mu, sigma)classmethodCreates a positive gaussian prior
set_initial_value(value)Set the initial value of this parameter. Will print an error if this value is impossible according to our priors
set_value(value)Set the current value of this parameter, will update the log_prior accordingly
uniform_prior(initial_guess, minimum, maximum)classmethodCreates a uniform prior, constant between min and max