Skip to main content

torch-einops-utils

Some utility functions to help myself (and perhaps others) go faster with ML/AI work

maybe_return

return just the primary output by default, extras only on request

from torch_einops_utils import maybe_return

@maybe_return('memories')
def forward(self, ids, return_memories = False):
    memories = build_memories(ids) if return_memories else None

    return backbone(ids), memories

model(ids)                             # logits
model(ids, return_memories = True)     # Output(logits, memories)
logits, memories = model(ids, return_memories = True)  # unpacks

any number of extras, individually or all at once

@maybe_return('memories', 'hiddens')
def forward(self, ids, return_memories = False, return_hiddens = False):
    ...
    return logits, memories, hiddens

model(ids, return_hiddens = True)  # Output(logits, hiddens)
model(ids, return_all = True)      # Output(logits, memories, hiddens)

primary may be a tuple of names, or a callable receiving the bound call arguments, for when the shape of the primary depends on the mode

def primary_fields(kwargs):
    if not kwargs.get('return_loss', False):
        return ('logits', 'memory') if kwargs.get('return_memory', False) else 'logits'

    return ('loss', 'loss_mask') if not kwargs.get('reduce_loss', False) else 'loss'

@maybe_return('pooled_repr', primary = primary_fields)
def forward(self, ids, return_loss = False, return_memory = False, reduce_loss = False, return_pooled_repr = False):
    ...
    if return_loss:
        return loss, loss_mask, pooled_repr

    return logits, memory, pooled_repr

model(ids)                            # logits
logits, memory = model(ids, return_memory = True)
loss, loss_mask = model(ids, return_loss = True)
loss = model(ids, return_loss = True, reduce_loss = True)
loss, pooled = model(ids, return_loss = True, reduce_loss = True, return_pooled_repr = True)

log_table

clean, aligned logging for a single record or a list of records

from torch_einops_utils import log_table

log_table(ep = 200, reward = 187.04, steps = 1000, avg100 = 66.03)
# ep 200  reward 187.04  steps 1000  avg100 66.03

log_table([
    dict(ep = 200, reward = 187.04, avg100 = 66.03),
    dict(ep = 225, reward = 76.72, avg100 = 89.98),
], formatters = dict(reward = '.2f', avg100 = '.2f'))
ep   reward  avg100
200  187.04   66.03
225   76.72   89.98

formatters takes a format spec or a callable per column, and format_table returns the string without printing

Metadata

Release files for torch-einops-utils 0.2.4

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for torch-einops-utils 0.2.4
File Size Uploaded Provenance Actions
torch_einops_utils-0.2.4.tar.gz 42.9 kB Without provenance Details for torch_einops_utils-0.2.4.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for torch-einops-utils 0.2.4
File Interpreter ABI Platform Actions
torch_einops_utils-0.2.4-py3-none-any.whl Python 3 none any Details for torch_einops_utils-0.2.4-py3-none-any.whl

Total release size: 69.7 kB

Release files / torch_einops_utils-0.2.4.tar.gz

Download URL torch_einops_utils-0.2.4.tar.gz
Size 42.9 kB
Tags Source
SHA-256 checksum
How to use checksums
068b40e5a53528ba6c1484f065ebbcda9f5d525ab00016484246f6a4c19241b1
BLAKE2b-256 checksum
How to use checksums
53165b8a3b4a8569ae698643e0f0e5716dd8aded3019d701ec2b0b67974c62c9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.8.17

Release files / torch_einops_utils-0.2.4-py3-none-any.whl

Download URL torch_einops_utils-0.2.4-py3-none-any.whl
Size 26.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ad31b62f543ed3e319381e678a14b238ae032c5e8d9c8abfa4176000af2ba874
BLAKE2b-256 checksum
How to use checksums
89655d3dd6129c7d6ff3fe62d0a5d97fc31bb5c04dbb5d3b8314b8bcb2ad0507
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.8.17

Security for torch-einops-utils 0.2.4

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.2.4 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page