The Database file is the center of all HyperX operations. This file (*.hdb3) is where all design and material data is stored for manipulation by the software, along with all corresponding Analysis/Sizing results.
-
Operating on a Database requires at least one Project.
-
A Database also has Database-level Defaults, which define certain Analysis/Sizing settings for all Projects in the Database. See Database Defaults for an explanation of each.
-
All entities housed in the Property Tree are members of the Database and can therefore be shared between Projects and saved as part of Database Templates. This includes:
Properties:
Library (Referenced by Properties):
Projects are linked to FEMs and contain all HyperX-specific organizational entities, which operate in conjunction with Database properties during Analysis/Sizing.
Database Templates are used to enforce consistent Database Defaults, Material Libraries, Design Properties, Load Properties, and Analysis Properties across multiple Databases.
HyperX offers a wide variety of options for analysis settings and design criteria to be considered throughout the Analysis/Sizing process. The majority of these settings can be stored as inherent properties of the Database - "Database Defaults." In doing so, these defaults will be inherited by all Projects in the Database, rather than having to set them for each Project individually.
Database Defaults are set on the Database Default Form, which is launched from the 'Database' tab of the Ribbon. They are categorized by: Project Settings, Design Load Case Settings, Zone-specific settings, and Composite settings.
Project Defaults
Project Defaults are settings that apply to an entire Project, such as units and model import options.
-
FEM Units - Units in which the model was created.
-
Display Units - Units that are displayed in the HyperX interface (regardless of model units).
-
Import Defaults
-
Import Displacements - Select whether or not to import displacements from FEA results (required for stiffness optimization).
-
Pressure and Temp Import Mode - Select whether or not pressures and temperatures are to be imported from the input file(s), and from which rundeck (first, or all) they are to come from.
-
Design Load Defaults
Design Load Defaults allow for the definition of a limit and ultimate safety factor that is applied to every Design Load.
Zone Defaults
All values found on the Zone Settings form can be set as default for any Zone created in any Project in the current Database. See Zone Settings Form for a complete description of all values.
Composite Defaults
All options for composite-based analyses can be applied as Database Defaults for all applicable Design Properties in a Project. See Composite Settings for a complete description of all values.
Advanced Settings for the Database and Project can be found by clicking the "Advanced Settings" button on the Database tab of the Ribbon.
In the resulting form, you can customize various settings related to expanding/modifying HyperX processes, specifying coefficient values, etc. These settings are applied to all Projects in a Database or just the current Project by using the "Global" or "Project" version of the setting, respectively.
A new Database can be created from scratch by launching a new instance of HyperX or from an existing Database by navigating to Database>New in the Ribbon.
Option #1: Create a New Database from a New HyperX Instance
-
Launch HyperX.
-
In the resulting window under 'New,' select a Database Template.
-
Use the file browser to name the Database and select a file location. Click 'Save.'
-
This ends the official 'Database Creation' process.
-
To actually begin working in the new Database, continue to follow the steps and add a Project.
-
Option #2: Create a New Database from an Existing, Open Database
-
Navigate to the Database tab of the Ribbon and select 'New'.
-
Select a Database Template.
-
Use the file browser to name the Database and select a file location. Click 'Save.'
-
This ends the official 'Database Creation' process.
-
To actually begin working in the new database, continue to follow the steps and add a Project.
-
Database Templates are used to enforce consistent Database Defaults, Material Libraries, Design Properties, Load Properties, and Analysis Properties across multiple Databases.
Additionally, and particularly useful for collaborating team members working with HyperX, all Database-level entities and settings can be imported from one Database to another. This can be done directly from the parent Database, or via Excel spreadsheet.
Option #1: Import Database Data Directly from Database
-
Navigate to the Database tab of the Ribbon and select the 'Import Database Data' button.
-
Select 'From Database' in the rise-up menu.
-
Use the resulting file explorer to navigate to the Database file (
.hdb3) to import from. -
Select all desired entities and settings for import using the Database Import Form.
-
Click 'Import'.
Option #2: Import Database Data from Excel Spreadsheet
Note
This option will only include Materials, Laminates, and Laminate Families. Database Defaults, Projects, Design Properties, Analysis Properties, and Load Properties can only be imported using Option #1.
-
Export all desired data from the original Database to an Excel spreadsheet. See Export Database Data.
-
In the current Database - which is to import data from the original - navigate to the Database tab of the Ribbon and select the 'Import Database Data' button.
-
Select 'From Excel' in the rise-up menu.
-
Use the resulting File Explorer to navigate to the Excel file from (1) - which contains all data to be imported.
-
Click 'Open'.
Selected Database data - namely Materials, Laminates, and Laminate Families - can be exported in bulk to Excel spreadsheet. This spreadsheet can be shared and reviewed among team members, as well as imported to another Database.
To export selected entities to Excel:
-
On the Database tab of the Ribbon, select 'Export Database Data'.
-
Use the resulting Database Export form to select all entities desired for export.
-
Use the file explorer to give the Excel file a name and saving it to the desired location.
Any existing HyperSizer Pro database (*.hdb) created in a version greater than 7.0 can be migrated to a HyperX Database (.hdb3*). To migrate a Database, simply open the desired .hdb with HyperX. Follow the resulting prompts to complete the process.
Important
This process only works for migrating from HyperSizer Pro to HyperX. There is no migration of HyperX Databases back to HyperSizer Pro.
Upon this migration, please note the following differences between the two Databases:
-
Non-FEA projects in HyperSizer Pro will not be seen in HyperX.
-
Groups, Components, and Assemblies do not exist in HyperX.
-
Group Data (i.e. sizing bounds, etc) will be converted to HyperX.
-
Components will be converted to Zones.
-
Assemblies will be converted to Structures.
-
-
Any HyperSizer Pro Component that was not in an Aassembly will not be imported into HyperX.
-
Cross-sections defined on the Sizing Form for each Component in HyperSizer will be converted to Design Properties - one for each unique combination of cross-section definitions.
-
The prescribed criteria on the Failure Tab for each Component in HyperSizer will be converted to Analysis Properties in HyperX - one for each unique combination of criteria per Component concept.
-
Load Properties will be generated and assigned to all combinations of Zones according to how the load processing technique was defined on the Component Sizing form.
-
Linking groups in HyperSizer Pro will become disconnected Zones in HyperX.
-
Frozen Components in HyperSizer Pro will no longer be frozen when translated to HyperX Zones.
-
FEM Joints in HyperSizer Pro will not translate to HyperX.
As of HyperX version 2023.3.9, users can use the Database Compare tool to compare ("Diff") two Databases to view and export a report all of the changes that exist between the Databases and Projects selected.
How-To Compare Databases
-
On the Database tab of the Ribbon, select 'Project Data' and select 'Database Compare' from the dropdown.
-
Set your desired inputs on the 'Database Compare' form.
-
Set an 'Original Database' as the source of the comparison.
-
Optionally, specify a Project within that Database for comparison.
-
-
Set a 'Modified Database' as the target of the comparison.
-
Optionally, specify a Project within that Database for comparison.
Note
The data compared by default is based on the number of Projects specified.
-
-
If only one or no Projects are specified, only Failure Mode and Plugins data will be compared.
If Projects are specified for both Databases, data for Structures, Sets, Zones, Plies, Transitions, Joints, Section Cuts, Elements, Design Loads, CADs, and Discrete Fields will also be compared.
In the 'Compare' section, select additional aspects of the Databases to compare:
-
Design, Analysis, and Load Properties - Will compare Property information between the Databases when selected.
Note
If you specify Projects for both Databases, Property information will automatically be compared whether this option is checked or not.
-
Materials, Laminates, Fasteners, and Rivets - Will compare information about these entities in addition to the other data being compared.
-
Project Setup - Will compare Advanced Settings (Database- and Project-level) and Rundecks in addition to the other data being compared.
Important
This selection will only have an effect if Projects are specified for both Databases.
-
-
Press the 'Compare' button to compare the Databases based on your inputs and launch the 'Database Compare Simple Report' Form to view the results.
-
Viewing and Exporting the Report
In the 'Database Compare Simple Report' form you can view all of the differences between the two Databases you've selected for comparison.
The top-level view will show all the categories of changes that exist between the two Databases. Each category in the 'Changes Detected' section can be expanded with each level of expansion showing greater detail about what specifically was changed.
The comparison results can also be exported as HTML by pressing the 'Details' button at the bottom of the form.
After clicking the button and selecting where to save the exported HTML, you can view and share all of the comparison results by viewing the file in a browser.
As of HyperX version 2025.1.4, users can manually compact Databases to potentially reduce their file size. You can select this option from the Database tab of the Ribbon.
Database compaction is automatically run during Database migrations, but this option allows users to manually compact the Database file. If you've been working on one version of a Database for a while and the file size has increased more than you'd like, compacting the Database might reclaim some of disk space.
Projects are linked to FEMs and contain all HyperX-specific organizational entities, which operate in conjunction with Database properties during Analysis/Sizing.
Database Templates are used to enforce consistent Database Defaults, Material Libraries, Design Properties, Load Properties, and Analysis Properties across multiple Databases.
Database Templates are used to enforce consistent Database Defaults, Material Libraries, Design Properties, Load Properties, and Analysis Properties across multiple Databases.