Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to get consistent order of spawned clients between multiple runs with Flower's simulation? #3328

Open
philip-s15 opened this issue Apr 24, 2024 · 3 comments
Labels
part: misc framework Issue/PR for general applications for Flower framework. stale If issue/PR hasn't been updated within 3 weeks.

Comments

@philip-s15
Copy link

What is your question?

Hi there!

I am using Flower for my machine learning research project, so reproducibility is quite important to me. I have noticed that when comparing multiple Flower simulation runs, the order in which the virtual clients are spawned is not consistent between the runs, even though I manually set all the libraries' seeds to a consistent value.

My question is whether it is possible to ensure that the order in which clients are spawned becomes consistent between multiple runs with the same code. I have tried looking at the Ray documentation, but I could not find anything related to manually setting a seed.

Thanks in advance!

@edogab33
Copy link
Contributor

same problem here

@artsasse
Copy link

struggling with that problem too

@WilliamLindskog WilliamLindskog added stale If issue/PR hasn't been updated within 3 weeks. part: misc framework Issue/PR for general applications for Flower framework. labels Dec 11, 2024
@WilliamLindskog
Copy link
Contributor

Hi @philip-s15, thanks for raising this. Is it the order that they are spawned or is it more what dataset is allocated to a specific client e.g. part_a --> client_1, part_b --> client_2 and so forth?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
part: misc framework Issue/PR for general applications for Flower framework. stale If issue/PR hasn't been updated within 3 weeks.
Projects
None yet
Development

No branches or pull requests

4 participants