Pawel, I found a workaround for your issue and I will be logging a report with development to have this issue fixed for a future version of the software, as well as creating a wiki to document the problem/solution. In the meantime, here are the steps you can take to resolve your issue: 1) Go to Analysis > Calculation Options and change the solver from Implicit (CivilStorm) to Explicit (SWMM). 2) Open your flextable for your catchments and add the field called "Drying Time (Days)". 3) Sort your flextable in Ascending or Descending order on this field and change all the values of the catchments that have a 0 to any valve larger than 0. The value can be 0.01 if you want it to be as close to 0 as possible. 4) Go back to Analysis > Calculation Options and change the solver from Explicit (SWMM) to Implicit (CivilStorm). 5) Compute the model again and that should resolve your issue. Regards, Mark
↧
Forum Post: RE: CivilStorm SS4 error: One or more EPA-SWMM catchment failed to compute.
↧
Wiki Page: Is it possible to reproject a model? (Solution 500000056749)
Applies To Product(s): BENTLEY WATERGEMS Version(s): N\A Environment: N\A Area: Modeling Subarea: N\A Original Author: Jesse Dringoli, Bentley Technical Support Group Problem Is it possible to reproject a model (move it from one coordinate system to another) in WaterGEMS, WaterCAD or SewerGEMS? For example migrating from NAD27 to NAD83. Solution First, assess if it may be appropriate to simply Move all the model elements to the new coordinate system location instead of performing a reprojection/transformation. This likely will not be ideal in most cases, as it often needs to be distorted / warped and each type of projection can do this in a different way. For example going from NAD27 to NAD83 in particular has some challenges. For example see the link further below under "See also". As of version 08.11.05.61 (WaterGEMS) and 08.11.05.58 (SewerGEMS), there is no direct tool for performing a Reprojection in standalone or ArcMap integrated mode. However, you can utilize the "Project" tool from Arc Toolbox, if you own Esri ArcGIS. Note that when doing this, you must create a new feature dataset. Unfortunately, this breaks the link between the WaterGEMS database and the geodatabase. Please follow these steps for a workaround: 1) Back up your model. 2) Use the Arc toolbox "project" tool to reproject the WaterGEMS model's associates personal geodatabase. Choose a new feature dataset in the same geodatabase, with a different name. 3) When done, delete the original feature dataset and then rename the newly projected dataset to the old name. You will also need to rename each feature class (PRV, pipe, junction, etc) since a '_1' will be appended to the end. Remove the '_1' from each of these. 4) Close Arc Toolbox and open the geodatabase in a database program such as Microsoft Access. Locate the table named "GDB_ObjectClasses" and note the range of numbers in the "ID" field (the first number at the top, in particular) 5) Close this table and open the table named "WaterGEMSClassMap". You will see a table for "FeatureClassId". Basically, these numbers no longer match up with the ID's you saw in the "GDB_ObjectClasses". You must renumber this field, matching the "FeatureClassId" to the same feature class type (PRV, pipe, etc) from "GDB_ObjectClasses". Most likely, you can simply start with the lowest number you saw in "GDB_ObjectClasses" and increment up from there. 6) Open the project in arcmap. It will appear to be reprojected but in actuality, the WaterGEMS database has not been updated with the new geometry. Export all the layers (pipe, PRV, junction, etc) to shapefiles. This will ensure that labels are exported with it. 7) Close ArcMap and open the .wtg file in WaterGEMS standalone. Run modelbuilder, using all of the exported shapefiles as the source. 8) Uncheck all spatial creation options and choose only the label fields for the table linkings for each element type. This should synchronize just the geometry (x/y) 9) Open the project in arcmap. Both the geodatabase and the Watergems database should be in agreement. In WaterCAD, since you cannot integrate with ArcGIS, you would need to export each element type to a shapefile (via the export button in the flextables), reproject in ArcGIS, then update the geometry using Modelbuilder. See Also http://resources.esri.com/help/9.3/arcgisengine/java/gp_toolref/coverage_toolbox/transforming_between_nad27_and_nad83.htm http://communities.bentley.com/products/hydraulics___hydrology/f/5925/p/7101/10556#10556
↧
↧
Forum Post: Calibrator caculation failed
Hello, I have model that from example of customer, It is poor value for calibrator. , I don't know how to correct bug "' 42513 "Base" "(N/A)" "-1" "(N/A)" 0.000 "An error occurred when trying to calibrate the model. Please check the model for errors." Calibrator Engine" Please help me, thanks!
↧
Wiki Page: Submodel Import/Export
Applies To Product(s): Bentley WaterGEMS, WaterCAD, HAMMER, StormCAD, SewerCAD, SewerGEMS, CIvilStorm, PondPack Version(s): V8 XM and V8 i Environment: N/A Area: N/A Subarea: N/A Original Author: Mark Pachlhofer, Bentley Technical Support Group Overview This technote will show you how to import one model file ("submodel") into another model file ("target"). It is meant to provide clarification and explanation beyond what is given in the Help documentation. Note that this Technote was written for WaterCAD and WaterGEMS but the same concepts apply to HAMMER, StormCAD, SewerCAD, SewerGEMS, CIvilStorm and PondPack (V8i and V8 XM.) Definitions Target Model - The model that is accepting the submodel file. Submodel - The model that is being imported. Network Elements - The elements in your drawing pane that make up your model. These are junctions, pipes, valves, tanks, reservoirs, pumps , hydrants, etc. Rules for Importing Submodels 1. Existing elements in the target model will be matched with incoming elements from the submodel using their labels. 2. Incoming submodel input data will override target model data for any element matched by its label. 3. If a submodel element of the same label does not already exist in the target model, it will be created during the submodel import. Element Types Governed by Submodel Rules The rules for importing submodels govern the following element types: Analysis Menu Scenarios Alternatives Calculation Options Components Menu Controls Pump Definitions Unit Demands Zones Patterns Minor Loss Coefficients Pressure Dependent Demand Funtions GPV Headloss Curves ConstituentsValve Characteristics Time Series Field Data Tools Menu User Data Extensions Hyperlinks Example 1 In this example, the Submodel and Target Model have no elements in common (i.e., scenarios, alternatives, calculation options, and network elements do not match). Town 'A' (The Target Model) In the model illustration below, take notice of the labels for the elements outlined in red: Alternatives e.g., "Year 2000 Active Topology" "Plus Two 18in Pipes," "Diameter times 2") Scenarios (e.g., "Year 2000 Conditions," "Plus Two 18in Pipes") Calculation Options (e.g., "Year 2000 Conditions") Network Elements (e.g., Pipes P-90 and P-60, Junctions J-50 and J-40, Pumps, Reservoirs, Tanks, etc.) Town 'B' (The Submodel) In the model illustration below, take notice of the labels for the items outlined in red: Alternatives (e.g., "Model_B_Active Topology") Scenarios (e.g., "Model_B_Average_Day") Calculation Options (e.g., "Model_B") Network Elements (e.g., Pipes B_Pipe-9 and B_Pipe-11, Junctions B_Junc-7 and B_Junc-6, Pumps, Reservoirs, Tanks, etc.) Result of Importing Submodel into Target Model In the illustration below, the target model network elements are visible on the left, and the imported submodel network elements are outlined in red on the right. Since the target model elements have no label names in common with the submodel elements, all of the submodel elements will be created the target model, according to rule 3 above. None of the data in the target model will be overwritten in this case, since there were no matching labels. Observe how the scenarios, alternatives, calculation options, and element labels for all the submodel items have been brought into the target model (see red outlined areas). For example, for the Active Topology alternatives, all of the submodel's (Town 'B') network elements have come in as inactive for the original "Year 2000 Active Topology." The reason is because the newly imported elements did not previously exist in that alternative, so the default attributes are used. In the case of active topology, the default is inactive. So, the newly imported elements are inactive in the "Year 2000 Active Topology" alternative. In the case of the physical alternative, if the submodel's physical alternatives don't match the target model's, the default physical attributes will be used for the newly imported elements, for the physical alternatives that already existed in the target model. So in this example, since the physical alternative in the submodel ("Model_B_Physical") doesn't exist in the target model, it was brought in as a new alternative. So, the pipes from the submodel in the scenarios that use the "Year 2000 Physical" will have 6" diameters and junctions will have zero elevations and so forth. In order to see the original attributes of the submodel elements, the scenario would need to use the "Model_B_Physical" physical alternative. Example 2 In this example, the submodel and target model have some elements in common (i.e., scenarios, calculation options, and network elements J-100, J-210, and P-250). Town 'A' (The Target Model) In the model illustration below, take notice of the labels for the items outlined in red: Alternatives (e.g., "Year 2000 Active Topology" "Plus Two 18in Pipes," "Diameter times 2") Scenarios (e.g., "Year 2000 Conditions," "Plus Two 18in Pipes") Calculation Options (e.g., "Year 2000 Conditions") Network Elements (eg., Pipe "P-250" and Junctions "J-100" , "J-210") Town 'B' (The Submodel) In the model illustration below, take notice of the labels for the items outlined in red: Alternatives (e.g., "Model_B_Active_Topology") Scenarios (e.g., "Year 2000 Conditions") Calculation Options (e.g., "Year 2000 Conditions") Network Elements (eg., Pipe "P-250" and Junctions "J-100" , "J-210") Result of Importing Submodel into Target Model In this model below we have connected the submodel (right) network to the target model network (left) at junctions J-100, J-210, and pipe P-250 (center). This connection occurs because both models shared some of the same junction and pipe labels as import rule 2 states. The submodel data is therefore going to overwrite the existing target model data in any items governed by the rules that are common to both models (illustrated below). You can see that for both the submodel and target model there is also a common scenario name. If any of the properties for this scenario were different the submodel properties for this scenario would overwrite the properties for the target model. Above we see the target model network has all become inactive except for the junctions and the pipe that are shared by both models. This happens because the submodel data is overwriting the scenario data for the 'Year 2000 Conditions' scenario (import rule 2). In the illustration below, Town 'A' Demands and Pipe Diameter before the import are outlined in red Junction Demands Pipe P-250 Diameter J-100 = 19.60 gpm 6 inches J-210 = 72.60 gpm In the illustration below, Town 'B' demands and pipe diameter before the import are outlined in red Junction Demands Pipe P-250 Diameter J-100 = 72.0 gpm 8 inches J-210 = 40.0 gpm In the illustration below, pipe size and junction demands after the import are outlined in red Junction Demands Pipe P-250 Diameter J-100 = 72.0 gpm 8 inches J-210 = 40.0 gpm Example 3 In this example, the submodel and target model share all of the same network elements but, none of the same scenarios, calculation options, or alternatives. Town 'A' (The Target Model) In the model illustration below, take notice of the labels for the items outlined in red: Scenarios Calculations Options Alternatives Average Day Demand Average Day Conditions Average Day Fire Flow Fire Flow Fire Flow Constituent Analysis Constituent Constituent Alternative - 1 Town 'A'_2 (Submodel) In the model illustration below, take notice of the labels for the items outlined in red: Scenarios Calculation Options Alternatives Peak Conditions Peak Condtiions Peak Peak Times 2 Peak Times 2 Result of Importing Submodel into Target Model In the model below we can see the import of the submodel results in all the network elements remaining the same because all these elements had the same labels. Hypothetically, if any of the properties of the network elements were different in the submodel from the target model the properties of the result would contain the values that were contained in the submodel (import rule 2). The significant change that happens in this model, much like in the first example, is that the scenarios, alternatives, and calculation options from the submodel all get added to the target model without overwriting anything. In the model illustration below, take notice of the labels for the items outlined in red: Scenarios Calculation Options Alternatives Average Day Demand Average Day Conditions Average Day Fire Flow Fire Flow Fire Flow Constituent Analysis Constituent Constituent Alternaitve - 1 Peak Conditions Peak Conditions Peak Peak Times 2 Peak Times 2 Steps for completing a Submodel Export/Import 1) Open the model that you want to export the submodel part from. 2) Select the part (or entire) model that you want to export. This can be done in many ways. Three common ways are by using your mouse to draw a box around certain areas, using your mouse to left click and select one element or multiple elements while holding down the shift key, or by holding down the CTRL key + A , which will select all the elements on screen. The default color for selected elements is red. 3) With the elements selected in the display panel go to File > Export > Submodel. Name and save your model to a location that you will remember. 4) Now open your target model and after it load go to File > Import > Submodel. Note: if you would like to import the entire model and not a subsection of the model, only step 4 is required. Meaning, in the target model, simply go to File > Import > Submodel, then select the .wtg.mdb file associated with the submodel you would like to import. Troubleshooting If you know you imported the model but don't see anything or are missing part of the model on in your display area. Answer: Go to Tools > Options and see if the option on the Global tab for "Display Inactive Topology" is checked. Also notice the color the inactive topology is set to. If all or part of the model you imported is gray Answer: Your model has likely imported correctly but, all or part of it is currently inactive. If you want it to appear as an "active" status element the active scenario you have to use the active topology tool (Tools > Active Topology Selection) or go into the active topology alternative and change the status of the inactive elements. The reason this happens is because the active topology alternative in the submodel did not match the target model. So, the default status of inactive is used. If you do not want to manually change this in the resultant model, you will need to first go back to the target model and change the labels and structure of the active topology alternatives, so that they match between the models. The attributes/data from the submodel were lost Answer: If the properties of the submodel elements appear to use the default values (such as 6" for all diameters, zero elevation, etc), most likely the physical alternative(s) in your submodel did not match the physical alternatives in the target model. You will either need to correct this manually, or go back to the target model and change the labels and structure of the alternatives so they match exactly to the target's What if models have same labels? Answer: If models have same labels such as P-1 in Project A and P-1 in Project B as well, then the tool from the link below can be used to prefix the Labels before importing. Once the import process is done, the prefixed label can be removed too. http://communities.bentley.com/other/old_site_member_blogs/peer_blogs/b/akshayas_blog/archive/2013/07/11/update-labels-of-a-hydraulic-model-using-waterobjects-net.aspx See Also Product TechNotes and FAQs Haestad Methods Product Tech Notes And FAQs External Links Water and Wastewater Forum Bentley Technical Support KnowledgeBase Bentley LEARN Server
↧
Forum Post: RE: Darwin Designer considering fire flow?
Hello Ahmed, For item 1, what demands are you applying to the model? You will not want to apply the extra fire flow demand to each junction, but rather apply the fire flow demand at the most important part of the model (i.e., where fire flow demands are most important). Please see the Help documentation for additional information on this. For item 3, you may need to apply the information in the customer meter directly to the junctions. You may want to use LoadBuilder to apply the data to the junctions instead of customer meter elements. Regards, Scott
↧
↧
Forum Post: RE: Calibrator caculation failed
I have model that from customer, I want to calibrate base on some SCADA signals of pressure which I was given. But I can't do that because it appear that "' 42513 "Base" "(N/A)" "-1" "(N/A)" 0.000 "An error occurred when trying to calibrate the model. Please check the model for errors." Calibrator Engine". Please help me how can I check this bug,
↧
Wiki Page: How can I use the customer meter element demands with Darwin Calibrator?
Applies To Product(s): Bentley WaterGEMs, Bentley WaterCAD, Bentley HAMMER Version(s): 08.11.05.61 Environment: N/A Area: Modeling Subarea: Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem Description How can I use the customer meter element demands with Darwin Calibrator? Or How can I take demand data from customer meter elements and enter it quickly into my other node elements, such as junctions, hydrants, or tanks? Steps to Resolve With the initial release of SELECTseries 5, Darwin Calibrator and Darwin Designer only considered demands that were placed on a junction, hydrant, or tank elements. An update was made available after release, to support the use of the Customer Meter element with Calibrator and Designer. Without this patch, demands from customer meters will not be considered in Calibrator or Designer. This update will be available in the next release and in SELECTseries 5 cumulative patch sets dated after December 2014. For information on downloading cumulative patch sets, please see the below article. If further assistance is needed, please contact technical support or post to the Hydraulics and Hydrology forum. How do I download WaterGEMS, WaterCAD, HAMMER, SewerGEMS, SewerCAD, CivilStorm, StormCAD, PondPack, FlowMaster, CulvertMaster Alternative Updating your version/patch is the ideal solution, but if you would like to convert your customer meter demands to junctions, consider the below steps: 1) Download the attached Excel spreadsheet https://bentley.sharefile.com/d/sc3b67ab5c9948139 2) Open it and become familiar with it 3) Open Modelbuilder (Tools > Modelbuilder) and on step 1 choose Excel 2013/2010/2007 (12.0) as the data source type then click the next button. 4) On step two set accept the defaults because this information will not matter for what we are doing. Do the same thing for steps 3 and 4. 5) The field matching you do for step 5 will depend on what information you have entered in your customer meter element. In the screen shot below the example shows how you would go about doing the field matching for most properties of the customer meter element. If you only need to export certain information like customer meter Label and Demand (Base) you don't need to field map all the other columns. 6) On step 6 when asked if you "Would like to build a model now?" choose 'No' and hit the Finish button. 7) On the main Modelbuilder manager make sure the new sheet you created is highlighted in blue by single clicking on it and then hit the "Sync Out Button", which is the button to the left of the question mark icon (Help Button). This will export all your customer meter information to your spreadsheet. 8) Now double click on the Modelbuilder run you created to reopen the Modelbuilder Wizard. Follow the directions in this wiki that explains how to import demands from a spreadsheet to you node elements. https://communities.bentley.com/Products/Hydraulics___Hydrology/w/Hydraulics_and_Hydrology__Wiki/importing-demands-from-a-spreadsheet
↧
Forum Post: RE: Darwin Designer considering fire flow?
Ahmed, Re: item 3 - Please see the below Support Solution for details on an update to SELECTseries 5 to enable the use of the customer element with Darwin Calibrator and Designer: communities.bentley.com/.../17483.how-can-i-use-the-customer-meter-element-demands-with-darwin-calibrator
↧
Wiki Page: Problems running query in SCADAConnect using GE iHistorian
Applies To Product(s): Bentley WaterGEMS Version(s): 08.11.05.61 Environment: N\A Area: Calculations Subarea: N\A Original Author: Terry Foster, Bentley Technical Support Group Problem Description Why am I not getting results for query in SCADAConnect when connecting to iHistorian? I get the following error message: Error Message: 'IhOLEDB.iHistorian.1' failed with no error message available, result code: DB_E_NOTABLE(0x80040E37).Error Details: System.Data.OleDb.OleDbException: 'IhOLEDB.iHistorian.1' failed with no error message available, result code: DB_E_NOTABLE(0x80040E37). at System.Data.OleDb.OleDbCommand.ExecuteCommandTextErrorHandling(OleDbHResult hr) ... Or: **ERROR** API Error: DATA RETRIEVAL COUNT EXCEEDED API Error: DATA RETRIEVAL COUNT EXCEEDED Steps to Resolve iHistorian uses a different SQL syntax than what is used in SCADAConnect and therefore was not fully supported as of the initial release of v8i SELECTseries 5 An enhancement is now available as a patch to SELECTseries 5, adding functionality and support for iHistorian to WaterCAD and WaterGEMS. This functionality will be included in the next release. If you are using SCADAConnect with iHistorian, and using WaterGEMS SELECTseries 5, please contact our technical support group for the patch. See Also
↧
↧
Wiki Page: What are the differences between StormCAD and CivilStorm? When should I use StormCAD instead of CivilStorm?
Applies To Product(s): Bentley SewerGEMS, Bentley CivilStorm, Bentley StormCAD Version(s): 08.11.XX.XX Environment: N/A Area: Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem What are the differences between StormCAD and CivilStorm? When should I use StormCAD instead of CivilStorm? Solution StormCAD uses the rational method to calculate peak flow in a system based on peak rainfall intensity, while CivilStorm takes rainfall hyetographs (rain vs. time) and develops hydrographs (flow vs. time) for each pipe and routes the flows dynamically. If you are studying a small area where only peak flow is of interest, or if you need to design a system based on the standard rational method, then StormCAD should be adequate. If you are working on a large area where hydrograph routing and storage are significant, where you need to use a dynamic solver, or if you need to otherwise analyze more complex effects such as flooding and controls structures, then CivilStorm (or SewerGEMS) is what you need. If you get involved with combined sewers where rain and sanitary sewage is carreid in the same pipe, we recommend you use SewerGEMS. The primary difference between StormCAD and CivilStorm is that StormCAD is used to analyze and design a system based on peak rainfall intensity while CivilStorm takes rainfall hyetographs (rain vs. time) and develops hydrographs (flow vs. time) for each pipe, with the ability to handle more complex effects. See Also StormCAD FAQ What is the difference between SewerCAD, SewerGEMS and SewerGEMS Sanitary? What is the difference between SewerGEMS and CivilStorm?
↧
Forum Post: RE: Calibrator caculation failed
It sounds as if you received the model and used Darwin Calibrator. Model calibration consists of two steps: 1. Determining the source of poor calibration and 2. making adjustments to make the model calibrated. Darwin is great for step 2. In my experience 95% of the work in calibration is in step one. Before you think about using Calibrator, you need to make dozens of simulation runs with the different scenarios you will use to 1. make sure the models are stable, 2. identify which parameters the model is sensitive to, 3. look for inconsistent/inaccurate field data, 4. eliminate gross errors in the model due to incorrect connectivity and closed valves, 5. ensure that the elevations of the pressure sensors are correct and 6. generally get a feel for the model. Only after you are sure that you have identified the source of model error should you try to make adjustments using Calibrator. Best wishes in your work, Tom
↧
Wiki Page: How is the headloss for a weir calculated in the control structure for the storm and sewer products?
Applies To Product(s): Bentley SewerGEMS, Bentley SewerCAD, Bentley CivilStorm Version(s): 08.11.xx.xx Environment: N\A Area: Modeling Subarea: N\A Original Author: Scott Kampa, Bentley Technical Support Group Problem Description How is the headloss for a weir calculated in the control structure for the storm and sewer products? How is the headloss for a submerged weir calculated? Steps to Resolve The solver uses the traditional weir equation and the effective head, which is the difference between upstream and downstream water elevation (or downstream and upstream, if flow is reversed), to calculate the weir flow. If the weir is not submerged the effective head is the difference of water elevation and weir crest elevation. Because of the assumptions of this calculation, the headloss for a submerged weir is not calculated. If you need to make adjustments to compensate for headloss, you can adjust the weir coefficient.
↧
Wiki Page: "Objects reference..." error when trying to change scenarios
Applies To Product(s): Bentley SewerCAD Version(s): 08.11.03.84 Environment: N\A Area: Other Subarea: N\A Original Author: Terry Foster, Bentley Technical Support Group Error or Warning Message Object reference not set to an instance of an object or 05/27/2015 09:24:21.42 System.NullReferenceException: Object reference not set to an instance of an object. at Haestad.Domain.ModelingObjects.DomainElementManagerBase.SupportedFields() at Haestad.Mapping.Support.ElementSymbologyDefinitionManager.FieldAt(FieldNameProperties fieldName, IDomainElementManager manager) at Haestad.Mapping.Support.ElementSymbologyAnnotationDefinitionManager.ApplyAnnotation(IDomainProject project, ElementSymbologyAnnotationDefinition annotationDefinition, HmIDCollection& elementIds, IFeatureAnnotationManager featureManager, IDomainElementManager manager, AnnotationActionType action, HmIDCollection allElementIds) at Haestad.Mapping.Support.ElementSymbologyAnnotationDefinitionManager.RefreshAnnotation(IDomainProject project, ElementSymbologyAnnotationDefinition annotationDefinition, IFeatureAnnotationManager featureManager, IDomainElementManager manager, HmIDCollection allElementIds) at Haestad.Mapping.Library.MappingLibrary.RefreshDrawing(IMappingProject project, IFeatureManager featureManager, ElementSymbologyManagerCollection elementSymbologyManagerCollection, Boolean refreshFlowArrows) at Haestad.Mapping.Library.MappingLibrary.RefreshDrawing(IMappingProject project, IFeatureManager featureManager, ElementSymbologyManagerCollection elementSymbologyManagerCollection) at Haestad.Drawing.Domain.LayoutControllerBase.RefreshDrawing() at Haestad.StormSewerProduct.Drawing.StormSewerProductLayoutController.ScenarioEventChannel_ScenarioChanged(Object sender, ScenarioChangedEventArgs e) at Haestad.Framework.Support.ScenarioManagerChangeHandler.Invoke(Object sender, ScenarioChangedEventArgs e) at Haestad.Framework.Support.ScenarioEventChannel.OnScenarioChanged(Object aobject, ScenarioChangeType changetype, Int32 scenarioid, Int32 previousScenarioId) at Haestad.Framework.Support.ScenarioEventChannel.NotifyScenarioChanged(Object aoSender, ScenarioChangeType changetype, Int32 scenarioid, Int32 previousScenarioId) at Haestad.Framework.EditorModel.UndoableScenarioMakeCurrentAction.DoSucceeded() at Haestad.Framework.Support.UndoableActionBase.DoAction(IUndoableActionManager aundoableActionManager) at Haestad.Drawing.Control.Library.DrawingLibrary.DoScenarioChange(IDomainProject domainProject, IFeatureManager featureManager, ScenarioEventChannel scenarioEventChannel, Object ownerWindow, Int32 scenarioID) at Haestad.Drawing.Control.Forms.GraphicalDrawingParentForm.DoScenarioChange(Int32 newScenarioId) at Haestad.Drawing.Control.Forms.GraphicalDrawingParentForm.ComboBox_SelectionChangeCommitted(Object sender, EventArgs e) at System.Windows.Forms.ComboBox.OnSelectionChangeCommitted(EventArgs e) at System.Windows.Forms.ComboBox.OnSelectionChangeCommittedInternal(EventArgs e) at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m) at System.Windows.Forms.ComboBox.WndProc(Message& m) at TD.SandBar.FlatComboBox.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) Explanation When user tries to change scenarios, they get the error. How to Avoid Option 1 This is usually due to the "Invert (Start)" conduit annotation. Edit the annotation and click Apply, then OK, and the problem no longer occurs. Option 2 Upgrade to the latest build of the software. See Also How do I download the water and storm sewer products?
↧
↧
Forum Post: RE: Calibrator caculation failed
Thanks Dr.Tom Walski I calibrated successfully, I export to scenario, alternative in order to run hydraulic. Unfortunately, It is so different HGL between Darwin results and hydraulic model results. How can I explain this issue? Regards, Dang
↧
Forum Post: RE: Calibrator caculation failed
This is where you as a hydraulic engineer need to review the model and data and determine WHY the model and the field data don't agree. This part is mostly detective work. There are many reasons why the model and field data don't agree. You need to go through them and eliminate possible reason until you determine the source of the problem.
↧
Forum Post: RE: Calibrator caculation failed
If you're saying that you already calibrated the model and got good agreement between the model results and field data and are now trying to see the same results in the model itself that Calibrator provided, please take a look at the below Support Solution: communities.bentley.com/.../18867.how-do-i-match-the-results-i-am-getting-from-darwin-calibrator-in-my-model
↧
File: DimensionlessHuff_50_400_3Q_50%
Huff distribution - 50 400 3Q 50%
↧
↧
File: DimensionlessHuff_10_50_2Q_50
Huff distribution 10 50 2Q 50%
↧
Wiki Page: Dimensionless Huff 10-50 2ndQ 50% and 50-400 3rdQ 50% distributions throw an index was outside the bounds of the array error
Applies To Product(s): Bentley PondPack Version(s): 08.11.01.56 Environment: N/A Area: Layout and Data Input Subarea: Original Author: Mark Pachlhofer, Bentley Technical Support Group Problem Description When I try to use a dimensionless Huff 10-50 2ndQ 50% or 50-400 3rdQ 50% distribution I get an error message that says, "System.IndexOutOfRangeException: Index was outside the bounds of the array." error. Reason This is caused by these particular distributions in your engineering libraries not containing any data. Steps to Resolve Use the information below and copy then paste the information in to the collection Go to Components > Engineering Libraries Expand the 'Dimensionless Rainfall Curves' library by clicking the plus sign (+) to the left of it Expand the Bul70-71.xml library by clicking on the plus (+) sign Locate the appropriate distribution and click on it. You will notice there is information populated on the right side of the dialog box. On the right side of the dialog box click on where you see . You should now see an ellipsis. Click on it. Now you can download either file from here and copy and paste in the depth results. Huff Distribution 50 400 3Q 50% Huff Distribution 10 50 2Q 50% See Also Modifying and adding items to an engineering library
↧
Forum Post: RE: How to create a Selection Set from Excel
Hi, I tried the first option in WaterGems but it did'nt work, even for one pipe. For example: Label IN (P-24) * P-24 is pipe label When I press "Apply" I receive the following error: "there was an error with the expression. 1: no such column: P" Is there any rule that I have not consider? Thanks
↧