Mwa-hyperbeam

Latest version: v0.7.2

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

Scan your dependencies

Page 1 of 2

0.7.2

Fixed
- CI (no code changes).

0.7.1

Fixed
- A (seemingly rare) race condition in FEE GPU code.
- examples/analytic_cuda_device.cu wasn't complete.

0.7.0

Added
- Expose Rust function `fix_amps_ndarray`
- FFI functions

See the changes below for an explanation.

- `get_fee_freq_map`
- `get_fee_tile_map`

Changed
- FFI functions

Most of these changes are to disambiguate the FEE beam from the analytic beam
and hopefully encourage a consistent naming scheme.

- `calc_jones` -> `fee_calc_jones`
- `calc_jones_array` -> `fee_calc_jones_array`
- `closest_freq` -> `fee_closest_freq`
- `calc_jones_gpu` -> `fee_calc_jones_gpu`
- `calc_jones_gpu_device` -> `fee_calc_jones_gpu_device`
- `calc_jones_gpu_device_inner` -> `fee_calc_jones_gpu_device_inner`
- `get_freq_map` -> `get_fee_device_freq_map`
- `get_tile_map` -> `get_fee_device_tile_map`
- The old `get_*_map` functions returned device pointers. Callers should now
use the `get_fee_device_*_map` functions for this purpose. New functions
`get_fee_*_map` yield the host pointers for the maps.

0.6.1

Added
- The "analytic" MWA beam
- There are (unfortunately) two flavours -- "RTS" and "mwa_pb". Both are
supported.

0.6.0

Added
- Support for compiling GPU code with HIP
- FFI function `calc_jones_gpu_device_inner`
- This is the same as `calc_jones_gpu_device`, but allows the caller to pass
in their own device buffers, so that `hyperbeam` doesn't need to allocate
its own.
- Set the $CXX variable to the C++ compiler in $CUDA_PATH, if $CXX is not
already set and $CUDA_PATH/bin/g++ exists.

Changed
- The minimum required Rust version is now 1.64.
- Using single-precision floating point calculations on a GPU (CUDA or HIP) is
now done with the `gpu-single` feature, not `cuda-single`.
- `hyperbeam` no longer depends on `ERFA`.
- The [pure-Rust version](https://github.com/cjordan/rust-erfa) is now used
instead, and this means that the C library is no longer required.
- CPU code now runs significantly faster.
- CUDA code now runs significantly faster.
- GPU FFI functions now take `i32` instead of `u32` for the number of
directions.
- This isn't a downgrade; the internal code always used an `i32`, so it was
dishonest for the code to look like it accepted more than `i32::MAX`
directions.
- `array_latitude_rad` arguments have been renamed to `latitude_rad`
- This functionally changes nothing, but is maybe a little less confusing.
"array" was used in the sense of the Murchison Widefield _Array_, not as a
collection of numbers.

Fixed
- Calling GPU FEE functions without any directions no longer causes a GPU error.

0.5.1

Fixed
- A seemingly-rarely-occurring bug in CUDA FEE code.
- Some Y dipole values were being used for X dipole values (:facepalm:), but
despite this bug being present for many people over many thousands of
observations, I only spotted this on a particular observation.
- Fix `get_num_unique_tiles` being unavailable for `FEEBeamCUDA`.
- Some function comments.
- Some clippy lints.

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.