Hi All,
We recently implemented UN from GN for our water distribution system. We've mostly built out our pressure tier (we have hundreds of pressure zones), and have been experimenting with different isolation trace configurations at the pressure tier. For the vast majority of our subnetworks, isolation traces run really fast. The exception is our very large gravity zones that have hundreds of thousands of features and a large number of controllers each. On these areas, when an isolation trace is run, they come back with no results and a "Trace completed with warnings" message WARNING 002535. This message seems too vague to use to troubleshoot. We don't have any dirty areas or topology errors. On the subnetworks in question, their 'is dirty' flag shows False. In the trace config, we're using condition barriers and filter barriers as relevant to our data. Have tried outputs of selection and aggregated geometry with the same results. Watching server resources at time trace is running, don't see any significant strain on RAM or Processors. Have java heap size set to 512. UN version UN5 on Server 10.9.1. Patches have been applied. There's no practical way to break these large subnetworks down into smaller areas. If anyone else has faced similar issues working with large subnetworks please let me know how you dealt with it. Also, if anyone has any ideas on how to troubleshoot please let me know.
thanks,
