Get log probability color

[djstrong]

No description provided.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 6442059

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
namekit.io	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 30, 2024 2:51pm
namerank.io	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 30, 2024 2:51pm

5 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
examples.nameguard.io	⬜️ Skipped (Inspect)			Dec 30, 2024 2:51pm
namegraph.dev	⬜️ Skipped (Inspect)			Dec 30, 2024 2:51pm
nameguard.io	⬜️ Skipped (Inspect)			Dec 30, 2024 2:51pm
namehashlabs.org	⬜️ Skipped (Inspect)			Dec 30, 2024 2:51pm
storybook.namekit.io	⬜️ Skipped (Inspect)			Dec 30, 2024 2:51pm

[lightwalker-eth]

@djstrong Hey great to see this!

@notrab Hey, could you please take the lead on the next steps for this PR? Thank you!

[lightwalker-eth]

@notrab Hey, could you please help to advance next steps here? The big picture is that this function is attempting to generate a RGB hex code that can be used to dynamically determine the color of an indicator based on a log_probability value. I asked @djstrong to focus on the math side of this logic so that we could then pass this goal off to you for refinement to align with TypeScript / Tailwind / CSS best practices. Please let us know if any questions!

@notrab Requested enhancements on this for you to lead include:

1. Rename the val param to something approximating log_probability to be more self documenting
2. Refine the return type to better align with best practices for how a color code might be returned.