Skip to content
Snippets Groups Projects
Commit 980a4f46 authored by David Hendriks's avatar David Hendriks
Browse files

small updates

parent 4d76adee
No related branches found
No related tags found
No related merge requests found
...@@ -61,8 +61,6 @@ Building issues with binary_c itself: ...@@ -61,8 +61,6 @@ Building issues with binary_c itself:
Pip install failed: Pip install failed:
- Run the installation with `-v` and/or `--log <logfile>` to get some more info - Run the installation with `-v` and/or `--log <logfile>` to get some more info
- If gcc throws errors like `gcc: error: unrecognized command line option ‘-ftz’; did you mean ‘-flto’?`, this might be due to that the python on that system was built with a different compiler. It then passes the python3.6-config --cflags to the binarycpython installation, which, if done with gcc, will not work. Try a different python3.6. I suggest using `pyenv` to manage python versions. - If gcc throws errors like `gcc: error: unrecognized command line option ‘-ftz’; did you mean ‘-flto’?`, this might be due to that the python on that system was built with a different compiler. It then passes the python3.6-config --cflags to the binarycpython installation, which, if done with gcc, will not work. Try a different python3.6. I suggest using `pyenv` to manage python versions. If installing a version of python with pyenv is not possible, then try to use a python version that is avaible to the machine that is built with the same compiler as binary_c was built with.
if pip installation results in `No files/directories in /tmp/pip-1ckzg0p9-build/pip-egg-info (from PKG-INFO)`, try running it verbose (`-v`) to see what is actually going wrong. if pip installation results in `No files/directories in /tmp/pip-1ckzg0p9-build/pip-egg-info (from PKG-INFO)`, try running it verbose (`-v`) to see what is actually going wrong.
...@@ -931,6 +931,11 @@ class Population: ...@@ -931,6 +931,11 @@ class Population:
# #
print("Process {} is handling system {}".format(ID, localcounter)) print("Process {} is handling system {}".format(ID, localcounter))
# In some cases, the whole run crashes. To be able to figure out which system that was on, we log each current system to a file (each thread has one). Each new system overrides the previous
with open(os.path.join(self.grid_options["tmp_dir"], "thread_{}_current_system.txt".format(self.process_ID)), 'w') as f:
f.write(full_system_dict)
# Evolve the system # Evolve the system
self._evolve_system_mp(full_system_dict) self._evolve_system_mp(full_system_dict)
......
...@@ -49,7 +49,7 @@ grid_options_defaults_dict = { ...@@ -49,7 +49,7 @@ grid_options_defaults_dict = {
"_binary_c_config_executable": os.path.join( "_binary_c_config_executable": os.path.join(
os.environ["BINARY_C"], "binary_c-config" os.environ["BINARY_C"], "binary_c-config"
), # TODO: make this more robust ), # TODO: make this more robust
"_binary_c_dir": os.environ["BINARYC_DIR"], "_binary_c_dir": os.environ["BINARY_C"],
########################## ##########################
# Custom logging # Custom logging
########################## ##########################
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment