Development build. This page describes main, not a released package. The latest published Lodestar.Gpu is 0.1.0 — read its documentation.

Home › Gpu › GPU kernels

Which permutation family a signature is built from.

public enum MinHashScheme

Example — one resident batch, both families.

using Lodestar.Gpu.Compute;

using var context = GpuContext.Create(preferCpu: true);
using var resident = DeviceTokenHashes.Upload(context, [[11u, 22u, 33u]]);
var kernel = new TiledMinHashSignatures(context);

IReadOnlyList<uint[]> legacy =
    kernel.Signatures(resident, [3UL], [13UL], MinHashScheme.Legacy);
IReadOnlyList<uint[]> affine =
    kernel.Signatures(resident, [3UL], [13UL], MinHashScheme.Affine32);

bool agree = legacy[0][0] == affine[0][0];  // => False

Members — two, and they share no value.

Remarks — the same two families Lodestar.Text.Similarity.MinHashScheme names, and a separate enum on purpose. This package carries no edge to any other, which is what the satellite tier is for and why MersennePrime and the 32-bit mask are spelled twice as well.

The cost of that is visible to a caller using both packages: using Lodestar.Gpu.Compute; and using Lodestar.Text.Similarity; together make the bare name ambiguous, and one of them needs a using alias. That is the honest price of the missing edge rather than an oversight — the MinHash permutation rule records why the edge is not worth creating for two members.

Affine32 applies the MurmurHash3 finalizer inside the kernel, as the shared tile fills, so one DeviceTokenHashes serves both families rather than belonging to one.

Applies to — net10.0, netstandard2.1.

See also — TiledMinHashSignatures.Signatures, the namespace index.