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
When running a strategy, the first level of parametrization shoud be done via configuration files.
However when a user first install gryphon, most of default values used are "hidden in code", especially invisible for users running 'builtin' strategies.
I am wondering if it wouldn't be better to have builtin strategies creating their configuration file upon first run, so that the user can easily find and modify what he needs, at his level, in the folder where he runs the strategy from....
Thoughts?
The text was updated successfully, but these errors were encountered:
Something like this could be good, although I don't know off the top of my head the right way to implement it.
Another option would be to display the configuration settings at runtime, before the strategy begins executing, and have a prompt asking the user to confirm the settings. We could provide a link back to documentation at the same time.
When running a strategy, the first level of parametrization shoud be done via configuration files.
However when a user first install gryphon, most of default values used are "hidden in code", especially invisible for users running 'builtin' strategies.
I am wondering if it wouldn't be better to have builtin strategies creating their configuration file upon first run, so that the user can easily find and modify what he needs, at his level, in the folder where he runs the strategy from....
Thoughts?
The text was updated successfully, but these errors were encountered: