Skip to main content
Solved

Run FMEFactoryPipeline repeatedly with PythonCaller

  • March 24, 2016
  • 8 replies
  • 37 views

verdoodtdries
Supporter
Forum|alt.badge.img+23

Hellow fellow FME-users, 


I'm trying to run FMEFactoryPipeline repeatedly within a PythonCaller. 


After some iterations it stops running unexpectedly and FME is only providing me the unhelpful error message: "Error running translation".


I think the order of the function I'm calling on the pipeline factory is wrong.

This is the order I'm using right now:

# initialize pipeline
pipeline = fmeobjects.FMEFactoryPipeline()
# Add pipeline factory (spatialrelator in my case)
pipeline.addFactory()
# Push features through the pipeline
pipeline.processFeature()
# Execute the pipeline
pipeline.allDone()

Or I'm forgetting to call a certain function on the pipeline object.


Documentation on FMEFactoryPipeline can be found here: http://docs.safe.com/fme/html/FME_Objects_Python_A...



I attached an example workspace.

Has someone experience with this issue?


Thank you very much.

Best answer by larry

Hello,

SAFE confirmed that there is a bug with 2014 SP5, 2015 and 2016.

They are expecting a fix in 2016.1.

Regards,

Larry

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

8 replies

Forum|alt.badge.img
  • March 25, 2016

I have the same issue as you with 2015 and 2016. I'll try to find the source of the problem and come back to you later today or early next week.


Forum|alt.badge.img
  • March 25, 2016

Hello,

I played a bit with the factory code and it seems to be an issue with 2015 and 2016.

The attached workspace runs fine in 2014 but crashes 2015 and 2016.

I submitted the workspace to SAFE for investigation (case #C113361).

Regards,

Larry


Forum|alt.badge.img
  • March 25, 2016

Hello,

I played a bit with the factory code and it seems to be an issue with 2015 and 2016.

The attached workspace runs fine in 2014 but crashes 2015 and 2016.

I submitted the workspace to SAFE for investigation (case #C113361).

Regards,

Larry

@daleatsafe Can I add a reference to the SAFE case number here?


fmelizard
Safer
Forum|alt.badge.img+21
  • Safer
  • March 25, 2016

@daleatsafe Can I add a reference to the SAFE case number here?

Please do. We'll want to give this a look and will in any case, but no problem having a reference in here.


Forum|alt.badge.img
  • March 25, 2016

Please do. We'll want to give this a look and will in any case, but no problem having a reference in here.

Done, thanks.


Forum|alt.badge.img
  • Best Answer
  • April 4, 2016

Hello,

SAFE confirmed that there is a bug with 2014 SP5, 2015 and 2016.

They are expecting a fix in 2016.1.

Regards,

Larry


verdoodtdries
Supporter
Forum|alt.badge.img+23
  • Author
  • Supporter
  • April 5, 2016

Hello,

SAFE confirmed that there is a bug with 2014 SP5, 2015 and 2016.

They are expecting a fix in 2016.1.

Regards,

Larry

Thank you very much Larry. I'm looking forward to the new release.


Forum|alt.badge.img
  • April 21, 2016

Hello,

SAFE confirmed that there is a bug with 2014 SP5, 2015 and 2016.

They are expecting a fix in 2016.1.

Regards,

Larry

Just tested FME Desktop 2016.1 Release Candidate (build 16489) and this is fixed.

Can be downloaded here:

https://www.safe.com/support/support-resources/fme-downloads/beta/