make a default yaml for user params

[bnord]

• look through the current config yaml
• what part of that do we actually want the user to mess with
• differentiate between what should be changed by the user and what shouldn't (e.g., speed of light vs. omega matter)

[bnord]

Which part of the yaml file should be protected and almost never changed?

I'm guessing this is the universal constants?

When we decide that, we can hide those constants somewhere.

[bnord]

here's the yaml
https://github.com/deepskies/SimSZ/blob/dev-pipeline/SimSZ/settings/config.yaml

[evavagiakis]

For most universal constants we are using built-in ones from astropy etc., it looks like right now it's just T_CMB in the .yaml and I don't think there's motivation to hide this (what if someone wants to toggle it?)

[bnord]

the base_config.yaml has the constants we might want to hide. They were explicitly defined in config.yaml, so I wasn't sure if they should be kept or assumed.

[bnord]

https://github.com/deepskies/SimSZ/blob/dev-pipeline/SimSZ/settings/base_config.yaml

[bnord]

We needed the base_config.yaml in DeepCMBSim, because CAMB requires a bunch of parameter choices that we don't want users to have to make.

We may not need that here. I'm not sure.

[evavagiakis]

I'm not familiar with the code on dev-pipeline as I've only been working on dev-massdist (other branches are stale) and I don't have a base_config.yaml I've been working with, I'm using astropy for fundamental constants (has unit capabilities) and not defining them in a yaml

[bnord]

I will close this.

When we define the input yaml config, we should take care to note if there are any parameters that should be defined, but that we don't want the user to have to mess with.