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
In "write_rms_eval_log_file.m" and "analyze_OF_param_influence.m", the same code basically appears to be repeated for each hyper-parameter. Instead, one can introduce error structures whose fields correspond to hyper-parameters and error types (e.g. error.min_std_dev.sg_init) and loop over the hyper-parameters, for instance. This remark applies to a lesser extent to other parts of the code, see for instance best_par at the end of "rms_of3D.m". This will help with code extensibility, as one could introduce different types of error more easily after this change.
The text was updated successfully, but these errors were encountered:
In "write_rms_eval_log_file.m" and "analyze_OF_param_influence.m", the same code basically appears to be repeated for each hyper-parameter. Instead, one can introduce error structures whose fields correspond to hyper-parameters and error types (e.g.
error.min_std_dev.sg_init
) and loop over the hyper-parameters, for instance. This remark applies to a lesser extent to other parts of the code, see for instancebest_par
at the end of "rms_of3D.m". This will help with code extensibility, as one could introduce different types of error more easily after this change.The text was updated successfully, but these errors were encountered: