0.7.1

What's Changed

Full Changelog: 0.7.0...0.7.1

0.7.0

What's Changed

• 81 only add coordinates to soil property payload when not none by @tlukkezen in #99
• 93 Throw ValueError when providing less than 2 CPTs to create_grouper_payload() by @tlukkezen in #99

New Contributors

• @dependabot made their first contribution in #48

Full Changelog: 0.6.0...0.7.0

0.6.0

What's Changed

• Feat results viewer by @PabloVasconez in #80

Minor release adding the following 🚀 powerful result viewers 🚀 which will significantly improve the insight into the calculation results:

• ViewerCptResults: Viewer for the CPT results of the bearing capacity calculations vs. pile tip level (demo video).
• ViewerCptResultsPlanView: Viewer for the CPT results of the bearing capacity calculations in
  plan view for a fixed pile tip level (demo video).
• ViewerCptGroupResults: Viewer for the CPT group results of the bearing capacity calculations vs. pile tip level (demo video).

The viewers are added to the example notebook PileCore_multi_cpt_grouper.ipynb. For more details about how to use it, take a look at the docs.

Full Changelog: 0.5.1...0.6.0

0.5.0

This release connects py-pilecore to the freshly released PileCore-API v3.0.

What's Changed

• !refactor: pile properties in line with PileCore API v3 definition by @tlukkezen in #72

One of the main breaking changes in the API is the definition of a foundation pile object. This is also reflected in py-pilecore by adding a brand new PileProperties object, which holds the geometry and pile_type information. This PileProperties object can be created with the function create_basic_pile():

    create_basic_pile(
        pile_name=pile_name,
+       main_type=main_type,
        specification=specification,
        installation=installation,
        pile_shape=pile_shape,
        height_base=height_base,
+       core_secondary_dimension=core_secondary_dimension,
+       core_tertiary_dimension=core_tertiary_dimension,
+       base_secondary_dimension=base_secondary_dimension,
+       base_tertiary_dimension=base_tertiary_dimension,
+       core_diameter=core_diameter,
+       base_diameter=base_diameter,
+       pile_material=pile_material,
+       custom_material=custom_material,
        settlement_curve=settlement_curve,
        adhesion=adhesion,
        alpha_p=alpha_p,
        alpha_s_clay=alpha_s_clay,
        alpha_s_sand=alpha_s_sand,
        beta_p=beta_p,
        pile_tip_factor_s=pile_tip_factor_s,
        is_auger=is_auger,
        is_low_vibrating=is_low_vibrating,
        negative_fr_delta_factor=negative_fr_delta_factor,
    )

Most of the input arguments were already known as arguments for creating the API payload, but there are also some new arguments, as marked above.

The changes in the pile dimensions are probably standing out the most. They reflect the changes in the pile geometry model in the API, which is made to be more modular. In the new model, we always require a core component of the pile, and allow extra components to be formed around it (like a Russian doll model). Therefore, we now require the dimensions of the core, while the base dimensions are optional.

It can also be seen that the pile can also be assigned a material, which sets properties like the E-modulus and the color for plotting purposes.

The pile and its separate components can be visualized with plotting methods, so that you can inspect the pile shape in py-pilecore before sending it to the API.

Furthermore, it is important to notice that we also renamed and simplified the definition of the default_pile (previously pile_type_specification). Not just the name is shorter: We also changed the required input for creating the pile-type, so be sure to check out the new pile_type tables!

Full Changelog: 0.4.2...0.5.0

0.4.2

What's Changed

• feat: bandwidth of attribute; resolve #69 by @RDWimmers in #70
• feat(#64): Auto convert pile-type-specification inputs to strings by @tlukkezen in #71

Full Changelog: 0.4.1...0.4.2

0.4.1

What's Changed

• Feat delaunay tessellation by @RDWimmers in #63
• deps: upgrade dependencies with pip-compile by @tlukkezen in #65
• docs: Add SingleCPTBearingResults reference to docs by @tlukkezen in #66
• feat(#40): Pass soil_load=0.0 when input is None. by @tlukkezen in #67

Full Changelog: 0.4.0...0.4.1

0.4.0

What's Changed

• feat: combine grouper and single results by @RDWimmers in #61

Full Changelog: 0.3.4...0.4.0

0.3.4

What's Changed

• fix: Raise RuntimeError with /get-task-status response "msg" value instead of "status_code" when "state"=="FAILURE"

Full Changelog: 0.3.3...0.3.4

0.3.3

What's Changed

• ci: Use PyPi tokenless authentication
• individual-friction-ranges: Set soil-properties friction-range-strategy to "manual" when providing a value in the individual-friction-range input

Full Changelog: 0.3.2...0.3.3

0.3.2

What's Changed

• fix: Don't filter NaN values in the table result from SingleCPTBearin… by @tlukkezen in #59

Full Changelog: 0.3.1...0.3.2