Civil Storm View (catchments)

Question

Hello Bentley Support, 
 A Civil Storm model was built by an earlier version (SELECT) and on a desktop computer then I'm now looking at it at a different machine and using CONNECT edition. Couple of issues attracted my attention by opening the file. 
 1. if I simply open the file and try to double click any of the elements whether a catchment or inlet it just crashes and shows the send report dialogue box but doesn't exit the program. 
 i tired to first run the the model prior to clicking and somehow it stopped giving the error. Why is that happening on the first place and how does it get prevented by running the model 
 2. I opened the file on two machines (different than that desktop computer) and in one machine the catchments appears distorted while if I open the same file on the second machine it just looks fine. I even picked the catchment and just moved it from its place in both files to verify what is going on .. see snapshots of the same file from two machines and the lines that are appearing. (please note these are different than the catchment outlet 
 3. Files of Civil Storm are so big from my model (excess 150MB for the compressed file) such that when i tried to submit a ticket through product support I couldn't upload the model zipped file. What is the standard procedure in this case to pass the file. I did submit a ticket at the end but just attached the screenshots rather than the actual model. 
 Why are models file sizes getting to this size (databases ...etc but would have expected still a smaller size) 
 
 regards 
 Ahmed

Scott Kampa · Accepted Answer

Hello, 
 There are a couple of things you can try. First, before opening the model try compacting the database. To do this, go to File > Database Utilities > Compact Database. If this doesn't resolve the issue, try the following. 
 Close the model but you can leave CivilStorm open. Browse to where the model is saved and create a new folder. Then copy just the .stsw and .stsw.sqlite files to the new folder. Next, open the model from the new folder location. If there is an issue with one of the supporting files, this can help. 
 If it doesn't, we will likely need to see a copy of the model files. The size of the zipped file may be a result of including backup and report files. If you haven't done so already, zip up just the .stsw and .stsw.sqlite files to send to us, then use the steps here to send the files: Sharing Hydraulic Models on the Haestad forum . It would also be good to get a copy of the details of the error message. You can get this by clicking the icon in the lower left of the error dialog you provided as a screenshot. 
 Regards, 
 Scott

Jesse Dringoli · Answer

AHQ - Here are some additional thoughts and ideas to add to Scott's message: 
 1) Can you provide the details of the crash, as seen when clicking the bottom on the lower-left corner? At a glance, I do not see that you have submitted the crash log. You can also do that and let me know, then I can retrieve it based on your email address. 
 Based on the information in your forum post, I suspect the issue may be due to a problem with the newer version reading results saved in the older version. When re-computing the model, new results files will be written, which may be why the problem stopped. Another option would be to try deleting the output files in the same folder as the model. 
 2) This issue could be related to the database cache or the way that the computer's video hardware is rendering the drawing pane. The model's .DWH file stores information about how the model appears in the drawing pane, so if that file was not included when you copied the model to another computer, then the program will regenerate it when opening, which could be a source of the difference in what you see. Try zooming in to an area where the polygons do not look right, and go to File > Database Utilities > Update Database Cache. 
 If this does not help, try updating the video hardware per the below article. You can also try toggling "use accelerated redraw" under Tools > Tools > Options > Global. 
 Updating video drivers and troubleshooting video hardware issues 
 3) Based on the email address associated with your Bentley Communities account, unfortunately I do not see a Service Request in our system. Did you submit it using a different email address? If so, can you provide the Service Request number? In general if the file size is large, first ensure that the files are zipped and that you only include the main two files - .STSW and .SQLITE. If the zip file is still large, you can upload it via our secure Sharefile system. Over Service Request, you can request a Sharefile link. You can also use the link that Scott provided. 
 Regarding the file size in general - the model database size will increase with the number of: 
 a) Model elements b) Support elements (patterns, storm events, conduit catalog entries, etc) c) Scenarios/alternative 
 As Scott mentioned, you can try the compact database option to reduce the size of the SQLITE file. You can also clean out leftover/unneeded alternatives. 
 The .STSW file will increase in size based on the number of presentation settings in the model: 
 a) color coding and annotations b) profile and graph chart option changes c) Various other supporting components 
 If the .STSW file is extremely large, this could indicate that is is somehow bloated with chart option information, similar to what is mentioned here: 
 System.OutOfMemoryException when viewing graphs or saving a model

Jesse Dringoli · Answer

Update: I was able to reproduce the crash in the current version, 10.00.00.45. I was also unfortunately able to reproduce the problem in the soon-to-be-released CONNECT Edition Update 1, 10.01.00.70. So, I will discuss this with our developers. I have also recorded this in your open Service Request. In the meantime though, re-computing should resolve the problem when it arises. Apologies for the inconvenience.

Jesse Dringoli · Answer

Just to circle back to this discussion - the error/crash in question was resolved in the latest cumulative patch set. The issue was related to reading of output/result files saved in an older version. See new related wiki article: 
 "Specified method is not supported" error in model with saved SWMM results form an older version

Jesse Dringoli · Answer

Hello AHQ, 
 Thanks for sending the files. I was not able to reproduce, even in the older version you're using (08.11.05.113). Based on the crash log though, I was able to determine that this is a known issue (770100) that has been addressed in the upcoming CONNECT Edition Update 1 release (due to be available soon - it will have a version number of 10.01.00.XX). It appears to be related to attempting to read old results files, or results for elements that do not have computed values stored in the output files. 
 Do you perhaps have "always compute hydrology" unchecked, under the Analysis menu? 
 If you can provide any specific steps to get the model into the crashing state, that would be helpful in confirming that the issue is indeed resolved in 10.1. In the meantime, re-computing the model should help.

Civil Storm View (catchments)

Top Replies