Damask-parse

Latest version: v0.2.24

Safety actively analyzes 629908 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 7

0.2.6

Changed

- Accept a nested list (in addition to an ndarray) for `grains` dict item in `microstructure_image` argument of `utils.volume_element_from_2D_microstructure` function.

0.2.5

Added

- Add function for adding buffer material zones to a volume element: `utils.add_volume_element_buffer_zones`.

Changed

- Require `unit_cell_alignment` dict (e.g. `{'x': 'a', 'z': 'c'}`) in `orientations` dict to more explicitly account for different unit cell alignment conventions. (DAMASK uses x parallel to a for hexagonal systems.)

0.2.4

Changed

- Return `orientations` from `read_geom` in a way consistent with `orientations` in other functions.

Fixed

- Fix case where default geom size and origin values are not used in `write_geom`.
- Correctly parse geom file size header information, whether specified as integer or floating point.

0.2.3

Changed

- Separate orientations (Euler angles) can now be passed into `geom_to_volume_element`. This can be used if the geometry file does not contain a header with microstructure/texture information.

0.2.2

Fixed

- Function `write_load_case` now uses the general format code, `.10g` (rather than fixed floating point, `.10f`). This means the load case file is less likely to go over the 256-character limit that is currently imposed by DAMASK.

0.2.1

Fixed

- Fix order of extracted incremental data in `get_HDF5_incremental_quantity` for DAMASK version 3, where `incxxx` is no longer zero-padded.
- Add `write_numerics` and move `write_numerics_config` to `legacy` sub-package.

Page 4 of 7

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.