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

Running Multiple Instances of AutoscoperM Locally #157

Open
QYetman opened this issue Jan 20, 2025 · 0 comments
Open

Running Multiple Instances of AutoscoperM Locally #157

QYetman opened this issue Jan 20, 2025 · 0 comments

Comments

@QYetman
Copy link

QYetman commented Jan 20, 2025

We’re trying to run an optimization on the filter settings using a particle swarm optimization implemented in Python. Using Microsoft MPI and mpi4py to parallelize it and PyAutoscoper to communicate between the Python script and AutoscoperM running through Slicer (I have been opening all the instances of AutoscoperM I need at the start of the run). The issue is that I can’t seem to find a way to communicate with multiple instances of AutoscoperM running locally. AutoscoperConnection(address, …) seems to be hardcoded to a specific port that AutoscoperM always uses.

Spoke with JC at the most recent Autoscoper meeting. It was suggested that an option to specify the port when starting AutoscoperM could be added. He also mentioned code that could be used to find a free port for AutoscoperM to use. The AutoscoperConnection() class could then have the option to specify the port as well.

Let me know if you require any further information.

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

No branches or pull requests

1 participant