Skip to main content
Solved

Workspace stops working

  • July 18, 2018
  • 2 replies
  • 19 views

caracadrian
Contributor
Forum|alt.badge.img+23

I am running a workspace that generates contours on a point cloud and writes them to dwg.

Workspace stalls indefinitely, doesn't crash, I get some warnings. Only message is "Sorter(SorterFactory): Completed 7.17% of intermediate processing" in the status bar.

The .fmwt can be downloaded from here (OneDrive)

Best answer by caracadrian

Thanks @ChrisAtSafe, changing the order of the transformers (Generalizer before the LineCombiner) doesn't give the desired result, the 2DForcer workaround does.

I found another workaround: set the Conflict Resolution in the ContourGenerator transformer to Perturb Input Points On Contour Interval. I don't understand why this fixes the LineGenerator to Generalizer stall. I will submit a PR tomorrow so I can attach logs and workspace to it.

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.

2 replies

chrisatsafe
Contributor
Forum|alt.badge.img+2
  • Contributor
  • 606 replies
  • July 18, 2018

Hi @caracadrian,

I'm not sure why the workspace is stalling. However, I was able to successfully run the translation by changing the order of the transformers (Generalizer before the LineCombiner). I have attached a template with the workaround for you: contours-on-pntcloud.fmwt

It seems the original translation stalls when features are being sent from the LineCombiner to the Generalizer (as shown in the screenshot). I have submitted a PR for this issue: PR #84420.

If you would like to be notified of any updates you can also submit a problem report (please quote your Q&A; URL).

Another option is to use a 2DForcer before the LineCombiner (using the order of your original translation).

Hope this helps.

- Chris


caracadrian
Contributor
Forum|alt.badge.img+23
  • Author
  • Contributor
  • 571 replies
  • Best Answer
  • July 18, 2018

Thanks @ChrisAtSafe, changing the order of the transformers (Generalizer before the LineCombiner) doesn't give the desired result, the 2DForcer workaround does.

I found another workaround: set the Conflict Resolution in the ContourGenerator transformer to Perturb Input Points On Contour Interval. I don't understand why this fixes the LineGenerator to Generalizer stall. I will submit a PR tomorrow so I can attach logs and workspace to it.