Intrusion with structural trend processing time

Is it usual for the processing time to increase dramatically when applying a structural trend to an intrusion model? About 6 minutes processing with a global trend versus <8 hours with a structural trend. In fact even leaving the process running overnight the structural trend model still hadn't finished. Maybe there is something else I'm doing / not doing? 
Tagged:

Comments

  • No responses to this, can I assume then that no-one else has come across the same issue? 
  • Hey @JamesLally; just wondering if you reached out to the support team about this query?  If not, and assuming this is still something that concerns you, I would recommend jumping onto www.myseequent.com  and submitting a support request. 


  • I didn't at the time, assumed it was maybe just my hardware and thought someone else might have noticed it. Would still like to know what was happening though - can I assume that the lack of response here means it's never been raised as an issue?
  • @JamesLally I'm not across the support space myself so couldn't comment if it has been raised and possibly explained or resolved for other people. All I can say is that I've not seen the issue get as far as the product or development teams (spaces I am across).

    I had a quick look at the knowledge articles to see if there's anything documented there but didn't find anything specific: https://my.seequent.com/support/search?page=&types=KnowledgeBaseArticle&product=27   

    I'll reach out to our engineering team and see if they can shed some light on it. 
  • @JamesLally  yep; as I suspected; the extreme slow down you're seeing doesn't sounds right and the suggestion from Tim (our research engineer) is, if possible, to provide a cut-down version of the project to our support team for further investigation. If you reach out to support they will give you all the steps you need to pursue this as an option.