SeweCad V8i can perform an Constraint based Automatic Design. It uses a design algorithm that attempts to minimize pipe size and excavation, which is typically the most expensive part of installing sewer piping and structures. My question is, What kind of algorithm does SewerCad use for to perform an Automatic Design?, I mean, what is the name? Is heuristic? Where can I find information about it? literature, books, etc.
Thank you for your answers.
It looks like this question was already answered in this previous post:
communities.bentley.com/.../284742.aspx
Was there something else that you still had a question about?
Regards,
Mark
thank you for your answer,
yes, I need more information about it, the last time, they sent me a topic called "Design Priorities", and in this document don't talk about design algorithm that SewerCad uses for to perform an Automatic Design. I want to know specifically about the algorithm used in this program.
Thanks again
Jesus,
My best guess is algorithm is probably confidential information, but, perhaps, Tom or one of my other colleagues on our development team can jump in provide you with more information on that.
thank you for your answer again,
I understand. I hope somebody can help me. It is very important for me. I need general information, not confidential information.
Regards
Jesús
What specifically do you need to know about how the algorithm works that was not answered in the other post?
Mark,
I need to know, what is the name for algorithm? which is the heuristic method used? what is the history?, is there some literature where I can consult?
I'm doing an investigation for my undergraduate thesis, called optimized design of sewerage systems and I will use SewerCad for it. I know that SewerCad try to minimize the cost, but I need to know as this program does.
thanks
I spoke to a few people and here is the best information that I can give you. The method/algorithm that we use is the heuristic method of solving the design problem, but it doesn't have an official name and not it's not really a secret. The best documentation that I can provide you with is the information that outlines our design priorities because they describe the iterative process that we use (see attached). This is a slight revision to what Jesse sent you in the last post, but for the most part it's the same information.
Yes, you are correct in your statement that it does try to minimize the cost of the system design.
I hope that helps out.