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

simulation log output lags behind terminal output #299

Open
jasmainak opened this issue Apr 3, 2021 · 4 comments
Open

simulation log output lags behind terminal output #299

jasmainak opened this issue Apr 3, 2021 · 4 comments
Labels
bug Something isn't working

Comments

@jasmainak
Copy link
Collaborator

When I run the simulation, I see the following:

image

@jasmainak jasmainak added the bug Something isn't working label Apr 3, 2021
@jasmainak
Copy link
Collaborator Author

see also #300 . I am wondering if it might be a simpler design choice to ask users to look at the terminal output ?

@blakecaldwell
Copy link
Member

This should only happen when falling back to JoblibBackend with 1 core because mpi4py can't be loaded. While it would be a useful feature to be able to run HNN GUI without MPI, I think this involves an enhancement, not a bug.

If you'd like to support this, two options are:

  1. Run Joblib backend in a separate process, like mpi_child.py
  2. Modify _simulate_single_trial to support a cell_parallel option. The _PC.psolve() function must be avoided because it will take over all threads in the python process (slows down GUI threads too). Note that other ParallelContext functions are not problematic, just psolve.
    if cell_parallel:
        _PC.psolve(h.tstop)
    else:
        # this needs more to work correctly, check out NEURON docs
        _CVODE.solve(h.tstop)
    

@jasmainak
Copy link
Collaborator Author

Thanks for the suggestion. I'll look into the MPI installation and try it again soon.

@ntolley
Copy link
Contributor

ntolley commented Apr 6, 2021

Can confirm that this doesn't occur with a functioning MPI install:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants