#15 closed defect (fixed)
Timing traces are not working
Reported by: | Víctor de Buen Remiro | Owned by: | Jorge |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Kernel | Version: | head |
Severity: | normal | Keywords: | |
Cc: |
Description
Some timing traces give imposible values under Windows TOL version. For
example estimating a simulated ARIMA model:
My old local TOL version says
Tiempo Test de datos input para 205 variables ... 0.343000000000000
segundos
But the new CVS version says
Tiempo Test de datos input para 205 variables ... -1236950581 segundos
My old local TOL version says
Tiempo Método de minimización cuadrática de Marquardt 8 minutos 49.000
segundos
But the new CVS version says
Tiempo Método de minimización cuadrática de Marquardt 0.000 segundos
Change History (5)
comment:1 Changed 21 years ago by
Status: | new → assigned |
---|
comment:2 Changed 21 years ago by
Owner: | changed from danirus to jsperez |
---|---|
Status: | assigned → new |
comment:3 Changed 21 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
A solution is already in CVS, files changed: tol_btime.h, tol_btext.h, time.cpp,
txt.cpp, txtalgeb.cpp
comment:4 Changed 18 years ago by
bug_file_loc: | → http://cvs.tol-project.org/viewcvs.cgi/tol_tests/tol/Bugzilla/_NON_AUTOTESTEABLE_BUG_ |
---|
comment:5 Changed 18 years ago by
bug_file_loc: | http://cvs.tol-project.org/viewcvs.cgi/tol_tests/tol/Bugzilla/_NON_AUTOTESTEABLE_BUG_ → http://www.tol-project.org |
---|
--Resolved by Jorge Suit Pérez