motionroutinesmodule::updateprescribedmotions Interface Reference

Updates the prescribed motions. More...

Private Member Functions
subroutine	updateprescribedmotionsa (t, h, beta, gamma, sysVel, sysAcc, motions, linearStatic, ierr, lpu)
	Updates the prescribed motions. More...
subroutine	updateprescribedmotionsb (motions, ierr)
	Updates the prescribed motions. More...

Detailed Description

Updates the prescribed motions.

Member Function/Subroutine Documentation

updateprescribedmotionsa()

subroutine motionroutinesmodule::updateprescribedmotions::updateprescribedmotionsa ( real(dp), intent(in)  t, real(dp), intent(in)  h, real(dp), intent(in)  beta, real(dp), intent(in)  gamma, real(dp), dimension(:), intent(in)  sysVel, real(dp), dimension(:), intent(in)  sysAcc, type(motiontype), dimension(:), intent(inout)  motions, logical, intent(in)  linearStatic, integer, intent(out)  ierr, integer, intent(in), optional  lpu  )

private

Updates the prescribed motions.

Parameters

[in]	t	Current simulation time
[in]	h	Time increment size
[in]	beta	Newmark time integration parameter
[in]	gamma	Newmark time integration parameter
[in]	sysVel	System velocity vector
[in]	sysAcc	System acceleration vector
	motions	Array of all prescribed motions in the model
[in]	linearStatic	If .true., multi-load case linear static analysis
[in]	lpu	File unit number for debug output of motions from file
[out]	ierr	Error flag

A prescribed motion can be updated either by evaluating the general function connected to it, or by reading new values from the binary file provided. The latter approach is typically used in sub-model analysis.

Author

Knut Morten Okstad

Date

Oct 2004

updateprescribedmotionsb()

subroutine motionroutinesmodule::updateprescribedmotions::updateprescribedmotionsb ( type(motiontype), dimension(:), intent(inout)  motions, integer, intent(out)  ierr  )

private

Updates the prescribed motions.

Parameters

	motions	Array of all prescribed motions in the model
[out]	ierr	Error flag

This version only (re)evaluates the prescribed motion functions, and is typically used after the initial configuration has been defined in order to ensure that all functions depending on other state variables are up to date before starting the time integration.

Author

Knut Morten Okstad

Date

Sep 2010

---

The documentation for this interface was generated from the following file:

• src/vpmSolver/motionRoutinesModule.f90