Error running Reentry induction protocol "error on file /usr/local/bin/hydra_pmi_proxy (No such file or directory)"

Question

Hi I am using the docker container of OpenCarp, I have installed VTK, and Meshalizer (compiled from sources) using CMake and all the installation steps went ok. I am also able to run meshalyzer and to see the meshalizer GUI.

But when I to run the reentry example with the command

./run.py --np 2 --protocol prepace --prepace_bcl 500 --prebeats 4 --visualize

I get the following error

[mpiexec@we05c906] HYDU_create_process (utils/launch/launch.c:74): execvp error on file /usr/local/bin/hydra_pmi_proxy (No such file or directory)
[mpiexec@we05c906] HYD_pmcd_pmiserv_proxy_init_cb (pm/pmiserv/pmiserv_cb.c:448): assert (!closed) failed
[mpiexec@we05c906] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): callback returned error status
[mpiexec@we05c906] HYD_pmci_wait_for_completion (pm/pmiserv/pmiserv_pmci.c:196): error waiting for event
[mpiexec@we05c906] main (ui/mpich/mpiexec.c:336): process manager error waiting for completion
Traceback (most recent call last):
  File "./run.py", line 730, in <module>
    run()
  File "/usr/local/lib/python3.6/dist-packages/carputils/tools.py", line 528, in wrapped
    ret = run(args, job)
  File "./run.py", line 560, in run
    model.prepace.prepace(args, job, cmd, meshname, sinus, steady_state_dir, tissue_init)
  File "/usr/local/lib/python3.6/dist-packages/carputils/model/prepace.py", line 93, in prepace
    os.rename(old_file, new_file)
FileNotFoundError: [Errno 2] No such file or directory: 'prepace_block_50000.0um_resolution_400.0um_cv_0.3_with_4_beats_at_500.0_bcl_lump_1/vm.igb' -> 'prepace_block_50000.0um_resolution_400.0um_cv_0.3_with_4_beats_at_500.0_bcl_lump_1/vm_prepace.igb'

Answer 1

Hi Sirius,

I think the very last line is the relevant hint. The prepace function misses one of the intermediate results files. You can check manually if it's there but my guess is that something went wrong with one of the previous simulation steps.

The logs should contain hints on what is going wrong. Alternatively, you can try to run the script step by step in a manual fashion.