Solved

Hi how to avoid to repeat 3 days of data read after a translation failed? Seems the temporary folder run out of space. Can I swap the temporary location and restart the process from certain point instead of starting again from the begin? Alex

  • 14 October 2021
  • 5 replies
  • 1 view

Hi how to avoid to repeat 3 days of data read after a translation failed? Seems the temporary folder run out of space. Can I swap the temporary location and restart the process from certain point instead of starting again from the begin? Alex
icon

Best answer by sigtill 14 October 2021, 10:45

View original

5 replies

Badge +21

Hi @alexandreaalves​ . Turn off "Feature caching" and this should work much smoother. To change the temp folder you can have a look here: https://community.safe.com/s/article/fme-temp-environment-variable

Hi @alexandreaalves​ . Turn off "Feature caching" and this should work much smoother. To change the temp folder you can have a look here: https://community.safe.com/s/article/fme-temp-environment-variable

Hi @Sigbjørn Herstad​ , I am new on it.

How can I turn of the "Feature caching" and is that possible to run this again from a certain point avoiding to loss 3 days importing and combining Point Clouds?

Badge +21

Hi @Sigbjørn Herstad​ , I am new on it.

How can I turn of the "Feature caching" and is that possible to run this again from a certain point avoiding to loss 3 days importing and combining Point Clouds?

Hi @alexandreaalves​ - this article explains the Feature caching in detail: https://www.safe.com/blog/2018/05/caching-data-fme-evangelist174/

Badge +21

Unfortunately no way to continue this translation when it has stopped, as all the "caches" are now yellow and will be started over again. However it should take a lot less time to process once you have turned off feature caching. Try the workspace with only 2 input files and see that you get the correct outputfiles - then you can run it on all the files afterwards.

Unfortunately no way to continue this translation when it has stopped, as all the "caches" are now yellow and will be started over again. However it should take a lot less time to process once you have turned off feature caching. Try the workspace with only 2 input files and see that you get the correct outputfiles - then you can run it on all the files afterwards.

Really helpful, thank you.

Alex

Reply