Skip to main content
Solved

A problem with Statistics Calculator

jan
Contributor
Forum|alt.badge.img+1
  • janContributor
  • Contributor

The statistics Calculator gives this error when trying to count the sum of an attribute: 2020-08-11 12:49:59|2233.8| 2.3|ERROR |Python Exception <MemoryError>: 

2020-08-11 12:49:59|2233.8| 0.0|FATAL |@Python failed to execute function `StatisticsCalculator.recordFeature'

2020-08-11 12:49:59|2233.8| 0.0|ERROR |StatisticsCalculator_2_InputProcessor (TeeFactory): StatisticsCalculator_2_InputProcessor: @Python execution failed

2020-08-11 12:49:59|2233.9| 0.1|ERROR |StatisticsCalculator_2_InputProcessor: @Python execution failed

 

There was approx 2.5M features passing through each one having a value of 1. So the sum operation should not be exhaustive. What could cause this? A bug?

Best answer by jan

I removed the "fme_feature_type_name" attribute and it seems to have solved the problem.

View original
Did this help you find an answer to your question?

7 replies

jan
Contributor
Forum|alt.badge.img+1
  • janContributor
  • Author
  • Contributor
  • August 11, 2020

Using fme 2019.2

srg
Forum|alt.badge.img+10
  • srg
  • August 11, 2020

@jan​ Can you try running the process with only the attribute for which you need the statistics?

In other words use AttributeRemover to remove attributes of not interest for statistics calculation before sending the FME features to StatisticsCalculator.

jan
Contributor
Forum|alt.badge.img+1
  • janContributor
  • Author
  • Contributor
  • August 11, 2020
srg wrote:

@jan​ Can you try running the process with only the attribute for which you need the statistics?

In other words use AttributeRemover to remove attributes of not interest for statistics calculation before sending the FME features to StatisticsCalculator.

I can't remove but one attribute. I need all the others.

jan
Contributor
Forum|alt.badge.img+1
  • janContributor
  • Author
  • Contributor
  • Best Answer
  • August 11, 2020

I removed the "fme_feature_type_name" attribute and it seems to have solved the problem.

jan
Contributor
Forum|alt.badge.img+1
  • janContributor
  • Author
  • Contributor
  • August 11, 2020

Should this be reported as a bug!?

DanAtSafe
Safer
Forum|alt.badge.img+18
  • DanAtSafeSafer
  • Safer
  • August 11, 2020
jan wrote:

Should this be reported as a bug!?

Hi @jan​  Please try the latest FME 2020.2 beta and if the problem still exists then please submit a case. Thanks!

jan
Contributor
Forum|alt.badge.img+1
  • janContributor
  • Author
  • Contributor
  • August 12, 2020
DanAtSafe wrote:

Hi @jan​  Please try the latest FME 2020.2 beta and if the problem still exists then please submit a case. Thanks!

I think Safe should test it. My Client uses FME 2019.2 and it is a hard job changing version since also FME Server is used with the same version.

Reply


Helpful Members This Week

Community Stats

31,327
Posts
118,859
Replies
38,955
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.