HLR Section 8
Defaults & Customisation Options
CONTENTS
| 8.1 General Program Defaults 8.2 Directory Paths 8.3 Load Effect Factors 8.4 Dynamic Load Allowance (DLA) Relationship 8.5 Vehicle Phi Factors 8.6 Vehicle Reduction Factors 8.7 Customise Headings in the Summary Report 8.8 Customising Maps Used for Route Selection
| Other Links: | Main Index | Analysis | Structure Data | Vehicle Data |
8.1 General Program Defaults
| HLR allows a large number of parameters to be customised for site-specific conditions. The program defaults shown below can be set and saved for all future HLR runs:
| 8.1.1 General Default Settings Values entered into these fields will be automatically loaded into the system at run time. However, they can also be changed and used in the current run (if OK is clicked) or saved to the defaults database for future reference (by clicking Save Settings to Defaults File).
| Standard lane width - by default set to the Austroads BDS value of 3m Maximum overall vehicle width and height - for validating clearances during data entry Vehicle Reduction Factor - refer to Section 8.6.1 and Section 6.1.7 for a description of this factor. Ultimate Limit State Factor - also referred to as the ultimate load factor (see below) Working Overload Factor - often referred to as the Working Overstress Factor (refer to Section 6.2.1, Item 8 for further details as to how this factor is used within HLR)
| 8.1.2 Ultimate Limit State Factor Changes made to this factor will only be reflected in the Analysis Options form if the values are saved to the Defaults File. If only the OK button is clicked, the value in this field will not supplant the parameter in the Analysis Options tab (see Section 6.1 for further details). 8.1.3 Working Overload Factor The Working Stress Overload Factor found on the Analysis Options panel is normally set to the default value shown on this form (140%), although HLR allows it to be varied from 100% to 140%. If the WSO factor is left at the default value specified here-in the program will simply use the full working stress overload capacity when performing the moment comparison checks i.e., no further factoring will be performed. If, however, the Working Stress Overload Factor on the Analysis Options panel is changed to a value between 100% and 140%, HLR will linearly interpolate between the basic allowable capacity and the full overload capacity. If the default value on this form is changed from the standard 140% no factoring of moments will occur. Refer also to Section 6.2.8, Item 8, for a more detailed explanation of this factor and the way in which it is used. 8.1.4 Standard Design Vehicle This window simply displays a list of currently available design vehicles. Note that standard Design Vehicles cannot be created, edited or deleted at this point. If you wish to do so use the Vehicle option in the menu bar. (Refer also to Section 4.4 for instructions). 8.1.5 Number of Vehicle Movement Increments Vehicles are moved across continuous structures in increments that are based on the overall length of the bridge. After each increment a continuous beam analysis is performed and the results are then enveloped. The vehicle movement increment, Xi, is calculated as follows: Xi = Total length of bridge / (Number of increments per span * Number of spans) By default the number of increments per span is set to 50. If spans differ significantly in length the shorter spans will consequently have far fewer increments than the longer spans. For geometrically symmetrical structures, or for uni-directional travel only, this may not pose a problem. However, in structures that have significantly different end (or internal) span lengths the moment envelopes for travel in the forward and reverse directions may be quite different. In such cases you may have to change the number of increments per span. 8.1.6 Analysis Option
| Stop at restricted bridges - During the analysis this flag forces the system to stop when a restriction is encountered.
| Always use default distribution factors in the analysis - This flag forces the system to use the default distribution factors in the analysis, irrespective of whether a structure-specific DF table exists. (Refer to Section 8.3, Load Effects Factors).
| Use reduced axle loads in analysis - For vehicles with axle widths greater than the standard lane width this flag will force the system to use reduced axle loads in the analysis (refer to Section 4.2 (Vehicle Data) and Section 6.2 (Assessment Methodology) for further details).
8.1.7 Load Effects Labels This option enables four load effects labels to be customised to your own requirements. The first three labels relate to the calculated vehicle effects (M1, M2 and M3), while the fourth represents the label associated with the Working Overload moment capacity. These labels appear on both the results preview panel and various output reports. Because of limited space on these reports the length of each label has been restricted to the following
| M1 label | 19 characters
| M2 label | 17 characters
| M3 label | 17 characters
| Overload label | 8 characters
The Overload label is principally used for labelling the Working Overload moment capacity field in the structure data entry form. The three labels beginning with the letter 'M' appear in the Summary Report, the two detailed analysis reports and the Load Effects Factors tab. 8.1.8 Width Modified Axle Load Factors For an explanation of this function refer to Section 4.2.2 of the User Manual. The width-modified axle load factors can be preset in this tab to suit your own requirements viz:
| W1 | Transition axle width
| C1 | Width factor for axle widths up to W1
| C2 | Width factor for axle widths greater than W1
8.1.9 Flag to indicate if key Job ID data must be entered This flag will force HLR to check that key job ID data is entered when processing a new HL Application and key structure data is supplied when entering or editing structure data. 8.1.10 Flag to indicate if the total number of assessed structures is to be included in the Summary Report If ticked this flag will ensure that the check box on the Reports form is automatically ticked when the program is run. Note that the tick box on the Reports form controls whether the total number of structures appears on the Summary Report or not. This option merely sets the default state of that flag when the program is first started.
8.2 Directory Paths
| This tab allows you to view the full directory path specification for the following system components: Program files Temporary files (required if networking) Database files On-line Help files Location of the internet browser (used to display help information) Location of a wordprocessor / editor (used to display & edit the Summary Report)
| All directory paths with the exception of the first two (Program files and Temporary files) can be changed by either entering a new path specification or by clicking the Browse button. Note that the paths for Program files and Temporary files can only be changed outside of the HLR environment by editing the text file Defaults.txt (usually located in the Windows Program Files directory).
8.3 Load Effect Factors
| The expressions used to determine the moment and shear effects due to the heavy load vehicle are based on a number of empirical factors. These factors include: The dynamic load allowance factor (DLA) Effective girder spacing (Gspacing) The limit state factor (LSF) The girder distribution factor for 10kph & unrestricted travel speed The girder distribution factor for 5kph travel speed
| This form enables the default Dynamic Load Allowance factors (DLA1, DLA2, DLA3) and Girder Factors (GF1, GF2, GF3) to be specified.
| Refer to Section 6.2 (Assessment Methodology - Moment capacities exist) and Section 6.3 (Ratio Method - Moment capacities unavailable) for a detailed discussion as to how these factors are used. If any of the factors are modified, be sure to click the button marked Save Settings to Defaults File. This will ensure that they are used both in the current run and when HLR is accessed in the future. Refer also to Sections 5.3, 6.6 and 8.4 for details relating to DLA Factors and to Section 5.3 for information relating to the girder spacing (Gspacing).
8.4 Dynamic Load Allowance Relationship (DLA)
| The DLA-Frequency Curve form is used to define the default dynamic load allowance factor (DLA 1) for the heavy load vehicle travelling at unrestricted (open road) speed. It is based on a modified form of the 1998 Austroads Bridge Design Specification viz., where the BDS has only a single f - DLA "hump" the default relationship incorporated into HLR has two "humps". The relationship is entered into the table as pairs of DLA - structure frequency values and may be changed to suit local requirements. During analysis, HLR will extrapolated a DLA factor from this table if the default DLA1 is set to zero in the Load Effects Factors tab and the structure-specific DLA factor is also zero. (Refer to Section 6.6 for further information). If you do modify the DLA/Frequency table, be sure to click the button marked Save Table. This will ensure that the new relationship is used during the present, and all future, analyses. (Note: The DLA/Frequency table is stored in an ASCII text file called DLA-Freq.dat located in the same folder as the main program executable).
8.5 Vehicle Phi Factors
| Phi factors are only used in the Ratio Method of analysis and represent the effect of DL in a structure. (Refer to Section 6.3 for a detailed description of the use of Phi factors in the Ratio Method). They may be edited to suit local conditions via the Options/ Vehicle Phi Factors tab form. Note that if the values in the table are modified, you must click the button marked Save Table to ensure that the new relationship is used both during the present, and all future, analyses. Note that HLR will automatically set the factors for AASHO and MS18 design vehicles to those of the HS20 (so there is no need to create a separate entry for these two vehicles in the table). A default phi factor of 10,000 will be used if the design vehicle does not exist (this will ensure that the DL effect is ignored in the analysis). If additional (or different) structure types are to be added to the table it will be necessary to edit the ASCII file Phi-Fact.dat using a text editor (such as Notepad). Care must be taken to adhere to the format shown in the file. Also, check if any other dependant values need to be modified (such as the number of structure types and the number of design vehicles). Manual editing is recommended if you wish to replace one or more default vehicles/structure types with your own. The table can only accommodate a maximum of 10 Design Vehicles.
8.6 Vehicle Reduction Factors
| 8.6.1 Vehicle Load Reduction Factor This factor is set in the Default Settings tab (refer to Section 8.1 above). For a complete description of this factor refer to one of the following sections: Section 5.2.8 - This section describes how the factor can be suppressed for certain structures; Section 6.1.7 - This section describes how and where the run-time factor is specified; Section 6.2.1(9) - This section describes how the run-time factor is applied during the analysis;
| 8.6.2 Reduction Factors for NT Structures These factors have been provided to allow a particular class of single-lane timber bridge unique to the Northern Territory to be more realistically analysed. (Refer also to Section 6.5 for more detailed information regarding its application during analysis). They may be edited to suit local conditions via the Options/ NT-Factors tab form. Note that if the values in the table are modified, you must click the button marked Save Table to ensure that the new relationship is used both during the present, and all future, analyses. If additional values are to be added to the table it will be necessary to edit the ASCII file NT-Fact.dat using a text editor (such as Notepad). Care must be taken to adhere to the format shown in the file and to any other values that must be modified (such as the number of points defining the curve).
8.7 Summary Report Headings
| This form allows the first eight heading lines in the Summary Report to be customised. It is accessed via the main menu bar "Options / Summary Report Headings". An example is shown below:
| Heading text can be modified, added and deleted from the eight displayed lines. However, the existing lines themselves cannot be deleted nor new lines inserted or added. If, for example, you wish to "delete" line 2 simply delete the text in line 2 (but don't delete the label "LINE 2:" ). A blank line will be inserted in its place in the Summary Report. Default headings are saved to a text file called Default Summary Report Headings.txt in the HLR4 directory.
8.8 Customising Maps Used for Route Selection
| 8.8.1 Introduction Customised maps are used for point-and-click, GIS-style, route selection. Two types of maps are recognised by HLR. The first is the Main Index Map (often referred to as the Main Map or Index Map) and all others are sub-sets of it (referred to as Submaps). Both map types allow point-and-click navigation via predefined "hot-spot" areas and are structured and operate identically. The map-based route selection system may be customised to suit your own unique requirements by replacing the default TSA map image files stored in the ..\Database folder with your own images and modifying the associated Map Cross Reference Index.txt text file accordingly. The information given in this section will instruct you how to do this. Please note that when editing, and/or adding to, the Map Cross Reference Index.txt text file you must adhere to the basic structure and format in which the file exists in the database. All lines down to, and including, #MAP DATA... must be retained as-is. Everything below this line can be deleted and replaced with your own map and hotspot reference data. 8.8.2 Map Details Map files must be JPEG images created and sized in a way that fits the available image window area. On a 17" monitor running at a resolution of 800x600, TSA have found that images 540 pixels deep (measured from top to bottom) by 685 pixels wide (left to right) fit exactly into the picture drawing area. When running at higher resolutions both the map window and all maps will be proportionally reduced in size. However, three additional sets of maps have been manually rescaled and added to the map database. They are for the three standard screen resolutions of: 1024x768, 1280x960 and 1280x1024 (refer also to Clause 8.8.8 for details). There is no provision in this version of HLR to automatically adjust the map size to fill the available screen area. The reference point (or origin) of the map drawing window is the top left corner of the drawing area and the reference point of the picture (i.e. the map) is the top left corner of the JPEG image. Therefore, if the image is deeper or wider than the drawing window (i.e. greater than 540 x 685 pixels) it will be truncated either at the bottom or at the right hand side (or both - the image is not centered in the drawing window). Map files at 800x600 resolution are saved to the ..\Database folder using the naming convention Map-XX.jpg where 'XX' represents a unique submap number. It need not be a 2-digit number, although from a map management point of view it might be preferable if the number lies in the range 00 - 99. The name must begin with the word Map- and must be an image saved in the JPEG format (i.e. it must end with the suffix .jpg), otherwise it will not be recognised by HLR. For the other three standard resolutions the map name must conform to the convention: Map-XX-1024x768, or Map-XX-1280x960 or Map-XX-1280x1024. In summary:
1. All map names must begin with Map- and must be saved as .jpg files 2. The internal name separator must be a dash symbol (not the underscore). 3. The main index map must be designated as 'Map-00.jpg', or 'Map-00-1024x768.jpg' etc.
8.8.3 Tips and Hints for Creating Digital Maps Maps need only be as detailed as required to easily identify a route. They can start at a very large, state-wide scale, then cascade down to increasingly higher levels of local detail. All TSA database maps were created by taking digital still photographs of existing wall maps then editing them using Paintshop Pro, a proprietary image editing package. The software allows maps to be colour enhanced, resized, touched up, edited and saved as JPEG images. Map images were edited to slightly greater than 540 x 685 pixels in size and annotated with route and node details as shown in the images given below. A small amount of trial and error was necessary in each case in order to ensure that maps represented the required area, that they properly fitted into the window drawing area and that hot-spots representing node, route and submap numbers did not clash. Editing TSA maps: To change, modify or edit any of the TSA maps in the database use the original digital photos and images stored on the server in the folder called: L:\HLR Backup Files\Photos of Maps. When editing the maps, do so using the Paintshop Pro package and always operate on the .psp files. Node and route numbers are generally stored in Paintshop Pro in one layer, route lines are stored in another layer and the original digital map forms the first (base) layer. Every drawing attribute is treated as an object that can be individually scaled, painted, moved and edited. Once you have made the required changes save the modified image as a .psp file first and only then as a .jpg file. Do not save the image in the reverse order - you won't be able to preserve the edits (they will effectively be lost!). Finally, copy the edited .jpg maps over to the L:\HLR4\Database folder, delete the corresponding Map-XX.jpg files then rename the edited files to their Map-XX.jpg equivalents.
| 8.8.4 Hotspots & the Map Cross Reference Index File Hotspots represent areas on a map that, when clicked, result in some action being taken by the program viz: another map is displayed, a node or route is registered and so on. HLR recognises three types of hotspots:- maps, routes and nodes (represented, respectively, by the letters M, R and N). Hot-spots are defined by pairs of X and Y offset ratios that delineate an active rectangular "clickable" region. The X and Y ratio pairs represent proportional distances that are measured, respectively, from the left window edge and top window edge of the form to the boundary lines defining the hot-spot area. The diagram below illustrates this concept a little more clearly. X1 and X2 define the location of the left and right vertical boundaries of the hotspot representing Submap 1 and Y1 and Y2 the location of its horizontal boundaries. Although the hot-spot in this case has been enlarged to represent the full extent of the submap area, it could just as easily have been restricted to the vicinity of the submap number only. The extent for X1, X2, Y1 and Y2 is purely arbitrary and only depends on the sensitivity you wish to assign to the hot-spot area.
| Offset values X1, X2, Y1 and Y2 are converted to ratios by dividing each value by W and H respectively, producing four numbers that must be less than unity (Rx 1, Rx 2, Ry 1, Ry 2). They are then entered into the Map Cross Reference Index.txt file using the format: Current map number, Hotspot Type, Target Submap Number, Rx 1, Rx 2, Ry 1, Ry 2 A sample of one small part of the index file layout is given below. Referring to the first line following #MAP DATA" as an example, "00" represents the map number currently being displayed, "M" represents the Hotspot Type (a map), "01" indicates the Target Submap Number that is to be displayed if the user clicks on this hotspot, and the remaining numbers define the extent of the hotspot area (Rx 1=0.27, Rx 2=0.55, Ry 1=0.67, Ry 2=1.00).
#MAP DATA "00", "M", "01", 0.27, 0.55, 0.67, 1.00 "00", "M", "02", 0.27, 0.31, 0.50, 0.67 "00", "M", "02", 0.31, 0.41, 0.60, 0.67 "00", "M", "03", 0.43, 0.60, 0.35, 0.60 "00", "M", "04", 0.27, 0.41, 0.28, 0.43 ... etc. ...
| Hotspot numbers need not be listed in sequentially increasing order, but care must be taken that the active areas do not overlap, otherwise the wrong object may be activated when the user clicks onto that area on the screen. Note also that irregular hotspot map areas can be created by using multiple entries of target map numbers (such as for Submap 2 in the example shown above). In this case an "L" shaped hotspot area has been created for Submap 2 by defining two adjacent rectangular blocks of different heights. The larger area immediately above, and to the right of, Submap 2 was subsumed to Submap 3 (delineated by the blue lines). A larger hotspot area is generally preferable, since it is far less sensitive to the precise location of the mouse cursor when the user performs a left click operation. It therefore speeds navigation through the maps when creating a composite route. TIP! Most of the X,Y ratio pairs can be calculated fairly simply using a ruler measuring lengths directly off the screen. Run HLR and bring up the edited maps by selecting the map-based route selection option on the Routes tab. Measure the width, W, of the map drawing area and the height H. Calculate their reciprocals to, say, 4 decimal places. Using the ruler and the left edge of the map, read off the X1, X2 distances (to the nearest mm) for each hotspot object and multiply them by 1/W. Record these values in a table then do the same for Y1, Y2. Once you have done this for all objects on the submap, open the Cross Reference Index.txt file and either enter the new values or make the appropriate changes to the existing data. Exit from the map module then re-enter it again and check that the hotspots are working. (The Cross Reference Index.txt file is read by HLR every time the map system is accessed). If there is a problem, or interference occurs between adjacent hotspots, you may need to recalculate the X and/or Y ratios in the border areas between them.
| 8.8.5 Main Index Map The main index map must be designated as 'Map-00.jpg' (or 'Map-00-1024x768.jpg' etc if running at any one of the other three standard resolutions). It should generally be divided into large hotspot regions that correspond to the sub-maps you require (refer to the example shown above). You may include as many hot-spots on the main map as you like, subject only to the restriction that they should be comfortably visible by the user and uniquely identifiable to the mouse pointer. If hot-spot areas overlap (as in the example of Submaps 2 and 3 described above) you will need to decide which parts of each area are assigned to which prefered map.
| 8.8.6 SubMaps Submaps are structured in a similar way to the Main Map, with the exception that hot-spots representing adjacent maps are indicated by numbers superimposed onto coloured squares. As with the main index map, however, the active area associated with each hot-spot can be made as large (or as small) as you wish by setting X1, X2, Y1 and Y2 to appropriate values. For example, the diagram shown below displays an image of Submap 07 which has four active hotspots that link to Submaps 4, 6, 28 and 29. TSA have adopted the convention that all submap hotspots are designated by an appropriately numbered pink-shaded box. Detailed maps, (generally representing country towns or complex intersections), are indicated by an empty box outlined in the same colour as the submap label (as, for example, box 29 below).
| As with the main map, hotspots are entered into the Map Cross Reference Index.txt file as a set of offset ratios. Similarly, submap numbers need not be listed in sequentially increasing order, but care must be taken that the active areas do not overlap, otherwise the wrong map may be shown when the user clicks in that area on the screen. Enter as many records for a submap as there are hot-spots on it e.g. Submap 07 in the example above has four links to other submaps and therefore four separate entries in the Map Cross Reference Index.txt file. Note that it's not strictly necessary to define only that area of the hot-spot delineated by lines or boxes. A much wider circle around the immediate point can be specified if there is no interference from other adjacent hotspots. For example, the X1 coordinate for submap 28 has been entered as 0.00 rather than the exact value. This provides a larger clickable area and far less sensitivity to the exact placement of the mouse cursor (and therefore speeds up navigation around the maps). Additional hot-spot entries can either be slotted into the appropriate spot in the existing list (recommended for clarity and ease of use) or simply added to the bottom of the file.
... ... ... ... "07", "M", "04", 0.82, 1.00, 0.37, 0.80 "07", "M", "06", 0.82, 1.00, 0.00, 0.13 "07", "M", "28", 0.00, 0.20, 0.92, 1.00 "07", "M", "29", 0.70, 0.83, 0.25, 0.35 ... ... ... ... "07", "R", "4", 0.66, 0.74, 0.00, 0.08 "07", "R", "5", 0.21, 0.40, 0.73, 0.92 "07", "R", "5", 0.57, 0.70, 0.27, 0.41 ... ... ... ... "07", "N", "20", 0.57, 0.66, 0.00, 0.07 "07", "N", "27", 0.77, 0.87, 0.12, 0.25 "07", "N", "28", 0.20, 0.30, 0.92, 1.00 "07", "N", "71", 0.00, 0.05, 0.00, 0.11 "07", "N","143",0.70, 0.77, 0.14, 0.25 ... etc. ...
| 8.8.7 Routes and Nodes Routes and nodes are identified on submaps in a similar way to maps. Route hotspots are indicated by the route numbers superimposed onto a small coloured square, the colour generally reflecting the route colour as drawn on the map. Routes are designated in the Map Cross Reference Index.txt file by the letter "R" (as shown in the above example). Node hotspots are indicated by black numbers within yellow circles. They are designated in the Map Cross Reference Index.txt file by the letter "N" (as shown in the above example). Nodes that are non-active can be shown in white, or near-white circles, or by using some other convention. As with maps, the active area associated with each hot-spot can be made as large (or as small) as you wish by setting parameters X1, X2, Y1 and Y2 to appropriate values. These dimensions need not precisely delineate the boundaries of the node or route numbers but must define a unique, non-overlapping area of the map.
| 8.8.8 Changing Screen Resolution HLR recognises four standard screen resolutions: 800x600, 1024x768, 1280x960 and 1280x1024. For the system operated by the Department of Transport in SA maps have been generated at all four scales. Images have been proportioned in such a way that all hot-spots defined in the cross-indexing file (Map Cross Reference Index.txt) work at all four resolutions. (refer to Section 8.8.4 for further details). To change screen resolution go to Options in the main top menu, select Set screen resolution then click on the resolution required. If you want the system to remember this resolution in future runs save it to the user defaults file. (This file is called UserDefaults.txt and is found in the ..\HLR4\TempFiles folder).
Hit the Back arrow to return to the previous page or click here for the Main Index