Some time ago, it was pointed out that certain variable names related to profiles could be improved. Specifically, that profile_list and profile_indices might be confusing. Since consistent naming is important, any changes could impact all code related to profiles. Therefore, I think it's worth discussing this.
Currently, Result object has profile_result attribute of ProfileResult type, which "holds a list of profile lists. Each profile list consists of a list of ProfilerResult objects, one for each parameter". So, each ProfileResult entry is a collection of ProfilerResult objects, all computied using the same optimization result as a starting point, right? However, this is not very obvious. Should we create a ProfileResultCollection (or ProfileResultSet) class to combine ProfilerResult objects and explicitly indicate which optimization results was used to compute them?
Then, profile_list in profile.profile.parameter_profile ( and in profile.util.fill_profile_list, profile_nested_cis, visualize.profile_cis and so on) could become profile_collection_id.
We could keep profile_index or rename it to parameter_index.
Any opinins?
Some time ago, it was pointed out that certain variable names related to profiles could be improved. Specifically, that
profile_listandprofile_indicesmight be confusing. Since consistent naming is important, any changes could impact all code related to profiles. Therefore, I think it's worth discussing this.Currently,
Resultobject has profile_result attribute ofProfileResulttype, which "holds a list of profile lists. Each profile list consists of a list ofProfilerResultobjects, one for each parameter". So, eachProfileResultentry is a collection ofProfilerResultobjects, all computied using the same optimization result as a starting point, right? However, this is not very obvious. Should we create aProfileResultCollection(orProfileResultSet) class to combineProfilerResultobjects and explicitly indicate which optimization results was used to compute them?Then,
profile_listinprofile.profile.parameter_profile( and inprofile.util.fill_profile_list,profile_nested_cis,visualize.profile_cisand so on) could becomeprofile_collection_id.We could keep
profile_indexor rename it toparameter_index.Any opinins?