The Bundle also contains a few Parameters that provide settings for that Bundle. Note that these are not system-wide and only apply to the current Bundle. They are however maintained when saving and loading a Bundle.
Let's first make sure we have the latest version of PHOEBE 2.2 installed. (You can comment out this line if you don't use pip for your installation or don't want to update to the latest release).
In [ ]:
!pip install -I "phoebe>=2.2,<2.3"
As always, let's do imports and initialize a logger and a new Bundle. See Building a System for more details.
In [1]:
import phoebe
from phoebe import u # units
logger = phoebe.logger()
b = phoebe.default_binary()
Settings are found with their own context in the Bundle and can be accessed through the get_setting method
In [2]:
b.get_setting()
Out[2]:
or via filtering/twig access
In [3]:
b['setting']
Out[3]:
and can be set as any other Parameter in the Bundle
In [4]:
b['log_history@setting'].description
Out[4]:
This parameter can also be set by calling b.enable_history() or b.disable_history() and can be accessed with b.history_enabled.
In [5]:
b['log_history@setting']
Out[5]:
In [6]:
b.history_enabled
Out[6]:
In [7]:
b.enable_history()
In [8]:
b['log_history@setting']
Out[8]:
In [9]:
b.history_enabled
Out[9]:
In [10]:
b['dict_set_all@setting']
Out[10]:
In [11]:
b['teff@component']
Out[11]:
In our default binary there are temperatures ('teff') parameters for each of the components ('primary' and 'secondary'). If we were to do:
b['teff@component'] = 6000
this would raise an error. Under-the-hood, this is simply calling:
b.set_value('teff@component', 6000)
which of course would also raise an error.
In order to set both temperatures to 6000, you would either have to loop over the components or call the set_value_all method:
In [12]:
b.set_value_all('teff@component', 4000)
print(b['value@teff@primary@component'], b['value@teff@secondary@component'])
If you want dictionary access to use set_value_all instead of set_value, you can enable this parameter
In [13]:
b['dict_set_all@setting'] = True
b['teff@component'] = 8000
print(b['value@teff@primary@component'], b['value@teff@secondary@component'])
Now let's disable this so it doesn't confuse us while looking at the other options
In [14]:
b.set_value_all('teff@component', 6000)
b['dict_set_all@setting'] = False
In [15]:
b['incl']
Out[15]:
In our default binary, there are several inclination parameters - one for each component ('primary', 'secondary', 'binary') and one with the constraint context (to keep the inclinations aligned).
This can be inconvenient... if you want to set the value of the binary's inclination, you must always provide extra information (like '@component').
Instead, we can always have the dictionary access search in the component context by doing the following
In [16]:
b['dict_filter@setting'] = {'context': 'component'}
In [17]:
b['incl']
Out[17]:
Now we no longer see the constraint parameters.
All parameters are always accessible with method access:
In [18]:
b.filter(qualifier='incl')
Out[18]:
Now let's reset this option... keeping in mind that we no longer have access to the 'setting' context through twig access, we'll have to use methods to clear the dict_filter
In [19]:
b.set_value('dict_filter@setting', {})
The run_checks_compute option allows setting the default compute option(s) sent to b.run_checks, including warnings in the logger raised by interactive checks (see phoebe.interactive_checks_on).
In [20]:
b['run_checks_compute@setting']
Out[20]:
In [21]:
b.add_dataset('lc')
b.add_compute('legacy')
print(b.run_checks())
In [22]:
b['run_checks_compute@setting'] = ['phoebe01']
In [23]:
print(b.run_checks())
In [ ]: