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
Because QuEST is so marvelously generalized across propagator types, we should add the option for users to specify which propagator they'd like to use in the input file. Essentially, the enhancement here is to
Add a shared(? maybe unique) pointer to the Configuration struct. This pointer will hold the kernel we're eventually going to build.
Read the kernel type (as text) from input.cfg
Read the kernel parameters from input.cfg (this is trickier as different kernels have different numbers of parameters)
Assemble the parameters into the appropriate kernel at the end of parse_configs.
Step 4 will be the spot to add a switch statement that switches on the kernel type, but if we do things right that should be the only place we need to maintain such a field.
The text was updated successfully, but these errors were encountered:
Because QuEST is so marvelously generalized across propagator types, we should add the option for users to specify which propagator they'd like to use in the input file. Essentially, the enhancement here is to
Configuration
struct. This pointer will hold the kernel we're eventually going to build.parse_configs
.Step 4 will be the spot to add a switch statement that switches on the kernel type, but if we do things right that should be the only place we need to maintain such a field.
The text was updated successfully, but these errors were encountered: