Create Events

Combine channels and subcases to create events.

Tip: You can rename a created event by double-clicking on its names in the bottom half of the Load Map dialog.

Create Time Series Events

Static subcases are supported for all fatigue calculations with a Time Series loading type.
  1. Click the Load Map tool.
    Figure 1.


    The Load Map dialog opens.
  2. Using the bottom half of the dialog, specify how to create events then click .
    The fatigue subcases that are read from the result file can be paired with load histories either manually or automatically.

    All pairs will be superimposed.

    Note: The number of time points should be the same if the pairs under the same event are superimposed.
    OptionDescription
    Manual Event Creation
    Figure 2.


    When Manual is selected and you click , an event is created without any load history and subcase pair assigned. You can drag and drop an equal number of load histories and subcases under an event.
    Note: The subcases should be dropped under an event first and then the load history channels.
    Auto Event Creation
    Figure 3.


    When Auto and Single Event are selected, before you click ,
    1. Select a subcase and a load history channel, or
    2. Select multiple load histories and subcase pairs that have an equal number of time points.

    Only one event is created when you click .

    Figure 4.


    When Auto and Multiple Events are selected, before you click ,
    1. Select multiple load histories and subcase pairs.

      The load histories must have an equal number of time points.

    2. Total number of events created = Number of channels selected / Number of subcases selected.
  3. Adjust the load magnitude, scale, offset, repeats, max gate range, and configuration of the events/subcases.
    Tip:
    • Apply the value of a parameter to all the events/subcases by right-clicking on a value and selecting Apply value to all events.
    • From the Subcase window, select any subcase increment.
  4. Activate the checkboxes of the events to be considered in the evaluation.
  5. Optional: Create Event Group .
    Events groups can be created to combine required event combinations. See Figure 6.
    1. Click on to create the Event Group and then use the event creation options to create events within the group.
      Event group should be highlighted before creating individual events within the group. Event groups can also be created within a group leading to nested event group combination as shown in Figure 6.
Figure 5.


The following equation depicts how LDM, Scale, and Offset values work together to scale the FEA stress tensor at time t.

σ i j ( t ) = σ i j . F E A L D M ( P ( t ) S c a l e + O f f s e t ) MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaGaeq4Wdm3aaS baaSqaaiaadMgacaWGQbaabeaakiaacIcacaWG0bGaaiykaiabg2da 9maalaaabaGaeq4Wdm3aaSbaaSqaaiaadMgacaWGQbGaaiOlaiaadA eacaWGfbGaamyqaaqabaaakeaacaWGmbGaamiraiaad2eaaaGaaiik aiaadcfacaGGOaGaamiDaiaacMcacaWGtbGaam4yaiaadggacaWGSb GaamyzaiabgUcaRiaad+eacaWGMbGaamOzaiaadohacaWGLbGaamiD aiaacMcaaaa@55EB@

Where:
σ i j ( t ) MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaGaeq4Wdm3aaS baaSqaaiaadMgacaWGQbaabeaakiaacIcacaWG0bGaaiykaaaa@3C1E@
Results stress tensor at time t
σ i j . F E A MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaGaeq4Wdm3aaS baaSqaaiaadMgacaWGQbGaaiOlaiaadAeacaWGfbGaamyqaaqabaaa aa@3CCF@
Stress tensor from static analysis
P ( t ) MathType@MTEF@5@5@+= feaagKart1ev2aaatCvAUfeBSjuyZL2yd9gzLbvyNv2CaerbuLwBLn hiov2DGi1BTfMBaeXatLxBI9gBaerbd9wDYLwzYbItLDharqqtubsr 4rNCHbGeaGqiVu0Je9sqqrpepC0xbbL8F4rqqrFfpeea0xe9Lq=Jc9 vqaqpepm0xbba9pwe9Q8fs0=yqaqpepae9pg0FirpepeKkFr0xfr=x fr=xb9adbaqaaeGaciGaaiaabeqaamaabaabaaGcbaGaamiuaiaacI cacaWG0bGaaiykaaaa@391D@
The y point value of load-time history at time t
Figure 6.

Create Duty Cycle Events

HyperLife allows you to import duty cycle files (*.xml) which have complex duty cycle information for multiple durability events. HyperLife provides the following options in automatically creating the necessary events:
  • HyperLife LoadMap file (.xml)
  1. Click the Load Map tool.
    Figure 7.
    The Load Map dialog opens.
  2. In the Load Map dialog, click in the top-right.
  3. From the file dialog, browse for an *.xml file and click Open.
    • The load history files are imported into the channel window.
    • Subcase and channel pairs are created in the event window.
    • Event information specific to repeats, scale, LDM, and offset are updated.

Example of HyperLife Duty Cycle with Events. as seen in _____

<?xml version="1.0" encoding="UTF-8"?>
<HyperLifeInput profile="CrackGrowth" version="2024.1.0.31-HYLCG">
  <LoadMap typeofloading="Time Series">
    <Channel>
      <tabfat id="1" type="Time Data">D:/History_1.csv</tabfat>
      <tabfat id="2" type="Time Data">D:/History_2.csv</tabfat>
      <tabfat id="3" type="Time Data">D:/History_3.csv</tabfat>
      <tabfat id="4" type="Time Data">D:/History_4.csv</tabfat>
      <tabfat id="5" type="Time Data">D:/History_5.csv</tabfat>
      <tabfat id="6" type="Time Data">D:/History_6.csv</tabfat>
    </Channel>
    <FatigeEvents>
      <Event Configuration="superposition" Gate="0" id="1" name="Event_1">
        <Fatload LDM="0.5" Offset="0" Scale="6" block="1" resultfile="" sim="1" subcase="1" tabfatId="1" tabfatName=""></Fatload>
      </Event>
      <Event Configuration="superposition" Gate="0" id="2" name="Event_2">
        <Fatload LDM="0.5" Offset="0" Scale="6" block="1" resultfile="" sim="1" subcase="2" tabfatId="2" tabfatName=""></Fatload>
      </Event>
      <Event Configuration="superposition" Gate="0" id="3" name="Event_3">
        <Fatload LDM="0.5" Offset="0" Scale="6" block="1" resultfile="" sim="1" subcase="3" tabfatId="3" tabfatName=""></Fatload>
      </Event>
    </FatigeEvents>
    <Fatseq>
      <Fatevnt EventId="" EventName="Event_1" Repeats="1" Status="true"></Fatevnt>
      <Fatevnt EventId="" EventName="Event_2" Repeats="1" Status="true"></Fatevnt>
      <Fatevnt EventId="" EventName="Event_3" Repeats="1" Status="true"></Fatevnt>
    </Fatseq>
  </LoadMap>
</HyperLifeInput>

Example of HyperLife Duty Cycle with Event Groups, as seen in Figure 6.

<?xml version="1.0" encoding="UTF-8"?>
<HyperLifeInput profile="CrackGrowth" version="2024.1.0.31-HYLCG">
  <LoadMap typeofloading="Time Series">
    <Channel>
      <tabfat id="1" type="Time Data">D:/History_1.csv</tabfat>
      <tabfat id="2" type="Time Data">D:/History_2.csv</tabfat>
      <tabfat id="3" type="Time Data">D:/History_3.csv</tabfat>
      <tabfat id="4" type="Time Data">D:/History_4.csv</tabfat>
      <tabfat id="5" type="Time Data">D:/History_5.csv</tabfat>
      <tabfat id="6" type="Time Data">D:/History_6.csv</tabfat>
    </Channel>
    <FatigeEvents>
      <Event Configuration="superposition" Gate="0" id="1" name="Event_1">
        <Fatload LDM="1" Offset="0" Scale="1" block="1" resultfile="" sim="1" subcase="1" tabfatId="1" tabfatName=""></Fatload>
        <Fatload LDM="1" Offset="0" Scale="1" block="1" resultfile="" sim="1" subcase="2" tabfatId="2" tabfatName=""></Fatload>
      </Event>
      <Event Configuration="superposition" Gate="0" id="2" name="Event_2">
        <Fatload LDM="1" Offset="0" Scale="1" block="1" resultfile="" sim="1" subcase="3" tabfatId="3" tabfatName=""></Fatload>
      </Event>
      <Event Configuration="superposition" Gate="0" id="3" name="Event_3">
        <Fatload LDM="1" Offset="0" Scale="1" block="1" resultfile="" sim="1" subcase="4" tabfatId="4" tabfatName=""></Fatload>
        <Fatload LDM="1" Offset="0" Scale="1" block="1" resultfile="" sim="1" subcase="5" tabfatId="5" tabfatName=""></Fatload>
      </Event>
      <Event Configuration="superposition" Gate="0" id="4" name="Event_4">
        <Fatload LDM="1" Offset="0" Scale="1" block="1" resultfile="" sim="1" subcase="6" tabfatId="6" tabfatName=""></Fatload>
      </Event>
    </FatigeEvents>
    <FatigueEventGroups>
      <EventGroup id="1" name="EventGroup_1">
        <Fatevnt EventId="" EventName="Event_1" Repeats="1"></Fatevnt>
        <Fatevnt EventId="" EventName="Event_2" Repeats="1"></Fatevnt>
      </EventGroup>
      <EventGroup id="2" name="EventGroup_2">
        <Fatevnt EventId="" EventName="Event_3" Repeats="1"></Fatevnt>
        <Fatgrp EventId="" EventName="EventGroup_3" Repeats="1"></Fatgrp>
      </EventGroup>
      <EventGroup id="3" name="EventGroup_3">
        <Fatevnt EventId="" EventName="Event_4" Repeats="1"></Fatevnt>
      </EventGroup>
    </FatigueEventGroups>
    <Fatseq>
      <Fatgrp EventId="" EventName="EventGroup_1" Repeats="1" Status="true"></Fatgrp>
      <Fatgrp EventId="" EventName="EventGroup_2" Repeats="1" Status="true"></Fatgrp>
    </Fatseq>
  </LoadMap>
</HyperLifeInput>
The keywords from the .xml files define the required duty cycle information, such as:
  • Type of Load Type (typeofloading)
    <LoadMap typeofloading="Time Series">
  • Load History file name with extension
    <Channel>
        <tabfat id="1" type="Time Data">E:/load1.csv</tabfat>
    </Channel>
    
  • Event Information
    <FatigeEvents>
        <Event Configuration="superposition" Gate="0" id="1" name="Event_1">
            <Fatload LDM="1" Offset="0" Scale="6" block="1" resultfile="" sim="1" subcase="1" tabfatId="1" tabfatName=""></Fatload>
            <Fatload LDM="1" Offset="0" Scale="6" block="1" resultfile="" sim="1" subcase="2" tabfatId="2" tabfatName=""></Fatload>
        </Event>
    </FatigeEvents>
    
  • Group Information
    <FatigueEventGroups>
        <EventGroup id="1" name="EventGroup_1">
            <Fatevnt EventId="" EventName="Event_1" Repeats="1"></Fatevnt>
            <Fatevnt EventId="" EventName="Event_2" Repeats="1"></Fatevnt>
        </EventGroup>
        <EventGroup id="2" name="EventGroup_2">
            <Fatevnt EventId="" EventName="Event_3" Repeats="1"></Fatevnt>
            <Fatgrp EventId="" EventName="EventGroup_3" Repeats="1"></Fatgrp>
        </EventGroup>
        <EventGroup id="3" name="EventGroup_3">
            <Fatevnt EventId="" EventName="Event_4" Repeats="1"></Fatevnt>
        </EventGroup>
    </FatigueEventGroups>
  • Event Sequence
    <Fatseq>
        <Fatgrp EventId="" EventName="EventGroup_1" Repeats="1" Status="true"></Fatgrp>
        <Fatgrp EventId="" EventName="EventGroup_2" Repeats="1" Status="true"></Fatgrp>
    </Fatseq>
  • Load history file name with extension (Testname)
  • FE subcase ID in HyperLife (FELoadCase)
  • Type of Load Type (typeofloading)
  • Load History file name with extension
    <Channel>
        <tabfat id="1" type="Time Data">E:/load1.csv</tabfat>
    </Channel>
    
  • Event Information
    <FatigeEvents>
        <Event Configuration="superposition" Gate="0" id="1" name="Event_1">
            <Fatload LDM="1" Offset="0" Scale="6" block="1" resultfile="" sim="1" subcase="1" tabfatId="1" tabfatName=""></Fatload>
            <Fatload LDM="1" Offset="0" Scale="6" block="1" resultfile="" sim="1" subcase="2" tabfatId="2" tabfatName=""></Fatload>
        </Event>
    </FatigeEvents>
    
  • Event Sequence
    <Fatseq>
        <Fatevnt EventId="" EventName="Event_1" Repeats="1000"></Fatevnt>
        <Fatevnt EventId="" EventName="Event_2" Repeats="5000"></Fatevnt>
    </Fatseq>
    
  • Load history file name with extension (Testname)
  • FE subcase ID in HyperLife (FELoadCase)
  • Status to highlighted event selection
  • Update any parameters as needed or disable an event to exclude it from the solution.