Deactivated loads are still visible in PLAXIS Output

22 January 2019

It is possible for projects to have various loads being deactivated in a calculation phase, effectively by setting the load value to zero. When checking PLAXIS Output results, it can happen that the visualization of the load is still visible (blue arrows).

In Plaxis calculations, when it comes to a staged construction loading type, the activation of all loads and self-weight of soils, structures are considered to be an out-of-balance force. In order to solve this out-of-balance, the calculation will use a linear relationship with the ΣMstage multiplier to activate these new loads: once ΣMstage reaches one [1], the full weight and loads are active in the model.

The same logic is being followed in the case when a load is being deactivated, i.e. the load will be deactivated once ΣMstage reaches one [1].

When checking the calculation results of a phase that failed or any of the intermediate steps, the load visualization may still be visible as the load is not yet fully deactivated, as ΣMstage is not yet equal to one (1).

In the example below, the line load is being deactivated for the current phase (Phase_2).
For Phase_1 the calculation finished with ΣMstage equal to one, however, for Phase_2 it is stopped while the ΣMstage is equal to 0.80. This means that the line load is still not fully deactivated in this step.

To check the current value of the applied load (and, therefore, determine the remaining load to be deactivated), you can check this under Project>Load information and search for the load values with the subscript “a”, which stands for “applied”, e.g. qa,y.

Related posts

Privacy Preference Center


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


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

UserMatchHistory, lang, BizoID
lidc, bcookie


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