[REQUEST] Optimize handling of .Pars property

[m053m716]

Feature Request

What

Currently I think there are probably redundancies in the "checking" procedure implemented by the following methods:

• nigeLab.nigelObj/updateParams()
• nigeLab.nigelObj/getParams()
• nigeLab.nigelObj/setParams()
• nigeLab.nigelObj/saveParams()
• nigeLab.nigelObj/loadParams()

To expedite save and loadobj methods of nigeLab.nigelObj (as well as any other method that checks .Pars, time could probably be saved by checking and updating in these methods in an efficient way.

Urgency

Low

• @Nabarb: I mostly put this here since you might bring a fresh perspective to this particular problem. Currently it is working and I would just like to not break it, but undoubtedly this can be done in a better way.

[m053m716]

Addressed (to some extent) using struct flag: nigeLab.nigelObj.HasParsSaved.(defaultName)

• The flag is initialized with nigeLab.nigelObj.HasParsInit
• The flag is set to true on load from _Pars.mat file
• The flag is set to false when there is a load from nigeLab.nigelObj/updateParams([defaultName],'Direct'); which loads directly from +defaults/[defaultName].m
  • This avoids saving each time there is a call to updateParams(__,'Direct')
  • On a call to nigeLab.nigelObj/save(), if any of the nigelObj.HasParsSaved fields are false, they are subsequently saved and updated to true.
  • This saves redundant parameter-saves that would previously be done any time there was a call to nigeLab.nigelObj/saveIDFile()