This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Skeletonization and Active TOpology

Hi Everyone,

I'm using the Skeletonator to merge pipes in series. However I'm having a problem with the skeletonator ignoring inactive topology. To quote the help article for this:

"Skeletonization occurs on only active topology but considers all topology."

"The two series pipes still may not be skeletonized if any inactive topology could be affected by the execution of the skeletonization action. For example, if the two series pipes have an additional but inactive pipe connected to their common node, and if the series pipe removal action was allowed to proceed, the common node would be removed from the model, and the inactive topology would become invalid. This is prevented from occurring in Skelebrator"

But this is not what I'm experiencing at all. The skelebrator is repeatedly removing nodes connected to inactive pipes.

Why is this happening?

Regards,

Ryan

  • Hello Ryan,

    I did some testing in the current version of WaterGEMS and couldn't reproduce the issue. What version of WaterGEMS are you using? If it is an older version, see if you can upgrade, as that might help with the issue. 

    If you can't upgrade or if that doesn't help, it might be useful to see a copy of the model. You can use the following link to send the model files to us: Sharing model files on the Haestad forum

    Regards,

    Scott

  • Hello Ryan,

    One of my colleagues found a case where the issue you are mentioning is occurring. If the inactive pipe is at a tee, there are cases where the active pipe connected to the inactive pipe will be removed. Is that the case you are seeing? 

    I have opened defect 906377. Is this something you might be able to work around. If so, this is something that should be resolved in the next release of WaterGEMS.

    Regards,

    Scott

  • Hi Scott, I am running WaterGEMS(R) CONNECT Edition Update 1 10.01.01.04

    I(t is not removing the inactive pipe, it's simply removing the node connected to the end of the inactive pipe. The attached screenshot shows two examples where the interconnecting nodes joining inactive pipes to active ones were removed. These were done using the skelebrator, series pipe merge. Jesse already has a copy of the model that is exhibiting this problem.

    This raises a usability suggestion I have with the skelebrator, currently when in manual mode I can choose to protect pipes, which is very useful for protecting pipes with controls, etc (although I'm not sure why I can't simply tell the skelebrator to ignore pipes with controls on them) unfortunately there are also many cases where I would like to protect a node, not a pipe. Whenever I come across these I have to exit the skelebrator manual mode, protect the node and then re-enter the manual skelebration again.

  • Hello Ryan, 

    I also couldn't reproduce the issue with sample model in the latest version.  

    How did you upload the model files? Was it through Communities or service request portal? 

    Regards,

    Sushma Choure

    Bentley Technical Suppport

  • Hi Ryan,

    Just to clarify - we understand the issue with the inactive elements and I was able to reproduce it. As Scott mentioned, we have reported this to our developers to look into in a future release. We'd like to know if you are OK with waiting on a fix. In other words, can you work around this temporarily?

    Thanks for your feedback regarding protected elements. I have passed this along to our development and product management team for consideration, as Enhancement request # 907494. I have also attached this to your related Service Request.


    Regards,

    Jesse Dringoli
    Technical Support Manager, OpenFlows
    Bentley Communities Site Administrator
    Bentley Systems, Inc.

    Answer Verified By: Ryan Catling