PLAXIS 2D Command compatibility notes

28 July 2014

PLAXIS 2D 2018.00

Output

Commands using curve points

Following the support for an unlimited number of points for curves in Output, the following examples show the commands that have been updated:

  • getcurveresults
    • 2D 2017: getcurveresults Node_A Phase_5 ResultTypes.Soil.Ux
    • 2D 2018: getcurveresults CN_1 Phase_5 ResultTypes.Soil.Ux
  • getsingleresult
    • 2D 2017: getsingleresult Phases[4] ResultTypes.Soil.Ux Node_A
    • 2D 2018: getsingleresult Phases[4] ResultTypes.Soil.Ux CN_1
  • getcurveresultspath
    • 2D 2017: getcurveresultspath Node_A Phases[0] Phases[3] ResultTypes.Soil.Ux
    • 2D 2018: getcurveresultspath CN_1 Phases[0] Phases[3] ResultTypes.Soil.Ux

Note that for all commands you can also use Curvepoints.Nodes[0] instead of CN_1 to retrieve the results for the first selected node.

Phase/Step object compatibility

For more information on the changes in the properties for Phase and Step objects in PLAXIS Output program see PLAXIS Output Phase/Step object compatibility for details.

PLAXIS 2D 2017.00

Input

Select points for curves

The command __selectcurvepoints is no longer available. Instead, the following commands can be used:

selectmeshpoints
/output addcurvepoint "Node" (x y z)
/output addcurvepoint "StressPoint" (x y z)
/output update

For more information, you can check the article Select points for curves prior to calculation directly in Input.

Phases object updates

The phases object in Input has been updated. Below you can see the differences in properties between the versions:

2D 20162D 2017
.Deform.SumMWeight.Deform.SumMweight
.Deform.Loading.SumMStage.Deform.Loading.SumMstage
.Deform.Loading.SumMWeight.Deform.Loading.SumMWeight
.Reached.ReachedTime.Reached.Time
.Reached.ReachedStiffness.Reached.RelativeStiffness
.Reached.ReachedForceX.Reached.ForceX
.Reached.ReachedForceY.Reached.ForceY
.Reached.ReachedPMax.Reached.Pmax
.Reached.ReachedMStage.Reached.SumMstage
.Reached.ReachedMWeight.Reached.SumMweight
.Reached.ReachedMsf.Reached.SumMsf

PLAXIS 2D 2016.00

Input

Switch to Flow conditions mode

The gotowater command is pending deprecation in favour of the gotoflow command

Tunnel designer

In the tunnel designer a few things changed such that older command logs might not properly work:

  • the order of generated elements in Tunnel Designer has changed so this will not generate proper geometry or correct references when assigning e.g. plates, interfaces and line loads to these when using old command logs;
  • Names of the generated properties in Tunnel Designer (e.g. lineloads, plates) changed as well, for instance in the tunnel designer a line load was called Lineload_x while now is called TCS_x_LineLoad_x

Phases - dynamics

The time stepping settings for dynamic calculations has changed: we can now choose a new time step determination: "Semi-automatic" which behaves the same as the "Automatic" setting of PLAXIS 2D 2015. The "Automatic" setting is now fully automatic and should choose an appropriate number of dynamic substeps AND number of additional steps.

Output

Phase info inconsistencies with Input

We found a few inconsistencies between Input and Output for some parameter names from the Phase and Step info. Of course we would like to have consistency between the two programs to make sure that the parameters are easy to use and to make sure any scripting/Python programming is easier to make and understand.

The changed parameter names are:

description2D 2015.022D 2016.00
Phase identification namePhase_1.CaptionPhase_1.Identification
internal phase numberPhase_1.IDPhase_1.Number
time interval for last step [in project time unit]Phase_1.Info.TimeIntervalPhase_1.Info.TimeInterval
reached total end time of phase [in project time unit]Phase_1.Info.EstimatedEndTimePhase_1.Info.ReachedTime
time interval in seconds per step [dynamics only]Phase_1.Info.TimeIntervalSecondsPhase_1.Info.TimeIntervalSeconds
reached dynamic time in seconds [dynamics only]Phase_1.Info.ReachedTimePhase_1.Info.ReachedDynTime

Soil results

In 2D2015, there was a typo in the soil result objects related permeability. These have been now fixed:

  • ResultTypes.Soil.RelPermeability
  • ResultTypes.Soil.ActualPermeabilityX
  • ResultTypes.Soil.ActualPermeabilityY

 

PLAXIS 2D 2015.00

Embedded pile row changes to embedded beam row

The embedded pile row has been changed into embedded beam row to make clear this embedded beam can be used for more than just piles, e.g. grout anchors.

To create a new embedded beam row:
    embeddedbeamrow (x1 y1) (x2 y2)

To create a new embedded beam row material dataset:
    embeddedbeammat

Note: in this version the old commands for the embedded pile rows will be supported, but may become deprecated in later versions

Naming of cutobjects (staged construction)

Due to an issue in the sorting routine of the cut objects (i.e. the intersected result of soils, polygons, lines), and the fact that the source of a cut objects was not clear in its naming, the automatic naming of items in the intersected geometry (mesh mode, flow conditions mode, staged construction) has been changed. This also involves removing the prefix CS_ for these items, see this example:

  • PLAXIS 2D AE: CS_Line_1
  • PLAXIS 2D 2015: Line_1_1

Multiplier on vector based features

The name for the multiplier userfeature has been changed. For point loads and point prescribed displacements, this userfeature name has been changed from .Multiplier_x/_y/_z to .MultiplierFx/Fy/Fz. To set a LoadMultiplier for a dynamic point load using the command line:

  • 2D AE: set DynLineLoad_1_1.Multiplier_x Phase_1 LoadMultiplier_1
  • 2D 2015: set DynPointLoad_1_1.MultiplierFx Phase_1 LoadMultiplier_1

For line loads, this userfeature name has been changed from .Multiplier_x/_y_z to .Multiplierx/y/z, and this would be the command line:

  • 2D AE: _set DynLineLoad_1_1.Multiplier_x Phase_1 LoadMultiplier_1
  • 2D2015: _set DynLineLoad_1_1.Multiplierx Phase_1 LoadMultiplier_1

Linear boundary conditions for head, inflow and outflow

Linear boundary conditions for head, inflow, outflow had inconsistent settings. Now the behaviour can be chosen more explicitely and more consistently by offering these options:

  • "Vertical increment"
  • "Horizontal increment"
  • "Start/end values"

The option Linear is deprecated in 2D 2015, and replaced by the above mentioned options.

PLAXIS 2D AE.02

This page contains an overview of the changes in commands.

Bending moment

Since PLAXIS 2D AE.02, the parameter for the Point Load's bending moment has been changed from BendingMoment to simply M

Interface side

By fixing the issue called Local axis may flip with overlapping lines in PLAXIS 2D AE. the positive and negative interfaces may be on the opposite side of the line (and plate) compared to command log files created in PLAXIS 2D AE.00 or PLAXIS 2D AE.01. This could influence the replaying of these command log files.

Privacy Preference Center

Necessary

The Cookies are necessary for the site to function

CONSENT, NID, _cfduid, wp-settings-time-16, wp-setting-16, wordpress_test_cookie, gdpr[allowed_cookies], gdpr[consent_types], wp_woocommerce_session, wordpress_logged_in, wordpress_sec, PHPSESSID

Advertising

These Cookies are used to provide you with useful information based on recent browser data

_gads
UserMatchHistory, lang, BizoID
IDE
fr
NID
lidc, bcookie

Analytics

These are used to track user interaction and detect potential problems. These help us improve our services by providing analytical data on how users use this site

_ga, _gid

Other