Describe your use-case.
concept json are subject to change independently from config. so it's not asured training result will be the same. to keep the reliability when loading a config it would be helpful to have exact that concept loaded too, with same settings.
What would you like to see as a solution?
a temporary "#from config" entry in the concept's tab combobox, changed and activated on every load of a config, but not existing on OT start.
Have you considered alternatives? List them here.
automatically create separate json linked to the config file, maybe named same, but this would bloat the CB-list in short time.
Describe your use-case.
concept json are subject to change independently from config. so it's not asured training result will be the same. to keep the reliability when loading a config it would be helpful to have exact that concept loaded too, with same settings.
What would you like to see as a solution?
a temporary "#from config" entry in the concept's tab combobox, changed and activated on every load of a config, but not existing on OT start.
Have you considered alternatives? List them here.
automatically create separate json linked to the config file, maybe named same, but this would bloat the CB-list in short time.