Skip to main content
  1. HyperX Support
  2. Glossary
  3. File Organization

Project

A Project must be created to operate a Database. These second-level entities are linked to finite element models and contain all HyperX-specific organizational entities, which operate in conjunction with Database properties during Analysis/Sizing.

Video

About

Project_DBvsProject.png

  • At least one Project must exist to operate a Database.

  • Multiple projects may exist in a single Database.

    • Projects in the same Database have access to the same Database-level data.

    • Only one Project can be loaded into the Viewport at a time.

  • Projects contain HyperX-specific organizational entities (Structures, Sets, Zones)

  • Project-level Analysis and Sizing settings can be controlled via the Advanced Settings Form found on the Database tab of the Ribbon

Create

A Project must exist to operate and interact with a Database. Users are prompted to create a Project automatically when creating a new Database. However, Project creation can also be done at any time from the Ribbon or Project Options form.

Import

A Project can be imported into the current Database from another existing Database. Projects are just one of the many data entities that can be imported via the Database Data Import process. However, for convenience, this process can also be launched from the Projects section of the Database tab of the Ribbon.

  1. Select the 'Import Project' button from the Database tab of the Ribbon.

    project-manage-fromribbon.png

  2. Use the file browser to select the Database from which the desired Project should be imported.

  3. Select the Project(s) to import on the 'Projects' tab of the resulting Import form.

    project-import.png

  4. Click 'Import' to import the selected Project to the current Database.

Switch Between

While multiple Projects can be stored in the same Database, only one can be loaded (i.e. viewed) at a time. The user is able to switch between Projects via the Project Options form.

  1. Click the 'Project Options' button from the Database tab of the Ribbon.

    project-manage-fromribbon.png

  2. Select the desired Project from the dropdown.

    Project_SwitchList.png

  3. Click 'Load Project'.

Delete

A Project can be deleted from the Database using the Project Options form.

Note

The Project that is currently loaded cannot be deleted. The current Project must be switched (see Switch Projects) to delete it.

  1. Launch the Project Options form from the Database tab of the Ribbon.

    project-manage-fromribbon.png

  2. Use the dropdown menu to select the unwanted Project.

  3. Click the in-line 'Delete' button.

    Project_delete.png

Sharing

Sharing Projects

In many cases, particularly in a team environment, it can be useful to share HyperX projects between team members. HyperX has a utility to automatically package a project - and any selected accompanying files - into a single shareable file, which can then be unpackaged properly on the next team member's machine.

  1. To access the "Bundle Project" utility, click the Project Data button on the Database tab of the Ribbon.

    Project_data-fromRibbon.png

  2. Select "Create Project Bundle".

    Project-package.png

  3. Configure the following options:

    • Files (formerly Archive) - Choose which files are included in the bundled Project share file.

      • FEM Input Files - Select to include your FEM input files in the bundled file.

        • FEM Output Files - Select to include corresponding FEM output files in the bundled file.

        Including FEM Files, particularly output files, tends to drastically increase the size of the share file. The benefit, however, is that the FEM does not need to be re-run after unbundling and loads are consistent between team members

      • Working Folder - Select to include the Project Working Folder (which contains all temporary and results files corresponding to the existing analysis results) in the bundled file.

        • Include Loads Files - If you've already run a Sizing or Analysis, loads from the FEM have been imported into your Database and processed accordingly. Selecting this option will include the corresponding load files in the bundled file.

        Similar to FEM Files, including the Working Folder and/or Loads Files can drastically increase the size of the share file. However, doing so means ultimate consistency between team members - same Sizing/Analysis results files, same loads imported, etc.

      • Include Plugin Packages - Select to include any Plugin .dll files that are referenced by the Project in the bundled file.

    • Packages - Select Packages to include with the Project in the bundled file. You can use the dropdown menu on each Package to see its Source, the Modules it contains, which Packages require it. Note that if a Package is a dependency for another Package, it cannot be removed from the Project Bundle without first removing the Package that requires it.

      • Pin - Use this toggle to pin the Package version in the bundled Project. See "Updating Packages" here for more information.

      • Scrub Sources - A Source is a folder that contains Packages. This option, when enabled, removes Package Sources from the bundle so the bundled Project can only load the Packages explicitly included via this form. This option can prevent unintentionally exposing Packages that you don't want to share when you bundle a Package from a shared Source.

    • Options - Additional selections for configuring the bundled file.

      • Remove all other Projects from the Database - Select to ensure only the current Project is included in the bundled file (de-select to include all Projects in the Database).

        • Delete Unused Properties and Materials - Select to ensure that any Property or Material in the Database that isn't referenced by the current Project(s) will be deleted/not included in the bundled file.

      • Map FEM Files to Relative Paths - Select to assign FEM input and output files to paths relative to the unbundled Database. This allows the freedom to unbundle the Project and FEM files in any location without having to worry about fixed file paths to maintain.

    • Additional File - Attach additional files of any kind to include in the bundled file.

  4. Click "Bundle" to generate the shareable Project Bundle in a selected location.

Sharing Properties Between Projects

The Property Tree will automatically be filtered to only display Properties associated with the currently loaded Project. However, all Properties can be shared between Projects using Library forms.

  1. Open a Property Library form (see Design Property Library, Load Property Library, or Analysis Property Library) by double-clicking on the corresponding node in the Property Tree. The properties that are associated to the current Project are indicated with green checks. Note that these properties match those that are currently visible in the Property Tree. See the Design Property example below.

    Project_PropertiesOfProjects-example.png

  2. Select the desired Properties and click the 'Project' dropdown menu.

    Project-includeproperties.png

  3. Click 'Include' to push the selected Properties to the current Project. Alternatively, click 'Exclude' to remove selected Properties from the current Project (but not the Database). The Property list and Property Trees will both be updated accordingly, as shown below.

    project-includeproperties-example.png

Recently Viewed

Didn’t find what you’re looking for?

Submit a Request

Didn’t find what you’re looking for?

Create a New Post