Dear all,
is there a particular reason for not saving the results of osr (stored in osr_res during the run of osr.m) into oo_? If not, I would suggest to add a subfield osr to oo_ in order to store
oo_.osr.optim_params and oo_.osr.objective_function
My current reading is that those values are printed, but are not easily accessible.
Best,
Johannes
Le lundi 03 mars 2014 à 09:48 +0100, Johannes Pfeifer a écrit :
is there a particular reason for not saving the results of osr (stored in osr_res during the run of osr.m) into oo_? If not, I would suggest to add a subfield osr to oo_ in order to store
oo_.osr.optim_params and oo_.osr.objective_function
My current reading is that those values are printed, but are not easily accessible.
That looks good to me.
Michel, is there any reason for not doing this?
My mistake. The preprocessor seems to already do this. Seems I had the path set to an older version.
-- Johannes Pfeifer Hausserstr. 29 72076 Tuebingen Germany
Am 07.03.2014 um 18:05 schrieb Sébastien Villemot sebastien@dynare.org:
accessible.
-
Johannes Pfeifer -
Sébastien Villemot