Skip to content

FACTO: Fix unary op domain constraints - #64

Open
bdemirb wants to merge 2 commits into
meta-pytorch:mainfrom
bdemirb:facto_fix_domain_constraints
Open

bdemirb wants to merge 2 commits into
meta-pytorch:mainfrom
bdemirb:facto_fix_domain_constraints

Conversation

@bdemirb

@bdemirb bdemirb commented Oct 29, 2026 •

Copy link
Copy Markdown

Limit generated domains for invalid unary and divisor inputs.

Constrain acos and asin to [-1, 1], acosh to [1, inf), atanh to (-1, 1), sqrt to [0, inf), rsqrt and log ops to (0, inf), and log1p to (-1, inf).

Also constrain logit inputs to [0, 1] when eps is None, and require non-zero divisors for div.Tensor_mode, floor_divide.default, and remainder.Tensor.

This keeps FACTO from generating invalid cases that show up as AoT, export, and runtime noise.

Limit generated domains for unary ops with restricted real\ninputs.\n\nConstrain acos and asin to [-1, 1], acosh to [1, inf),\natanh to (-1, 1), sqrt to [0, inf), rsqrt and log ops\nto (0, inf), and log1p to (-1, inf). This keeps FACTO\nfrom generating invalid real-valued cases that show up\nas AoT and export noise.
@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Meta Open Source bot. label Oct 29, 2026
Constrain logit inputs to [0, 1] when eps is None and\nrequire non-zero divisors for div.Tensor_mode with\nrounding_mode, floor_divide.default, and\nremainder.Tensor.\n\nThis reduces invalid generated cases that show up as\nbackend noise in Arm FACTO runs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Meta Open Source bot.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant