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
I am not sure this is the appropiate place for giving some feedback on Pumas functionalities (I did not know where to refer to, so I chose to do it here as a Github issue). If there is other place, I would love to know :)
I have noticed that the metrics_table function returns as "Estimation Time" the cpu time for only the last iteration from the optimization trace.
Maybe this is just a personal opinion, but I find this a bit confusing.
As the table summarizes metrics from the optimization, I would have expected instead to get returned the whole elapsed CPU time for the optimization (sum up cpu time per iteration).
Any thoughts/opinions on this?
The text was updated successfully, but these errors were encountered:
Dear Pumas team,
I am not sure this is the appropiate place for giving some feedback on Pumas functionalities (I did not know where to refer to, so I chose to do it here as a Github issue). If there is other place, I would love to know :)
I have noticed that the
metrics_table
function returns as "Estimation Time" the cpu time for only the last iteration from the optimization trace.Maybe this is just a personal opinion, but I find this a bit confusing.
As the table summarizes metrics from the optimization, I would have expected instead to get returned the whole elapsed CPU time for the optimization (sum up cpu time per iteration).
The text was updated successfully, but these errors were encountered: