You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The default values for the config file variables need to be documented.
There are some modules with default values defined explicitly in the
module, e.g. in material.py
It would be useful to have a standard location where the default config
values are located. That would make it easier to be consistent with the GUI as well.
I am thinking of adding a separate defaults module to the config package.
The text was updated successfully, but these errors were encountered:
This sounds good to me, Don. And actually, a lot of config in HEXRDGUI is stored in dicts. We put the default values for our config in a yaml file like this one.
After loading saved settings, we recursively set default values if any keys are missing.
You might be able to do a yaml file for the defaults here as well.
The default values for the config file variables need to be documented.
There are some modules with default values defined explicitly in the
module, e.g. in material.py
But most default values are hardcoded using the config get() method, as in fitgrains.py:
It would be useful to have a standard location where the default config
values are located. That would make it easier to be consistent with the GUI as well.
I am thinking of adding a separate defaults module to the config package.
The text was updated successfully, but these errors were encountered: