Skip to content

Update mapping from gradient strength input to decay_length recipe entry #99

@mogres

Description

@mogres

Use Case

Currently, the gradient strength is mapped to the decay_length parameter in the recipe json as decay_length = 1 - gradient strength. This limits the decay length between 0 and 1 since the gradient strength is restricted between 0 and 1.

Updated recipes in the manuscript use weaker gradients with decay lengths >1. We want to include these recipes and also have a more robust mapping between the two quantities. I propose it would be more appropriate to map decay_length = 1 / gradient strength with the appropriate checks to avoid division by zero.

Acceptance Criteria

Run a recipe with gradient strength > 1

Details

  • This method would require a check for division by zero
  • This method would require changing the slider limits from 0-0.99 to 0.01-100 (or even higher)

Possible approach

  • Update handleStrengthChange to update mapping
  • Add checks to avoid division by zero
  • Update the range of valid values for gradient strength

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions