estimatedPrintTime - which estimator created it?

Nils · January 29, 2025, 7:22am

Hi.

I am looking for the information which estimator created the estimation of a specific file...in the API and during debugging I see the estimatedPrintTime only and missing something like estimatedPrintTimeOrigin. During printing it is easily possible and I am still using it.

"gcodeAnalysis": {
"estimatedPrintTime": 1188,
"filament": {
"length": 810,
"volume": 5.36
}
},

(File operations — OctoPrint master documentation)

github.com

NilsRo/OctoPrint-SlicerEstimator/blob/5a339c75c12e81ed2d6745c68053088f580b26fa/octoprint_SlicerEstimator/static/js/SlicerEstimator.js#L112


      
          self.printerStateViewModel.estimatedPrintTimeString = ko.pureComputed(function () {
            if (self.printerStateViewModel.estimatedPrintTime() != null && self.currentEstimatedPrinttime() == self.printerStateViewModel.estimatedPrintTime()) {
              return self.estimatedPrintTimeString() + " ✔";
            } else {
              return self.estimatedPrintTimeString();
            }
          });
          
          
          // Overwrite the printTimeLeftOriginString function
          ko.extenders.addSlicerEstimator = function (target, option) {
            let result = ko.pureComputed(function () {
              let value = self.printerStateViewModel.printTimeLeftOrigin();
              switch (value) {
                case "slicerestimator": {
                  return option;
                }
                default: {
                  return target();
                }
              }

Cheers,
Nils

jneilliii · January 30, 2025, 5:48am

You are correct. The file metadata stored as part of the analysis doesn't appear to include the estimated source. They are separate data models and what you are seeing for job information while printing is Progress Information vs gcode analysis information.

Nils · January 30, 2025, 7:27am

Thanks! Than I can stop looking for it and let my workaround running...