Skip to content

[BIT-638] Max-upscale pruning_scores#95

Merged
opentaco merged 7 commits intomainfrom
feature/BIT-638/max-upscale-pruning_score
Apr 5, 2023
Merged

[BIT-638] Max-upscale pruning_scores#95
opentaco merged 7 commits intomainfrom
feature/BIT-638/max-upscale-pruning_score

Conversation

@opentaco
Copy link
Contributor

@opentaco opentaco commented Mar 31, 2023

Currently pruning_scores are a u16 quantization of normalized emission, which is problematic given ~4096 values and a Pareto distribution of emissions. Currently finney has a max emission of ~11% and a min non-zero emission of ~0.0002% (0.000002), but the lowest u16 quantity is 1/2^16 = 0.000015 (0.0015%).

The purpose of pruning_scores is to make relative comparisons during registration to determine the neuron to replace, which has the lowest pruning_score. Therefore, it doesn't have to be normalized, so this PR proposes max-upscaling where max(pruning_scores) = u16::MAX. So scale scores relative to the max score, so 0.0002/11 = 0.000018 (> 0.000015 u16 min quantity).

Assumes that pruning_scores is used only for relative comparison, and doesn't have to be normalized.

@opentaco opentaco changed the title [BIT-638] Max-upscale pruning_score [BIT-638] Max-upscale pruning_scores Mar 31, 2023
Copy link
Contributor

@camfairchild camfairchild left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@opentaco opentaco merged commit 8a72934 into main Apr 5, 2023
@opentaco opentaco deleted the feature/BIT-638/max-upscale-pruning_score branch April 5, 2023 14:49
opentaco added a commit that referenced this pull request Apr 5, 2023
* Add vec_max_upscale_to_u16

* Do max-upscale pruning_scores

* Add epoch test log details for u16 pruning_scores

* Norm when no max

* Added max-upscaling unnormalized handling

* Update spec_version to 116
@shibshib
Copy link
Contributor

shibshib commented Apr 5, 2023

Main chain upgraded @ block 114,315

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants