Problems on installing Avalon on intel macOS about avalon HOT 15 CLOSED

Yep, check_install needed that guard too, fixed now and you should see the change soon. Thanks for pointing this out! I'll close this but let us know if it's not fixed for you and we can reopen.

from avalon.

@zangobot we've synced over the changes, so the install should work if you install via git: pip install git+https://github.com/Avalon-Benchmark/avalon. Wwe'll push a pip release after consolidating a few more changes.

from avalon.

@zplizzi yes, looks like torch has slipped into a non-core dependency. @zangobot you can install all the train extras like so:

pip install "git+https://github.com/Avalon-Benchmark/avalon#egg=avalon-rl[train]"

from avalon.

What is the specific context you are executing this code in? I've see this crop up in a different conda install while using vscode's jupyter integration specifically (but not the web UI). It might also be related to pytorch/pytorch#5858 (comment).

from avalon.

A python script, not a notebook, just to test the environment. Also, the python module for testing the installation fails. I will have a look at that issue (which seems to be still open), thanks!

from avalon.

@zangobot pretty sure you just need to put your code under if __name__ == '__main__': as that error message suggests. multiprocessing when using the spawn method requires this idiom (I think so that the child processes don't also run code they're not supposed to?). OSX defaults to spawn (but we also set it to spawn for some of the child processes explicitly), it's possible that test that's failing for you works on linux because linux defaults to fork.

from avalon.

Thank you!

from avalon.

I would need to reopen this.
I tried a clean install with the pip install command you sent me, but some dependancies are missing:
ModuleNotFoundError: No module named 'tree'

from avalon.

Sorry about that, for now that should be fixed by running pip install dm-tree==0.1.7 before retrying the installation. We'll fix the pip dependency list.

from avalon.

I think I have found another bug.
When trying to install the Godot binaries, this happens:

2022-12-21 09:35:57.009 | INFO     | __main__:install_available_binaries_for_current_platform:130 - Installing editor build from https://github.com/Avalon-Benchmark/godot/releases/download
2022-12-21 09:35:57.014 | INFO     | __main__:fetch_binary:92 - Downloading 3.4.4.avalon.0.9.3/macos-editor.zip into /FOLDER/envs/avalon/lib/python3.10/site-packages/avalon/bin/godot_editor
2022-12-21 09:36:06.834 | INFO     | __main__:install_available_binaries_for_current_platform:144 - Note: No headless runner currently available for macos. Symlinking editor build in its place.

and running the avalon.common.check_install crashes in this way:

avalon.datagen.errors.GodotError: returncode=SIGHUP(1) 
Log: /var/folders/t9/9c25d13553s4q7t2v2c0b0z00000gn/T/science/tmp/4752303b-0a49-4c60-af70-86148b943079/godot.log
Artifacts: /var/folders/t9/9c25d13553s4q7t2v2c0b0z00000gn/T/science/godot/godot_env_artifacts__74530bad-1408-45a2-a47b-1ee630f60d17.tar.gz

from avalon.

Can you attach the contents of that log file?

from avalon.

The content of the log is

realpath: illegal option -- e
usage: realpath [-q] [path ...]

from avalon.

@zangobot looks like you're using the /bin/realpath that ships with macos ventura which appears to be fairly non-standard – for now could you try with brew install coreutils?

We may be able to switch to something like -f $(realpath ...) instead to avoid the need for coreutils on ventura, or even just skip these checks in the usual usage from python as we can verify things before reaching the bash script.

from avalon.

Closing this as it's become a bit of a catch-all. Please open new issues for any other errors y'all encounter.

I've made an internal issue to improve the output of check_install such as outputting some of the godot log if it errors.

from avalon.

Hello!
So, yes, I have already installed the coreutils.
I'll open a new issue soon about it then.

from avalon.