Skip to content

Conversation

@benedettadavico
Copy link
Contributor

@benedettadavico benedettadavico commented Oct 24, 2025

This change is Reviewable

@vercel
Copy link

vercel bot commented Oct 24, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
nym-explorer-v2 Ready Ready Preview Comment Nov 20, 2025 4:40pm
2 Skipped Deployments
Project Deployment Preview Comments Updated (UTC)
docs-nextra Ignored Ignored Preview Nov 20, 2025 4:40pm
nym-node-status Ignored Ignored Preview Nov 20, 2025 4:40pm

(file_download_score, ping_ips_performance)
})
.unwrap_or(0f64);
.unwrap_or((0.0, 0.0));
Copy link
Contributor

Choose a reason for hiding this comment

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

I'd say define a helper struct, like

struct NodeScore {
  download_speed_score: f64,
  ping_ips_score: f64
}

rather than passing an (f64, f64) tuple, because somebody, at some point, will accidentally mix them up

Copy link
Contributor

Choose a reason for hiding this comment

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

or maybe you could even include there mixnet_performance and have fn calculate_weighted_score(&self) -> f64 so that it would be slightly more maintainable and easier to adjust the inidividual weights

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.

3 participants