You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am having issues running the MPILogHandler, which would be very useful for debugging/understanding some large runs.
The example examples/1_simple/logger_example.py fails because 'initialize_logging' should be imported directly from 'simsopt.util'. Fixing that, we get the error:
which, after some digging, I found out is due to a failed relative import of from .._core/dev import SimsoptRequires in simsopt.util.mpi_logger.py.
This is probably because MPILogHandler is spawned in a child process that is only fed the file and cannot resolve the relative import as this requires rest of simsopt.
Commenting out the SimsoptRequires produces acceptable log files, but now the logger does not exit when the script completes.
does anyone have experience with MPI logging, and knows a fix? MPILogHandler seems based on 2013 code, there might be better solutions now... Looking for suggestions and willing to implement them when pointed in the right direction.
The text was updated successfully, but these errors were encountered:
I am having issues running the MPILogHandler, which would be very useful for debugging/understanding some large runs.
The example
examples/1_simple/logger_example.py
fails because 'initialize_logging' should be imported directly from 'simsopt.util'. Fixing that, we get the error:which, after some digging, I found out is due to a failed relative import of
from .._core/dev import SimsoptRequires
insimsopt.util.mpi_logger.py
.This is probably because
MPILogHandler
is spawned in a child process that is only fed the file and cannot resolve the relative import as this requires rest of simsopt.Commenting out the
SimsoptRequires
produces acceptable log files, but now the logger does not exit when the script completes.does anyone have experience with MPI logging, and knows a fix? MPILogHandler seems based on 2013 code, there might be better solutions now... Looking for suggestions and willing to implement them when pointed in the right direction.
The text was updated successfully, but these errors were encountered: