Closed barrettk closed 1 year ago
@kyleam FYI I looked into this and it seems the issue is on the bbi side of things. It could be because the post processing time was reported to be 0 seconds, but Im assuming this is more likely to be related to the location or something:
inst/model/nonmem/complex/acop-fake-bayes/acop-fake-bayes.lst
:
Elapsed postprocess time in seconds: 0.00
Elapsed finaloutput time in seconds: 0.00
#CPUT: Total CPU Time in Seconds, 19.117
Stop Time:
Thu Mar 4 13:44:50 EST 2021
Yes, it's on the bbi side of things and is because the JSON encoding is set up to omitempty:
ip-10-128-38-27:bbr$ git grep -i 'postproc' 'inst/model/*.lst'
inst/model/nonmem/basic/1/1.lst: Elapsed postprocess time in seconds: 0.46
inst/model/nonmem/complex/1001/1001.lst: Elapsed postprocess time in seconds: 0.46
inst/model/nonmem/complex/acop-fake-bayes/acop-fake-bayes.lst: Elapsed postprocess time in seconds: 0.00
inst/model/nonmem/complex/acop-iov/acop-iov.lst: Elapsed postprocess time in seconds: 0.00
inst/model/nonmem/complex/example2_saemimp/example2_saemimp.lst: Elapsed postprocess time in seconds: 0.00
inst/model/nonmem/complex/iovmm/iovmm.lst: Elapsed postprocess time in seconds: 1.04
ip-10-128-38-27:bbr$ git -C ../bbi grep 'postp' 'parsers/nmparser/structs.go'
parsers/nmparser/structs.go: PostprocessTime float64 `json:"postprocess_time,omitempty"`
parsers/nmparser/structs.go: PostprocessTime: DefaultFloat64,
@kyleam should this issue be closes now?
@kyleam should this issue be closes now?
gh-274 is set to auto-close it, but its merge is held up by an unresolved (and very likely unrelated) ci failure.
The following 'complex' model does not report post processing time: